Re: [uf-discuss] Fwd: Twitter Is Now Even More Geeky
So yeah, it's hAtom + hCard + XFN. Pretty good, especially since we haven't seen too much hAtom pickup outside of a few WordPress blogs. We've started using hAtom at Nature: http://tinyurl.com/3652ue http://tinyurl.com/2te483 Just a couple of places atm, but more coming. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] hCalendar listings for complex/irregular recurring events
On 11/5/07 19:31, Brian Suda [EMAIL PROTECTED] wrote: --- you should look into RDATE, this allows you to specific only specific dates. The wiki has some information, http://microformats.org/wiki/hcalendar-brainstorming but i think it still needs to be flushed out. Not quite on topic but one thing I'd love to see in any future date pattern: The ability to use the include pattern to include values common to multiple events A lot of the event stuff I mark-up is already partially qualified by a partial datetime: - broadcasts for a year+month+day - episodes for a year+month - posts for a year+month - edits for a year+month+day Would be good if we didn't have to repeat this information all the way down the page http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Fwd: Twitter Is Now Even More Geeky
On May 13, 2007, at 8:16 PM, Kevin Marks wrote: On May 13, 2007, at 7:49 PM, Chris Messina wrote: XFN. All of the side bars use [rel=contact]. -ryan So yeah, it's hAtom + hCard + XFN. Pretty good, especially since we haven't seen too much hAtom pickup outside of a few WordPress blogs. Also rel=me on the URL links in personal pages, which is excellent going in to Internet Identity workshop this week. Cool! Thanks for the input. I've blogged a summary here, since Twitter doesn't seem to have their own link: http://ihack.us/2007/05/14/twitter-gets-microformatted/ I added it to the hCard examples; there isn't an hAtom examples page yet, is there? http://microformats.org/wiki/hcard-examples-in-wild#New_Examples -- Ernie P. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] Receipt Microformat
Looking back in the archive, Martin Owens started a thread about a Receipt Microformat. As stated he had the following format which is a good start. Before I do more research, I wanted to be assured that I wasn't duplicating any efforts. Thanks. -Joe [hReceipt] Transaction ID Order Number Date TotalCost BillingAddress [hCard] Packages [hPackage] [hPackage] DeliveryAddress [hCard] DeliveryCost Purchases [hPurchase] [hPurchase] ProductSku ProductName Cost -Joe ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Receipt Microformat
All discussions about new microformats should be directed to the microformats-new. From there we can further discuss steps, process, etc. thanks, -brian On 5/14/07, Joe Osowski [EMAIL PROTECTED] wrote: Looking back in the archive, Martin Owens started a thread about a Receipt Microformat. As stated he had the following format which is a good start. Before I do more research, I wanted to be assured that I wasn't duplicating any efforts. Thanks. -Joe [hReceipt] Transaction ID Order Number Date TotalCost BillingAddress [hCard] Packages [hPackage] [hPackage] DeliveryAddress [hCard] DeliveryCost Purchases [hPurchase] [hPurchase] ProductSku ProductName Cost -Joe ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss -- brian suda http://suda.co.uk ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] W3HTML WG, HTML5, semantics, and so on
On May 13, 2007, at 3:13 AM, Henri Sivonen wrote: On May 11, 2007, at 3:15 PM, John Allsopp wrote: (abbr pattern problems, Clearly, there's a need for markup for the generic pattern of marking up a triple of data presented to humans, the microformat class and a normalized easy-to-parse representation of the data. HTML5 time addresses only one instance of this pattern. I'm not sure it's clear that we need a general mechanism. AFAIK, the only real problem is with datetime fields. Everything else seems to work pretty well now. The problem with using abbr for this pattern is that title='' is intended to be human-readable and the pattern contaminates abbreviation data, so with microformats abbr is now less useful for e.g. non-microformat-aware but abbr-aware screen readers. The question that needs to be asked is: Will microformat producers and consumers be willing to migrate to a replacement of the abbr pattern if one is provided or will they continue to use abbr anyway for backwards compat? There's no way that we'll get 100% of microformat producers to switch to the new mechanism, but with advocacy we can get a large number to upgrade. If producers switch so will consumers (and I'll put it in the test suite, too :D). For example, should HTML 5 define a uf-data='' attribute as a common attribute such that the value of this attribute would be considered in preference over textContent by microformat consumers? Or should HTML 5 just mitigate the damage to the title attribute by defining a boolean attribute title-is-uf='' for flagging title='' attributes not meant for human consumption? I don't think so. This fails to solve a specific problem (solves a general problem that I'm not sure we need to solve). It also encourages hiding data, which is Not a Good Thing(tm). Is it too late to get rid of this? abbr title='uf data'human data/abbr Like I said, we probably won't be able to upgrade 100% of the data in the wild, so consumers will still have to support it, but we can probably get a lot. Would this be accepted by the uf community? span uf-data='uf data'human data/span Like I said, we should focus on specific problems and solutions, of which time does a great job of solving the the datetime-in-abbr- title issue. If not, would this be backwards-compatible with uf consumers? span title='uf data' title-is-ufhuman data/span Consumers would all have to be updated. So while it's backwards compatible with existing content, it isn't future compatible (if you started publishing this before consumers were updated, your content would not be handled correctly). -ryan ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] W3HTML WG, HTML5, semantics, and so on
Ryan King wrote: I'm not sure it's clear that we need a general mechanism. AFAIK, the only real problem is with datetime fields. Everything else seems to work pretty well now. Geo information is also problematic. For example, should HTML 5 define a uf-data='' attribute as a common attribute such that the value of this attribute would be considered in preference over textContent by microformat consumers? Or should HTML 5 just mitigate the damage to the title attribute by defining a boolean attribute title-is-uf='' for flagging title='' attributes not meant for human consumption? I don't think so. This fails to solve a specific problem (solves a general problem that I'm not sure we need to solve). It also encourages hiding data, which is Not a Good Thing(tm). How would that encourage more hiding data than the current use of title? P -- Patrick H. Lauke __ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __ Co-lead, Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __ Take it to the streets ... join the WaSP Street Team http://streetteam.webstandards.org/ __ ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
