-
Notifications
You must be signed in to change notification settings - Fork 305
PATCH jsonld, rdf+xml and n3 #1695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
|
Should XML+RDF be spec compliant. rdfA is not ??? |
Are you talking specifically about the content type of the file being PATCHed? I sincerely hope that in the future RDFa will be patchable but that's a big task and not in the spec (yet) so no, I don't think we can offer to support it now. The simple case of creating a new RDFa file with PATCH could easily work but it does not make sense to me to support it if none of the other operations can work. As for XML+RDF - I am not familiar enough with parsing it to know for sure, but it seems to me that there would be no special issues for PATCH and therefore should be supported. |
|
^^ By which I mean that we should support sending a text/n3 PATCh to change an xml+rdf document, not that we should support sending an xml+rdf PATCH. |
|
I feel out of my depth to review this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, ship it! In the long run we should actually also have a test for this in the test suite probably - created solid-contrib/test-suite#148 about that
No description provided.