- From: Steve Harris <steve.harris@garlik.com>
- Date: Thu, 31 Mar 2011 10:20:23 +0100
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
Yes, but isn't that what SPARQL 1.0 specifies now?
STRING_LITERAL_LONG2 ::= '"""' ( ( '"' | '""' )? ( [^"\] | ECHAR ) )* '"""'
ECHAR ::= '\' [tbnrf\"']
I don't see any mention of normalising whitespace, but grammars really aren't my thing.
<rdf-wg> I'll add it to list of Turtle open questions though </rdf-wg>
- Steve
On 2011-03-31, at 10:11, Andy Seaborne wrote:
> I meant to send this to RDF-WG - autocomplete failure - . My apologies.
> It is also relevant to SPARQL though:
>
> { :x :p """
> abc
> """ }
>
> will match only if the line-end conventions are the same between data originating environment and query-writing environment.
>
> Andy
>
>
> On 31/03/11 09:53, Steve Harris wrote:
>> Hm, I don't understand, surely it should be whatever UTF-8 data appears between the """s? If the file has UNIX style line endings you'll get \n, otherwise \r\n, or \r as apprpriate.
>>
>> This is especially relevant if you're trying to store e.g. HTTP headers, which are sensitive to the terminating line characters.
>>
>> - Steve
--
Steve Harris, CTO, Garlik Limited
1-3 Halford Road, Richmond, TW10 6AW, UK
+44 20 8439 8203 http://www.garlik.com/
Registered in England and Wales 535 7233 VAT # 849 0517 11
Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Thursday, 31 March 2011 09:20:58 UTC