Fair enough. I think I'll go ahead and do some crazy-zaney-stuff and not call it a microformat in the interest of getting something done/to show. Once that's done and the ocean is boiled, then we'll talk. ;)
Seriously though, I think that along the path to a microformat, when one doesn't obviously exist and there aren't enough cowpaths to make it obvious what to pave, we need to start getting into the methodology of explore--then do something--document why--then maybe later if it catches on, codify in a microformat. This is what I recommended with my Community Mark concept, except for an alternative to trademark.' http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Chris On 1/16/06, Tantek Çelik <[EMAIL PROTECTED]> wrote: > I want to first question the need for a separate user profile microformat. > > Use hCard first and then document specific reasons why your particular > real-world application has other real-world needs. > > Without bases in real-world examples and needs, you'll end up with a > kitchen-sink mess format like some other profile formats which shall go > unnamed. > > Thanks, > > Tantek > > _______________________________________________ > microformats-discuss mailing list > [email protected] > http://microformats.org/mailman/listinfo/microformats-discuss > _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
