You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already have, currently, a discrepancy in the security vocabulary. The term defined in the vocabulary is expiration but it is referred to in the security vocabulary context file as expires. The vocabulary contains the following comment:
Historically, this property has often been expressed using expires as a shortened term in JSON-LD. Since this shortened term and its mapping to this property are in significant use in the ecosystem, the inconsistency between the short term name (expires) and the property identifier (...#expiration) is expected and should not trigger an error.
I realized today that there are four more similar discrepancies between the context file and the vocabulary namely
short name for JSONLD in the context
vocabulary term used in the context
current vocabulary term
authentication
authenticationMethod
authentication
capabilityInvocation
capabilityInvocationMethod
capabilityInvocation
capabilityDelegation
capabilityDelegationMethod
capabilityDelegation
keyAgreement
keyAgreementMethod
keyAgreement
I presume that the vocabulary file should be changed, and it should refer to ...Method with a similar comment. However, I would prefer to get a reinforcement from the WG before doing a change.
We already have, currently, a discrepancy in the security vocabulary. The term defined in the vocabulary is
expiration
but it is referred to in the security vocabulary context file asexpires
. The vocabulary contains the following comment:I realized today that there are four more similar discrepancies between the context file and the vocabulary namely
I presume that the vocabulary file should be changed, and it should refer to
...Method
with a similar comment. However, I would prefer to get a reinforcement from the WG before doing a change.@dlongley @msporny
The text was updated successfully, but these errors were encountered: