Re: More questions about the VC Document 2.0 (part 2)

Hi,

concerning #2:

If your use case may be sufficient with JSON, then it might be 
interesting to follow the progress of SD-JWT VC, see 
https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/

The specification is adopted by the OAuth Seurity working group at IETF 
and defines JSON-only verifiable credentials with SD-JWT.


Best regards,

Paul


On 31.10.23 10:19, ステファニー タン（SBIホールディングス） wrote:
> Hello, everyone.
>
> We have more questions about some parts of the VC Document 2.0. Thanks 
> again to all who answered last time and in our previous questions. 
> It's certainly generating a lot of productive discussion in our team.
>
>  1. In the document, there is this line about multiple issuers in a
>     VP: "The data in a presentation
>     <https://www.w3.org/TR/vc-data-model-2.0/#dfn-presentation> is
>     often about the same subject
>     <https://www.w3.org/TR/vc-data-model-2.0/#dfn-subjects>, but might
>     have been issued by multiple issuers
>     <https://www.w3.org/TR/vc-data-model-2.0/#dfn-issuers>. The
>     aggregation of this information typically expresses an aspect of a
>     person, organization, or entity
>     <https://www.w3.org/TR/vc-data-model-2.0/#dfn-entities>. "
>     Has anyone here experimented with it before?
>
>  2. Is it correct to understand that it is generally possible to
>     convert JSON data with definitions as JSON-LD to JWT (SD-JWT) format?
>     Since the use cases for implementation using JSON-LD and BBS are
>     not common enough to be able to consider standards like ISO/W3C,
>     we must realistically consider using SD-JWT, but we would like to
>     confirm whether this is feasible with the VC2.0 Data model (using
>     JSON-LD).
>
> Thank you so much for any advice you can give.
>
> best regards,
> Stefannie
>
>
>