Open laurensdeb opened 1 year ago
@RubenVerborgh Shouldn't this challenge have criteria?
I'm assuming those from #73.
Ok. @laurensdeb For completeness sake, can you add the criteria in this challenge as well? Thanks!
@pheyvaer I will be adding these, probably towards the end of this week.
Pitch
Once data is written into a Solid Pod, it is outside of the control of an authentic data source. For some data in the Pod, the user themselves may be the authentic source, like for their contact information or calendar. However, for other kinds of data like your high school or university diploma's, your driver's license and national identity card, an external party like a government or company is the source. When sharing the data originating from these parties, we want to uphold their integrity and authenticity to ensure that they can be validated by a data consumer.
Desired solution
The broader W3C community has proposed the use of Verifiable Credentials in order for a particular issuer, i.e. an organization, government or even an end-user themselves, to assert certain identity claims. The current framework of Verifiable Credentials does not consider the use of a personal data vault to store these Credentials, however the concept of repository might be closely related to what we want to achieve with Solid. While we have been able to identify a number of similarities between concepts in the VC and Solid specifications, we are still lacking formal alignment between the two domains.
Our desired solution to this challenge would be as follows:
Acceptance criteria
TBD
Pointers
Scenarios