Orie Steele

related https://gpg.jsld.org/contexts/#publicKeyGpg

Best Practices for Inline Contexts

2

I am starting to feel like although they increase the size, they are a best practice over remote / by reference contexts.... A couple notes: 1. prefixing is safer in...

Missing documentation for capabilityChain

2

## Missing Documentation **Line number of the property that is missing a definition** https://github.com/w3c-ccg/security-vocab/blob/master/contexts/security-v2.jsonld#L33

Missing documentation for invoker

1

## Missing Documentation **Line number of the property that is missing a definition** https://github.com/w3c-ccg/security-vocab/blob/master/contexts/security-v1.jsonld#L44

Missing documentation for invocationTarget

1

## Missing Documentation **Line number of the property that is missing a definition** https://github.com/w3c-ccg/security-vocab/blob/master/contexts/security-v1.jsonld#L43

Missing documentation for allowedAction

1

## Missing Documentation **Line number of the property that is missing a definition** https://github.com/w3c-ccg/security-vocab/blob/master/contexts/security-v2.jsonld#L28

https://github.com/w3c-ccg/security-vocab/pull/56#discussion_r475814675 We don't need to include it.

Proposal for deterministic IDs for Sha256HmacKey2019

4

``` { "id":"urn:digest:6a8fdcd1377afccf388999796e278cfb2768cce7b8f2534b7f281d91934b3be4", "type":"Sha256HmacKey2019", "privateValueBase58": "..." } ``` where id is sha256 of `privateValueBase58`.... We need this for secure data stores.... @dlongley @dmitrizagidulin

Add guidance for not using "prefix" in JSON-LD

1

@dlongley I heard you prefer not to register prefixes, and instead use full URLs... That should be documented in this repo somewhere... I am attempting to follow that guidance, and...