- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Mon, 5 Oct 2009 08:54:19 -0400
- To: public-webapps <public-webapps@w3.org>
When scanning the Test Suite Version of the P&C spec I noticed some MAY and OPTIONAL assertions for which there are no associated test assertions. This implies these "assertions" aren't really necessary and should be removed or made non-Normative (e.g. hints to an implementor). Section 2: [[ http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#conformance A user agent MAY support other legacy/proprietary widget formats. ]] Section 4: [[ http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#user-agents It is OPTIONAL for a user agent to support the optional aspects of the Zip specification. ]] Section 7.11.1 [[ http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#the-content-element Aside from the default encoding, it is OPTIONAL for a user agent to support other character encodings. ]] Section 9: [[ http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#steps-for- processing-a-widget-package A user agent MAY optimize steps for processing a widget package and associated processing rules, or MAY perform the steps in a different order, but the end result MUST be indistinguishable from the result that would be obtained by following the specification. It is OPTIONAL for a user agent to validate language tags against the IANA Language Subtag Registry during the steps for processing a widget package. ]] Section 9.1.11 [[ http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#processing-rules It is OPTIONAL for a user agent to support any of the media types listed in the media type identification table. ]] Section 9.1.12 [[ http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#processing-rules It is OPTIONAL for a user agent to support the media types given in the file identification table. ]]
Received on Monday, 5 October 2009 12:56:20 UTC