W3C home > Mailing lists > Public > semantic-web@w3.org > November 2009

Re: XML problems with percent encoding

From: Toby Inkster <tai@g5n.co.uk>
Date: Tue, 17 Nov 2009 12:53:49 +0000
To: Damian Steer <pldms@mac.com>
Cc: Sebastian Hellmann <hellmann@informatik.uni-leipzig.de>, 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>
Message-ID: <1258462429.13013.9.camel@ophelia2.g5n.co.uk>
On Tue, 2009-11-17 at 10:13 +0000, Damian Steer wrote:
> RDF/XML remains the only recommended rdf serialisation, but it can't
> serialise every rdf graph.
> Not a happy situation. 

Actually XHTML+RDFa is a W3C Recommendation, with the same (de jure)
status as RDF/XML. It's capable of representing almost every RDF graph.
(With the exception of literals containing certain Unicode control
characters which are completely illegal in XML.)

XHTML+RDFa uses CURIEs rather than QNames. CURIEs are a superset of
QNames and allow a much wider set of characters to be used.

For example, <http://ko.dbpedia.org/property/%EA%B4%91%EC%9E%90> can be
serialised as:

	<div xmlns:dbp-ko="http://dbpedia.org/property/"

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.

Toby A Inkster
Received on Tuesday, 17 November 2009 12:54:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:48:03 UTC