- From: Tal Leming <tal@typesupply.com>
- Date: Thu, 27 May 2010 11:18:34 -0400
- To: Sylvain Galineau <sylvaing@microsoft.com>
- Cc: Jonathan Kew <jfkthame@googlemail.com>, Vladimir Levantovsky <Vladimir.Levantovsky@MonotypeImaging.com>, Christopher Slye <cslye@adobe.com>, "www-font@w3.org" <www-font@w3.org>, "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>
On May 26, 2010, at 6:18 PM, Sylvain Galineau wrote: > <metadata-extended> > <property group="catalog-info" name="RefID" value="AAA-6667" /> > <property group="catalog-info" name="UnicodeRange" value="standard" /> > <property group="catalog-info" name="UpdateURI" value="http://www.fontvendor.com/update/AAA-6667" /> > <property group="EU" name="CopyrightNumber" value="FR-33323-2010" /> > <property group="EU" name="CopyrightGrantDate" value="20111021" /> > <property group="AdobeDreamweaver" name="category" value="headline" /> > <property group="AdobeDreamweaver" name="recommended-min-size" value="14pt" /> > </metadata-extended> What if we do something more simple? We could add a section to the Extended Metadata section about extensions. It could say something like: Extensions to the metadata are allowed, but they may not be displayed by UAs. If extensions are added, they must not be nested any deeper than two levels from the top-level metadata element. This would limit the depth of the nesting to what we have in the spec now. You made a good point about not wanting UAs to have to update each time a new element is added to the spec. I think that by not defining a specific extension syntax like the above, we could achieve that goal. Everything would be allowed, as long as it followed the nesting limits. A UA could implement a "show everything" UI now and not have to worry about updating when metadata version 3.7 comes along. Tal
Received on Thursday, 27 May 2010 15:19:11 UTC