Re: Reusing VCs in a safe and meaningful way

You might be interested in:

https://github.com/w3c-ccg/traceability-vocab

Sounds similar to a few of the workflows defined by it.

You are welcome to join the weekly calls, or send comments to this list
after watching them if they are not accessible do to timezone.

OS


On Thu, Sep 7, 2023, 9:45 PM ステファニー タン（SBIホールディングス） <tstefan@sbigroup.co.jp>
wrote:

> Dear all,
>
> This is Stefannie again. First off, I would like to thank everyone who
> sent in their opinions, suggestions and follow-up questions with our
> previous question regarding DID method-specific-id. I passed it on to our
> engineering team and we are currently doing further investigation.
>
> I have another question from our engineering side, this time regarding how
> VCs can be reused in a safe and meaningful way.
>
> Please see below our Business design, Business Flow and Technical
> Solutions that we are considering.
>
> [Business Design]
> Companies should get a VC from a trust-worthy organization before they can
> transact with each other.
>
> [Business Flow]
> Here is the Business flow for the case when Company A needs to sell
> Product B to Company B,  and Product C to Company C.
>
>    1. Company A gets a VC (VC-A) from the trust-worthy organization.
>    2. Company A, in its internal system, makes TraceID-B for selling
>    Production B to Company B.
>    3. In the same way, Company A, in its internal system, makes TraceID-C
>    for selling Production C to Company C.
>    4. Company A needs to share Production B info(i.e. production name),
>    TraceID-B and the VC-A with Company B.
>    5. In the same way, Company A needs to share Production C info(i.e.
>    production name),  TraceID-C and the VC-A with Company C.
>
> [Technical Solution]
> To achieve the above, while keeping in line with DID VC protocol, we
> discussed two solutions.
>
>    1. Company A builds a new self-signed VC-B with Production B info and
>    TraceID-B.  Then, Company A makes VP-B by signing against VC-A and VC-B.
>    Finally, Company A passes VP-B to Company B for verification purposes.
>    2. Company A makes VP-B by signing against VC-A. Then,  Company A
>    builds a new self-signed VC-B with Production B info and TraceID-B and
>    VP-B.  Finally, Company A passes VC-B to Company B for verification
>    purposes.
>
>
> We are wondering which one of the two solutions fits more into the DIDVC
> protocol.  At the same time, we would like to know whether there are
> potentially other solutions.
>
> Best regards,
> Stefannie
> SBI Holdings, Inc.
>
>
>
>