Commit d41c9af 1 parent 764ef2c commit d41c9af Copy full SHA for d41c9af
File tree 1 file changed +13
-4
lines changed
1 file changed +13
-4
lines changed Original file line number Diff line number Diff line change @@ -2484,12 +2484,13 @@ <h4>Enveloped Verifiable Credentials</h4>
2484
2484
</ dd >
2485
2485
</ dl >
2486
2486
2487
- < p >
2487
+ < p >
2488
2488
The example below shows a [=verifiable presentation=] that contains an
2489
2489
enveloped [=verifiable credential=]:
2490
- </ p >
2490
+ </ p >
2491
2491
2492
- < pre class ="example nohighlight " title ="Basic structure of a presentation ">
2492
+ < pre class ="example nohighlight "
2493
+ title ="Basic structure of a presentation ">
2493
2494
{
2494
2495
"@context": [
2495
2496
"https://www.w3.org/ns/credentials/v2",
@@ -2502,7 +2503,15 @@ <h4>Enveloped Verifiable Credentials</h4>
2502
2503
"type": "EnvelopedVerifiableCredential"
2503
2504
}]</ span >
2504
2505
}
2505
- </ pre >
2506
+ </ pre >
2507
+
2508
+ < p class ="note " title ="Processing enveloped content as RDF ">
2509
+ It is possible that an implementer might want to process the object described in
2510
+ this section, and the enveloped presentation expressed by the `id` value, in an
2511
+ RDF environment and create linkages between the objects that are relevant to
2512
+ RDF. The desire and mechanisms for doing so are use case dependent and will,
2513
+ thus, be implementation dependent.
2514
+ </ p >
2506
2515
2507
2516
</ section >
2508
2517
You can’t perform that action at this time.
0 commit comments