protected should be allowed
troyronda opened this issue · 4 comments
https://w3c.github.io/json-ld-api/#algorithm
5.13 For each key-value pair in context where key is not @ base, @ direction, @ import, @ language, @ propagate, @ protected, @ version, or @ vocab, invoke the Create Term Definition algorithm, passing result for active context, context for local context, key, defined, and the value of the @ protected entry from context, if any, for protected .
Example usage:
https://www.w3.org/2018/credentials/v1
Usage of this context results in an error:
Received unexpected error: invalid term definition: true
This error occurs because @ protected is not included in:
Line 225 in 39d0d03
@troyronda, many thanks for reporting. @ protected is a part of JSON-LD 1.1 spec, which is only partially supported by this library. It's a relatively new term. We plan to bring compliance to 1.1 to 100% before the end of the year (but I can't promise that).
Regards,
Stan
@troyronda I've created a new PR that implements the majority of the current JSON-LD 1.1 features, see #24. I intend to publish a new version in the next couple of days. Watch this space!