[uf-new] Issue HP6 - P-V seems like a catch-all for hProduct
msporny at digitalbazaar.com
Tue Feb 17 22:12:54 PST 2009
hProduct currently allows the author to use the P-V pattern for anything
that doesn't fit neatly into hProduct. While it is true that this is a
nice way to expand hProduct and see where future versions of hProduct
might need to be expanded, there is a danger that over-use of the P-V
pattern will result in weird issues between future Microformats.
For example, if hProduct lists a number of P-Vs and another Microformat
starts using P-V heavily, there will be clashes between the overlapping
Microformats. These clashes will result in the wrong P-Vs being assigned
to the wrong object.
It also seems a bit sloppy - using P-V may be a clear sign that the
problem being solved isn't small enough, or that you're attempting to
boil the oceans in a clever way. Anybody else have some thoughts about
the use or abuse of P-V in Microformats?
President/CEO - Digital Bazaar, Inc.
blog: Scaling Past 100,000 Concurrent Web Service Requests
More information about the microformats-new