RE: WOFF and extended metadata

Strictly speaking, the proposed sentence defines recommended behavior, where some kind of UI is to be provided by UA to show the content of metadata. It does not however prescribe any particular way to implement that UI, nor does it define any specific user interface features. This is all left to the implementers to decide.

Without this sentence, the spec would be incomplete because it provides the description of syntax and semantics of metadata but fails to mention what it is expected to be used for, and whether UA is expected to act on it. The proposed sentence resolves this issue by providing clear recommendations that UA should only display the content based on user's request. 

Regards,
Vlad


> -----Original Message-----
> From: public-webfonts-wg-request@w3.org [mailto:public-webfonts-wg-
> request@w3.org] On Behalf Of Christopher Slye
> Sent: Tuesday, May 25, 2010 2:33 PM
> To: public-webfonts-wg@w3.org
> Cc: www-font@w3.org
> Subject: Re: WOFF and extended metadata
> 
> Sorry Vlad, I agree it sounds like a UI requirement. Can you imagine a
> solution that satisfies this recommendation that's not? I can't.
> 
> However, I am strongly in favor of some language which specifically
> addresses this subject (the exposure of metadata to the viewer), so I
> do support the inclusion of this particular sentence.
> 
> -C
> 
> 
> On May 25, 2010, at 11:12 AM, Robert O'Callahan wrote:
> 
> > "If the metadata is present, browsers SHOULD provide the means for
> the Extended Metadata content to be displayed at user's request."
> >
> > That is a UI requirement.
> >
> > However, phrased that was as a SHOULD, everyone can just ignore it,
> so I guess it's mostly harmless.
>

Received on Tuesday, 25 May 2010 19:14:08 UTC