solid
Drop SPARQL query functionality on GET
This should likely not be in the core spec (especially since it is unclear what subset should be supported). Can be in an extension though.
@RubenVerborgh Just so I understand the implications of this: Would this mean moving the parts on SPARQL and/or SPARQL UPDATE out of LDP?
Liked this in general because I think it's always good to simplify specifications where possible, but realized I might not understand the implications of this.
Also, if yes, that it means moving SPARQL out of LDP, we should thread very carefully. This is functionality that both rdflib.js and LDflex is dependent on, ain't it?
This is a proposal for moving SPARQL query functionality out of the spec. Using SPARQL UPDATE as body of a PATCH request can stay.
LDflex does not depend on server-side SPARQL queries; I don’t think any lib/app does, since NSS doesn’t support it.
Ok, as long as SPARQL UPDATEs as part of body stays, I don't have any objections ^_^
I don't see the point of removing this.
it is unclear what subset should be supported
So to fix that, let's document it better! :)
I'm not very familiar with SPARQL, but to me it seemed quite simple you can do any SPARQL query on an RDF source, as long as it's valid SPARQL? Can you elaborate on what is unclear?
