W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > March 2009

Re: Suggestion: Parameterised Queries

From: Arjohn Kampman <arjohn.kampman@aduna-software.com>
Date: Tue, 10 Mar 2009 10:15:37 +0100
Message-ID: <49B62FB9.5050300@aduna-software.com>
To: bnowack@semsol.com
CC: public-rdf-dawg-comments@w3.org
Benjamin Nowack wrote:
> Hi,
> 
> ARC uses "${var}" for parameters, a notation that's sometimes
> used in template languages.
> 
> Downside:
>    It requires a grammar tweak.
> 
> Upside: 
>    It separates vars from parameters so that a processor can 
>    detect missing input data, and it opens the door to things
>    like ${var.stripTags()}, ${var.toLowerCase()}, or 
>    ${now().toXSD()}
> 
> Related implementation issue: 
>    How to detect/specify the type of an input parameter, i.e.
>    should &var=foo be handled as <foo>, "foo", or _:foo, or
>    whether there should also be a &var-type=uri|bnode|literal.

Sesame encodes the values in their N-Triples notation, which has
two advantages:

- it seperates URI's, bnodes and literals; no need for something like
   a var-type parameter

- it encodes arbitrary unicode characters to ASCII characters,
   preventing any HTTP character encoding issues

-- 
Arjohn Kampman, Senior Software Engineer
Aduna - Semantic Power
www.aduna-software.com
Received on Tuesday, 10 March 2009 09:16:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 March 2009 09:16:20 GMT