Checking a historical artifact...

[iherman]

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.

@dlongley @msporny

[dlongley]

Yes, the vocabulary needs to be updated to reflect the vocab terms used in the context as stated above in the table.

[iherman]

This issue is being taken care of in #243; it can be closed if and when the PR is merged.

[msporny]

PR #243 has been merged, closing.