- From: Brent Zundel <brent.zundel@evernym.com>
- Date: Fri, 29 Mar 2019 07:03:28 -0600
- To: Mike Varley <mike.varley@securekey.com>
- Cc: Pete Rowley <prowley@wireline.io>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CAHR74YUTgNbqLGJzdviSNZ7yzJ7WOEdjqvjas6YvDruDFDWFPw@mail.gmail.com>
The proof object may be an array. On Fri, Mar 29, 2019, 06:57 Mike Varley <mike.varley@securekey.com> wrote: > Hi Pete, my understanding of the spec is that for your use case, you would > need to define a new ‘type’ and then put your array under that object. > Something like: > > > > "proof": { > > "type": "arrayOfProofs", > > "theproofs" : [ … ] > > } > > > > But I am not an author or editor – so my above answer is a bit of a test > to see if I understand the spec correctly? (if oversimplified?) > > > > Thanks > > > > MV > > > > *From: *Pete Rowley <prowley@wireline.io> > *Date: *Friday, March 29, 2019 at 3:42 AM > *To: *"public-credentials@w3.org" <public-credentials@w3.org> > *Subject: *VC/VP proofs > *Resent-From: *<public-credentials@w3.org> > *Resent-Date: *Friday, March 29, 2019 at 3:41 AM > > > > I'm trying to construct a VerifiablePresentation that has the following > properties: > > > > 1. the VC is not a bearer token > > 2. the VC id refers to itself (not some external entity) > > 3. the VC contains its own public key (so that presentation proofs are a > proof that the VC holder is the true holder, not a man in the middle) > > 4. Given a set of VC in a presentation, the presentation has a proof for > each VC (referenced by the VC id) > > > > Section 4.7 says a proof is "one or more cryptographic proofs." But all > examples show a single object structure for the proof, not an array. Can an > array be substituted or is this something to be defined within the proof > object itself? > > > > I think it would be helpful if it were possible to nest presentations so > that each VC can have its own presentation in order to closely represent > the relationships of proofs to VC here. > > > > -- > > - Pete > > https://wireline.io >
Received on Friday, 29 March 2019 13:04:03 UTC