Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-transferable use case #127

Closed
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -791,6 +791,36 @@ <h3>Devices</h3>
</dd>
</dl>
</section>
<section>
<h3>Generic</h3>
<p>
The generic domain contains use cases that can apply to any or all of the proceeding domains
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not common US English usage of proceeding, and I am not sure what is intended by it. (The sentence also lacks a closing ..)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think preceding was intended.

</p>
<dl class="left dl-horizontal">
<dt>
<udef>E.1 Non-transferability of credentials</udef>
</dt>
<dd>
<p>
Many different types of plastic cards today have the words "Non-transferable" or similar printed on them. Examples include:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be useful/helpful if it would be described more explicitly why in certain credential types non-transferability is valuable, in addition to what kind of credentials have that property.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To give you a definitive answer, one would need to ask the existing issuers of plastic cards as to why they inserted this property onto their cards. The fact that they do is not in dispute.
One can hypothesise as to the use cases by looking at the specific cards that have these properties. In the case of my historical cathedral card the intended use case is that only the card holder should be able to enter the cathedral free of charge and that the original card holder (i.e. the issuee) should not give the card to anyone else. In the case of credit cards the use cases are self explanatory: only the subject of the credit card is authorised to use it anywhere where the card can be used.
Does this help?

</p>
<ul>
<li>
Some credit cards state "This card is not transferable and is for use only by the authorised signatory"
</li>
<li>
A pass to a historical cathedral in England has the words "Not transferable" printed on the back
</li>
<li>
A wholesale shopping card that is only available to traders states "Non Transferable" on the front"
</li>
</ul>
<p>
These and all similar use cases should be enabled when the plastic cards are converted to verifiable credentials.
</p>
</dd>
</dl>
</section>
</section>
<section>
<h2>User Tasks</h2>
Expand Down