On 25/06/12 14:05, Martynas Jusevičius wrote:
Thanks, I didn't realize XMLLiterals have to be canonical.
You don't mean XMLLiterals are going away, do you?
Escaped XML would cut off all XML processing tools (I heavily use XSLT
on RDF/XML, for example).
Not going way.
They have a special status in that their lexical form is changed by the
RDF/XML parser to be canonical, they don't behave like normal datatypes.
The RDF/XML behaviour will remain but, for example, Turtle parsers will
not be required to canonicalize.
[[ http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0198.html
RESOLVED: in RDF 1.1: [a] XMLLiterals are optional; [b] lexical space
consists of well-formed XML fragments; [c] the canonical lexical form is
http://www.w3.org/TR/xml-exc-c14n/, as defined in RDF 2004; [d] the
value space consists of (normalized) DOM trees.
]]
and
http://www.w3.org/2011/rdf-wg/track/issues/13
Andy
Martynas
On Mon, Jun 25, 2012 at 2:43 PM, Damian Steer <[email protected]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25/06/12 13:34, Andy Seaborne wrote:
The best RDF-WG is going to do is make XMLLiteral less mandatory.
'Less mandatory'? :-)
I was writing a similar reply as this came in. It's horrible trying to
explain it, and it will be nice not to have to do that post-rdf 1.1.
Damian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/oXQIACgkQAyLCB+mTtymq8wCfW3+7CMm6uHdJhHJ+hbqbWrE3
V/oAoOlmJJfrM1k3brwi1p+j+fswdQrf
=x69P
-----END PGP SIGNATURE-----
