From lists at ben-ward.co.uk Mon Jul 7 09:37:48 2008 From: lists at ben-ward.co.uk (Ben Ward) Date: Mon Jul 7 09:37:58 2008 Subject: [uf-new] Re: Reviving hProduct In-Reply-To: References: Message-ID: Hi Jay, On 7 Jul 2008, at 17:11, Jay Myers wrote: > All, > > It seems like the hProduct microformat hasn't seen a lot of > revisions since it's initial brainstorming in 2006 (feel free to > correct me on this if there are current efforts taking place :-) ). > I'm attempting to revise the schema for use in an upcoming August / > September project release. I have taken the current brainstorming > schema and added on some new items. I would like to open this up to > discussion and move this format forward, and any assistance the > community would be able to provide would be helpful. It's great that you're keen to take a lead on further brainstorming. Please conduct work on new microformats on the [uf-new] mailing list, rather than discuss. Thanks! > Altered schema: http://jay.beweep.com/hproduct/hproduct-schema.txt > Unstyled HTML example: http://jay.beweep.com/hproduct/hproduct-example.html The old product brainstorm is discarded, so please edit the wiki. Either start a fresh brainstorm section on the current page, or work with the existing text. > The altered schema: For reference, much of the schema you describe there has been rolled into hListing, which whilst also technically a proposal, is more mature and has been implemented successfully by a number of people. That covers the price/merchant side of things. The documentation for listing, and interating on it to reach draft also needs doing, I apologise for not following through my intent to take a lead on that. Lots of other ?f things have come up that always seem more urgent. I'd suggest that product-specific fields focus on the product _item_, e.g. where you have .hListing > .item, or .hReview > .item, you could insert an ?hProduct? there, enhancing the semantics, and achieving listing products with prices through the formats being used in combination. Regards, Ben (This post has been cross-posted to ?f-new. Please reply *only* to ?f- new) From hayes at appozite.com Mon Jul 7 10:37:12 2008 From: hayes at appozite.com (Hayes Davis) Date: Mon Jul 7 10:37:14 2008 Subject: [uf-new] Re: Reviving hProduct In-Reply-To: References: Message-ID: I apologize for the cross-posting, but Ben moved this thread to new right as I was hitting send apparently. In the interest of collecting the discussion on this topic all in one place, here's what I said on discuss: I'm glad to see someone else showing an interest in this. I'd love to see a product microformat revived as well for an application I'm working on. We might want to move this discussion to microformats-dev but I'm not sure... Anyway, some comments on your proposed changes: 1) The rel="product". Does that really describe the relationship between this instance/description of the product and the product page? I'm not sure it does. I get what you're saying though, I think, which is that this is the "canonical product page". 2) I think the change from an msrp attribute described on the wiki to a "price" attribute makes sense. I'm not sure about including "savings" in there. It's not technically the price of the item. It's more of an "adjustment". 3) What would you see as a value for the availability? I see in your example this is a text description of how the user can acquire it (e.g. "in store pickup"). When I initially read that attribute, it made me think more of an inventory quantity. Might there need to be an attribute for that as well? 4) As for the URL, I would think that might be better represented as a rel "purchase" value indicating that the target URI is for purchasing this item. Hayes From jmyers at visi.com Mon Jul 21 07:20:53 2008 From: jmyers at visi.com (Jay Myers) Date: Mon Jul 21 07:21:05 2008 Subject: [uf-new] Reviving hProduct Message-ID: From jmyers at visi.com Mon Jul 21 07:43:57 2008 From: jmyers at visi.com (Jay Myers) Date: Mon Jul 21 07:44:04 2008 Subject: [uf-new] Reviving hProduct In-Reply-To: References: Message-ID: From schechter at google.com Tue Jul 29 16:54:20 2008 From: schechter at google.com (Greg Schechter) Date: Tue Jul 29 16:54:28 2008 Subject: [uf-new] Microformats on YouTube Message-ID: Hi All, I'm an engineer at YouTube and we would like to add microformats to our site. I was wondering if I could get some suggestions on the best way to go about adding microformats to our site. I'm very new to the idea of microformats, so any suggestions on what we should be putting into the site would be very helpful. Thanks Greg Schechter From csarven at gmail.com Tue Jul 29 17:52:34 2008 From: csarven at gmail.com (Sarven Capadisli) Date: Tue Jul 29 17:52:38 2008 Subject: [uf-new] Microformats on YouTube In-Reply-To: References: Message-ID: On Tue, Jul 29, 2008 at 6:54 PM, Greg Schechter wrote: > Hi All, > I'm an engineer at YouTube and we would like to add microformats to > our site. I was wondering if I could get some suggestions on the best > way to go about adding microformats to our site. I'm very new to the > idea of microformats, so any suggestions on what we should be putting > into the site would be very helpful. Hi Greg, For: http://youtube.com/watch?v=Nz3lXu3VxVg * Related Videos, Text Comments and Promoted Videos should be a list (ul, ol). Assign XOXO to root ul, ol. [1] * hAtom for "Write here, right now" video, and each Related Videos, Text Comments, Promoted Videos. [2] * hCards for every username. [3] * On "previous" and "next" anchors, assign rel-prev and rel-next. [4] * Use
for the YouTube logo. Assign hCard, rel-home, rel-me, rel-bookmark, rel-note as well. [4] * You can use these concepts on other pages as well. Like the user profile can contain the vCard of the user. [1] http://microformats.org/wiki/xoxo [2] http://microformats.org/wiki/hAtom [3] http://microformats.org/wiki/hCard [4] http://microformats.org/wiki/existing-rel-values That would be a good start IMO. Sarven Capadisli http://www.csarven.ca From brian.suda at gmail.com Wed Jul 30 01:24:48 2008 From: brian.suda at gmail.com (Brian Suda) Date: Wed Jul 30 01:24:56 2008 Subject: [uf-new] Microformats on YouTube In-Reply-To: References: Message-ID: <21e770780807300124ka78229cwaf2a6a67d2f0ab89@mail.gmail.com> 2008/7/29, Greg Schechter : > Hi All, > I'm an engineer at YouTube and we would like to add microformats to > our site. I was wondering if I could get some suggestions on the best > way to go about adding microformats to our site. I'm very new to the > idea of microformats, so any suggestions on what we should be putting > into the site would be very helpful. --- Microformats are about adding more semantic meaning into the mark-up. Before microformats there is POSH (plain-old semantic HTML). POSH does not have any sort of specs for specific formats, but instead champions the use of the basic HTML elements that already exist. Such as using a

