RE: Change in definition of RDF literals

> It seems to say that the lexical form is canonicalized.

Agreed, it does say that.


Clicking through on the issue list from reagle-01 we see
that the assumption that the lexical form is canonical is correct.



http://www.w3.org/2001/sw/RDFCore/20030123-issues/#reagle-01

click on accepted:
http://lists.w3.org/Archives/Public/www-rdf-comments/2003AprJun/0021.html

[[
The RDF Core WG has resolved

http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Apr/0097.html
item 13,
to accept this issue and address it as proposed in
http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Mar/0151.html
]]

In which we read:

syntax:
New text:
[[
The string used as the lexical form of the XML Literal
is the Exclusive XML Canonicalization [XML-XC14N])
with comments and with empty <a href="
http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces
-PrefixList
">
InclusiveNamespaces PrefixList
</a>
of the
literal text l, i.e. the entire element content
of this property element.
]]


concepts
new text:
[[
The lexical space
is the union of the set of all pairs ( string, lang ) and the set of all
strings string,
for which:
+ lang is any language identifier [RFC-3066] normalized to lowercase;
+ string is well-balanced, self-contained XML element content [XML];
+ string is
<a href="
http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-exclusive-canonical
-XML
">
exclusive
Canonical XML </a> (with comments, with empty <a href="
http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces
-PrefixList
">
InclusiveNamespaces PrefixList
</a>);
+ the XML document corresponding to the pair or the string is a well-formed
XML document [XML] that also conforms to XML Namespaces [XML-NS].
]]

Received on Thursday, 15 May 2003 03:49:49 UTC