Re: Proof purposes (was Re: Proposed work item: did:key DID Method)

I'm in favor of leaving it as is, assertionMethod makes it clear this
section is about how to make assertions, not a list of assertions, claims
or proofs.

I'd love if the did spec did not rely on:

    "sec": "",

And instead defined the terms locally, at least until there is a major
release / version published.

I suspect this is not possible without breaking JSON-LD...

Next best option would be to centralize the hosting / documentation of
JSON-LD security contexts into some organization under W3C, and then have
verifiable credentials, dids, etc all reference the same context... I
recall there was a possibility of JSON-LD Crypto/Security group forming, is
there any chance that might be a better home for these contexts?


On Mon, Nov 25, 2019 at 10:26 AM Manu Sporny <>

> On 11/24/19 3:48 PM, Dmitri Zagidulin wrote:
> > We've added the list of commonly used proof purposes
> Bikeshedding... but noting "assertionMethod"... why not just
> "assertion"? Then we'd have "authentication, assertion, keyAgreement,
> contractAgreement... just a drive-by bike shedding thought.
> -- manu
> --
> Manu Sporny (skype: msporny, twitter: manusporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches

Chief Technical Officer


Received on Monday, 25 November 2019 18:07:59 UTC