security-vocab

security-vocab copied to clipboard

The security context references https://w3id.org/security#. But https://w3id.org/security redirects to https://w3id.org/security/, which redirects to https://w3c-ccg.github.io/security-vocab/, which does not return JSON-LD - even if the HTTP Accept header is set to `application/ld+json`...

clehner

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

OR13

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

OR13

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

OR13

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

OR13

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

OR13

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...

OR13

Ensure microdata is applied correctly to all entries

1

OR13

remove reliance on https://w3id.org/security/v1

OR13

Add Documentation for SchnorrSecp256k1Signature2019

1

https://w3c-ccg.github.io/ld-cryptosuite-registry/#secp256k1 https://github.com/decentralized-identity/SchnorrSecp256k1Signature2019

OR13