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

https://github.com/w3c/did-core/blob/master/contexts/did-v0.11.jsonld#L24

https://github.com/w3c-dvcg/ld-proofs/blob/gh-pages/index.html#L546

https://github.com/web-payments/web-payments.org/blob/master/contexts/security-v2.jsonld#L25

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": "https://w3id.org/security#",

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?

OS
ᐧ

On Mon, Nov 25, 2019 at 10:26 AM Manu Sporny <msporny@digitalbazaar.com>
wrote:

> 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
> https://tinyurl.com/veres-one-launches
>
>

-- 
*ORIE STEELE*
Chief Technical Officer
www.transmute.industries

<https://www.transmute.industries>