search

w3c / json-ld-syntax

JSON-LD 1.1 Specification
https://w3c.github.io/json-ld-syntax/
Other
112 stars 22 forks source link

Should we consider a simple initial context like in RDFa? #44

Closed iherman closed 6 years ago

iherman commented 6 years ago

(Spin-off from #42)

There may be a number of prefixes that we could 'predefine', i.e., having them part, formally, of an initial @context. This would simplify to encourage users to use terms from, say, DCMI, in a consistent manner for things like comments or descriptions, without requiring them to extend the context (which, for many authors, may be a challenge).

RDFa has a similar notion but I actually do not think we should replicate that; we could make it much smaller and less dynamic. Taking into account the JSON-LD user community, I would probably restrict it to rdf, rdfs, xsd, cc, dc/dcterms, and schema. Extending this list could be restricted to future revisions of JSON-LD 1.1.

azaroth42 commented 6 years ago

For reference, in 1.0 this was discussed here: https://github.com/json-ld/json-ld.org/issues/80

gkellogg commented 6 years ago

When discussed in 1.0 it became an issue when the context is re-defined using @context: null and was rejected. For those using http://schema.org, this is already done for them, which probably covers most uses.

gkellogg commented 6 years ago

Resolved to close.

azaroth42 commented 6 years ago

WG resolved to close, won't fix, but to open a new issue to create a best practice for a suggested context that could be imported into other contexts.

BigBlueHat commented 6 years ago

The new issue opened to "create a best practice for a suggested context" https://github.com/w3c/json-ld-syntax/issues/59