Re: status of non-prefixed values in @rel

Mark, Ben,

this is a reply to this thread, and not this particular mail (that is 
why I removed the body of the mail, but left the subject:-)

First of all, I agree with Manu that we have much more pressing issues 
with RDFa, so we should avoid getting into long discussions. But I also 
saw Shane and Ben's answer on their need for the @rel="next", so Manu's 
proposal may not meet general consensus...:-(

Let us also realize that issue of the @rel="foo", ie, the issue of 
unwanted triples is, in fact, not specific to this case. For any 
namespace that I use, eg, 'foaf', @rel="foaf:foo" might be 'illegal', 
ie, 'unwanted' in the sense that it is not defined by the 'foaf' 
namespace. But it is _not_ the responsibility of RDFa to check those. 
RDFa just blindly generates the triples.

Hence, what I propose is to ignore this problem:-) To be more specific, 
what I propose is that:

1. the ":foo" and "foo" would have the same meaning when used in @rel, 
@rev, (and @property?)
2. They would generate URIs in the http://www.w3.org/1999/xhtml/vocab# 
namespace
3. the RDFa syntax document should _not_ list the allowed property 
values for @rel and @rev (and @property) as it did in earlier 
incarnations; instead, it should refer to the namespace document for 
http://www.w3.org/1999/xhtml/vocab#
4. a namespace document should be set up for 
http://www.w3.org/1999/xhtml/vocab#, listing the values that are defined 
in this namespace. This namespace document is controlled/maintained _by 
the XHTML working group_ which may add new terms sometimes in the future 
(or even remove some). This is _not_ the responsibility of RDFa.

How does that sound?

Ivan


-- 

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