json-ld-bp
json-ld-bp copied to clipboard
w3c
JSON-LD 1.1 Best Practices Note
These document was never published, but the specStatus indicates its a WG-NOTE. This causes issues when people look at the ED and see a reference to a non-existing note. IMO,...
examples
Hi, the examples use `"@context": "http://schema.org"` while schema.org states that the context is found elsewhere: https://schema.org/docs/developers.html It should be ` "@context": "https://schema.org/docs/jsonldcontext.json",`
Coming from today's WoT Thing Description meeting: We wondering if there is a standardized place where we can find the Frame and/or validation document (eg, SHACL, JSON Schema,... ) for...
Given a response object like: ```json { "@context": "https://schema.org", "type": "Collection", "hasPart": [ { "id": "123", "type": "ScreeningEvent", "location": "abc" }, { "id": "456", "type": "ScreeningEvent", "location": "abc" } ]...
Of note are discussions in https://github.com/w3c/json-ld-syntax/issues/366 and https://github.com/rubensworks/jsonld-streaming-parser.js/issues/65. Best practices should include the principles of JSON-LD streaming, where keys come in a strict order, as well as the use of...
Instead of normatively requiring an initial context, such as RDFa does, instead JSON-LD has the ability to import contexts. This approach means that the existing context rules are followed, and...
As evidenced by [reports](https://github.com/w3c/json-ld-syntax/issues/91), there is some confusion about how to use multilingual data values alongside language maps. @pchampin [noted](https://github.com/w3c/json-ld-syntax/issues/91#issuecomment-445313785) that using an alias is a good way to work...
While reading https://github.com/w3c/pub-manifest/issues/65 I tested the following JSON-LD in the [playground](https://json-ld.org/playground): ```json { "@context": { "name": { "@id": "http://example.com/name", "@type": "xsd:string" } }, "name": true } ``` This resulted in...
