<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Pedro<br>
</p>
<div class="moz-cite-prefix">On 16/02/2023 04:58, Pedro Felix via
Openid-specs-ab wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAM-Bv-qHxntX3sqjaH9EOJpGLDTU8nYTrPphfrUGFYzPSteHnA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Hi,
The latest OpenID4VCI spec
(<a class="moz-txt-link-freetext" href="https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-11.html">https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-11.html</a>)
requires that certain JSON objects "... MUST be processed using full
JSON-LD processing", namely credentials_supported and
credentials_definition (e.g
<a class="moz-txt-link-freetext" href="https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-11.html#section-e.1.3.3">https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-11.html#section-e.1.3.3</a>),
when the format is jwt_vc_json-ld or ldp_vc.</pre>
</blockquote>
This is not actually the case. JSON-LD is fully conformant JSON and
JSON processing tools can be used to obtain VCs that are LD
compliant. There is currently a discussion in the VC-WG about the
use of the @context property (which turns JSON into JSON-LD) and
this is still ongoing. Once this issue has been resolved we will
need to revisit the OID4VCI spec to make it conformant to the
VC-DMv2 spec.<br>
<blockquote type="cite"
cite="mid:CAM-Bv-qHxntX3sqjaH9EOJpGLDTU8nYTrPphfrUGFYzPSteHnA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
IINM, this requires all the internal fields to be
"fully-contextualized", i.e., they need to be mapped to URIs by a
JSON-LD context. This already happens for credentialSubject, which is
defined on the <a class="moz-txt-link-freetext" href="https://www.w3.org/2018/credentials/v1">https://www.w3.org/2018/credentials/v1</a> context
(credentialSubject maps to
<a class="moz-txt-link-freetext" href="https://www.w3.org/2018/credentials#credentialSubject">https://www.w3.org/2018/credentials#credentialSubject</a>)
However, there are other fields which are introduced by the OpenID4VCI
spec, such as cryptographic_binding_methods_supported,
cryptographic_suites_supported, used inside credentials_supported and
which aren't mapped to URIs.</pre>
</blockquote>
<p>These are metadata properties that are in the issuer's metadata
file. They are not necessarily in the VCs that the issuer issues
(though they could optionally be placed there, in which case a new
@context may need to be defined for them - but again this will
have to wait until the @context issue is resolved in the VC-WG,
because the use of @vocab may cover these (and any other) new
properties)</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAM-Bv-qHxntX3sqjaH9EOJpGLDTU8nYTrPphfrUGFYzPSteHnA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
So,
1) Doesn't the OpenID4VCI spec need to map those fields to full URIs,</pre>
</blockquote>
Not if they remain in the metadata file only<br>
<blockquote type="cite"
cite="mid:CAM-Bv-qHxntX3sqjaH9EOJpGLDTU8nYTrPphfrUGFYzPSteHnA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
if they are to be used with "full JSON-LD processing"?
2) Should the OpenID4VCI spec define a context with those mappings and
make it available in a openid.net URL, similar to what the W3C does
with <a class="moz-txt-link-freetext" href="https://www.w3.org/2018/credentials/v1">https://www.w3.org/2018/credentials/v1</a>?</pre>
</blockquote>
<p>Yes it would be best to, if it also says that these new
properties can be properties of the issued credentials</p>
<p>Kind regards</p>
<p>David<br>
</p>
<blockquote type="cite"
cite="mid:CAM-Bv-qHxntX3sqjaH9EOJpGLDTU8nYTrPphfrUGFYzPSteHnA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
Thanks.
Regards,
Pedro
_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="https://lists.openid.net/mailman/listinfo/openid-specs-ab">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
</body>
</html>