Hello, With the recent discussion on RDF/LD patching I looked on the SPARUL [1] & Turtle [2] specs and was surprised to notice that they are not 100% compatible.
The difference I found was in the escaping of literal values where, in turtle we are allowed to have unicode escaping while in SPARUL we are not Turtle [26]UCHAR::='\u' HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> | '\U' HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> HEX <http://www.w3.org/TR/turtle/#grammar-production-HEX> This means we cannot just reuse turtle blocks inside insert/delete SPARUL blocks without pre-processing. Am I correct or did I overlook something? In addition, does the aforementioned rule add anything in turtle besides extra serialization options? Best, Dimitris [1] http://www.w3.org/TR/sparql11-query/#rSTRING_LITERAL1 [2] http://www.w3.org/TR/turtle/#grammar-production-STRING_LITERAL_QUOTE -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas
