Hi Danny,
I'm not quite sure what point you are making in relation to RDFa, but if you are saying that it will have problems unless it mandates the use of <code>@profile</code>, then I have to disagree.
Since RDFa is based on RDF, then everything is a URI, which means that it is <em>already</em> in the form that you seem to favour.
This means that there is no need to mandate the use of <code>@profile</code>, at least in relation to the question of ambiguity, since RDFa does not have the same problems in this area that microformats does. I explain this in more detail in <a href="http://internet-apps.blogspot.com/2007/12/rdfa-profile-and-following-your-nose.html">RDFa, @profile and following your nose</a>.
Regards,
Mark
--
Mark Birbeck, formsPlayer
mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
http://www.formsPlayer.com | http://internet-apps.blogspot.com
standards. innovation.@en
I'm not quite sure what point you are making in relation to RDFa, but if you are saying that it will have problems unless it mandates the use of <code>@profile</code>, then I have to disagree.
Since RDFa is based on RDF, then everything is a URI, which means that it is <em>already</em> in the form that you seem to favour.
This means that there is no need to mandate the use of <code>@profile</code>, at least in relation to the question of ambiguity, since RDFa does not have the same problems in this area that microformats does. I explain this in more detail in <a href="http://internet-apps.blogspot.com/2007/12/rdfa-profile-and-following-your-nose.html">RDFa, @profile and following your nose</a>.
Regards,
Mark
--
Mark Birbeck, formsPlayer
mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
http://www.formsPlayer.com | http://internet-apps.blogspot.com
standards. innovation.@en