@damoo raised this issue in chat. From the ensuing discussion:
JZ: If the spec says servers must support N3 patch and may support SPARQL patch, it would make sense for rdflib to support it. Although webOperation can be used to send an N3 patch to servers which support it, so I'm not sure it is a critical issue.
దామోదర @damooo
And it would also make sense for solid-os to support solid compatible servers!. Using rdflib or otherwise.
Alain Bourgeois @bourgeoa
SolidOS does support compatible servers through webOperation. But I suppose I misunderstand your use case.
Jeff Zucker @jeff-zucker
However, for example, when SolidOS submits a form, it does so with a SPARQL patch. If, in the future, a server decides not to implement SPARQL patch, our forms system would break.
Likewise, when deciding if something is editable rdflib's updater looks for application/sparql-update in the accept-patch header but not for text/n3.
damooo
commented
2 years ago
@damoo raised this issue in chat. From the ensuing discussion:
JZ: If the spec says servers must support N3 patch and may support SPARQL patch, it would make sense for rdflib to support it. Although webOperation can be used to send an N3 patch to servers which support it, so I'm not sure it is a critical issue.
దామోదర @damooo And it would also make sense for solid-os to support solid compatible servers!. Using rdflib or otherwise.
Alain Bourgeois @bourgeoa SolidOS does support compatible servers through webOperation. But I suppose I misunderstand your use case.
Jeff Zucker @jeff-zucker However, for example, when SolidOS submits a form, it does so with a SPARQL patch. If, in the future, a server decides not to implement SPARQL patch, our forms system would break.
Likewise, when deciding if something is editable rdflib's updater looks for application/sparql-update in the accept-patch header but not for text/n3.