You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In section 2.2 the text (still?) says a triple term can be assigned to the subject or object of an RDF Triple — which I understand is RDF-star, and not RDF 1.2 (?)
And then the text goes on to say a triple term is denoted by <<( and )>> (which I understand is correct for a triple term as the object) — but the example then uses << and >>, with the triple term in the subject. Which is a bit of a mix up, I believe, and does not match the current N-Triples 1.2 draft, which AFAIU, is correct.
Perhaps I've not explained this well... but if you take a look at the above link... I'm pretty certain that the whole of section 2.2 for N-Quads 1.2 should in fact be the same as section 2.2 in the current N-Triples 1.2 draft:
On both of these page:
https://w3c.github.io/rdf-n-quads/spec/#triple-terms
https://www.w3.org/TR/rdf12-n-quads/#triple-terms
In section 2.2 the text (still?) says a triple term can be assigned to the subject or object of an RDF Triple — which I understand is RDF-star, and not RDF 1.2 (?)
And then the text goes on to say a triple term is denoted by
<<(
and)>>
(which I understand is correct for a triple term as the object) — but the example then uses<<
and>>
, with the triple term in the subject. Which is a bit of a mix up, I believe, and does not match the current N-Triples 1.2 draft, which AFAIU, is correct.Perhaps I've not explained this well... but if you take a look at the above link... I'm pretty certain that the whole of section 2.2 for N-Quads 1.2 should in fact be the same as section 2.2 in the current N-Triples 1.2 draft:
https://www.w3.org/TR/rdf12-n-triples/#triple-terms
https://w3c.github.io/rdf-n-triples/spec/#triple-terms
Would you like a pull request for this?
Or is it just easier for one of you folk (@gkellogg ?) to make this edit?
The text was updated successfully, but these errors were encountered: