3 quick questions:
1. how would this work for a tracklist for a radio/tv programme. Like this?:
span class=haudio
span class=fnNagasaki Nightmare/span
span class=albumBest Before 1984/span
span class=contributorCrass/span
/span
span class=haudio
span class=fnThe Classical/span
span
From: Manu Sporny [EMAIL PROTECTED]
Approach #1 ITEM+HAUDIO:
span class=haudio
span class=fn albumAlbum Name/span
span class=contributorArtist Name/span
div class=item haudio
span class=fnA Song/span
abbr class=duration title=P268T4:46/abbr
/span
Please excuse the fmt of this msg. My daughter dropped an oj in my
kybd and so I'm typing this on a loaner blackberry.
The dfn of item in hreview is much looser than it is in
existingpatterns and actually clearly says that in hreviw its one item
but elsewhere it couuld be more than one.
Even if
On Oct 14, 2007, at 9:20 PM, Manu Sporny wrote:
Scott, Andy - do each of you have further thoughts on approach #1
(assuming we can change the definition for ITEM)? Would it be
acceptable
to either of you?
I don't have strong feelings either way on item vs. track.
--
Scott Reynen
Not wanting to add to the confusion but would it not be possible to have
infinitely nested haudios with neither item or track and use mfo when the
markup enforces containment that you don't want to be reflected in the
model?
On 15/10/07 14:11, Scott Reynen [EMAIL PROTECTED] wrote:
On Oct 14,
On Oct 15, 2007, at 7:28 AM, Michael Smethurst wrote:
Not wanting to add to the confusion but would it not be possible to
have
infinitely nested haudios with neither item or track and use mfo
when the
markup enforces containment that you don't want to be reflected in the
model?
As much as
Michael Smethurst wrote:
3 quick questions:
1. how would this work for a tracklist for a radio/tv programme. Like this?:
span class=haudio
span class=fnNagasaki Nightmare/span
span class=albumBest Before 1984/span
span class=contributorCrass/span
/span
span class=haudio
span
Scott Reynen wrote:
Not wanting to add to the confusion but would it not be possible to have
infinitely nested haudios with neither item or track and use mfo when the
markup enforces containment that you don't want to be reflected in the
model?
As much as I'd like to move forward a general
On 15/10/07 15:51, Scott Reynen [EMAIL PROTECTED] wrote:
On Oct 15, 2007, at 7:28 AM, Michael Smethurst wrote:
Not wanting to add to the confusion but would it not be possible to
have
infinitely nested haudios with neither item or track and use mfo
when the
markup enforces containment
From: Manu Sporny [EMAIL PROTECTED]
That is a cut-and-paste problem (exacerbated by everybody else
cutting-and-pasting) and a mis-understanding of how ISO-8601 works,
thanks for the correction, Paul. The corrected value should be:
title=PT268S
OR
title=PT4M46S
That field must follow
The problem:
We need some sort of container to hold track/song information in an
hAudio album. The contents of this container will be another hAudio
chunk or text (which will be the FN of an hAudio object).
There are two proposals that are on the table right now. The end result
and semantics for
On Sun, 2007-10-14 at 16:01 -0400, Manu Sporny wrote:
The problem:
We need some sort of container to hold track/song information in an
hAudio album. The contents of this container will be another hAudio
chunk or text (which will be the FN of an hAudio object).
There are two proposals that
In message [EMAIL PROTECTED],
Scott Reynen [EMAIL PROTECTED] writes
the way Manu phrased this gave me an idea for a third solution to this
problem: use class=haudio alone. Any hAudio without an album
property is already assumed to be a single track. If the only reason
we're specifying
13 matches
Mail list logo
