Re: status of non-prefixed values in @rel

Ben Adida wrote:
> 
> I still think the right solution is to generate nothing when it's not a
> reserved word, *because* of HTML existing use, and I just don't see why
> that's so difficult.
>

Ben,

I think the issue is how to control that. If we add a finite set of 
'allowed' values into the RDFa document, this list will become outdated 
at the moment when the XHTML group decides to add new values to their 
list of @rel. (And you are right, new, registered profiles might even 
add values to the namespace in some way.)

That is why I proposed not to add a specific set into the RDFa document, 
refer to the general mechanism, and just generate whatever is there...

(I do not feel strongly about it, and I see the caveats. But I try to 
find the easiest and quickest way of moving forward...)

Ivan




> Mark, you said:
> 
>> I think everyone generally agreed with the 'preprocessor'
>> approach, but since no-one ever wrote that up in any meaningful way,
>> it meant that it was pretty academic.
> 
> I wrote it up and had it working quite well a while ago in my parser. I
> temporarily disabled it while we figured out this issue. I'll reenable
> the code and show you how it works later today. It's really quite
> simple: ignore all values without a ":", and run a pre-processor to
> update the DOM with the xh: prefix on reserved values.
> 
> -Ben

-- 

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