W3C home > Mailing lists > Public > www-archive@w3.org > July 2007

Re: microformats, profiles, and taking back rel/class names [standardizedFieldValues-51]

From: Harry Halpin <hhalpin@ibiblio.org>
Date: Wed, 18 Jul 2007 15:13:49 -0400
Message-ID: <469E666D.2010802@ibiblio.org>
To: Mark Baker <distobj@acm.org>
Cc: www-archive@w3.org


Mark Baker wrote:
> Taken to www-archive, as this response would just be repeating what
> I've already said on www-tag.
That's fine, and thanks for talking this through.

[snip]
>>
>> In that regard, why not make @class do the "Right Thing" instead of
>> inventing @class2?
>
> Because of the backwards compatibility reasons I've given, and the
> problems it would create for already deployed software.
But, if no one is using @profile in combination with class since it's
undefined, why not define it as something like namespacing the class
element? Or, for that matter, div and span elements? Especially as that
would be compatible with mixing and matching current microformats?

I'm not the only one whose thinking this way - Ryan King from Technorati
had this conversation with me where we thought this might be a sensible
way to address the @profile/head issue.


> Mark.


-- 
		-harry

Harry Halpin,  University of Edinburgh 
http://www.ibiblio.org/hhalpin 6B522426
Received on Wednesday, 18 July 2007 19:14:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:07 GMT