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

Remove normative statements from vocab #1077

Closed
awoie opened this issue Apr 5, 2023 · 6 comments
Closed

Remove normative statements from vocab #1077

awoie opened this issue Apr 5, 2023 · 6 comments
Assignees
Labels
pending close Close if no objection within 7 days

Comments

@awoie
Copy link
Contributor

awoie commented Apr 5, 2023

IMO, the vocab (https://www.w3.org/2018/credentials/) should not contain normative statements (verbs) about things the VCDM already states. This is confusing to readers and redundant to the normative statements made in the VCDM specification (=> aka THE "standard").

I suggest removing all normative verbs from the vocab. Some examples are listed below ...

The value of the holder property MUST be a URI. It is RECOMMENDED that dereferencing the URI results in a document containing machine-readable information about the holder that can be used to verify the information expressed in the credential.

The value of the issuer property MUST be a URI. It is RECOMMENDED that dereferencing the URI results in a document containing machine-readable information about the issuer that can be used to verify the information expressed in the credential.

@awoie awoie changed the title Vocab contains normative statements Remove normative statements from vocab Apr 5, 2023
@awoie
Copy link
Contributor Author

awoie commented Apr 5, 2023

For example, the Activity Pub work (also W3C REC) does not use any normative verbs in their vocab: https://www.w3.org/ns/activitystreams

@andyfmiller
Copy link

This is confusing to readers and redundant to the normative statements made in the VCDM specification

And conflicting in at least one place. As you noted the vocab describes Issuer as:

The value of the issuer property MUST be a URI.

While the standard describes it:

The value of the issuer property MUST be either a URL or an object containing an id property.

@iherman iherman self-assigned this Apr 19, 2023
@iherman
Copy link
Member

iherman commented Apr 19, 2023

I agree. The separate, but relevant, issue on this is #1080: once the VCDM is stable and all terms have a proper anchor, the vocabulary specification should be systematically changed, removing most of the texts and referring to the VCDM specification itself as a normative source of the description. It is on my desk to do so, but #1080 should be completed beforehand.

@iherman
Copy link
Member

iherman commented Jun 22, 2023

The issue was discussed in a meeting on 2023-06-21

  • no resolutions were taken
View the transcript

2.2. Remove normative statements from vocab (issue vc-data-model#1077)

See github issue vc-data-model#1077.

Kristina Yasuda: We don't have ivan on this call. Do we mark as before CR?

Brent Zundel: +1.

Manu Sporny: Could we mark it as pending close instead? 1080 is already saying that Ivan wants to anchor the things in the vocab to the specification. If we do 1080, then 1077 gets closed.
… Could we mark as duplicate?

Brent Zundel: My understanding is that they are different. One talks about adding statements to the vocab. 1077 mentions what to do with the ones that are already normative.

Manu Sporny: I wonder if Ivan could check if 1080 and 1077 are dupes of one another and they can be closed?

@msporny
Copy link
Member

msporny commented Jun 22, 2023

This issue is very close to a duplicate of #1080. Based on comments from @iherman here: #1080 (comment) , I'm marking this issue as a duplicate and pending close.

@msporny msporny added the pending close Close if no objection within 7 days label Jun 22, 2023
@brentzundel
Copy link
Member

No objections raised since marked pending close, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending close Close if no objection within 7 days
Projects
None yet
Development

No branches or pull requests

6 participants