-
Notifications
You must be signed in to change notification settings - Fork 106
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
Modeling Travel Use Case as an extension example #187
Comments
These are broadly OK. Comments I have on the various VCs are
The type property in the birth certificate should of course be
and not
and the address object also ideally needs a type property because this address is US centric and not globally recognised, which leads to the following
I would say the claim property should be "childTravelPass" and not "potentialAction". The latter semantics are too vague.
Please also see my comment in #182 concerning the use of the type property. |
Types like the one you call out on address are in the domain of @context and will be agreed upon between the issuer and verifier. As long as the data model supports this sort of industry specific negotiation, then we've done what's required to move ahead. The Type at the top level "VerifiableCredential" is one that we specify w/ some bare minimum content. Types such as "BirthCertificate" not ours to define, as long as the issuer can declare it in a way that the verifier can accept it, the data model is good. I recommend that @dlongley make a PR with this example in the data model spec, incorporating @David-Chadwick tweaks. |
There was a suggestion on the weekly call to make an example document that shows how the specification addresses (some or all of) the use cases. we'll have to remember to keep them aligned with the data model spec as it evolves over time. |
will work to either
|
Added as an appendix section in the Use Case document in PR86 w3c/vc-use-cases#86 |
The aim of this issue is to hash out some example VCs that would address the Travel Use Case. To close this issue out we'd create a PR that adds the examples we get consensus on to a "guidance on writing extensions" section in the data model spec.
There are potentially four VCs to model here: Malathi's passport, Anand's passport, Anand's birth certificate, and Rajesh's child travel pass ("permission to travel").
I've modeled Malathi's passport in two different ways to get some feedback. The first way is simpler in that it just makes claims about Malathi without any concept of an additional "passport document". This deviates from how people understand passports to work today so I've included a second model that makes a claim that Malathi holds a "passport document" with a certain identifier etc. Our data model supports both approaches.
Malathi's passport (simple model):
Malathi's passport (passport is a document model):
Anand's passport:
Anand's birth certificate:
Permission to travel from Rajesh
Used schema.org vocab here -- could have used activitystreams vocab
The text was updated successfully, but these errors were encountered: