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
Today in #json-ld, Manu and I discussed improving the compact form serializers to produce shorter, more compartmentalized, digest-able output. The optimization is primarily against @iri-keyed blocks, esp. with predicates having multiple IRI targets.
Any value like { @iri: /joe } should be automatically compacted to just "/joe" and a coercion rule should be added to the @context.
We also briefly speculated whether this should be described as a new form, eg. "short".
In any case, there should be a form where all non-data terms are separated into @context sections as much as possible. This will help pave the way for JSON-LD Web Services to encourage plain k/v pairs with "default @context". And support /really/ thin clients that don't have any LD know-how (@iri) whatsoever (ignore all @).
RESOLVED: JSON-LD processors MUST implement the compaction API. The algorithm for compaction optimization is not defined. There is an 'optimize' flag that can be set to true or false to enable compaction optimization.
Today in #json-ld, Manu and I discussed improving the compact form serializers to produce shorter, more compartmentalized, digest-able output. The optimization is primarily against @iri-keyed blocks, esp. with predicates having multiple IRI targets.
Any value like { @iri: /joe } should be automatically compacted to just "/joe" and a coercion rule should be added to the @context.
We also briefly speculated whether this should be described as a new form, eg. "short".
In any case, there should be a form where all non-data terms are separated into @context sections as much as possible. This will help pave the way for JSON-LD Web Services to encourage plain k/v pairs with "default @context". And support /really/ thin clients that don't have any LD know-how (@iri) whatsoever (ignore all @).
Explicit example:
{ "@context": {"foo": "http://example.com/foo#"}, "foo:bar": [{ "@iri" : "http://example.com/blah" }, { "@iri" : "http://example.com/blah" }] } }
optimized to:
{ "@context": {"foo": "http://example.com/foo#", "@Coerce": {"@iri": ["foo:bar"]}}, "foo:bar": ["http://example.com/blah", "http://example.com/blah"] }
The text was updated successfully, but these errors were encountered: