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.
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@directionto generate directional language strings.