-
Notifications
You must be signed in to change notification settings - Fork 21
/
index.html
2912 lines (2763 loc) · 114 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<title>The Security Vocabulary</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline,
-->
<script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "CG-DRAFT",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "security-vocabulary",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
// previousPublishDate: "1977-03-15",
// previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "https://w3c-ccg.github.io/security-vocab/",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
//extraCSS: ["prettify.css"],
// editors, add as many as you like
// only "name" is required
editors: [
{
name: "Manu Sporny",
url: "http://manu.sporny.org/",
company: "Digital Bazaar, Inc.",
companyURL: "https://digitalbazaar.com/"
},
{
name: "Orie Steele",
url: "https://transmute.industries/",
company: "Transmute Industries, Inc.",
companyURL: "https://transmute.industries/"
},
{
name: "Tobias Looker",
url: "https://mattr.global/",
company: "Mattr",
companyURL: "https://mattr.global/"
},
],
// authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
//authors: [
// { name: "Your Name", url: "http://example.org/",
// company: "Your Company", companyURL: "http://example.com/" },
//],
github: "https://github.com/w3c-ccg/security-vocab/",
// extend the bibliography entries
localBiblio: {
"ED25519-2020": {
title: "Ed25519 Signature 2020",
date: "November 2020",
href: "https://w3c-ccg.github.io/lds-ed25519-2020/",
authors: [
"Orie Steele"
],
status: "Community Group Draft",
publisher: "W3C Credentials Community Group"
},
"LD-CRYPTOSUITE-REGISTRY": {
title: "The Linked Data Cryptosuite Registry",
date: "May 2021",
href: "https://w3c-ccg.github.io/ld-cryptosuite-registry/",
authors: [
"Manu Sporny",
"Orie Steele"
],
status: "W3C Community Group Draft",
publisher: "W3C Credentials Community Group"
},
"MULTIBASE": {
title: "The Multibase Data Format",
date: "February 2021",
href: "https://datatracker.ietf.org/doc/html/draft-multiformats-multibase-03",
authors: [
"Manu Sporny"
],
status: "Internet-Draft",
publisher: "IETF"
},
"MULTICODEC": {
title: "The Multicodec Data Format",
date: "May 2021",
href: "https://github.com/multiformats/multicodec/blob/master/table.csv",
authors: [
"Steven Allen",
"David Dias"
],
status: "Draft",
publisher: "Protocol Labs"
}
},
// name of the WG
wg: "Credentials Community Group",
// URI of the public WG page
wgURI: "https://w3c-ccg.github.io/",
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-credentials@w3c.org",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "",
// Run the following pre-processing commands
preProcess: []
};
</script>
<script type="text/javascript" src="prettify.js" class="remove"></script>
<script type="text/javascript" src="lang-jsonld.js" class="remove"></script>
<script type="text/javascript" class="remove">
var oldonload = window.onload;
window.onload = function() {
if (oldonload) oldonload();
prettyPrint();
};
</script>
</head>
<body prefix="rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs: http://www.w3.org/2000/01/rdf-schema#
vs: http://www.w3.org/2003/06/sw-vocab-status/ns#
sec: https://w3id.org/security#">
<section id='abstract'>
<p>
The Security vocabulary is used to enable Internet-based applications to
encrypt, decrypt, and digitally sign information expressed as
<a href="http://en.wikipedia.org/wiki/Linked_data">Linked Data</a>.
It also provides vocabulary terms for the creation and management of a
decentralized
<a href="http://en.wikipedia.org/wiki/Public_key_infrastructure">Public Key Infrastructure</a>
via the Web.
</p>
</section>
<section id='sotd'>
<p>
This is an experimental vocabulary and is not intended for use in production
systems by non-experts.
</p>
</section>
<section>
<h2>Introduction</h2>
<p>
This document describes a number of classes and properties that can be used to
express <a href="http://en.wikipedia.org/wiki/Digital_signatures">
digital signatures</a> and achieve cryptographic protection for Linked Data
resources. This specification was designed as a modular part of the
<a href="http://payswarm.com/">PaySwarm</a> decentralized payment system
for the Web.
</p>
<p class="issue">
This entire document is a work in progress and should be considered in beta
until it is ratified as an official document via the World Wide Web Consortium.
</p>
</section>
<section>
<h2>Classes</h2>
<section id="EcdsaSecp256k1Signature2019" about="https://w3id.org/security#EcdsaSecp256k1Signature2019"
typeof="rdfs:Class">
<h3>EcdsaSecp256k1Signature2019</h3>
<p>
This class represents a linked data signature suite. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#ecdsa-secp256k1">ecdsa-secp256k1</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Expected properties</dt>
<dd>type, created, verificationMethod, proofPurpose, jws</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"type": "EcdsaSecp256k1Signature2019",
"created": "2020-03-30T20:54:52Z",
"verificationMethod": "did:example:123#qfknmVDhMi3Uc190IHBRfBRqMgbEEBRzWOj1E9EmzwM",
"proofPurpose": "assertionMethod",
"jws": "eyJhbGciOiJFUzI1NksiLCJiNjQiOmZhbHNlLCJjcml0IjpbImI2NCJdfQ..EsCNG3KD8CcurIBd354JMIYvsBr9bvF17RQbfqEg5dZy45vmSGVg1U5_rlXihjGLb3EtTK9-73X3YYYgfW2Byg"
}
</pre>
</section>
<section id="EcdsaSecp256k1RecoverySignature2020" about="https://identity.foundation/EcdsaSecp256k1RecoverySignature2020#EcdsaSecp256k1RecoverySignature2020"
typeof="rdfs:Class">
<h3>EcdsaSecp256k1RecoverySignature2020</h3>
<p>
This class represents a linked data signature suite. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#ecdsasecp256k1recoverysignature2020">ecdsasecp256k1recoverysignature2020</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Expected properties</dt>
<dd>type, created, verificationMethod, proofPurpose, jws</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"type": "EcdsaSecp256k1RecoverySignature2020",
"created": "2020-04-11T21:07:06Z",
"verificationMethod": "did:example:123#vm-3",
"proofPurpose": "assertionMethod",
"jws": "eyJhbGciOiJFUzI1NkstUiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..pp9eiLCMfN4EfSB3cbl3UxJ4TtgUaTfByDaaB6IZbXsnvIy5AUIFjbgaiFNtq9-3f8mP7foD_HXpjrdWZfzlwAE"
}
</pre>
</section>
<section id="EcdsaSecp256k1VerificationKey2019" about="https://w3id.org/security#EcdsaSecp256k1VerificationKey2019"
typeof="rdfs:Class">
<h3>EcdsaSecp256k1VerificationKey2019</h3>
<p>
This class represents a linked data signature verification key. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#ecdsa-secp256k1">ecdsa-secp256k1</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Expected properties</dt>
<dd>id, type, controller, publicKeyJwk</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"id": "did:example:123#WqzaOweASs78whhl_YvCEvj1nd89IycryVlmZMefcjU",
"type": "EcdsaSecp256k1VerificationKey2019",
"controller": "did:example:123",
"publicKeyJwk": {
"crv": "secp256k1",
"x": "4xAbUxbGGFPv4qpHlPFAUJdzteUGR1lRK-CELCufU9w",
"y": "EYcgCTsff1qtZjI9_ckZTXDSKAIuM0BknrKgo0BZ_Is",
"kty": "EC",
"kid": "WqzaOweASs78whhl_YvCEvj1nd89IycryVlmZMefcjU"
}
}
</pre>
</section>
<section id="EcdsaSecp256k1RecoveryMethod2020" about="https://identity.foundation/EcdsaSecp256k1RecoverySignature2020#EcdsaSecp256k1RecoveryMethod2020"
typeof="rdfs:Class">
<h3>EcdsaSecp256k1RecoveryMethod2020</h3>
<p>
This class represents a linked data signature verification key. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#ecdsasecp256k1recoverymethod2020">ecdsasecp256k1recoverymethod2020</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Expected properties</dt>
<dd>id, type, controller</dd>
</dl>
<pre class="example prettyprint language-jsonld" title="Example using publicKeyJwk">
{
"id": "did:example:123#WqzaOweASs78whhl_YvCEvj1nd89IycryVlmZMefcjU",
"type": "EcdsaSecp256k1RecoveryMethod2020",
"controller": "did:example:123",
"publicKeyJwk": {
"crv": "secp256k1",
"x": "4xAbUxbGGFPv4qpHlPFAUJdzteUGR1lRK-CELCufU9w",
"y": "EYcgCTsff1qtZjI9_ckZTXDSKAIuM0BknrKgo0BZ_Is",
"kty": "EC",
"kid": "WqzaOweASs78whhl_YvCEvj1nd89IycryVlmZMefcjU"
}
}
</pre>
<pre class="example prettyprint language-jsonld" title="Example using blockchainAccountId">
{
"id": "did:example:123#keys-1",
"type": "EcdsaSecp256k1RecoveryMethod2020",
"controller": "did:example:123",
"blockchainAccountId": "eip155:1:0x89a932207c485f85226d86f7cd486a89a24fcc12"
}
</pre>
</section>
<section id="RsaSignature2018" about="https://w3id.org/security#RsaSignature2018"
typeof="rdfs:Class">
<h3>RsaSignature2018</h3>
<p>
This class represents a linked data signature suite. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#rsa">rsa</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Expected properties</dt>
<dd>type, created, verificationMethod, proofPurpose, jws</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"type": "RsaSignature2018",
"created": "2017-06-18T21:19:10Z",
"proofPurpose": "assertionMethod",
"verificationMethod": "https://example.edu/issuers/keys/1",
"jws": "eyJhbGciOiJSUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..TCYt5X
sITJX1CxPCT8yAV-TVkIEq_PbChOMqsLfRoPsnsgw5WEuts01mq-pQy7UJiN5mgRxD-WUc
X16dUEMGlv50aqzpqh4Qktb3rk-BuQy72IFLOqV0G_zS245-kronKb78cPN25DGlcTwLtj
PAYuNzVBAh4vGHSrQyHUdBBPM"
}
</pre>
</section>
<section id="RsaVerificationKey2018" about="https://w3id.org/security#RsaVerificationKey2018"
typeof="rdfs:Class">
<h3>RsaVerificationKey2018</h3>
<p>
This class represents a linked data signature verification key. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#rsa">rsa</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Expected properties</dt>
<dd>id, type, controller, expires, publicKeyPem</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"id": "did:example:123456789abcdefghi#keys-1",
"type": "RsaVerificationKey2018",
"controller": "did:example:123456789abcdefghi",
"expires": "2017-02-08T16:02:20Z",
"publicKeyPem": "-----BEGIN PUBLIC KEY...END PUBLIC KEY-----\r\n"
}
</pre>
</section>
<section id="SchnorrSecp256k1Signature2019" about="https://w3id.org/security#SchnorrSecp256k1Signature2019"
typeof="rdfs:Class">
<h3>SchnorrSecp256k1Signature2019</h3>
</section>
<section id="SchnorrSecp256k1VerificationKey2019" about="https://w3id.org/security#SchnorrSecp256k1VerificationKey2019"
typeof="rdfs:Class">
<h3>SchnorrSecp256k1VerificationKey2019</h3>
</section>
<section id="ServiceEndpointProxyService" about="https://w3id.org/security#ServiceEndpointProxyService"
typeof="rdfs:Class">
<h3>ServiceEndpointProxyService</h3>
</section>
<section id="Digest" about="https://w3id.org/security#Digest"
typeof="rdfs:Class">
<h3>Digest</h3>
<p>
This class represents a message digest that may be used for data integrity
verification. The digest algorithm used will determine the cryptographic
properties of the digest.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Expected properties</dt>
<dd>digestAlgorithm, digestValue</dd>
</dl>
<p>
The example below describes a cryptographic digest:
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": "https://w3id.org/security/v1",
"@type": "Digest",
"digestAlgorithm": "http://www.w3.org/2000/09/xmldsig#sha1",
"digestValue": "981ec496092bf6ee18d6255d96069b528633268b"
}
</pre>
</section>
<section id="EncryptedMessage"
about="https://w3id.org/security#EncryptedMessage"
typeof="rdfs:Class">
<h3>EncryptedMessage</h3>
<p>
A class of messages that are obfuscated in some cryptographic manner. These
messages are incredibly difficult to decrypt without the proper decryption key.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Expected properties</dt>
<dd>authenticationTag, cipherAlgorithm, cipherData, cipherKey,
initializationVector, publicKey</dd>
</dl>
<p>
The example below expresses a message that has been encrypted using an
<a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">AES</a>
cipher in
<a href="http://en.wikipedia.org/wiki/GCM_mode">Galois/Counter Mode</a> and a
128-bit key (AES-128-GCM). The key has been encrypted using an RSA public key.
The encrypted message, <code>cipherData</code>, and encrypted key,
<code>cipherKey</code>, are both base64-encoded. To decrypt the message, first
the <code>cipherKey</code> must be decrypted using the private key associated
with the <code>publicKey</code>. Then, the <code>cipherData</code> can be
decrypted using the decrypted <code>cipherKey</code>,
<code>cipherAlgorithm</code>, <code>initializationVector</code>, and
<code>authenticationTag</code>.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": "https://w3id.org/security/v1",
"@type": "EncryptedMessage",
"cipherData": "VTJGc2RHVmtYMThOY3h2dnNVN290Zks1dmxWc3labi9sYkU0TGloRTdxY0dpblE4OHgrUXFNNi9l\n↩
a1JMWjdXOApRSGtrbzh6UG5XOFo3WWI4djJBUG1abnlRNW5CVGViWkRGdklpMEliczNWSzRQTGdB\n↩
UFhxYTR2aWFtemwrWGV3Cmw0eFF4ancvOW85dTlEckNURjMrMDBKMVFubGdtci9abkFRSmc5UjdV\n↩
Rk55ckpYalIxZUJuKytaQ0luUTF2cUwKcm5vcDU1eWk3RFVqVnMrRXZZSkx6RVF1VlBVQ0xxdXR4\n↩
L3lvTWd4bkdhSksxOG5ZakdiekJxSGxOYm9pVStUNwpwOTJ1Q0Y0Q2RiR1NqL0U3OUp4Vmh6OXQr\n↩
Mjc2a1V3RUlNY3o2Z3FadXZMU004KzRtWkZiakh6K2N5a1VVQ2xHCi9RcTk3b2o3N2UrYXlhZjhS\n↩
ZmtEZzlUeWk3Q2szREhSblprcy9WWDJWUGhUOEJ5c3RiYndnMnN4eWc5TXhkbHoKUkVESzFvR0FJ\n↩
UDZVQ09NeWJLTGpBUm0zMTRmcWtXSFdDY29mWFNzSGNPRmM2cnp1Wko0RnVWTFNQMGROUkFRRgpB\n↩
bFQ0QUpPbzRBZHpIb2hpTy8vVGhNOTl1U1ZER1NPQ3graFAvY3V4dGNGUFBSRzNrZS8vUk1MVFZO\n↩
YVBlaUp2Ckg4L1ZWUVU4L3dLZUEyeTQ1TzQ2K2lYTnZsOGErbGg0NjRUS3RabktFb009Cg==",
"cipherKey": "uATtey0c4nvZIsDIfpFffuCyMYGPKRLIVJCsvedE013SpEJ+1uO7x6SK9hIG9zLWRlPpwmbar2bt\n↩
gTX5NBzYC5+c5ZkXtM1O8REwIJ7wmtLdumRYEbr/TghFl3pAgXhv0mVt8XZ+KLWlxMqXnrT+ByNw\n↩
z7u3IxpqNVcXHExjXQE=",
"cipherAlgorithm": "aes-128-gcm",
"authenticationTag": "q25H1CzsE731OmeyEle93w==",
"initializationVector": "vcDU1eWTy8vVGhNOszREhSblFVqVnGpBUm0zMTRmcWtMrRX=="
"publicKey": "https://example.com/people/john/keys/23"
}
</pre>
</section>
<section id="GraphSignature2012" about="https://w3id.org/security#GraphSignature2012"
typeof="sec:Signature">
<h3>GraphSignature2012</h3>
<p>
A graph signature is used for digital signatures on RDF graphs.
The default canonicalization mechanism is specified in the
RDF Graph normalization specification, which effectively deterministically
names all unnamed nodes. The default signature mechanism uses a SHA-256 digest
and RSA to perform the digital signature.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Parent Class</dt>
<dd>Signature</dd>
<dt>Expected properties</dt>
<dd>creator, signatureValue</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URGNA2012">
https://w3id.org/rdf#URGNA2012</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="http://www.w3.org/2000/09/xmldsig#rsa-sha256">
http://www.w3.org/2000/09/xmldsig#rsa-sha256</a>
</dd>
</dl>
</dd>
</dl>
<p>
The example below shows how a basic JSON-LD signature is expressed in a
JSON-LD snippet. Note that the signature property is directly embedded in the
object. The signature algorithm specifies how a signature can be generated
and verified.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": ["https://w3id.org/security/v1", "http://json-ld.org/contexts/person.jsonld"]
"@type": "Person",
"name": "Manu Sporny",
"homepage": "http://manu.sporny.org/",
"signature": {
"@type": "GraphSignature2012",
"creator": "http://manu.sporny.org/keys/5",
"signatureValue": "OGQzNGVkMzVmMmQ3ODIyOWM32MzQzNmExMgoYzI4ZDY3NjI4NTIyZTk="
}
}
</pre>
</section>
<section id="LinkedDataSignature2015"
about="https://w3id.org/security#LinkedDataSignature2015"
typeof="rdfs:Class">
<h3>LinkedDataSignature2015</h3>
<p>
A Linked Data signature is used for digital signatures on RDF Datasets.
The default canonicalization mechanism is specified in the RDF Dataset
Normalization specification, which effectively deterministically names all
unnamed nodes. The default signature mechanism
uses a SHA-256 digest and RSA to perform the digital signature. This
signature uses a algorithm for producing the data that it signs and
verifies that is different from other Linked Data signatures.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Parent Class</dt>
<dd>Signature</dd>
<dt>Expected properties</dt>
<dd>creator, signatureValue</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URDNA2015">
https://w3id.org/rdf#URDNA2015</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="http://www.w3.org/2000/09/xmldsig#rsa-sha256">
http://www.w3.org/2000/09/xmldsig#rsa-sha256</a>
</dd>
</dl>
</dd>
</dl>
<p>
The example below shows how a basic JSON-LD signature is expressed in a
JSON-LD snippet. Note that the signature property is directly embedded in the
object. The signature algorithm specifies how the signature can be generated
and verified.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": ["https://w3id.org/security/v1", "http://json-ld.org/contexts/person.jsonld"]
"@type": "Person",
"name": "Manu Sporny",
"homepage": "http://manu.sporny.org/",
"signature": {
"@type": "LinkedDataSignature2015",
"creator": "http://manu.sporny.org/keys/5",
"created": "2015-09-23T20:21:34Z",
"signatureValue": "OGQzNGVkMzVmMmQ3ODIyOWM32MzQzNmExMgoYzI4ZDY3NjI4NTIyZTk="
}
}
</pre>
</section>
<section id="LinkedDataSignature2016">
<h3>LinkedDataSignature2016</h3>
<p>
A Linked Data signature is used for digital signatures on RDF Datasets.
The default canonicalization mechanism is specified in the RDF Dataset
Normalization specification, which effectively deterministically names all
unnamed nodes. The default signature mechanism
uses a SHA-256 digest and RSA to perform the digital signature.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Parent Class</dt>
<dd>Signature</dd>
<dt>Expected properties</dt>
<dd>creator, signatureValue</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URDNA2015">
https://w3id.org/rdf#URDNA2015</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="http://www.w3.org/2000/09/xmldsig#rsa-sha256">
http://www.w3.org/2000/09/xmldsig#rsa-sha256</a>
</dd>
</dl>
</dd>
</dl>
<p>
The example below shows how a basic JSON-LD signature is expressed in a
JSON-LD snippet. Note that the signature property is directly embedded in the
object. The signature algorithm specifies how the signature can be generated
and verified.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": ["https://w3id.org/security/v1", "http://json-ld.org/contexts/person.jsonld"]
"@type": "Person",
"name": "Dave Longley",
"homepage": "https://w3id.org/people/dave",
"signature": {
"@type": "LinkedDataSignature2016",
"creator": "https://w3id.org/people/dave/keys/2",
"created": "2016-11-05T03:12:54Z",
"signatureValue": "OGQzNGVkMzVmMmQ3ODIyOWM32MzQzNmExMgoYzI4ZDY3NjI4NTIyZTk="
}
}
</pre>
</section>
<section id="MerkleProof2019" about="https://w3id.org/security#MerkleProof2019">
<h3>MerkleProof2019</h3>
<p>
A Linked Data signature is used for digital signatures on RDF Datasets.
The default canonicalization mechanism is specified in the RDF Dataset
Normalization specification, which effectively deterministically names all
unnamed nodes. The default signature mechanism
uses a SHA-256 digest and ECDSA to perform the digital signature. More information at
<a href="https://w3c-ccg.github.io/lds-merkle-proof-2019/">https://w3c-ccg.github.io/lds-merkle-proof-2019/</a>
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Parent Class</dt>
<dd>LinkedDataSignature</dd>
<dt>Expected properties</dt>
<dd>proofValue</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URDNA2015">
https://w3id.org/rdf#URDNA2015</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="https://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256">
https://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256</a>
</dd>
</dl>
</dd>
</dl>
<p>
The example below shows how a basic JSON-LD signature is expressed in a
JSON-LD snippet. Note that the proof property is directly embedded in the
object. The signature algorithm specifies how the signature can be generated
and verified.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://www.w3id.org/blockcerts/v3.0-alpha",
"https://www.w3.org/2018/credentials/examples/v1"
],
"id": "urn:uuid:bbba8553-8ec1-445f-82c9-a57251dd731c",
"type": [
"VerifiableCredential",
"BlockcertsCredential"
],
"issuer": "did:example:23adb1f712ebc6f1c276eba4dfa",
"issuanceDate": "2010-01-01T19:33:24Z",
"credentialSubject": {
"id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
"alumniOf": {
"id": "did:example:c276e12ec21ebfeb1f712ebc6f1"
}
},
"proof": {
"type": "MerkleProof2019",
"created": "2020-11-03T14:13:42.808099Z",
"proofValue": "zMcm4LfQFUZkWZyLpVrzYzaHRssD3xGQ6Yh6nEhErjfAqnxDWo7gBawdhynnbiucoqqwye54oTs5p6frH385nVvBf2UXMgRVtBZLq6tHN1MY1hQBMBBtXbWbYzj99GotAJRs7PxcvQmUQKHs8hkokZhgw92CNAtvDn2jeycvuyFPtWorxZaGP23mDkgwpberKmAqcPcsUFNooGe1UkQj8wws8D9paKHwFWxyCMvXNuYUGaBdZDaSpcd7uv3kEwgZAzAHb1jMgDeLSN1EdZA33LhPj5ACxMKs3vmwpTnjpNiALoZpJan",
"proofPurpose": "assertionMethod",
"verificationMethod": "did:example:23adb1f712ebc6f1c276eba4dfa#key-1"
}
}
</pre>
</section>
<section id="X25519KeyAgreementKey2019" about="https://w3id.org/security#X25519KeyAgreementKey2019"
typeof="rdfs:Class">
<h3>X25519KeyAgreementKey2019</h3>
<p>
This class represents a verification key.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Expected properties</dt>
<dd>id, type, controller, publicKeyBase58</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"id": "did:example:123#z6LSeu9HkTHSfLLeUs2nnzUSNedgDUevfNQgQjQC23ZCit6F",
"type": "X25519KeyAgreementKey2019",
"controller": "did:example:123",
"publicKeyBase58": "96XGGce9y12gRTxEcnuvpP8tCZzE39WkpKHvUZ6DLg6d"
}
</pre>
</section>
<section id="Ed25519VerificationKey2018" about="https://w3id.org/security#Ed25519VerificationKey2018"
typeof="rdfs:Class">
<h3>Ed25519VerificationKey2018</h3>
<p>
This class represents a linked data signature verification key. See <a href="https://w3c-ccg.github.io/ld-cryptosuite-registry/#ed25519">eddsa-ed25519</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Expected properties</dt>
<dd>id, type, controller, publicKeyBase58</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"id": "did:example:123#z6MkkQBvgvqb6zGvS4cydworpUaRDzpszSFixq49ahbDeUTG",
"type": "Ed25519VerificationKey2018",
"controller": "did:example:123",
"publicKeyBase58": "6wvt6gb9mSnTKZnGxNr1yP2RQRZ2aZ1NGp9DkRdCjFft"
}
</pre>
</section>
<section id="Ed25519Signature2018">
<h3>Ed25519Signature2018</h3>
<p>
A Linked Data signature is used for digital signatures on RDF Datasets.
The default canonicalization mechanism is specified in the RDF Dataset
Normalization specification, which deterministically names all
unnamed nodes. The default signature mechanism
uses a SHA-256 digest and JWS to perform the digital signature.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Parent Class</dt>
<dd>Signature</dd>
<dt>Expected properties</dt>
<dd>verificationMethod, jws</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URDNA2015">
https://w3id.org/rdf#URDNA2015</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="https://tools.ietf.org/html/rfc8037#section-3.1">
https://tools.ietf.org/html/rfc8037#section-3.1</a>
</dd>
</dl>
</dd>
</dl>
<p>
The JWS used with Linked Data Signatures is the detached and unencoded payload variant. See the links below for details:
</p>
<ul>
<li>
<a href="https://tools.ietf.org/html/rfc7797">JSON Web Signature (JWS) Unencoded Payload Option</a>
</li>
<li>
<a href="https://medium.com/swlh/json-web-signature-jws-and-jws-detached-for-a-five-year-old-88729b7b1a68">JSON Web Signature (JWS) and JWS Detached for a five-year-old.</a>
</li>
</ul>
<p>
The example below shows how a basic JSON-LD proof is expressed in a
JSON-LD snippet. Note that the proof property is directly embedded in the
object. The signature algorithm specifies how the proof can be generated
and verified.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": ["https://w3id.org/security/v1", "http://json-ld.org/contexts/person.jsonld"]
"@type": "Person",
"name": "Dave Longley",
"homepage": "https://w3id.org/people/dave",
"proof": {
"type": "Ed25519Signature2018",
"verificationMethod": "https://w3id.org/people/dave/keys/2",
"created": "2016-11-05T03:12:54Z",
"proofPurpose": "assertionMethod",
"jws": "eyJhbGciOiJFZERTQSIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..dXNHwJ-9iPMRQ4AUcv9j-7LuImTiWAG0sDYbRRDDiyAjOV9CUmjLMKiePpytoAmGNGNTHDlEOsTa4CS3dZ7yBg"
}
}
</pre>
</section>
<section id="Ed25519VerificationKey2020">
<h3>Ed25519VerificationKey2020</h3>
<p>
A linked data proof suite verification method <code>type</code>
used with <code>Ed25519Signature2020</code>.
</p>
<p class="advisement">
This suite is unstable and subject to change.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Parent Class</dt>
<dd>owl:Thing</dd>
<dt>Expected properties</dt>
<dd>id, type, controller, publicKeyMultibase</dd>
</dl>
</section>
<section id="Ed25519Signature2020">
<h3>Ed25519Signature2020</h3>
<p>
A linked data proof suite proof <code>type</code>
used with the verification method type <code>Ed25519VerificationKey2020</code>.
</p>
<p class="advisement">
This suite is unstable and subject to change.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Parent Class</dt>
<dd>Signature</dd>
<dt>Expected properties</dt>
<dd>verificationMethod, proofValue</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URDNA2015">
https://w3id.org/rdf#URDNA2015</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="https://tools.ietf.org/html/rfc8032">
https://tools.ietf.org/html/rfc8032</a>
</dd>
</dl>
</dd>
</dl>
</section>
<section id="JsonWebKey2020">
<h3>JsonWebKey2020</h3>
<p>
A linked data proof suite verification method <code>type</code>
used with <code>JsonWebSignature2020</code>.
</p>
<p class="advisement">
This suite is unstable and subject to change.
</p>
<p>
See also: <a href="https://github.com/w3c-ccg/lds-jws2020">w3c-ccg/lds-jws2020</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">unstable</dd>
<dt>Parent Class</dt>
<dd>owl:Thing</dd>
<dt>Expected properties</dt>
<dd>id, type, controller, publicKeyJwk</dd>
</dl>
<pre class="example prettyprint language-jsonld">
{
"id": "did:example:123#_Qq0UL2Fq651Q0Fjd6TvnYE-faHiOpRlPVQcY_-tA4A",
"type": "JsonWebKey2020",
"controller": "did:example:123",
"publicKeyJwk": {
"kty": "OKP",
"crv": "Ed25519",
"x": "VCpo2LMLhn6iWku8MKvSLg2ZAoC-nlOyPVQaO3FxVeQ"
}
}
</pre>
</section>
<section id="JsonWebSignature2020">
<h3>JsonWebSignature2020</h3>
<p>
A Linked Data signature is used for digital signatures on RDF Datasets.
The default canonicalization mechanism is specified in the RDF Dataset
Normalization specification, which deterministically names all
unnamed nodes. The default signature mechanism
uses a SHA-256 digest and JWS to perform the digital signature.
</p>
<p class="advisement">
This suite is unstable and subject to change.
</p>
<p>
See also: <a href="https://github.com/w3c-ccg/lds-jws2020">w3c-ccg/lds-jws2020</a>.
</p>
<dl>
<dt>Status</dt>
<dd property="vs:term_status">stable</dd>
<dt>Parent Class</dt>
<dd>Signature</dd>
<dt>Expected properties</dt>
<dd>verificationMethod, jws</dd>
<dt>Signature Properties</dt>
<dd>
<dl>
<dt>Default Canonicalization Algorithm</dt>
<dd>
<a rel="canonicalizationAlgorithm"
href="https://w3id.org/rdf#URDNA2015">
https://w3id.org/rdf#URDNA2015</a>
</dd>
<dt>Default Signature Algorithm</dt>
<dd>
<a rel="signatureAlgorithm"
href="https://tools.ietf.org/html/rfc8037#section-3.1">
https://tools.ietf.org/html/rfc8037#section-3.1</a>
</dd>
</dl>
</dd>
</dl>
<p>
The JWS used with Linked Data Signatures is the detached and unencoded payload variant. See the links below for details:
</p>
<ul>
<li>
<a href="https://tools.ietf.org/html/rfc7797">JSON Web Signature (JWS) Unencoded Payload Option</a>
</li>
<li>
<a href="https://medium.com/swlh/json-web-signature-jws-and-jws-detached-for-a-five-year-old-88729b7b1a68">JSON Web Signature (JWS) and JWS Detached for a five-year-old.</a>
</li>
</ul>
<p>
The example below shows how a basic JSON-LD proof is expressed in a
JSON-LD snippet. Note that the proof property is directly embedded in the
object. The signature algorithm specifies how the proof can be generated
and verified.
</p>
<pre class="example prettyprint language-jsonld">
{
"@context": ["https://w3id.org/security/v1", "http://json-ld.org/contexts/person.jsonld"]
"@type": "Person",
"name": "Dave Longley",
"homepage": "https://w3id.org/people/dave",
"proof": {
"type": "JsonWebSignature2020",
"verificationMethod": "https://w3id.org/people/dave/keys/2",
"created": "2016-11-05T03:12:54Z",
"proofPurpose": "assertionMethod",
"jws": "eyJhbGciOiJFZERTQSIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..dXNHwJ-9iPMRQ4AUcv9j-7LuImTiWAG0sDYbRRDDiyAjOV9CUmjLMKiePpytoAmGNGNTHDlEOsTa4CS3dZ7yBg"
}
}
</pre>
</section>
<section id="BbsBlsSignature2020" about="https://w3id.org/security#BbsBlsSignature2020"
typeof="rdfs:Class">
<h3>BbsBlsSignature2020</h3>
<p>
A Linked Data signature is used for digital signatures on RDF Datasets.
The default canonicalization mechanism is specified in the RDF Dataset
Normalization specification, which deterministically names all
unnamed nodes. Importantly, a BbsBlsSignature digests each of the statements
produced by the normalization process individually to enable selective disclosure.
The signature mechanism uses Blake2B as the digest for each statement and produces a single
output digital signature.
</p>
<dl>