W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

[Widgets] LCWD#3 comments (2)

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Wed, 18 Nov 2009 13:03:03 +0100
To: WebApps WG <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C28942D7529@OBEEX01.obe.access-company.com>
5.3 (grammar: I hope these are final corrections :( )

Should be
Since the current form makes it optional twice

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

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

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 / "!" /
                       "#" / "$" / "&" / "." /
                       "+" / "-" / "^" / "_"

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'"
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.


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


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 Wednesday, 18 November 2009 12:03:50 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:20 UTC