- From: Jeremy Carroll <jeremy@topquadrant.com>
- Date: Wed, 18 Nov 2009 07:08:10 -0800
- To: Sebastian Hellmann <hellmann@informatik.uni-leipzig.de>
- CC: Toby Inkster <tai@g5n.co.uk>, Damian Steer <pldms@mac.com>, semantic-web@w3.org, Michael Martin <martin@informatik.uni-leipzig.de>, Christopher Jona Sahnwaldt <christopher@sahnwaldt.de>, Matthias Weidl <matthias.weidl@googlemail.com>, Anja Jentzsch <anja@anjeve.de>, Richard Cyganiak <richard@cyganiak.de>, Robert Isele <robertisele@gmail.com>
Sebastian Hellmann wrote: >> >> As it happens, some properties containing lots of percent-encoding can >> be represented fine in RDF/XML. e.g. <http://ko.dbpedia.org/property/%EA >> %B4%91%EC%9E%8F> which can be: >> >> <foo:F xmlns:foo="http://ko.dbpedia.org/property/%EA%B4%91%EC%9E%8"> >> >> The problems arise when neither hex digit of the last character is in >> the range A-F. >> This example is flawed. While your RDF/XML parser may read this as you state, such behavior is incorrect. The XML Namespaces rec assigns namespaces prefixes (such as foo above) with IRI references. http://ko.dbpedia.org/property/%EA%B4%91%EC%9E%8 is not an IRI reference. Therefore a very strict XML parser should reject xmlns:foo="http://ko.dbpedia.org/property/%EA%B4%91%EC%9E%8" However, I believe they are explicitly allowed to not check for this (I haven't referred to chapter and verse). But, an argument based on this flawed example is suspect Jeremy
Received on Wednesday, 18 November 2009 15:08:55 UTC