On Dec 11, 2006, at 23:42, James Graham wrote:
Those people who really are just using class names as site-specific style hooks must face the possibility that someone will register their "opaque" classname with some unexpected semantics or restrictions on its use and, suddenly, find their previously conformant documents rendered non-conformant
That depends on how conformance is defined.
and open to misinterpretation by any UA which happens to implement some feature based that classname.
On the face of it, it seems to me that problem can be mitigated to an acceptable level by keeping microformats sufficiently complex. How likely is it that a class name constellation that looks like a hCard or a hCalendar appears on a Web page accidentally *and* processing it as a hCard or as a hCalendar (respectively) would cause harm? I think duck typing can go a long way here.
-- Henri Sivonen [EMAIL PROTECTED] http://hsivonen.iki.fi/
