On Tue, 2007-05-08 at 16:20 -0400, Manu Sporny wrote:
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
On May 9, 2007, at 9:57 AM, Martin McEvoy wrote:
fn is good for the artist but not their art? as you would have two fn
properties in one haudio.
This is a parsing issue with a solution, so it shouldn't influence
our choice of markup. Specifically, a solution is for parsers to
recognize
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], 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
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
