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

Re: RDFa review ... too late, but maybe still helpful for the group

From: Mark Birbeck <mark.birbeck@webbackplane.com>
Date: Mon, 13 Oct 2008 05:56:37 +0100
Message-ID: <ed77aa9f0810122156x3713d365i8bc62a5db112e725@mail.gmail.com>
To: "Shane McCarron" <shane@aptest.com>
Cc: "Ben Adida" <ben@adida.net>, "Axel Polleres" <axel.polleres@deri.org>, public-rdf-in-xhtml-tf@w3.org, "Passant, Alexandre" <Alexandre.Passant@deri.org>, "Benjamin Heitmann" <benjamin.heitmann@deri.org>

Hi Shane,

> My comments are in line.  Mark, there is an item in here that we really need
> your input to react to.
> [...]
> "next" is syntactically legal as a CURIE.  However, section 7 says "the
> *mapping to use when there is no prefix* is not defined, which effectively
> prohibits the use of CURIEs that do not contain a colon;"  This means that
> within the context of RDFa+XHTML "next" is NOT permitted.

I would see "next" as a CURIE, in the sense that the CURIE definition
allows predefined tokens to be created, which are parsed before any
other processing happens. Although the RDFa spec isn't actually using
the CURIE spec, we created this space within the CURIE spec for host
languages to define tokens which were substituted _before_ unprefixed
terms are processed. And we do point out that these tokens still need
to map to a URI.

So I would see "next", "prev", "license", etc., as examples of CURIE
tokens that map directly to URIs, rather than going via the prefix/no
prefix rules.

> [...]
>>> == 5.5 Sequence ==
>>>> 9. . the actual literal value is obtained as follows:
>>>> * as a [typed literal] if:
>>>>  * @datatype is present, and does not have an empty value
>>> Note that this condition covers the case @datatype=rdf:XMLLiteral, so it
>>> should be changed to: "does not have an empty value, nor the value
>>> XMLLiteral"
>> I think technically that's covered by the other condition matching, but
>> you're right that this would help clarify things and be more precise.
> This is probably correct, but I am reluctant to make this change without
> Mark's agreement and explicit wording.

Oops...I think Axel is right!

Although we could squirm and say that the section referred to is like
a switch/case, and the best match wins, in many similar cases in the
spec we have a 'first match wins' approach.

In this case it would mean that if an author used
@datatype="rdf:XMLLiteral" explicitly (and there are some use cases
for doing that), the parser wouldn't go through the step "The value of
the XML literal is...".

I've added Axel's suggested wording...thanks Axel.



Mark Birbeck, webBackplane



webBackplane is a trading name of Backplane Ltd. (company number
05972288, registered office: 2nd Floor, 69/85 Tabernacle Street,
London, EC2A 4RR)
Received on Monday, 13 October 2008 04:57:18 UTC

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