- From: Michael Prorock <mprorock@mesur.io>
- Date: Tue, 16 Jan 2024 07:29:24 -0700
- To: ステファニー タン(SBIホールディングス) <tstefan@sbigroup.co.jp>
- Cc: "public-credentials@w3.org" <public-credentials@w3.org>
- Message-ID: <CAGJKSNT6imgmX2P-w2Os3yGHYQLVZURU9eDC92cZie8sxJrHpA@mail.gmail.com>
Stefannie, You may want to take a look at the Trace Interop which deals with some of these questions: https://w3id.org/traceability/interoperability and the corresponding vocabulary: https://w3id.org/traceability Amongst other things, there is the notion of a Traceable Presentation that lets you assign a workflow ID and and type specifically so that individual credentials can be correlated. This permits credentials to be presented as they are created in an asynchronous manner and still correlated after verification. Mike Prorock CTO, Founder https://mesur.io/ On Tue, Jan 16, 2024 at 1:34 AM ステファニー タン(SBIホールディングス) < tstefan@sbigroup.co.jp> wrote: > Hi, all > > This might seem like a silly question, so I hope you would indulge me. > > In the context of using VCs in a traceability context (for example, supply > chain). As the product moves along the supply chain and verifiable > credentials are also issued by each actor (to represent certifications of > inspection, etc. and might differ depending on the product), I imagine that > the VP at the end would be difficult to verify since the contents become > very long and complex to inspect. > > In such a case, I am looking for real-life use cases or examples on how > this complexity is handled. I assumed that it might be through an interface > of some sort… > > Any thoughts or comments are very much appreciated. Thank you in advance. > > Best, > Stefannie >
Received on Tuesday, 16 January 2024 14:29:43 UTC