Re: Identifiers in Verifiable Credentials

What kind of NFTs are you building?

- Adrian

On Tue, Jun 8, 2021 at 6:30 PM Steve Capell <steve.capell@gmail.com> wrote:

> Isn’t it true that pretty much every VC that is about a “thing” (eg an
> invoice about a shipment , a bill of lading about a consignment, an origin
> certificate about a product , etc) are bearer VCs because the verifier only
> cares about proof of issuer ID.  the ID of the thing (subject) isn’t
> something that the thing has to (or is able to) prove.  It’s just an
> assertion by the issuer
>
> These “esoteric” cases represent 99% of my use cases and volumes
>
> Steven Capell
> Mob: 0410 437854
>
> > On 9 Jun 2021, at 6:02 am, Manu Sporny <msporny@digitalbazaar.com>
> wrote:
> >
> > On 6/6/21 5:57 PM, Kerri Lemoie wrote:
> >> I’m not clear on the uses for the optional id in the vc assertion. It
> >> would be helpful to learn about some examples or suggested uses.
> >
> > I saw answers for why you wouldn't want to use an `id` in the VC
> assertion. I
> > didn't see many examples of why you would want to use `id`. Here are two:
> >
> > * You have a single-use bearer token (movie ticket, age
> >  token) that you want to determine if it's been used
> >  before or not. Identifiers like this are useful for that
> >  use case:
> >
> >  urn:uuid:ddf810cc-c891-11eb-9fd3-67046f0b67f0
> >
> >  These sorts of identifiers also compress well when
> >  using CBOR-LD (to 16 bytes) and help when encoding
> >  to QR Codes.
> >
> > * You have a public Verifiable Credential where you
> >  might want to publish other information, such as
> >  an HTML representation of the VC. An Open Badge
> >  URL might be a good use here.
> >
> > There are other uses, but they tend to be fairly use case specific and
> thus,
> > esoteric.
> >
> > -- manu
> >
> > --
> > Manu Sporny - https://www.linkedin.com/in/manusporny/
> > Founder/CEO - Digital Bazaar, Inc.
> > blog: Veres One Decentralized Identifier Blockchain Launches
> > https://tinyurl.com/veres-one-launches
> >
> >
>
>