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
Typically, a JSON-LD document is a JSON object, which naturally maps to a CBOR map.
But unlike JSON, CBOR allows non-strings as keys of a map. Since JSON-LD has a number of recurring keys (the keywords), space could be saved by conventionally encode these with a shorter type (a 1-bytes integer would be enough).
E.g., we could decide that 1 means @context, 2 means @type, etc.
In order to make this convention explicit, it would be cleaner to prefix this top-level map with a dedicated CBOR semantic tag.
The text was updated successfully, but these errors were encountered:
Typically, a JSON-LD document is a JSON object, which naturally maps to a CBOR map.
But unlike JSON, CBOR allows non-strings as keys of a map. Since JSON-LD has a number of recurring keys (the keywords), space could be saved by conventionally encode these with a shorter type (a 1-bytes integer would be enough).
E.g., we could decide that 1 means
@context
, 2 means@type
, etc.In order to make this convention explicit, it would be cleaner to prefix this top-level map with a dedicated CBOR semantic tag.
The text was updated successfully, but these errors were encountered: