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: Ivan Herman <ivan@w3.org>
Date: Mon, 17 May 2010 14:36:36 +0200
Cc: W3C RDFa WG <public-rdfa-wg@w3.org>
Message-Id: <EB21C6FB-7F5D-4BAB-BCD7-673BFEB872A6@w3.org>
To: Toby Inkster <tai@g5n.co.uk>

On May 17, 2010, at 14:23 , Toby Inkster wrote:

> 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.
> 

That is a good point

I.



> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf







Received on Monday, 17 May 2010 12:36:36 UTC

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