-
Notifications
You must be signed in to change notification settings - Fork 19
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
[EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? #14
Comments
Example 1 has been updated to remove https://w3c.github.io/vc-data-integrity/#example-a-simple-json-data-document Closing. |
@msporny Are Example 1 (and Example 2) considered to be credentials that are compliant with Verifiable Credential V2 specification? Reference: https://w3c.github.io/vc-data-integrity/#example-a-simple-json-data-document |
No, and they don't need to be to use the Data Integrity specification. |
Understoood. Just the same, a clarifying comment needs to be added. Especially given the title of your spec is:
|
The examples fall under this category ^^^ What sort of clarifying statement would you like to see in the document? I'm re-opening this issue now, given that you have requested changes. |
@msporny When I look at the surrounding text, I feel the explanation would be somewhat convoluted. Recommendation: Remove Example 1 and related text ...or... change/fix the title (e.g. Credential Data Integrity spec) and then position Example 1 as a credential with no credential data integrity features/capabilities. "Level zero" support. Which of the remaining examples are also not VC2 compliant? |
PR #105 has been raised to address this issue. This issue will be closed once that PR has been merged. |
In https://w3c-dvcg.github.io/ld-signatures/#ex-1-a-simple-linked-data-document, it states...
Is this technically a Linked Data compliant document? ...it's impossible to tell from the definition of the linked data document in the Terminology section (see Issue https://github.com/w3c-dvcg/ld-signatures/issues/23)
The text was updated successfully, but these errors were encountered: