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

Re: Undeclared prefix in @datatype -- what happens?

From: Richard Cyganiak <richard@cyganiak.de>
Date: Thu, 27 Aug 2009 20:22:09 +0100
Cc: Damian Steer <pldms@mac.com>, RDFa <public-rdf-in-xhtml-tf@w3.org>
Message-Id: <04029715-0C0F-4FCE-BE47-183A1C56FDFA@cyganiak.de>
To: Toby Inkster <tai@g5n.co.uk>
On 27 Aug 2009, at 19:09, Toby Inkster wrote:
> The spec doesn't specify this. If there were a definitive answer, it  
> would be step #9 in the processing sequence.

Ok. Thanks Toby. Not the answer I was hoping for, but anyway ...

> My vote, if this were to be written up as an errata, would be to  
> specify that if @datatype is non-empty but does not contain a valid  
> CURIE,

(Well, it's a syntactically valid CURIE, it just uses an undeclared  
prefix.)

> to treat it as datatype="" - i.e. the value of the attribute is  
> ignored but the presence of the attribute is not ignored. This would  
> be consistent with non-CURIE rel, rev, typeof, etc.

Sounds reasonable to me.

 From practical experience it seems to me that missing namespace  
prefixes are one of the most common authoring errors -- so it would be  
good if different parsers did the same thing in that case.

Thanks again,
Richard



>
> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
>
>
>
Received on Thursday, 27 August 2009 19:22:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 27 August 2009 19:22:54 GMT