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

[widgets] P&C Last Call comments, 4

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Mon, 1 Jun 2009 00:44:27 +0200
To: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C0A26D782DF@OBEEX01.obe.access-company.com>
8.12
in which case a user agents that
should be
in which case a user agent that

In other words, the required attribute denotes that a feature is absolutely needed by the widget to function correctly,
and without the availability of this feature the widget serves no useful purpose or won't execute properly.
should be
In other words, the required attribute denotes WHETHER a feature is absolutely needed by the widget to function correctly,
and WHETHER without the availability of this feature the widget serves any useful purpose or WHETHER it will execute properly.
or
In other words, the value "true" of the required attribute denotes that a feature is absolutely needed by the widget to function
correctly, and without the availability of this feature the widget serves no useful purpose or won't execute properly.

... meaning that the feature must be made available to the widget by the widget at runtime.
should be
... meaning that the feature must be made available to the widget at runtime.
or
... meaning that the feature must be made available to the widget by the user agent at runtime.

8.13
"Outside the context of a feature  element, a param element does not represent anything and a user agent must ignore it."
This sentence seems redundant, because the "Context in which this element may be used:" part is normative enough.

8.14
"Unless an end-user explicitly requests that these values be reverted to the values as declared in the configuration document, a

user agent must not revert to these values on subsequent initialization of the widget."
More information about management of these values is needed. What is reverting? How can the end-user explicitly request that these

values are reverted to the value from config.xml? This is UI/UX aspect that needs specification.

8.15
I suggest to move this section before section 8.5, because it defines what "Localizable" (used from 8.5) means.

8.16
The its:dir attribute and the <its:span> element can each be used as a child of ...
should be
The <its:span> element with the its:dir attribute MAY each be used as a child of ...

9.
Rule for getting a list of keywords from an attribute
There are dropping and chopping (operations not clearly defined). Maybe the algorithm could be defined more precisely?
It returns a list, takes a string as input.
So the first suggestion is to use different variable name from the temporary "result" and the actual "result".

9.1 Step 7
"During the processing of a configuration document, an error condition can ask the user agent ignore an object (e.g., a file or a

DOM node)."
Not sure what it means.

________________________________________

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 Sunday, 31 May 2009 22:45:08 GMT

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