chasemp added a subscriber: chasemp. chasemp added a comment. Yesterday in IRC it seemed like there was consensus we don't have any actual (quantifiable) concerns regarding query length at the moment.
SMalyshev: chasemp: I'm not worried too much about query length The 2008 <http://www.w3.org/TR/rdf-sparql-protocol/#query-bindings-http> guidelines seem explicit that GET is the mechanism of choice up to the point that length for GET isn't viable. The 2013 <http://www.w3.org/TR/sparql11-http-rdf-update/> guidelines still indicate the use of POST query but also outline that it isn't the only operation for which POST is necessary <http://www.w3.org/TR/sparql11-http-rdf-update/#http-post>: This protocol is a companion to the use of both SPARQL Update and SPARQL Query over the SPARQL protocol via HTTP POST. Both protocols specify different operations performed via the HTTP POST method. At first glance, it seems like this means mangling all POST to GET would result in an incompatibility with the sparql protocol. If we are saying we don't want to leave clients (which follow a somewhat odd spec to my mind) in the dust I don't think we are accomplishing that, and as Brandon outlined POST in the Wikimedia multi-dc world has specific consequences. Besides knowing that at some point length is a factor do we have a demonstratable need for this functionality (which will be very nuanced in implementation)? TASK DETAIL https://phabricator.wikimedia.org/T112151 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Smalyshev, chasemp Cc: chasemp, JanZerebecki, BBlack, Andrew, Deskana, Joe, gerritbot, nichtich, Jneubert, Karima, Aklapper, Smalyshev, JGirault, jkroll, Wikidata-bugs, Jdouglas, aude, Manybubbles _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
