[uf-discuss] Re: New Wiki Page: widget-brainstorming

[Kevin Lawver]

Mark,
	We didn't do a very good job at looking at existing microformats for 
the relevant pieces we could re-use (because no format really exists for 
"widgets"), but we plan on it.  Your point about hCard is excellent. 
The author info should probably just BE an hCard.  Good point on 
camelCase as well.  We'll look at switching them.
	Is word-word the preferred format for classes in microformats? 
Personally, I usually use camelCase, but if there's already a 
convention, we'll stick to that.

Thanks for the feedback!

Kevin
http://lawver.net

Mark Pilgrim wrote:
> On 10/28/05, Shawn Carnell <ShawnCarnell at aol.com> wrote:
> 
>> I'm one of Kevin's colleagues.  He's out today but i wanted to let you know
>>that we've posted our widget specification proposal.  You can find it at
>>http://dev.lawver.net/modulet/profile/.  I've also placed a
> 
> 
> Some quick thoughts:
> 
> - You create rel="mail" and rel="author" for author information.  Why
> not reuse hCard?
> - You create rel="documentation".  Why not reuse rel="help" (one of
> the link types defined in HTML:
> http://www.w3.org/TR/html4/types.html#type-links )
> - re: defaultWidth, minimumWidth, and allowMultiple.  Please don't
> define camelCase attribute names.  I can tell you from bitter
> experience working with syndicated feeds that it never lasts; you'll
> end up with defaultwidth and minimumwidth in the wild within weeks, if
> not days.  hCard uses "organization-name" and "organization-unit" for
> class names that simply must be multiple words.  See
> http://microformats.org/wiki/hcard-examples#3.5.5_ORG_Type_Definition
> for example.
> 
> --
> Cheers,
> -Mark
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>