42
42
43
43
// editors, add as many as you like
44
44
// only "name" is required
45
- editors : [
46
- { name : "Tobias Looker" , url : "https://mattr.global/" ,
47
- company : "Mattr" , companyURL : "https://mattr.global/" , w3cid : 109171 , }
45
+ editors : [ {
46
+ name : "Tobias Looker" , url : "https://mattr.global/" ,
47
+ company : "Mattr" , companyURL : "https://mattr.global/" , w3cid : 109171 ,
48
+ } , {
49
+ name : "Greg Bernstein" , url : "https://www.grotto-networking.com/" ,
50
+ company : "Invited Expert" , w3cid : 140479
51
+ } , {
52
+ name : "Manu Sporny" , url : "https://digitalbazaar.com/" ,
53
+ company : "Digital Bazaar" , companyURL : "https://digitalbazaar.com/" ,
54
+ w3cid : 41758
55
+ }
48
56
] ,
49
57
50
58
// extend the bibliography entries
63
71
// wgPatentURI: "https://www.w3.org/community/about/agreements/cla/",
64
72
65
73
github : "https://github.com/w3c/vc-di-bbs" ,
66
-
74
+
67
75
// URI of the patent status for this WG, for Rec-track documents
68
76
// !!!! IMPORTANT !!!!
69
77
// This is important for Rec-track documents, do not copy a patent URI from a random
@@ -401,7 +409,7 @@ <h3>JsonWebKey</h3>
401
409
< p class ="advisement ">
402
410
Developers are advised to not accidentally publish a representation of a private
403
411
key. Implementations of this specification MUST raise errors if expression
404
- of public key information includes a key parameter that is marked as
412
+ of public key information includes a key parameter that is marked as
405
413
`Private` in the IANA JSON Web Key Parameters registry.
406
414
</ p >
407
415
@@ -513,7 +521,7 @@ <h3>bbs-signature-2023</h3>
513
521
< p >
514
522
This suite relies on detached digital signatures represented using [[MULTIBASE]].
515
523
</ p >
516
-
524
+
517
525
< p >
518
526
The `verificationMethod` property of the proof MUST be a URL.
519
527
Dereferencing the `verificationMethod` MUST result in an object
@@ -576,7 +584,7 @@ <h3>bbs-proof-2023</h3>
576
584
< p >
577
585
This suite relies on detached digital signatures represented using [[MULTIBASE]].
578
586
</ p >
579
-
587
+
580
588
< p >
581
589
The `verificationMethod` property of the proof MUST be a URL.
582
590
Dereferencing the `verificationMethod` MUST result in an object
@@ -926,16 +934,16 @@ <h3>Proof Verification </h3>
926
934
< section >
927
935
< h3 > bbs-proof-2023</ h3 >
928
936
< p >
929
- The `bbs-proof-2023` cryptographic suite takes an input document,
937
+ The `bbs-proof-2023` cryptographic suite takes an input document,
930
938
that has previously been secured using `bbs-signature-2023`,
931
- derives from this original document a set of messages to be disclosed
932
- representing a redacted form of the original document, and
939
+ derives from this original document a set of messages to be disclosed
940
+ representing a redacted form of the original document, and
933
941
applies the < a data-cite ="CFRG-BBS-SIGNATURE#name-proofgen "> Proof Gen</ a >
934
942
algorithm to produce a proof of knowledge for the disclosed messages.
935
943
The result is a new `proof`, containing the following attributes:
936
944
</ p >
937
945
938
-
946
+
939
947
< ul >
940
948
< li >
941
949
`generators`
@@ -947,10 +955,10 @@ <h3>bbs-proof-2023</h3>
947
955
`proofValue`
948
956
</ li >
949
957
</ ul >
950
- < p > This operation can be applied by any
958
+ < p > This operation can be applied by any
951
959
< a data-cite ="VC-DATA-MODEL-2#dfn-holders "> holder</ a > of a `bbs-signature-2023`
952
960
secured document, and as such, `bbs-proof-2023` MUST be implemented with
953
- awareness of the mandatory to disclose fields the original
961
+ awareness of the mandatory to disclose fields the original
954
962
< a data-cite ="VC-DATA-MODEL-2#dfn-issuers "> issuer</ a > required.
955
963
</ p >
956
964
< p class ="issue " data-number ="3 "> </ p >
@@ -982,7 +990,7 @@ <h3>Proof Serialization </h3>
982
990
< h3 > Proof Verification </ h3 >
983
991
< p class ="issue " data-number ="85 "> </ p >
984
992
</ section >
985
-
993
+
986
994
</ section >
987
995
</ section >
988
996
@@ -999,9 +1007,9 @@ <h2>Security Considerations</h2>
999
1007
< p class ="issue "> TODO: We need to add a complete list of security
1000
1008
considerations.</ p >
1001
1009
</ section >
1002
-
1003
1010
1004
-
1011
+
1012
+
1005
1013
< section class ="appendix ">
1006
1014
< h2 > Acknowledgements</ h2 >
1007
1015
< p >
0 commit comments