W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > November 2007

Re: References to CSS rules in RDFa syntax document

From: Ivan Herman <ivan@w3.org>
Date: Thu, 01 Nov 2007 12:03:29 +0100
Message-ID: <4729B281.20804@w3.org>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: W3C RDFa task force <public-rdf-in-xhtml-tf@w3.org>

Manu Sporny wrote:
> Mark Birbeck wrote:
>> On the space normalisation, XPath defines the normalize-space()
>> function as follows:
>>   Function: string normalize-space(string?)
>>   The normalize-space function returns the argument string with
>>   whitespace normalized by stripping leading and trailing whitespace
>>   and replacing sequences of whitespace characters by a single space.
>>   Whitespace characters are the same as those allowed by the S
>>   production in XML. If the argument is omitted, it defaults to the context
>>   node converted to a string, in other words the string-value of the
>>   context node.
> +1, this certainly seems like a very clear way to say what we want. This
> processing would be performed for both strings and XMLLiterals, correct?
> In other words, the following XHTML (Test Case #11):
> <div about="">
>    Author: <span property="dc:creator">Albert Einstein</span>
>    <h2 property="dc:title">
>         E = mc<sup>2</sup>: The Most Urgent Problem of Our Time
>    </h2>
> </div>
> Should produce the following triples:
> @prefix _5:
> <http://www.w3.org/2006/07/SWD/RDFa/testsuite/xhtml1-testcases/0011.>.
> @prefix dc: <http://purl.org/dc/elements/1.1/>.
> _5:xhtml dc:creator "Albert Einstein";
>   dc:title """E = mc<sup>2</sup>: The Most Urgent Problem of Our Time"""
>           ^^<http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral>.
>> So I believe we should either refer to these two ideas, or even import
>> the prose as is, if we have to.

Wait, that is a different issue. It is still undecided whether the
canonicalization should apply on XML Literals. Mark's proposal is to use
XPath for the definition of canonicalization, not (yet) on what exactly
it applies to!


> I think we should import the prose as is... it might be annoying for
> implementors to have to refer to other large documents when implementing
> their parser. You had also mentioned that we might not want to refer to
> external documents that could change their processing rules (don't know
> if XPath would ever do this, but we might as well be consistent).
> -- manu


Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf

Received on Thursday, 1 November 2007 11:03:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:25 UTC