should JSON-LD 1.2 support RDF 1.2 basic ?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 139
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
The current charter says that JSON-LD 1.2 will focus on errata, and that JSON-LD 1.3 will align with RDF 1.2.
The rationale was that RDF 1.2 adds complexity for the syntax, because of triple terms.
A middle way could be to align JSON-LD 1.2 with RDF 1.2 basic, i.e. RDF 1.2 without triple terms. The only other major change between RDF 1.1 and RDF 1.2 are directional language strings, which JSON-LD already supports, so this would be almost free, and at least new JSON-LD would not rely on a subsumed version of RDF.
Concretely, what would need to change is a new possible value for rdfDirection, rdf-1.2, which would be the default value, and would lead value objects with @direction to generate directional language strings.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current JSON-LD 1.1 API definition of rdfDirection and the linked RDF 1.2 Concepts sections. Compare RDF 1.2 basic with RDF 1.1, especially directional language strings and triple terms, then evaluate the proposed rdf-1.2 default. Done means the working group has resolved the JSON-LD 1.2 scope and specified any required changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- backend-api-design, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100