W3C

List of comments on “Widgets 1.0: Packaging and Configuration” (dated 29 October 2009)

Quick access to

There are 4 comments (sorted by their types, and the section they are about).

question comments

Comment LC-2315: Scott - author question
Commenter: Scott Wilson <scott.bradley.wilson@gmail.com> (archived message)
Context: 7.9 The author Element
Not assigned
Resolution status:

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

editorial comments

Comment LC-2312: Marcin 1
Commenter: Marcin Hanclik <Marcin.Hanclik@access-company.com> (archived message)
Context: in
assigned to Marcos Caceres
Resolution status:

Hi,

A couple of comments to the latest P&C.

7.4
Media type attribute
Media type attribute defines the grammar and refers to RFC2045/6.
What about referring to RFC4288 that includes the grammar required for MIME registration [1]? (I have no strong opinion about this point, though.)


Numeric attribute
"For example, the characters "002", "323", "23214""
Could be
"For example, the character strings "002", "323", "23214""

7.11.1
"When an icon element is used, it is required for authors to use the src attribute."
Should be an authoring guideline.

7.13.1
"that a user agent will behave as the required attribute"
Should be
"that a user agent will behave as if the required attribute"

Acknowledgments
It seems a paragraph is missing there.

Thanks,
Marcin

[1] http://tools.ietf.org/html/rfc4288#section-4.2

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.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-2314: Ericsson - icons
Commenter: Ola Andersson <ola.andersson@ericsson.com> (archived message)
Context: 6.6 Icons
assigned to Marcos Caceres
Resolution status:

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

Comment LC-2313
Commenter: Marcin Hanclik <Marcin.Hanclik@access-company.com> (archived message)
Context: 7.12 The content Element
Not assigned
Resolution status:

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.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org