[uf-discuss] Major change to microformat specs without prior
discussion or notification
Scott Reynen
scott at randomchaos.com
Thu Feb 7 10:49:02 PST 2008
On Feb 7, 2008, at 11:08 AM, Manu Sporny wrote:
> It invalidates the need for "mfo" in hcard, doesn't it?
> If it were applied to the rest of Microformats, it would invalidate
> the
> need for "mfo" entirely.
Not exactly. As <hober> said in IRC:
# [02:17:12] <hober> just to quickly clarify, the opacity parsing rule
applies to microformat X with regards to nested instances of X
# [02:17:34] <hober> (as opposed to nested instances of any, even
future, microformat)
That "nested instances of any, even future, microformat" is what MFO
[1] would cover, but probably never will because piecemeal solutions
like this eliminate the various problems MFO would solve all at once.
On the topic of whether this should have had wider discussion, I
thought it was well established long ago that the properties of an
AGENT hCard are not inherited by the container hCard, so I don't see
anything really changing here. Was anyone publishing agent hCards and
expecting the properties to also apply to the container? That seems
very counter-intuitive to me.
[1] http://microformats.org/wiki/mfo
Peace,
Scott
More information about the microformats-discuss
mailing list