W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > May 2010

Re: RDFa WG telecon minutes for 2010-05-13

From: Ben Adida <ben@adida.net>
Date: Fri, 14 May 2010 15:32:01 -0700
Message-ID: <4BEDCF61.2030807@adida.net>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: RDFa WG <public-rdfa-wg@w3.org>
On 5/13/10 9:07 AM, Manu Sporny wrote:
> NOTE: RDFa WG Members - there were a number of resolutions today
> concerning backwards-incompatible changes.

On the resolutions covered in the telecon:

plain literals: +1
host language for @lang: +1

The other two issues could be problematic, although maybe all that's 
needed is a bit more specificity on error handling.

"When both lang and xml:lang are specified on the same element, they 
MUST have the same value"

I don't think we can *will* the markup to be the way we want it to be. 
If both @lang and @xml:lang have the same value, then that line in the 
spec is superfluous. If they have different values, then the spec is 
unhelpful in resolving the conflict. I would propose that, instead of 
this resolution, we specify what happens when both are defined to be 
different values. Does the parser blow up? Do we give priority to one of 
them? Do we ignore both?

"For prefixes defined via xmlns: and @prefix, the prefix text should be 
converted to lowercase by the RDFa Processor."

So what happens in the following case:

<div xmlns:foo="http://a.com" xmlns:Foo="http://b.com">

Clearly one of these @xmlns will override the other, but which one? Is 
it alphabetical? I don't think we've ever defined an order for handling 
these @xmlns attributes, have we?

It probably gets more complicated with @prefix:

<div prefix="foo: http://a.com Foo: http://b.com">

Which one takes precedence here?

Received on Friday, 14 May 2010 22:32:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:47 UTC