json-ld-api
json-ld-api copied to clipboard
w3c
JSON-LD 1.1 Processing Algorithms and API Specification
In the expansion algorithm, while processing language mappings in step 13.7 and substeps, a variable name seems to be swapped: Step 13.7.4.2.3 says to check *item* as being well-formed accoding...
- Various tests of when `@type` of `@json` is used, the JSON may be an array, and the interaction with a `@container` of `@set` and `@list`. - Change compaction output...
I believe that the [RDF to object conversion](https://w3c.github.io/json-ld-api/#algorithm-16), step 2.3.4, has a blind spot. This is in the case `useNativeTypes` is used: > if the [datatype IRI](https://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri) of value equals...
EDIT (2024) to provide some context (no pun intended): In the Verifiable Credentials work, an argument to add `@vocab` to the core VC context was made (notably, I recommended against...
## Manifest ```bash jq '.sequence[] | select(."@id" == "#tc037")' tests/expand-manifest.jsonld ``` which gives: ```json { "@id": "#tc037", "@type": [ "jld:PositiveEvaluationTest", "jld:ExpandTest" ], "name": "property-scoped contexts which are alias of @nest",...
Tests are already consistent with this interpretation, although it was never documented in the API properly. Fixes #603. *** Preview | Diff
Add html/f005 with extractAllScripts set to true. See #606. For #603. cc/@niklasl
The JSON-LD section on [JSON-LD in HTML Documents](https://w3c.github.io/json-ld-syntax/#embedding-json-ld-in-html-documents) specifically says that all script all script elements are extracted, implying that the default value of |extractAllScripts| should be `true` for the...
(Note, this impacts YAML-LD which will treat input as multiple documents when `extractAllScripts` is `true`, which is the default for `flatten()` and `toRdf()`). Given an input document such as the...
## Context https://github.com/w3c/json-ld-api/issues/579 (for JSON-LD 1.1 API) or https://github.com/json-ld/yaml-ld/issues/143 (for YAML-LD, which derives from JSON-LD) seem to stem from a common issue: a reader of the API specification might be...