json-ld-syntax
json-ld-syntax copied to clipboard
JSON-LD 1.1 Specification
Kill "IRI"?
The heavy use of "IRI" as terminology in the spec, referencing RFC 3987, raises a number of thorny issues and actually makes JSON-LD out-of-sync with the latest developments at W3C....
On the call of 2018-12-14, we discussed (briefly) #20, #98, and #86. One realization that came out of the discussion was that we currently have two ways to refer to...
## Question It's not clear to me if it's legitimate to use `@type` in `@context` instead of in the JSON object, eg. ``` "@context": "@vocab": "https://schema.org/", birthplace: "@type": "City" birthplace:...
- Example 104 https://w3c.github.io/json-ld-syntax/#example-indexing-data-in-json-ld-by-node-identifiers-with-set-representation shows `@index: @id` with `@set` representation but doesn't explain its utility, since all such arrays are necessarily singletons - Example 105 https://w3c.github.io/json-ld-syntax/#example-indexing-data-in-json-ld-by-node-identifiers-using-none shows that an `@id`...
Text before https://w3c.github.io/json-ld-syntax/#example-indexing-languaged-tagged-strings-using-none-for-no-language: `string values not having a datatype` -> `string values not having a language tag`
(related to #397) - Example 119 https://w3c.github.io/json-ld-syntax/#example-indexing-graph-data-in-json-ld - Example 120 https://w3c.github.io/json-ld-syntax/#example-indexing-graphs-using-none-for-no-index Are supposed to demonstrate "default graph referencing multiple named graphs using an index map". - But both graphs end...
In object-oriented programmes the meaning of a property `name` of a class `Employee` is *bound to a class*. An *Employee_name* is *not* the same as a *Company_name* (a `name` property...
improve appendix B.1.3 as discussed in #387 *** ### :boom: Error: 504 Gateway Timeout :boom: ### [PR Preview](https://github.com/tobie/pr-preview#pr-preview) failed to build. _(Last tried on Jun 1, 2022, 7:58 PM UTC)_....
The spec doesn't describe explicitly enough what happens with JSON builtin types `integer` and `double`. - https://w3c.github.io/json-ld-syntax/#typed-values talks about 64-bit doubles and says "such as" without being exhaustive > 3....
I have an idea for a future version of JSON-LD. As a web developer, I would like to receive a JSON document from i.e. a simple API, add a `@context`...