Edit comment LC-2313 for Web Applications Working Group

Quick access to LC-2312 LC-2313 LC-2314 LC-2315

Comment LC-2313

Comment Shortname:

Commenter: Marcin Hanclik <Marcin.Hanclik@access-company.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeWidgets 1.0: Packaging and Configuration /**/ .produ... W3C Working Draft 29 October 2009 Abstract Status of this Document Table of Contents 1 Introduction 1.1 Design Goals and Requirements 1.2 How This Document is Organized 1.3 Typographic Conventions typographical conventions 1.4 The Widget Family of Specifications Widgets 1.0 family of specifications 2 Conformance 3 Definitions Arbitrary author Initialization language tag media type Reserved Supported Unsupported widget 3.1 Character Definitions space characters Unicode white space characters control characters forbidden characters 4 User Agents user agent widget user agent 4.1 Optional Aspects of the Zip Specification optional aspects of the Zip specification 4.2 Internationalization Tag Set Support 5 Zip Archive Zip archive packaging format file entry local file header file data data descriptor potential Zip archive valid Zip archive .Zip file magic numbers for a Zip archive 5.1 Compression Methods compression method compression method field valid compression methods Stored 5.2 Version of Zip Needed to Extract a File Entry version needed to extract valid versions needed to extract 5.3 Zip Relative Paths Zip relative path file name field valid Zip relative path Zip-rel-path locale-folder folder-name file-name allowed-char zip-UTF8-char safe-char UTF8-2 UTF8-3 UTF8-4 UTF8-tail language-range alphanum low-alpha ALPHA DIGIT SP 5.4 Interoperability Considerations 5.4.1 Paths Lengths 5.4.2 Character sets language encoding flag (EFS) 5.4.3 File Names 6 Widget Packages widget package 6.1 Invalid Widget Package invalid Widget package 6.2 Files and Folders root of the widget package file folder processable file 6.3 Reserved File and Folder Names Reserved File Names Table 6.4 Digital Signatures digital signature digitally signed 6.5 Start Files start file 6.5.1 Custom Start File custom start file 6.5.2 Default Start Files default start file If a user agent encounters a file matching a file name given... Default Start Files Table 6.6 Icons icon 6.6.1 Custom Icons custom icon 6.6.2 Default Icons default icon Default Icons Table 6.7 Media Type valid widget media type 6.8 File Extension widget file extension 7 Configuration Document configuration document valid configuration document file name A user agent must treat any file in an arbitrary folder or l... 7.1 Example Configuration Document 7.2 Namespace widget namespace 7.3 Proprietary Extensions 7.4 Attribute Types attribute types invalid Boolean attribute valid boolean value Keyword attribute keyword Keyword list attribute Media type attribute valid media type type subtype parameter Numeric attribute valid non-negative integer Path attribute valid path file name field Zip absolute path Zip-abs-path IRI attribute valid IRI Version attribute 7.5 Other Attributes xml:lang its:dir 7.6 The widget Element widget 7.6.1 Attributes of the widget Element id version height width viewmodes Viewport view mode 7.6.2 Usage example 7.7 The name Element name 7.7.1 Attributes of the name Element short 7.7.2 Usage Example 7.8 The description Element description 7.8.1 Attributes of the description Element 7.8.2 Usage Example 7.9 The author Element author 7.9.1 Attributes of the author Element href email 7.9.2 Usage Example 7.10 The license Element license software license 7.10.1 Attributes of the license Element href 7.10.2 Usage Example 7.11 The icon Element icon 7.11.1 Attributes of the icon Element src width height 7.11.2 Usage Example 7.12 The content Element content 7.12.1 Attributes of the content Element src type encoding The default encoding is [UTF-8], which has the name "UTF-8"... default encoding 7.12.2 Usage Example 7.13 The feature Element feature feature 7.13.1 Attributes of the feature Element name required 7.13.2 Usage example 7.14 The param Element param parameter 7.14.1 Attributes of the param Element name value 7.14.2 Usage example 7.15 The preference Element preference preference 7.15.1 Attributes of the preference Element name value readonly 7.15.2 Usage example 7.16 Indicating Text Directionality with its:span valid its:dir value 8 Internationalization and localization Internationalization Localization Localized content Unlocalized content localized file 8.1 Localization Model 8.2 Folder-based localization folder-based localization deprecated grandfathered redundant container for localized content locale folder 8.3 Element-Based Localization element-based localization localizable via xml:lang one element is allowed per language 8.4 Localization Examples 8.4.1 Simple Example 8.4.2 Complex Example 8.4.3 Fallback Behavior Example 9 Steps for Processing a Widget Package steps for processing a widget package 9.1 Processing Rules processing rules 9.1.1 Rule for verifying a zip archive rule for verifying a zip archive split into multiple files multiple volumes 9.1.2 Rule for extracting file data from a file entry rule for extracting file data from a file entry 9.1.3 Rule for Finding a File Within a Widget Package rule for finding a file within a widget package 9.1.4 Rule for Getting a Single Attribute Value rule for getting a single attribute value 9.1.5 Rule for Getting a List of Keywords From an Attribute rule for getting a list of keywords from an attribute 9.1.6 Rule for Verifying a File Entry rule for verifying a file entry CRC-32 9.1.7 Rule for Getting Text Content rule for getting text content text node 9.1.8 Rule for Getting Text Content with Normalized White Space rule for getting text content with normalized white space 9.1.9 Rule for Parsing a Non-negative Integer rule for parsing a non-negative integer 9.1.10 Rule for Identifying the Media Type of a File rule for identifying the media type of a file File Identification Table 9.1.11 Rule for Determining if a Potential Zip Archive is a Zip Archive rule for determining if a potential Zip archive is a Zip arc... Step 1 - Acquire a Potential Zip Archive Step 1 9.1.12 Acquisition of a potential Zip archive labeled with a media type Acquisition of a potential Zip archive labeled with a media... If a user agent supports acquisition of a potential Zip arch... During the acquisition of a potential Zip archive labeled wi... If the result of the user agent applying the rule for determ... Widgets 1.0: Packaging and Configuration W3C Working Dra... 9.1.13 Acquisition of Potential Zip Archive not Labeled with a Media Type When acquiring a potential Zip archive that has not been lab... Step 2 - Verify the Zip Archive Step 2 Verify the Zip Archive To verify that a Zip archive and its file entries conform to... Step 3 - Set the Configuration Defaults Step 3 In Step 3, a user agent must set the following variables and... Table of Configuration Defaults author email author href author name feature list icons start file encoding start file content-type widget config doc widget description widget height widget id widget license widget license file widget license href widget name widget preferences widget short name widget version widget width widget window modes widget start file user agent locales Step 4 - Locate and Process the Digital Signature Step 4 If the user agent does not support [Widgets-DigSig], then th... Step 5 - Derive the User Agent's Locale Step 5 end-user's language ranges language range subtags algorithm to derive the user agent locales Step 6 - Locate the Configuration Document Step 6 In Step 6, a user agent must apply the algorithm to locate t... locate the configuration document Step 7 - Process the Configuration Document Step 7 Process the Configuration Document 9.1.14 Terminology Used in Processing Algorithm in error ignore associate lookup 9.1.15 Algorithm to Process a Configuration Document algorithm to process a configuration document If doc is not namespace well-formed [XML], then the user age... If the root element is not a widget element in the widget na... If the id attribute is used, then let id be the result of ap... If the version attribute is used, then let version value be... If the height attribute is used, then let normalized height... If the width attribute is used, then let normalized width be... If the widget element does not contain any child elements, t... element list If this is not the first name element encountered by the use... If this is the first name element encountered by the user ag... If this is not the first description element encountered by... If this is the first description element encountered by the... If this is not the first license element encountered by the... If this is the first license element used, then the user age... If the src attribute of this icon element is absent, then th... Let path be the result of applying the rule for getting a si... Let file be the result of applying the rule for finding a fi... If file is not a processable file, as determined by applying... If the height attribute is used, then let potential height b... If the width attribute is used, then let potential width be... If this is not the first author element encountered by the u... If this is the first author element used, then the user agen... If a value attribute of the preference element is used, but... If this is not the first content element encountered by the... If this is the first content element, then the user agent mu... If the src attribute of the content element is absent, then... If path is not a valid path, then the user agent must ignore... If path is a valid path, then let file be the result of appl... If the type attribute is used, then let content-type be the... If the encoding attribute is used, then let content-encoding... If this param element is not a direct child of a feature ele... If a required attribute of this feature element is used, but... If feature-name is not a valid IRI, and required-feature is... If feature-name is not supported by the user agent, and requ... If feature-name is not supported by the user agent, and requ... If a value attribute is used, but the name attribute is abse... If a name attribute is used, but the value attribute is abse... Let param-name be the result of applying the rule for gettin... Step 8 - Locate the Start File Step 8 If widget start file of the table of configuration defaults... If widget start file does not contain a file, the user agent... algorithm to locate a default start file For each file name in the default start files table (from to... If after searching for every file in the default start files... Step 9 - Process the Default Icons Step 9 In Step 9, a user agent must apply the algorithm to locate t... algorithm to locate the default icons Appendix Media Type Registration for application/widget language encoding flag (EFS) Linking To a Widget Package From a HTML Document Auto-discovery List of Changes Since Last Publication list of changes Normative References [ABNF] [BCP47] [CP437] [CSS21] [Deflate] [DOM3Core] [ITS] [IANA-Charsets] [IRI] [MIME] [RFC2119] [RFC4647] [SNIFF] [SVGTiny] [Unicode] [URI] [UTF-8] [Widgets-DigSig] [Widgets-Views] [XML] [XMLNS] [ZIP] Informative References [CSS-MIME] [ECMAScript-MIME] [HTML4] [HTML5] [HTTP] [UTR36] [Widgets-Landscape] [Widgets-Reqs] [Widgets-Relax NG Schema] [P&C-Test-Suite] [Widgets-APIs] [Widgets-URI] [XHTML1.1] [XML-MIME] [ZIP-MIME]
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

5.3 (grammar: I hope these are final corrections :( )

[*folder-name]
Should be
*folder-name
Since the current form makes it optional twice

Zip-rel-path
file-name/
could be
file-name /
(note the space before '/')

safe-char
I suggest putting the '/' sign at the end of each line instead of at the beginning

7.4
Media type attribute
It is unclear why the valid-MIME-type production requires "parameter".
"parameter" could specify the charset and that could conflict with the @encoding attribute of the <content> element.
Also the valid-MIME-type could be replaced with the following from RFC4288
type-name = reg-name
subtype-name = reg-name

reg-name = 1*127reg-name-chars
reg-name-chars = ALPHA / DIGIT / "!" /
"#" / "$" / "&" / "." /
"+" / "-" / "^" / "_"

BTW:
I understand that W3CMediaReg uses RFC2046 (actually RFC2048), but RFC4288 (also BCP13) obsoletes RFC2048.
So it gets blurred to me.

Path attribute
"a valid path represent a hierarchical"
Should be
"a valid path represents a hierarchical"

Version attribute
"e.g. '1.0' is not greater than '2.0'"
Could be
"e.g. '1.0' is not less than '2.0'"
9.1.10
a) There is no step 11, <ol> was changed to <ul> after step 4.

b) SNIFF spec basically specifies the algorithms for the resources retrieved from the network.
The statement relevant to P&C seems to be:

" For resources fetched from the file system, user agents should use

platform-specific conventions, e.g. operating system file extension/

type mappings.
"
Therefore it is unclear what
"processing file<http://dev.w3.org/2006/waf/widgets/#file> through the [SNIFF]<http://dev.w3.org/2006/waf/widgets/#sniff> specification."
means (i.e. SNIFF is big, but we need just one sentence?).
Are we restricted e.g. to section 5 ("Unknown Type")?

c) The version of the SNIFF spec that is referred by P&C is 00 (by date) and it has already expired as ID.

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.

Related issues: (space separated ids)

WG Notes:

Resolution: Implemented clarification on MIME type handling and other minor things. Marcin approved the changes during the teleconf: http://lists.w3.org/Archives/Public/public-webapps/2009OctDec/0837.html and sent an email giving his approval: http://lists.w3.org/Archives/Public/public-webapps/2009OctDec/0871.html

(Please make sure the resolution is adapted for public consumption)