Remove SPARQL on GET - Githubissues

solid / solid-spec

Solid specification draft 0.7.0

Creative Commons Zero v1.0 Universal

1.13k stars 103 forks source link

Remove SPARQL on GET #206

Open RubenVerborgh opened 5 years ago

RubenVerborgh commented 5 years ago

it’s a bad idea for scalability, DOS, and other reasons
it’s not implementable the way it is written (subset not defined)
it’s not implemented or used anywhere as far as we know

I strongly favor removal over deprecation (#205).

dmitrizagidulin commented 5 years ago

👍

michielbdejong commented 5 years ago

Looks like two members of the query panel already agree on this so could be a quick decision :) cc @kjetilk @justinwb.

RubenVerborgh commented 5 years ago

@dmitrizagidulin Thanks, could you do that as a review, too? 🙂

@michielbdejong Not sure what part of process to follow here, given that this is not a normative section. We might or might not need a week for the public and approval by three editors; also unsure if I can merge. Assigning to you; feel free to unassign.

kjetilk commented 5 years ago

Actually, I am a bit conflicted, since I could see how it could be implemented easily, and I'm not sure very extensive edits are needed to the document at this point as we restart from scratch. It might just stay there for historical reasons. But OTOH, since it hasn't been implemented and has problems, it can be removed just fine too.

RubenVerborgh commented 5 years ago

@kjetilk The issue is that, whatever is in solid-spec, will end up in vNext; the only option to not have a feature end up in vNext is to remove it from solid-spec. So my main reason for creating this PR is to ensure that vNext does not have this security hole in it.