- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sat, 17 Dec 2022 15:16:25 -0500
- To: Steve Capell <steve.capell@gmail.com>
- Cc: Christopher Allen <ChristopherA@lifewithalacrity.com>, W3C Credentials CG <public-credentials@w3.org>
On Fri, Dec 16, 2022 at 7:52 PM Steve Capell <steve.capell@gmail.com> wrote: > We simply cannot use registries or lists as they are both unmaintainable and often cannot be public because the totality of information in them is essentially commercially sensitive customer lists So why not convey that information using either a protected list (via standard authz mechanisms like OAuth2) or just send them as a Verifiable Credential? That's the approach that the Verifiable Issuer/Verifier Lists spec uses. > Is there a separate work item on chained credentials and the linked semantics within them? If not will this work item address that ? If not should I start a new work item ? Need more detail on you on why you think "chained" is a requirement. I believe this work item will cover "linked semantics", but will most likely use JSON Schema to do the fine-grained matching. Do you have a write up of your use cases, Steve? We're familiar with supply chain use cases, and I see no reason why this solution wouldn't work for you... but I'm probably missing something... just don't know what I'm missing, yet. Enlighten me, please. :) -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. News: Digital Bazaar Announces New Case Studies (2021) https://www.digitalbazaar.com/
Received on Saturday, 17 December 2022 20:17:14 UTC