Aloha Andy, et al,
Use cases for alternates could be as follows:
1. Amazon.com page on a book with alternate versions, e.g.,
http://www.amazon.com/gp/product/0789723107/ref=cm_cr_pr_orig_subj
2. TED.com talks, which include links to mp4, zipped mp4 and itunes,
e.g.,
Cc-ing (hopefully) interested bbc parties
Hello Andy
Long time no hear
On 12/12/07 19:02, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Michael
Smethurst [EMAIL PROTECTED] writes
Just to say that hCalendar is used fairly extensively to describe
broadcasts on
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Michael
Smethurst [EMAIL PROTECTED] writes
Just to say that hCalendar is used fairly extensively to describe
broadcasts on bbc.co.uk/programmes here:
http://www.bbc.co.uk/programmes/genres/music
Robert O'Rourke wrote:
I know it defeats the object semantically speaking but what are the
other arguments against putting the machine-readable date/time in the
class attribute and do they outweigh the gain in accessibility?
For example, what's wrong with this:
abbr
Hello Microformaters,
* A user-agent could at the least identify one or more alternate
formats for the current item or a linked item.
* It could also identify the order of preference of alternates.
* This could be used by microformat-aware search to provide search
result links to alternates.
*
On Thu, December 13, 2007 09:27, Jeff McNeill wrote:
Use cases for alternates could be as follows:
[...]
Thank you. That explains what alternates are; but not how the proposed
microformat would be /used/. In other words, what would a user agent *do*
with them?
--
Andy Mabbett
** via webmail
Andy Mabbett wrote:
On Thu, December 13, 2007 09:27, Jeff McNeill wrote:
Use cases for alternates could be as follows:
[...]
Thank you. That explains what alternates are; but not how the proposed
microformat would be /used/. In other words, what would a user agent *do*
with them?
Benjamin Hawkes-Lewis wrote:
Robert O'Rourke wrote:
I know it defeats the object semantically speaking but what are the
other arguments against putting the machine-readable date/time in the
class attribute and do they outweigh the gain in accessibility?
For example, what's wrong with this:
On Dec 13, 2007 12:44 PM, Robert O'Rourke [EMAIL PROTECTED] wrote:
Perhaps in the case of a podcast or video blog you could tell your
feed-reader what format you prefer and it would grab the right file.
That's one possibility but I don't know of anyone who does
podcasts/video blogs in
On Thu, December 13, 2007 12:44 pm, Robert O'Rourke wrote:
Perhaps in the case of a podcast or video blog you could tell your
feed-reader what format you prefer and it would grab the right file.
That's one possibility but I don't know of anyone who does
podcasts/video blogs in multiple
Aloha,
Interesting that alternates was brainstormed in terms of hItem as
mentioned previously in the thread, but also could and perhaps should
initially apply to citation. If I understand the citation discussion
at http://microformats.org/wiki/citation-irc-notes-2006-04-09#Summary
an alternate
11 matches
Mail list logo
