- From: Steve Harris <steve.harris@garlik.com>
- Date: Wed, 23 Nov 2011 17:44:35 +0000
- To: Gavin Carothers <gavin@carothers.name>
- Cc: Andy Seaborne <andy.seaborne@epimorphics.com>, Richard Cyganiak <richard@cyganiak.de>, RDF-WG <public-rdf-wg@w3.org>
On 2011-11-22, at 21:26, Gavin Carothers wrote: >>> but you don't >>> seem to be arguing that unicode escapes should be allowed in the >>> strings “@prefix” or “@base” or in the rdf:type shortcut “a”. So it's >>> not even that consistent. >> >> I suggested some time ago that Turtle adopt the current SPARQL approach of >> putting unicode escape processing into the input stream. >> > > With both implementer and editor hat on I support using the SPARQL > model for input stream processing of escapes for Turtle. The only > issues I see are for N-Triples, which may resolve escaping another > way. There are also some funky issues with error reporting (as the > parser won't the see the escape sequence but only the character > produced) Yes, the SPARQL model seems more sensible and consistent. - 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 Wednesday, 23 November 2011 17:45:17 UTC