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

Re: On ISSUE-6 (invalid values in @datatypes cause plain literals to be generated)

From: Toby Inkster <tai@g5n.co.uk>
Date: Mon, 17 May 2010 13:23:49 +0100
To: Ivan Herman <ivan@w3.org>
Cc: W3C RDFa WG <public-rdfa-wg@w3.org>
Message-ID: <20100517132349.2d2e1e35@miranda.g5n.co.uk>
On Mon, 17 May 2010 13:31:46 +0200
Ivan Herman <ivan@w3.org> wrote:

> So, in mind mind, the question does not arise in these terms but
> rather: what is the specific problem that forces us to artificially
> disallow relative URI-s? 
> Note that the frequent usage for attribute values is something like
> @datatype="blabla"
> which will NOT be a relative URI, but will be interpreted (if
> possible) as a term.

This is precisely the specific problem that should force us to disallow
relative URIs. If people think they can use relative URIs, they'll use
things like datatype="foo.html", but that will be interpreted as a
term, as "." is allowed in NCNames. The rules on when something is
interpreted as a relative URI reference and when it's interpreted as a
token would be confusing to authors.

Toby A Inkster

Received on Monday, 17 May 2010 12:25:37 UTC

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