W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

[widgets] P&C Last Call comments, 6

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Tue, 2 Jun 2009 15:50:11 +0200
To: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C0A26ED9036@OBEEX01.obe.access-company.com>
9.1
a user agent must to decompress ...
should be
a user agent must decompress ...

... instructions on how to extract a file for Zip archive.
should be
... instructions on how to extract a file from Zip archive.

The rule for dealing with an invalid Zip archive is described in this section.
</p><p> could follow this sentence as in the previous subsection.

Rule for finding a file within a widget package

If none if found
should be
If none is found

... the name of the path (
could be
... the path (

Rule for finding a file within a widget package: algorithm

3.B If path points to a file entry  within the widget package, then return the corresponding file.
should be
3.B If path points to a file entry  within the widget package, let file be the result of applying the rule for extracting file data from a file entry to path.
And maybe jump to 4.B or terminate as 4.B and 4.C do.

An unusable file entry is one where by any of following conditions occur/apply ...
should be
An unusable file entry is one where any of following conditions occur/apply

Rule for Getting Text Content

"Let input be the [DOM3Core]  Element to be processed."
Unclear: Where does the [DOM3Core] Element come from? Probably some assignment like:
"the element to be processed MUST be interpreted as [DOM3Core] Element"
would help.

"Return the value of the textContent property for input."
Where does the textContent property come from? [http://www.w3.org/TR/DOM-Level-3-Core/core.html#Node3-textContent ? ]

" There may be implementation-specific limits on the range of integers allowed, and behavior outside such limits is undefined."
What about interoperability, again.

Rule for Identifying the Media Type of an Image

... the first bytes of the file matches one of ...
should be
... the first bytes of the file match one of ...

... in hexadecimal column of ..
and
... in the second column ...
both should be revisited, since the column names seem not to match the text. (Are the columns indexed from 0?)

"A 0 word following by a 1 word,"
Endianness is unclear.

The rule for identifying the media type of a file are given by ...
should be
The rule for identifying the media type of a file is given by ...

1. Let file be the file to be processed. ...
could be
1. Let filename be the name of the file to be processed.
2. If filename includes a file-extension, attempt ...

attempt to match the file-extension to one in the first column
should be
attempt to match the file-extension to one of the strings in the first column

Comments as above for "Rule for Identifying the media type of a file".


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 Tuesday, 2 June 2009 13:50:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT