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

Update term definitions according to the core vocab #185

Merged
merged 7 commits into from
Aug 1, 2023

Conversation

decentralgabe
Copy link
Collaborator

@decentralgabe decentralgabe commented Jul 25, 2023

Fix #182


Preview | Diff

Copy link
Collaborator

@OR13 OR13 left a comment

Choose a reason for hiding this comment

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

Seems like the term definitions should be to the vocabulary.

Cc@iherman

Copy link
Member

@iherman iherman left a comment

Choose a reason for hiding this comment

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

Unfortunately, that is incorrect... I propose to change the sentences as follows:

<p>
This term is part of the 
<a href="https://www.w3.org/ns/credentials#JsonSchema2023">Verifiable Credentials Vocabulary v2.0</a>.
</p><p>
This term is part of the 
<a href="https://www.w3.org/ns/credentials#VerifiableCredentialSchema2023">Verifiable Credentials Vocabulary v2.0</a>.
</p>

I do not believe referring to the JSON-LD spec's term definition brings anything here, so I removed that reference, too.

Of course, the URL-s must be updated if the final term names change.

(GitHub does not let me propose a direct edit to the full sentence, hence this comment.)

index.html Outdated
@@ -155,7 +155,7 @@ <h2>Data Model</h2>
<h3>JsonSchema2023</h3>
<p>
This <a href="https://www.w3.org/TR/json-ld/#dfn-term-definition">term definition</a>
is <code>https://www.w3.org/TR/vc-json-schema/#JsonSchema2023</code>.
is <code>https://www.w3.org/TR/vc-json-schema#JsonSchema2023</code>.
Copy link
Member

Choose a reason for hiding this comment

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

The slashless URI gets a 302 Found redirect to the slashed URI, where the fragment does not resolve.

The text found in that document always reads as the mixed case JsonSchema2023, but the fragment identifier for the section where it is defined is the lowercase #jsonschema2023, where it says --

This term definition is https://www.w3.org/ns/credentials#JsonSchema2023.

-- which gets a 302 Found redirect to https://www.w3.org/ns/credentials/ which gets a 404 Not Found.

This is confusing to me, and I've been working with all this stuff for quite a while. It seems that anyone new to any of this material who encounters the above will quickly throw up their hands and walk away.

index.html Outdated
@@ -238,7 +238,7 @@ <h3>JsonSchema2023</h3>
<h3>VerifiableCredentialSchema2023</h3>
<p>
This <a href="https://www.w3.org/TR/json-ld/#dfn-term-definition">term definition</a>
is <code>https://www.w3.org/TR/vc-json-schema/#VerifiableCredentialSchema2023</code>.
is <code>https://www.w3.org/TR/vc-json-schema#VerifiableCredentialSchema2023</code>.
Copy link
Member

Choose a reason for hiding this comment

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

Similar to comments above on JsonSchema2023.

@decentralgabe
Copy link
Collaborator Author

updated based on @iherman's comment.

@TallTed I notice the 404 as well, but I trust @iherman's suggestion. Maybe it'll be resolved after the core data model PR is merged?

@iherman
Copy link
Member

iherman commented Jul 26, 2023

Sorry @TallTed and @decentralgabe I screwed up. The right URLs should be

ie:

<p>
This term is part of the 
<a href="https://www.w3.org/2018/credentials/#JsonSchema2023">Verifiable Credentials Vocabulary v2.0</a>.
</p><p>
This term is part of the 
<a href="https://www.w3.org/2018/credentials/#VerifiableCredentialSchema2023">Verifiable Credentials Vocabulary v2.0</a>.
</p>

Sorry about the confusion.

@decentralgabe
Copy link
Collaborator Author

updated

index.html Outdated Show resolved Hide resolved
@iherman
Copy link
Member

iherman commented Aug 1, 2023

@OR13

Seems like the term definitions should be to the vocabulary.

Cc@iherman

@OR13, @decentralgabe, also with w3c/vc-data-model#1218, I believe this PR can be merged.

@decentralgabe decentralgabe merged commit a2b74ce into main Aug 1, 2023
1 check passed
@decentralgabe decentralgabe deleted the issue-182-term-defs branch August 1, 2023 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update term definitions to match the VCDM's vocab
5 participants