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

Re: CURIE objections in HTML5+RDFa (was: Re: RDFa and Web Directions North 2009)

From: Elias Torres <elias@torrez.us>
Date: Wed, 18 Feb 2009 10:38:58 -0500
Message-ID: <c2f4700902180738l404bf347v9856aab40b324785@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: Manu Sporny <msporny@digitalbazaar.com>, Sam Ruby <rubys@intertwingly.net>, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>, Dan Connolly <connolly@w3.org>, Ian Hickson <ian@hixie.ch>
On Wed, Feb 18, 2009 at 7:55 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
> On Feb 17, 2009, at 05:40, Manu Sporny wrote:
>> The front-runner for how we address the xmlns: issue seems to be
>> @prefix. I believe using @prefix to specify CURIE prefixes will address
>> all of your concerns with XHTML/HTML DOM incompatibilities. Please
>> confirm or reject this assertion (and be specific about what you
>> do/don't like about @prefix).
> If @prefix were used as the only mechanism for defining CURIE prefixes (that
> is, xmlns:foo would no longer be used), it would address all my XHTML/HTML
> API consistency concerns. However, it would not address my concerns about
> prefix-based indirection in general.
> What I like about @prefix is that the attribute would result in the ["",
> "prefix"] namespace,local pair in both Namespace-aware XML parsing as in
> HTML parsing. More on what I don't like about it below.

Can we please pause the great discussion for a moment and note the
places where we have made progress and place some markers to avoid

I have been watching the discussion from a distance and although come
from a practical perspective like Ben/Mark that we are (for now) able
to parse RDFa today with JavaScript using DOM-level APIs, I was
finally able to appreciate Henri's concern regarding the use of xmlns
in HTML5 for RDFa. In fact, I dealt with this to some extent when
helping Ivan make his XML-based python parser support HTML/x by making
use of html5lib's APIs. I'm also very impressed with Ian's arguments
for improving our use cases and clearly outlining our objectives. I'm
guilty of sometimes thinking that RDFa is wonderful because it's
structured metadata, but fail to justify it.

I think it's clearly from most of the folks involved with RDFa that
we're not at all against using @prefix if it let's us cross this
bridge and it seems that we have two emails from Henri showing
acceptance of something @prefix-like. This is a place where we should
focus some energy until we have clearly definable todos moving

My $0.02.

Received on Wednesday, 18 February 2009 15:39:34 UTC

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