-
Notifications
You must be signed in to change notification settings - Fork 112
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
Cross-check the domain
/range
statements in the vocabulary with the VCDM spec
#1319
Comments
The issue was discussed in a meeting on 2023-11-01
View the transcript2.2. Cross-check the
|
This is my review of the vocabulary mapping to the VCDM spec: https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#VerifiableCredential
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#VerifiablePresentation
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#credentialSubject
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#holder
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#issuer
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#relatedResource
https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#verifiableCredential
The items above are the only things I found. Thanks for all the work on the vocabulary @iherman ! :) |
(When I say "done", it means that I have a branch on my machine, a future PR, where I have made the change.)
Done.
You mean the text "The property's value should be a URL, i.e., not a literal." ? That is an automated text that reflects the following statement in the formal vocabulary:
i.e., the
Done
Same as the
You mean the text "The value of this property identifies a Verifiable credential graph. (Informally, it indirectly identifies a Verifiable credential contained in a separate graph.)"? I was hesitant about this. I know the new version of the spec makes it explicit that the value is a graph but, I believe, draw the attention on this in the HTML version is better. I have removed it temporarily (ie, put it in comment) but maybe others will have a different opinion... |
I am all ears for a better terminology, but I am not sure what to use (note that any change will require a change in the Looking at Maybe saying "Included in the domain of" instead of "In the domain of" would work better? |
This reflects the fact that these properties do not have a domain statement in the vocabulary (the domain is only defined on properties, these cross references are just generated into the HTML to make it more readable. They do not reflect direct ontology statements). Taking them on-by-one:
See my comment above on |
The issue was discussed in a meeting on 2023-11-15
View the transcript3.4. Cross-check the
|
Reversing some statements and/or using different predicates, might help... all any zero or more all any zero or more |
I am not sure how to interpret your comment in #1319 (comment), @TallTed. We are talking about the (generated) English sentence "In the domain of" in, say, https://w3c.github.io/vc-data-model/vocab/credentials/v2/vocabulary.html#VerifiablePresentation, like below: ![]() More exactly, we are looking at a way to replace it. The TTL/JSON-LD vocabulary is not in question (it uses a perfectly valid OWL construction for the union of possible domains). My question was whether, say, "Part of the domain of" would be a suitable replacement. The two lines in the example above are solely an information for the reader. There is no corresponding RDF sentence in the term definition of |
I've always preferred simpler language, so:
I know that's not accurate, but I doubt 95%+ of the developers that might find themselves reading the vocabulary document will know what the difference is (or the difference doesn't matter to them). |
I would be o.k. with this, but before I modify the underlying script (because that is what it takes) I would need more positive reactions (this is a purely editorial choice, so we do not need a formal WG resolution, but nevertheless...) |
I'm satisfied that @iherman has responded to all of the structural review comments I had. The only changes remaining are to address the "Contains text about the property that should be deleted." statements here: #1319 (comment) Since these are all editorial changes, I'm relabeling this issue to post CR. |
I have created #1361 to cover the minor changes in the vocabulary. I have not changed the items discussed in #1319 (comment); that is subject to a change in the script and not in this repo. I would actually suggest to review these types of styling issues when the dust settles around both the VCDM and the DI vocabularies (a possible change would affect both vocabularies, and possible other vocabularies that may come to the fore). |
PR #1361 has been merged, addressing the remaining issues in this PR; closing. |
This is a fresh version of #1263; to be done based on the latest version of the vocabulary, diagram, etc.
The text was updated successfully, but these errors were encountered: