From: Rob V. <rv...@do...> - 2010-04-28 15:57:14
|
Hi Tana Thanks for the feedback This behaviour of the Notation3Writer is by design, while quotes should be escaped in a normal literal e.g. "Normal literal with a \"quote\" in it" They are not required to be escaped in a long literal (though they may be escaped), for example the official test suite for the Turtle syntax (which is a subset of Notation 3) includes a test which uses unescaped quotes in a long literal e.g. """A long literal with unescaped "quotes" is acceptable""" If you are aware of other libraries/parsers which won't properly handle such literals then I would be happy to change this behaviour for future releases. By the way I released version 0.2.2 just over a week ago which contains some minor bug fixes and some major SPARQL optimisations which you might want to upgrade to. Best regards, Rob Vesse ---------------------------------------- From: "Tana Isaac" <Tan...@bb...> Sent: 28 April 2010 13:34 To: dot...@li... Subject: [dotNetRDF-bugs] Notation3Writer not escaping double quotes Hi there, Loving your work :-). Got a problem though using v0.2.1.24471: When a graph contains a literal node that contains double quotes the quotes aren't escaped by the Notation3Writer. E.g. ... graph.CreateLiteralNode("This is some text \"That contains quotes\""); . Outputs """ This is some text "That contains quotes""""; I believe it should output """ This is some text \ "That contains quotes\""""; Cheers, Tana Isaac http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. |