when you have paragraph text rather than a

or other elements. Along with using semantic elements, you can just choose semantic class values to further extend meaning, such as adding a class="favorite" to the favorite button, etc. Having a quick peek under the hood at the youtube HTML, there are lots of possibilities for both POSH and microformats. It would add meaning to the HTML and possibly shave-off a few KB from all the nested s and
s If you have any questions, feel free to post them to this discussion list and as a community we can help you move things forward. Thanks, -brian -- brian suda http://suda.co.uk From mail at tobyinkster.co.uk Thu Jul 31 15:25:12 2008 From: mail at tobyinkster.co.uk (Toby A Inkster) Date: Thu Jul 31 15:25:42 2008 Subject: [uf-new] hAudio - "sample" propagation from child to parent Message-ID: <3DEE511D-7935-4E79-8536-F40EB40DCE1A@tobyinkster.co.uk> The hAudio draft includes a section called Parser Processing Notes which includes the note that: > When processing the ITEM element, none of the properties of the > child hAudio should be pulled into the parent hAudio. I have a suggestion that the "sample" property be made an exception and that the spec suggest that parsers *MAY* propagate the sample property from children to the parent. This is because a sample of music from a track on an album may surely also be taken to be a sample of the album. I've run this past Manu (who's offline for a week or so) and he seems broadly in favour of it, so long as it doesn't introduce any extra burden on parsers or publishers. (And by making it a "may" rather than a "should" or "must", it shouldn't.) He suggested that I raise the issue here in case anyone else has any ideas against or in favour. -- Toby A Inkster