- From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Date: Thu, 24 Sep 2009 13:08:03 +0200
- To: Arthur Barstow <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>
Hi Art, Thanks for your comments. >>1. Abstract: >> >>a. I don't understand "the document's content" in this context. Changed to "the document". >>b. Missing a sentence terminator for the first sentence Fixed. >>c. Change the URI under the "Widgets 1.0 family of specifications" to: >> >> http://www.w3.org/2008/webapps/wiki/WidgetSpecs >> Fixed. >>d. Delete ", which together standarize widgets as a whole." >> Fixed. >>2. Status of the Document - change the URI under "Editor's Draft" to >>point to the latest Editor's draft of the spec and not a directory. >> Fixed. >>3. Section 1.1 - the following isn't accurate: >> >> [[ >>This document defines new media feature, its values and the DOM >>interface for querying the media features and types that apply to a >>document at a given instance in time, including events to detect when >>the values of the said features change. >>]] >> >>Change it to: >> >> [[ >>This document defines a new media feature and its values. >>]] >> Fixed. >>4. Section 1.2 - a User Agent in the context of this spec should >>implement this spec (not the P&C spec) >> Changed to: "A user agent is an implementation of this specification." >>5. Section 2 - We should strive for more consistency with the various >>widget spec's Conformance section. To that end, change the title to >>just "Conformance" and replace this entire section with just the >>following text in the Conformance section of the latest Editor's >>Draft of the widgets Interface spec i.e.: >> >> [[ >>All examples and notes in this specification are non-normative, as >>are all sections explicitly marked non-normative. Everything else in >>this specification is normative. >> >>The key words must, must not, should, recommended, may and optional >>in the normative parts of this specification are to be interpreted as >>described in [RFC2119]. >>]] >> Done. >>6. Section 3. and 3.1 >> >>a. I think there are problems with all four of the view modes >>definitions. As such, I would delete all of them and state they are >>defined in terms of their property values as specified in the table >>in Section 3.1 >> >>b. Rather than use "Characteristics" and "attributes", just use >>"property". For example, the statement: >> >> [[ >>The following attributes - summarized in the table below - >>characterize each of the values of the 'view-mode' media feature: >>]] >> >>Would become: >> >> [[ >>The following table defines each of the view-modes' values in terms >>of its properties. >>]] >> I reordered the sections and made the previous definitions non-normative. >>c. The heading of the last column in the table should be shortened to >>something like "width & height" >> Done. >>7. References >> >>a. Delete unused References: DOM2Events, DOM2Style, HTML4, CSS21, >>Widgets-Landscape, Widgets-Reqs >> >>b. Make Normative: [Media Queries] >> Done. Thanks, Marcin Marcin Hanclik ACCESS Systems Germany GmbH Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465 Mobile: +49-163-8290-646 E-Mail: marcin.hanclik@access-company.com ________________________________________ Access Systems Germany GmbH Essener Strasse 5 | D-46047 Oberhausen HRB 13548 Amtsgericht Duisburg Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda www.access-company.com CONFIDENTIALITY NOTICE This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited. If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Thursday, 24 September 2009 11:08:56 UTC