What
RDF 1.2 content can be created by PUT and POST, and never by PATCH.
Why
PATCH is N3 Patch and only N3 Patch (ADR-8), and Notation3 has formulas, not triple terms. So there is no patch document that can insert a triple term, a reifier or a directional literal into a resource.
Two bullets three lines apart in the README imply this and neither says it. The result is a write surface with a hole in it: whatever a client can create wholesale it cannot subsequently amend, and the failure is a parse error rather than an explanation.
How
- First establish what happens today: the N3 parser meeting
<<( … )>> presumably fails, and the error a client sees decides how bad this is.
- Then decide: document it as a known limit, extend the patch format, or accept a second one for this case. The last is the least attractive given ADR-8.
- Whatever the answer, it belongs in ADR-6 or ADR-8 rather than in an issue, because it is a consequence of both.
What
RDF 1.2 content can be created by
PUTandPOST, and never byPATCH.Why
PATCHis N3 Patch and only N3 Patch (ADR-8), and Notation3 has formulas, not triple terms. So there is no patch document that can insert a triple term, a reifier or a directional literal into a resource.Two bullets three lines apart in the README imply this and neither says it. The result is a write surface with a hole in it: whatever a client can create wholesale it cannot subsequently amend, and the failure is a parse error rather than an explanation.
How
<<( … )>>presumably fails, and the error a client sees decides how bad this is.