[uf-discuss] Custom Fields Microformat?

Aaron Gustafson aaron at easy-designs.net
Sat Nov 25 07:47:55 PST 2006

Manuel Simoni wrote:
> However, following the Microformats process and studying the
> Wordpress, Drupal/Content Construction Kit, Textpattern, and
> Movable Type custom field implementations,  I found that XOXO
> isn't suited to express the current behavior nicely.
> Rewriting the current formats of Wordpress:
> <ul class='post-meta'>
>  <li>
>   <span class='post-meta-key'>Priority: </span>
>   low
>  </li>
> </ul>
> and Drupal/CCK:
> <div class="field field-type-text field-field-priority">
>  <h3 class="field-label">Priority</h3>
>  <div class="field-items">
>   <div class="field-item">low</div>
>  </div>
> </div>
> in XOXO would be a reengineering effort for the affected
> communities, whereas the hcustomfield-* classes are minimally
> invasive: 
> <ul>
>  <li class="hcustomfield">
>   <span class="hcustomfield-name">Priority</span>:
>   <span class="hcustomfield-value">low</span>
>  </li>
> </ul>
> and
> <div class="hcustomfield">
>  <h3 class="hcustomfield-name">Priority</h3>
>  <div>
>   <div class="hcustomfield-value">low</div>
>  </div>
> </div>
> For example, XOXO would force implementors to adapt a list
> structure, which probably is too rigid for them. The
> hcustomfield-* classes let implementors use any layout they
> desire, and my examples show that the use of these three
> simple classes is enough to unify two major existing
> implementations (Wordpress and Drupal).

This is very similar to the property-value pair/group concept[1] we have
floated as part of hProduct.

[1] http://microformats.org/wiki/hproduct-brainstorming#Extensibility

I don't know if you think what we've put together would be applicable (we
were trying to keep it as simple as possible, hence the short names), but I
agree this is something that would be really nice to have and should be an
aspect of microformats, possibly existing as a microformat unto itself which
can be combined with other ones when/where it makes sense to create
subformats specific to a particular use (for instance, wine, televisions,
cars, etc. all have custom fields in the product world, most of which are
consistent within their category and could combine a property-value
construct with a standard hProduct to make a nice subformat -- perhaps a
better approach than the creation of niche microformats like hWine, though
I'm open to argument in the other direction).



Aaron Gustafson
Easy! Designs, LLC

More information about the microformats-discuss mailing list