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

Issuer control of granularity and decomposability of claims #40

Open
stonematt opened this issue Feb 2, 2017 · 5 comments
Open

Issuer control of granularity and decomposability of claims #40

stonematt opened this issue Feb 2, 2017 · 5 comments
Assignees

Comments

@stonematt
Copy link
Contributor

In use case E.1 Digital Transcript (https://opencreds.github.io/vc-use-cases/#education), Joleen is spearheading the concept of a 'extended transcript' - My question is about the "basic transcript" - and how it's a model for any issuer tracking collections of evidence that may or may not be in a hierarchy.

In the simple university case, there is a hierarchy of achievements from coursework -> exams (grade) -> course completion -> degree. In general, issues decide how their claims can be represented in the marketplace. Focusing on the top 2 levels for a moment.

A university issuers, issues a VC for the "degree" with course completion as evidence, as a result:

  1. Holder can share all data in the claim
  2. Holder can share only the degree w/out evidence (is this a new claim w/out evidence?)
  3. Holder cannot decompose the VC and share only 1 of the courses

-- Is Item 2 above the sort of thing we envision in 4.2 Assert Claim (https://opencreds.github.io/vc-use-cases/#assert-claim) where the holder can restrict the amount of information exposed?
-- Can the university require the full detail of the evidence anytime the claim is used?
-- If the exam was a distinct VC that included both score and grade as attributes, would we expect the issuer to be a able to mandate one as optional (like score) and one required (like grade)? This implies that issuer could mandate both attributes as required, thus restricting what the Holder can withhold.

@stonematt
Copy link
Contributor Author

Supported if Issuer uses a ZKP or selective disclosure technology

@dlongley
Copy link

Also supported if the issuer constructs more than one credential (atomizes them as needed) to enable the holder to selectively disclose (where the selection choices are up to the options provided by the issuer via multiple VCs).

@jandrieu
Copy link
Collaborator

Update at least one use case to show the issuer explicitly making a credential with selective disclosure.

@jandrieu
Copy link
Collaborator

jandrieu commented May 5, 2023

@dlongley or @stonematt Any interest in drafting a quick selective disclosure use case?

Our call for input is at https://lists.w3.org/Archives/Public/public-vc-wg/2023Apr/0000.html

Selective disclosure definitely would be a useful edition.

@jandrieu
Copy link
Collaborator

jandrieu commented Apr 5, 2024

Turns out we have a selective disclosure use case in H.4 Traveling illness.

It might also make sense to add additional language for other existing use cases, e.g., E.1 Digital Transcript could be updated to explicitly state that the transcript could be used in different contexts with the individual revealing different bundles of school information, e.g., (1) graduated (2) graduated with GPA, (3) graduated with GPA with course list (4) graduated with GPA, course list and course grades.

We are open to PRs that might add such elements.

Given that we do have at least one selective disclosure use case, we're marking this pending closed, but other PRs in this direction would be welcomed.

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

3 participants