> > > The hCard microformat alone theoretically blocks more than 20 class > > > names > > > > is true only if you qualify it with "when used in the context of an > > element that has the class name of 'vcard'". > > No, and I still hope that the "photo" class example makes that clear. > > No matter if a class name that is claimed by a microformat is already used or > gets introduced in a project, problems arise when the respective element > should be styled differently outside the respective microformat context. An > additional CSS rule already means a "problem" since it could be unnecessary > by design. Current practice thus needlessly influences the "regular" work, > and something like a simple "namespace" could already avoid that. >
In practice, authors can choose selectors that provides a mechanism that works similarly to using namespaces. uf photo: .vcard .photo other photos: .photo So the top level microformat class name can often serve the same purpose as a namespace for the tasks of authoring style sheets. The prescribed microformat properties don't stand alone... nodes can only become microformat properties when the DOM is properly organized. This DOM organization serves as a resolution mechanism for the issues you mentioned. -Ben -Ben _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
