Manu Sporny wrote:
The following hAudio issues have been resolved with the latest update to
the hAudio proposal (hAudio v0.8). If there are no objections, I'd like
to mark all of them as resolved.
Seeing no objections, issues 2, 9, 10, 11 and 13 have been resolved.
-- manu
--
Manu Sporny
On Sat, 2007-11-03 at 11:42 -0400, Manu Sporny wrote:
The hAudio Draft Specification has a new home:
http://microformats.org/wiki/haudio
Well done all Thanks Manu
the:
http://microformats.org/wiki/haudio-cheatsheet
Has been updated to the hAudio 0.8 Draft
For testing purposes
On Sat, 2007-11-03 at 11:42 -0400, Manu Sporny wrote:
The hAudio Draft Specification has a new home:
http://microformats.org/wiki/haudio
Just some minor points
1,
http://microformats.org/wiki/haudio#Price
span class=price
should this not be...
span class=money ?
as per the Currency
On 4 Nov 2007, at 00:53, Martin McEvoy wrote:
1,
http://microformats.org/wiki/haudio#Price
span class=price
should this not be...
span class=money ?
as per the Currency Proposal
http://microformats.org/wiki/currency-proposal
No. Should the currency microformat be completed, then that class
at the moment.
• All uses of the ABBR pattern for dates and times should use
hyphenated separators. We're still in an accessibility grey spot with
regards to the whole thing, but it was noted that splitting dates
with hyphens made it acceptable in some cases (2007-11-03 over
20071103). I
On 3 Nov 2007, at 15:42, Manu Sporny wrote:
The hAudio Draft Specification has a new home:
http://microformats.org/wiki/haudio
Contributor:
“The contents of the element should include a valid hCard
Microformat.”
Results in:
span class=contributorspan class=vcard
This is different
I think hAudio would be clearer to adopt the same pattern, so the
second (album) snippet would become:
div class=haudio
span class=fn albumIn Rainbows/span
/div
I second that. Makes more sense, is more consistent. Also makes it
easier to write a definition for Operator :D
On Sun, 2007-11-04 at 02:08 +, Martin McEvoy wrote:
On Sun, 2007-11-04 at 02:00 +, Julian Stahnke wrote:
I think hAudio would be clearer to adopt the same pattern, so the
second (album) snippet would become:
div class=haudio
span class=fn albumIn Rainbows/span
/div
and can also be expressed as ?
div class=haudio
span class=fnIn Rainbows/span
/div
No, that’d be a track.
___
microformats-new mailing list
microformats-new@microformats.org
http://microformats.org/mailman/listinfo/microformats-new
• All uses of the ABBR pattern for dates and times should use
hyphenated separators. We're still in an accessibility grey spot with
regards to the whole thing, but it was noted that splitting dates
with hyphens made it acceptable in some cases (2007-11-03 over
20071103). I
On Sun, 2007-11-04 at 02:49 +, Julian Stahnke wrote:
and can also be expressed as ?
div class=haudio
span class=fnIn Rainbows/span
/div
No, that’d be a track.
Are you sure?
http://microformats.org/wiki/audio-info-proposal#Multi-part_Podcast_Example
something else that need
On Sat, 2007-11-03 at 21:09 -0600, Scott Reynen wrote:
...It may be a track, or an album, or
something else entirely, but there's not enough information in the
markup to determine anything more than it's an audio recording.
A good description maybe this can be added to the wiki?
Thanks
On Sat, 2007-11-03 at 21:09 -0600, Scott Reynen wrote:
On Nov 3, 2007, at 8:49 PM, Julian Stahnke wrote:
div class=haudio
span class=fnIn Rainbows/span
/div
No, that’d be a track.
That would be an audio recording. It may be a track, or an album, or
something else entirely,
Scott
You were a solid supporter of using audio-title and helped make the
decision NOT to use FN
...We can't both re-use property names and ignore
the context of those property names. My dog's FN is not my FN, and
if the only way for me to make that clear is to use class=pet-name
instead
On Nov 3, 2007, at 10:14 PM, Martin McEvoy wrote:
You were a solid supporter of using audio-title and helped make the
decision NOT to use FN
That's not true. I think you have the order of events confused.
...We can't both re-use property names and ignore
the context of those property
15 matches
Mail list logo
