Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update to Candidate Recommendation JSON-LD Context. #277

Merged
merged 4 commits into from
Apr 7, 2021
Merged

Update to Candidate Recommendation JSON-LD Context. #277

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d6f2124
Update to Candidate Recommendation JSON-LD Context.
msporny Mar 28, 2021
abda671
Ensure that verificationMethod is a set.
msporny Mar 29, 2021
51269fc
Remove @set from verificationMethod definition.
msporny Apr 1, 2021
b8c3fca
Remove `@container`: `@set` from alsoKnownAs and service.
msporny Apr 7, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 21 additions & 53 deletions vocabs/v1/context.jsonld
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,89 +1,57 @@
{
"@context": {
"@version": 1.1,
"@protected": true,
"id": "@id",
"type": "@type",
"dc": "http://purl.org/dc/terms/",
"schema": "http://schema.org/",
"sec": "https://w3id.org/security#",
"didns": "https://www.w3.org/ns/did#",
"xsd": "http://www.w3.org/2001/XMLSchema#",
"EcdsaSecp256k1VerificationKey2019": "sec:EcdsaSecp256k1VerificationKey2019",
"Ed25519Signature2018": "sec:Ed25519Signature2018",
"Ed25519VerificationKey2018": "sec:Ed25519VerificationKey2018",
"JsonWebKey2020": "sec:JsonWebKey2020",
"JsonWebSignature2020": "sec:JsonWebSignature2020",
"Bls12381G1Key2020": "sec:Bls12381G1Key2020",
"Bls12381G2Key2020": "sec:Bls12381G2Key2020",
"RsaVerificationKey2018": "sec:RsaVerificationKey2018",
"SchnorrSecp256k1VerificationKey2019": "sec:SchnorrSecp256k1VerificationKey2019",
"X25519KeyAgreementKey2019": "sec:X25519KeyAgreementKey2019",
"ServiceEndpointProxyService": "didns:ServiceEndpointProxyService",
"LinkedDomains": "https://identity.foundation/.well-known/resources/did-configuration/#LinkedDomains",

"alsoKnownAs": {
"@id": "https://www.w3.org/ns/activitystreams#alsoKnownAs",
"@type": "@id",
"@container": "@set"
"@type": "@id"
},
"assertionMethod": {
"@id": "sec:assertionMethod",
"@id": "https://w3id.org/security#assertionMethod",
kdenhartog marked this conversation as resolved.
Show resolved Hide resolved
"@type": "@id",
"@container": "@set"
},
"authentication": {
"@id": "sec:authenticationMethod",
"@id": "https://w3id.org/security#authenticationMethod",
"@type": "@id",
"@container": "@set"
},
"capabilityDelegation": {
"@id": "sec:capabilityDelegationMethod",
"@id": "https://w3id.org/security#capabilityDelegationMethod",
"@type": "@id",
"@container": "@set"
},
"capabilityInvocation": {
"@id": "sec:capabilityInvocationMethod",
"@id": "https://w3id.org/security#capabilityInvocationMethod",
"@type": "@id",
"@container": "@set"
},
"controller": {
"@id": "sec:controller",
"@id": "https://w3id.org/security#controller",
"@type": "@id"
},
"created": {
"@id": "dc:created",
"@type": "xsd:dateTime"
},
"blockchainAccountId": "sec:blockchainAccountId",
"keyAgreement": {
"@id": "sec:keyAgreementMethod",
"@type": "@id",
"@container": "@set"
},
"publicKey": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

publicKey not being retained for backwards compatibility?

Copy link
Member Author

@msporny msporny Mar 29, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No I don't think we should, publicKey has been deprecated for a while now. It's usually a bad practice to keep deprecated things around, especially since we have the opportunity to do the right thing still (in CR) and because it would lead to two code paths in crypto libraries (and we really want to try and reduce things to a few code paths as possible to reduce attack surface).

"@id": "sec:publicKey",
"@id": "https://w3id.org/security#keyAgreementMethod",
"@type": "@id",
"@container": "@set"
},
"publicKeyBase58": "sec:publicKeyBase58",
kdenhartog marked this conversation as resolved.
Show resolved Hide resolved
"publicKeyJwk": {
"@id": "sec:publicKeyJwk",
"@type": "@json"
},
"service": {
"@id": "didns:service",
"@type": "@id",
"@container": "@set"
},
"serviceEndpoint": {
"@id": "didns:serviceEndpoint",
"@type": "@id"
},
"updated": {
kdenhartog marked this conversation as resolved.
Show resolved Hide resolved
"@id": "dc:modified",
"@type": "xsd:dateTime"
"@id": "https://www.w3.org/ns/did#service",
"@type": "@id",
"@context": {
"@protected": true,
"id": "@id",
"type": "@type",
"serviceEndpoint": {
"@id": "https://www.w3.org/ns/did#serviceEndpoint",
"@type": "@id"
}
}
},
"verificationMethod": {
"@id": "sec:verificationMethod",
"@id": "https://w3id.org/security#verificationMethod",
"@type": "@id"
msporny marked this conversation as resolved.
Show resolved Hide resolved
}
}
Expand Down