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

what is attribute ID in the verifiable credential? #946

Closed
Muthurajj opened this issue Oct 11, 2022 · 8 comments
Closed

what is attribute ID in the verifiable credential? #946

Muthurajj opened this issue Oct 11, 2022 · 8 comments
Assignees

Comments

@Muthurajj
Copy link

1.what is the purpose of the id ?
2.How to create the id url?
3.If the id is refer to identity for the claims in VC then we have storage the claims in server to identify gobally?

@brentzundel
Copy link
Member

The working repository for Verifiable Credentials Data Model is elsewhere. I will transfer this issue to that repository.

@brentzundel brentzundel transferred this issue from w3c/verifiable-credentials Oct 11, 2022
@OR13
Copy link
Contributor

OR13 commented Jan 25, 2023

@brentzundel brentzundel added the ready for PR This issue is ready for a Pull Request to be created to resolve it label Jan 25, 2023
@msporny
Copy link
Member

msporny commented Jan 25, 2023

It would be useful to add some editorial text for item 3 to clarify.

@msporny msporny self-assigned this Feb 15, 2023
@msporny
Copy link
Member

msporny commented Feb 15, 2023

We should add text that provides guidance around what an "id" is, whether or not it is required, what is expected to be there, must it be globally unique, there are cases where there isn't an ID for a VC, etc.

@OR13
Copy link
Contributor

OR13 commented Feb 15, 2023

related issue: #1031

@iherman
Copy link
Member

iherman commented Feb 16, 2023

The issue was discussed in a meeting on 2022-09-15

  • no resolutions were taken
View the transcript

5.5. what is attribute ID in the verifiable credential? (issue vc-data-model#946)

See github issue vc-data-model#946.

Kristina Yasuda: This needs clarification in the spec.
… Is anyone willing to write the clarifying text.

Manu Sporny: I can try.

Orie Steele: He's asking about what you should expect it to be and how should you handle it.
… This is related to the URL vs. URI confusion.

David Chadwick: I have an issue with the "parts of" wording.

Dmitri Zagidulin: (the question that almost all devs new to VCs ask is - 1) is 'id' required? 2) is it /supposed/ to be globally unique? Or can I use like a database row # for the id?.

David Chadwick: The credential schema should be one thing.
… There's a disagreement there.
… I don't think there's agreement that Gabe's proposal should be accepted.

Dmitri Zagidulin: Maybe this text belongs more in the Implementation Guide.
… I think we want to add it in the spec.
… Is it required and must it be globally unique?.
… We need guidance to say that it's not required and that it should be globally unique.
… If absent, use the signature string as an ID.

Joe Andrieu: We call them URIs. We refer to RFC 3986..

David Waite: There's a normative reference to the WhatWG specification.

Kristina Yasuda: If you'd like to revisit, please file an issue.

Brent Zundel: Yesterday we had a discussion about IDs.

@msporny
Copy link
Member

msporny commented May 6, 2023

@Muthurajj wrote:

If the id is refer to identity for the claims in VC then we have storage the claims in server to identify gobally?

This is a specific question that we can't easily answer in the specification, so I'll try to answer it here.

No, you don't have to store claims on a server if you use an id in any part of a VC as long as you express all the claims that you want in the VC itself. If, however, you only provide the id, then yes, you would want to store the claims on a server at the id specified in the VC. Note that this is not always the case if the id points to an image, video, or other non-Linked Data object.

As for the rest of your questions, I've raised PR #1114 in an attempt to answer them with more text in the specification. Please review the PR and let us know if that addresses your questions. This issue will be closed if that PR is merged.

@msporny msporny added pr exists and removed ready for PR This issue is ready for a Pull Request to be created to resolve it labels May 6, 2023
@brentzundel
Copy link
Member

I am closing this issue, as it has been addressed with the merging of #1114.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants