rel-enclosure was ruled out because it's not always a download, but
sometimes a way to purchase, right? What if hAudio suggested the use
of rel-enclosure for downloads and rel-payment for ways to purchase?
--
Chris Griego
On 5/8/07, Manu Sporny [EMAIL PROTECTED] wrote:
Martin McEvoy wrote:
Hey All! This is my first posting to this group, so please let me know if
I'm overstepping my bounds.
I realize that the audio-info-proposal is still being flushed out, but the
description of Aquire clearly states that this is the full-version of the
audio recording. I'm making an assumption
Manu Sporny wrote:
- The use of 'fn' instead of 'work-title'.
It has been proposed that 'fn' or 'n' be used instead of 'work-title',
or 'title'. What follows is an argument against using 'fn' and 'n' for
hAudio.
Assumptions:
- It is important that we choose the generic names that span all
On May 8, 2007, at 10:22 AM, Chris Griego wrote:
rel-enclosure was ruled out because it's not always a download, but
sometimes a way to purchase, right? What if hAudio suggested the use
of rel-enclosure for downloads and rel-payment for ways to purchase?
I think this is an excellent idea. In
On 5/8/07, Manu Sporny [EMAIL PROTECTED] wrote:
Manu Sporny wrote:
- The use of 'fn' instead of 'work-title'.
It has been proposed that 'fn' or 'n' be used instead of 'work-title',
or 'title'. What follows is an argument against using 'fn' and 'n' for
hAudio.
Assumptions:
- It is important
On May 8, 2007, at 10:22 AM, Brad Hafichuk wrote:
As a runner-up, source seems to be acceptable, as we're used to
using src for image (and embeded) media.
SOURCE is already a property in vCard [1], though it's not currently
used in hCard. In vCard, it's the source of the *information* in
On Tue, 2007-05-08 at 09:53 -0400, Manu Sporny wrote:
Martin McEvoy wrote:
-
acquire
Changed to be a class instead of a rel-attribute. There is still some
concern over the name 'acquire'. Primarily in that it doesn't
On 5/8/07 8:36 AM, Manu Sporny [EMAIL PROTECTED] wrote:
fn is short for 'full-name'
Not quite. In short, fn is short for formatted name.
and is grounded in the VCARD/hCard format.
Yes, and per http://www.ietf.org/rfc/rfc2426.txt section 3.1.1:
the formatted text corresponding to the name
Brian Suda wrote:
None of this applies to hAudio - and we don't want Microformat
implementors confusing how to use 'fn' in hAudio and how to use 'fn' in
hCard.
--- these are two very different things. This is a non-issue. hCard
parsers do onething, and you can defined Media parsers to do
Tantek Çelik wrote:
On 5/8/07 8:36 AM, Manu Sporny [EMAIL PROTECTED] wrote:
fn is short for 'full-name'
Not quite. In short, fn is short for formatted name.
and is grounded in the VCARD/hCard format.
Yes, and per http://www.ietf.org/rfc/rfc2426.txt section 3.1.1:
the formatted text
On May 8, 2007, at 2:20 PM, Manu Sporny wrote:
Brian Suda wrote:
None of this applies to hAudio - and we don't want Microformat
implementors confusing how to use 'fn' in hAudio and how to use
'fn' in
hCard.
--- these are two very different things. This is a non-issue. hCard
parsers do
Scott's argument was the final nail in the 'work-title' coffin. Work
title has been changed to 'fn' and is reflected on the wiki:
http://microformats.org/wiki/audio-info-proposal#Schema
http://microformats.org/wiki/audio-info-proposal#Formatted_Name
-- manu
In message [EMAIL PROTECTED],
Scott Reynen [EMAIL PROTECTED] writes
On May 8, 2007, at 10:22 AM, Chris Griego wrote:
rel-enclosure was ruled out because it's not always a download, but
sometimes a way to purchase, right? What if hAudio suggested the use
of rel-enclosure for downloads and
In message [EMAIL PROTECTED], Manu Sporny
[EMAIL PROTECTED] writes
Scott's argument was the final nail in the 'work-title' coffin. Work
title has been changed to 'fn'
Thereby giving us:
div class=haudio
span class=contributor hcard
span class=fn !-- fn
This kind of relates to something I was mulling over. If you link to a third
party site, how do you guarantee that you don't get a 404 response? I can't
think of any other solution short of periodically pinging that url and
checking the response. In theory just checking the content-type and
On Tue, 2007-05-08 at 22:08 +0100, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Manu Sporny
[EMAIL PROTECTED] writes
Scott's argument was the final nail in the 'work-title' coffin. Work
title has been changed to 'fn'
Thereby giving us:
div class=haudio
span
On Tue, 2007-05-08 at 23:07 +0100, Martin McEvoy wrote:
On Tue, 2007-05-08 at 22:08 +0100, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Manu Sporny
[EMAIL PROTECTED] writes
Scott's argument was the final nail in the 'work-title' coffin. Work
title has been changed to 'fn'
From what I can tell, the intention is to use the format X-something to
describe a parameter that is not registered with IANA. Put differently, IANA
reserves all keywords except for those starting with X-.
I haven't read-up on the work-title discussion as of yet...so no input as to
whether this
On May 8, 2007, at 3:55 PM, Andy Mabbett wrote:
I can foresee problems.
Suppose a publisher links to a third-party site, offering an audio
track
as a free sample (or vice versa). Later, that latter site decides to
start charging for the track - how would the publisher know that their
site
19 matches
Mail list logo
