W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2005

Re: [Fwd: SPARQL: Backslashes in string literals]

From: Dan Connolly <connolly@w3.org>
Date: Thu, 04 Aug 2005 09:38:21 -0500
To: andy.seaborne@hp.com
Cc: Dave Beckett <dave.beckett@bristol.ac.uk>, RDF Data Access Working Group <public-rdf-dawg@w3.org>
Message-Id: <1123166301.18971.424.camel@localhost>

On Thu, 2005-08-04 at 14:36 +0100, Seaborne, Andy wrote:
> > Turtle follows N-Triples and picks just uppercase for hex \u & \U
> > escapes (I think there was something in the older charmod drafts about
> > having just one way to encode it).  I'd prefer to follow that [0-9]
> > [A-F].
> Can't find anything in current charmod.

There are several requirements/guidelines near


C042  [S]  Specifications SHOULD NOT invent a new escaping mechanism if
an appropriate one already exists.

and here's one that might bite a little harder:

C046 ... In particular, if a character is acceptable in identifiers and
comments, then its escaped form should also be acceptable.

so charmod says this should work:

 SELECT ?foo\x0045bar WHERE { ?foo\x0045bar dc:title ?xyz }.

This is starting to look like a new issue... I was thinking of
saying this is re-opening punctuationSyntax, but I think it's different.

> Unless there is a single convention that will not catch people out, I prefer to 
> leave both in - it's not clear to me that there is a convention (I write mine in 
> upper case.)

Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Thursday, 4 August 2005 14:38:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:36 UTC