Re: [apps-discuss] font/* (and draft-freed-media-type-regs)

there is good reason to register when implementations are widely deployed, whatever stage of the process it is at. if the spec isn't stable then the registration can say so and point to a place where someone can track the spec and learn what the type might have meant...

Connected by DROID on Verizon Wireless

-----Original message-----
From: Chris Lilley <chris@w3.org>
To: Ned Freed <ned.freed@mrochek.com>
Cc: David Singer <singer@apple.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "Levantovsky, Vladimir" <Vladimir.Levantovsky@MonotypeImaging.com>, "gadams@xfsi.com Adams" <gadams@xfsi.com>
Sent: Tue, Nov 22, 2011 16:10:11 GMT+00:00
Subject: Re: [apps-discuss] font/* (and draft-freed-media-type-regs)

On Monday, November 21, 2011, 9:09:17 PM, Ned wrote:

>> Julian wrote:
>> I believe it would be better overall to register early, and then to
>> update the registration later on.

NF> +1

NF> And there is no need to change any rules to allow this. The decision of when to
NF> register a type is entirely up to the standards body doing the the registering.

NF> The word "stable" appears nowhere in RFC 4288.

Thanks for the confirmation, Ned, that there is nothing in the RFC that would prevent W3C registering media types at the W3C Candidate Recommendation stage.

--
 Chris Lilley   Technical Director, Interaction Domain
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss