- From: Ivan Herman <ivan@w3.org>
- Date: Thu, 26 Mar 2009 07:14:42 +0100
- To: Lee Feigenbaum <lee@thefigtrees.net>
- CC: SPARQL Working Group <public-rdf-dawg@w3.org>
- Message-ID: <49CB1D52.6080002@w3.org>
Why just Javascript? I have the impression that most SPARQL implementations are written in some other language, and this would force the implementation to include a JS engine. But, if not JS, then what? A language independent declarative description of a functionality? I think it is cool but way beyond what SPARQL1.1 could handle. Maybe SPARQL 2? :-) Ivan Lee Feigenbaum wrote: > I was just taking a look at > http://www.w3.org/2009/sparql/wiki/Feature:JavaScriptFunctions which was > submitted on our -comments list by Holger Knublauch of TopQuadrant. > > The gist, as I understand it, is asking implementations to dereference > URIs of unknown FILTER functions to retrieve RDF descriptions that > contain JavaScript implementations of the functions. > > I think this is pretty cool, myself, but it also seems very new, a very > high burden for implementors, and potentially fraught with security > concerns that I haven't thought of yet. > > I'd like to know if there are any other implementations of this feature > (which, to generalize a bit, I'd call a mechanism for interoperably > resolving unknown SPARQL functions) and also if there are any Working > Group members who care to advocate in favor of the group producing a > specification for this feature. > > Lee > -- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Thursday, 26 March 2009 06:15:30 UTC