Re: One issue per thread (was: Re: [uf-new] hProduct issues HP1-HP7)
On Sun, Feb 22, 2009 at 6:50 PM, Manu Sporny mspo...@digitalbazaar.com wrote: Could you please explain why it's better to discourage per-issue threads on the mailing list and instead direct people to the wiki? Why are we discouraging one form of recorded communication over another? I have written up a page that explains some of the reasons behind the microformats community's preference for using the wiki instead of email: http://microformats.org/wiki/wiki-better-than-email On Sun, Feb 22, 2009 at 6:50 PM, Manu Sporny mspo...@digitalbazaar.com wrote: Tantek Celik wrote: Please follow-up on the wiki and also one email announcing a batch of new issues is sufficient. Let's try to keep emails to a minimum for notification only, and capture discussion/iteration on the wiki. The reason I put each of these in a separate e-mail is to separate issues out into manage-able threads of discussion. I do admit that it's a personal preference, but threaded discussion seems to be a fairly accepted method of working through spec issues. Email-centric threaded discussion is fairly accepted method in many other standards communities/organizations (W3C, IETF). Per http://microformats.org/wiki/wiki-better-than-email#tradition , this has been different in the microformats community from the start of microformats, and deliberately so. Thanks, Tantek ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
One issue per thread (was: Re: [uf-new] hProduct issues HP1-HP7)
Tantek Celik wrote: Please follow-up on the wiki and also one email announcing a batch of new issues is sufficient. Let's try to keep emails to a minimum for notification only, and capture discussion/iteration on the wiki. The reason I put each of these in a separate e-mail is to separate issues out into manage-able threads of discussion. I do admit that it's a personal preference, but threaded discussion seems to be a fairly accepted method of working through spec issues. I realize that your preference is to edit the wiki and not respond via e-mail, but it's not clear to me how this is a better method of refining these specs, especially when we're just discussing things. I see that the mailing list rules have been updated as a result of my posts: http://microformats.org/wiki/mailing-lists#Avoid_sending_one_message_per_issue_raised Could you please explain why it's better to discourage per-issue threads on the mailing list and instead direct people to the wiki? Why are we discouraging one form of recorded communication over another? -- manu -- Manu Sporny President/CEO - Digital Bazaar, Inc. twitter: http://twitter.com/manusporny ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] hProduct issues HP1-HP7
Thanks Manu for documenting some hProduct issues on the wiki. I have added my comments to each one. http://microformats.org/wiki/hproduct-issues In short I agree that all of the issues raised so far are issues and went further on some of them. Please follow-up on the wiki and also one email announcing a batch of new issues is sufficient. Let's try to keep emails to a minimum for notification only, and capture discussion/iteration on the wiki. Thanks, Tantek ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] hProduct issues HP1-HP7
+ 1 from me on all issues HP1-HP7 To be honest one of the issues highlighted by Manu, the p-v property I don't quite understand ... what does it mean ? the lack of examples and data concerns me too sorry. Thanks Tantek Celik wrote: Thanks Manu for documenting some hProduct issues on the wiki. I have added my comments to each one. http://microformats.org/wiki/hproduct-issues In short I agree that all of the issues raised so far are issues and went further on some of them. Please follow-up on the wiki and also one email announcing a batch of new issues is sufficient. Let's try to keep emails to a minimum for notification only, and capture discussion/iteration on the wiki. Thanks, Tantek ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new -- Martin McEvoy http://weborganics.co.uk/ You may find it hard to swallow the notion that anything as large and apparently inanimate as the Earth is alive. Dr. James Lovelock, The Ages of Gaia ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] hProduct issues HP1-HP7
Great start on a product microformat Paul, Martin McEvoy wrote: + 1 from me on all issues HP1-HP7 To be honest one of the issues highlighted by Manu, the p-v property I don't quite understand ... what does it mean ? the lack of examples and data concerns me too sorry. OK I do understand p-v property - value what I don't understand is how I am supposed to use it?. h5 class=p-vby span class=property artistTenacious D/span/h5 why doesn't this work? h5 class=vcardby span class=fnTenacious D/span/h5 also li class=p-vspan class=propertyReleased/span: span class=valueabbr title=2006-11-14T12:00:01-05:00November 14, 2006/abbr/span/li huh? see: http://microformats.org/wiki/datetime-design-pattern abbr class=released title=2006-11-14T12:00:01-05:00November 14, 2006/abbr looks better? see http://microformats.org/wiki/hproduct#Examples_in_Production for example Also the example is a bit complex how about some minimal markup first? it might help us all get a grip of the basics first. I think a product microformat is a good idea but you have to think a little more micro, which is simple, minimal and only covers the most commonly used properties occurring 80% or more of the time based on solid examples that illustrate your problem precisely. Once you have worked out what that is ask yourself has any of this been done before? no! that doesn't mean with just microformats Manu is the key developer of haudio and ended up finding that what he wanted to do would be much more practical in RDFa it sounds a bit off putting but look elsewhere FIRST ...still not happy then we can talk about a microformat. have a look at http://microformats.org/wiki/principles and http://microformats.org/wiki/process understand them (I'm not saying you don't) they offer some really good guidance on what to do next. Best wishes. -- Martin McEvoy http://weborganics.co.uk/ You may find it hard to swallow the notion that anything as large and apparently inanimate as the Earth is alive. Dr. James Lovelock, The Ages of Gaia ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
