Hi Benoit,
Inline comments below. For the sake of the LC disposition of comments,
please be sure to indicate if you are satisfied with the changes I have
made
On 1/20/09 8:50 PM, SUZANNE Benoit RD-SIRP-ISS
benoit.suza...@orange-ftgroup.com wrote:
Hello All,
Here are some comments on the Jan 17th draft:
1.5 Global Definitions
There are some misplaced quotes that could be deleted and I propose the more
generic formulation:
The [Widgets-Landscape] defines a widget as an end-user's conceptualization of
an interactive single purpose application for displaying and/or updating local
data or data on the Web, packaged in a way to allow a single download and
installation on a user's machine, mobile phone, or any Internet-enabled
device. Because widgets are packaged, they can be liberally shared by users
without relying on [HTTP] (i.e., users can share widgets over Bluetooth or
through other distribution channels).
Fixed.
In addition with the defined words, we should also add the following:
A User is the actual consumer of the widget content that the author has
created.
Added, but as end-user as that is the term that is used throughout the
spec.
A User Agent is the runtime environment in which a widget runs. It is also
known as a widget engine.
That definition of user agent is not broad enough to encompass conformance
checkers. The definition you suggested is already covered by widget user
agent.
6 Widget Resources
In this section ther is a lot of references to ³localized folders² where the
wording should be more specific as it is not just anywhere but at the root
level of the righ local folder, therefore I propose the following edit:
* One or more start files, located at the root of the widget or in the
root of the language folders.
I know that localized folder seems weird there because localized folder
has not yet been defined when you get to that part of the document. I've
added root of the.
The formulation has also to be edited in the same way all throughout the rest
of the document. There is a distinction between the localization folder (ie
³/Locales/²) and the language folder (ie ³/Locales/FR/²)
The locales/ is defined as the container for localized content (there
was a mistake in the definition). However, I would prefer not to change
this.
Instead, I've tighten up the definition of both localized folder and the
container for localized content and added examples. Can you please check if
it is more clear now.
6.5 Content Localization
Author requirements: According to [BCP47], one should avoid region, script ...
(unless there is a good reason to include them) as the a widget user agent...
The ³a² seems to be a copy/paste edition leftover that should be deleted...
Fixed.
Localized Widget Example
In order to cover tha various aspects, I belive this very good example should
also include the following cases:
* a script.js localization
* a folder structure localization
Therefore I propose to ad the /Locales/en-gb/scripts/engine.js file in this
example with the related comments to explain the cases.
I made your suggested change to /en-au/.
6.7 Custom Icons and Default Icons
An icon must be located either at the root of the widget or in the root of the
language folder.
Same distinction as in section 6
fixed
A default icon must be located either at the root of the widget or in the root
of the language folder.
Same distinction as in section 6
Fixed
Default Icons
In the table order I¹m not sure I understand why the png ad the gifs are not
on top of the list.
The reason that the table is structured that way is that the optional types
are deemed to be more powerful then the required types: if the user agent
supports SVG, which could be an interactive animated icon, it will select
SVG first (rather then png or gif), and so on. PNG is also considered better
than GIF, so it is selected before gif.
6.8 Thumbnail
A thumbnail is an optional file inside the widget resource that graphically
represents the widget in a running state. The thumbnail must be located either
at the root of the widget or in the root of the language folder.
Same distinction as in section 6
fixed.
7 Configuration Document
Configuration documents can exist either at the root of the widget or in a the
root of the language folder.
Fixed.
Note: Any configuration document not at the root of the widget or not in the
root of the language folder will be treated by the widget user agent as an
arbitrary resource.
Fixed.
Same distinction as in section 6
7.3 Attribute Types
Window mode attribute
A keyword attribute whose value is one of the following valid window
modes: iconized, minimized, expanded, fullscreen and settings.
I propose the following wording for the various modes: iconized, minimized,
expanded, fullscreen and settings
I would include some kind of attributes to the full screen to allow the
determination of both
