Open csarven opened 3 weeks ago
note: lines beginning @prefix
are also valid; they are just required to end with .
, while lines beginning PREFIX
(case-insensitive!) must not end with .
.
Just so I understand you correctly, are you saying that @prefix
is valid in SPARQL Update/Query (application/sparql-update
)? My reading of https://www.w3.org/TR/sparql11-query/#rPrefixDecl is that it is invalid. Is there another reference somewhere that I'm overlooking? Or did you mean in the case of N3 / Turtle?
Oh, ugh. I'm sorry, I keep thinking that SPARQL and Turtle [@]prefix
statements were fully aligned, but it was only done in one direction (so copy-paste works from one to the other, but not from the other to the one).
I feel like this partial alignment should be considered an erratum for SPARQL 1.2/RDF 1.2, no matter how clear the independent grammars may be in-and-of themselves, because I'm not the only one who gets them flipped.
Snippet of an example request:
Snippet of an example response:
AFAICT, https://github.com/linkeddata/rdflib.js/issues/651 captures the issue in that NSS rejects SPARQL Update requests with valid payload using
PREFIX
(and accepts invalid payload containing@prefix
).