business-partner-agent
business-partner-agent copied to clipboard
hyperledger-labs
Arbitrary Credential Subject ID
There are Use Cases where the holder is not the subject of a credential.
I might e.g. want to testate some fact about some thing in my possession, e.g. a trade item that I am producing.
The W3C VC specification allows for arbitrary URIs as credential subject ids which should be resolvable and point to a document describing the subject. See https://w3c.github.io/vc-data-model/#identifiers ( https://w3c.github.io/vc-data-model/#credential-subject ). A GS1 digital link would work here just as well as a did.
To adress this, I would like to be able to (optionally) choose the VC credential subject id to be something else than the ID of the holder that I am issuing the credential to.
(Technically independent of, but use case related to #514 )
I've always thought this is an odd concept to be included in the VCs. A VC uses cryptography that apply to the holder--that they were issued the VC by the issuer. What data is in the VC is left open, and it can be anything. Why should it matter if the assertions from the issuer are about the holder, a third party subject, or no one. They are just assertions.
That said, it could be used for that purpose. Indy AnonCrrds has no metadata concept of "subject", so use of it with AnonCreds credentials would depend on whether or not there is an attribute in the credential called "subject".
Ahhh, very good point. So my feature request really is about JSON(-LD) credentials which are not yet supported by the BPA. For AnnonCreds I can work around this issue by explicitly adding a credentialSubject attribute. I was unaware that this field does not exist in the Indy world per se, thanks for the explanation!