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

Re: full URIs where a CURIE expected?

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 18 Jan 2009 18:52:47 -0500
Message-ID: <4973C0CF.3010505@digitalbazaar.com>
To: RDFa <public-rdf-in-xhtml-tf@w3.org>

Dan Brickley wrote:
> Here's the main markup. The question is whether the 'Bob' section is wrong.
> <div xmlns:foaf="http://xmlns.com/foaf/0.1/">
>    <ul>
>       <li typeof="http://xmlns.com/foaf/0.1/Person">
>         <a property="http://xmlns.com/foaf/0.1/name"
> rel="http://xmlns.com/foaf/0.1/homepage"
> href="http://example.com/bob/">Bob</a>
>       </li>

I believe the 'Bob' section is wrong because, per the spec, you can only
put a CURIE in @typeof and @property. @rel also must be either a
reserved word or a CURIE:


@datatype is also a CURIE-only attribute.

> What's up? If there's a way of squeezing thru the interpretation that
> full URIs are acceptable, this could help with identifying a subset that
> works easily in HTML5.

You could do a pretty nasty hack and do this on the containing DIV:

   <div xmlns:foaf="http://xmlns.com/foaf/0.1/"

...which would generate the triples that you wanted on that page - but
yick, I feel dirty just mentioning that as a possibility.

I think the real solution to the HTML5 prefix-declaration dilemma is to
introduce @prefix instead of @xmlns: as an alternative method of prefix
declaration. My understanding is that the HTML5 folks have an issue with
attribute names containing colons, but no issue with attribute contents
containing colons. So, this:


could also be declared something like this in non-XML family languages:


Do you think that would address the issue, or am I mis-reading something?

-- manu

Manu Sporny
President/CEO - Digital Bazaar, Inc.
blog: Bitmunk 3.1 Website Launch
Received on Sunday, 18 January 2009 23:53:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:00 UTC