Re: widgets feedback
DoC: ok
Re: widgets feedback
On Fri, Jul 3, 2009 at 5:12 PM, Marcos Caceresmarc...@opera.com wrote: Fixed issues below. If satisfied with the corrections, please give us an OK for the DoC :) DoC: OK I guess the person at Times Square that made the decision to activate the widget. Oh well. Someday that user will be replaced by an automated random heisencat. I guess I'll just have to wait for that cat. * sections marked with the text This section is non-normative, *authoring guidelines, I hope there's a space after that bullet :) * examples, including sentences that contain the words for example, * and notes. AFAIK, that is correct here. But I can't be bothered looking up a manual of style. Yeah, I think you're right.
Re: widgets feedback
On Fri, Jul 3, 2009 at 6:37 PM, Marcos Caceresmarc...@opera.com wrote: Fixed all editorial comments below for this third set of comments. If satisfied with the corrections, please give us an OK for the DoC :) DoC: OK This would be the author's fault for including an empty file. The UA still does the right thing (it loads the index.svg file and finds it is not well formed.) Should CC's be encouraged to complain about such things? I suppose not as it's fairly hard to determine if random start formats won't work...
Re: widgets feedback
On Fri, Jul 3, 2009 at 6:55 PM, Marcos Caceresmarc...@opera.com wrote: Addressed your final set of editorial issues. If satisfied with the corrections, please give us an OK for the DoC :) DoC: OK except for the one below. 4:37 PM A user agent will acquire a potential Zip archive from a data transfer protocol that either labels resources with a media type (e.g. [HTTP]) or from a data transfer protocol that does not label resources with a media type (e.g., BitTorrent, Bluetooth, etc.). A tautology ... (yes, i know we're trying to say this, but is there a better way to write it?) I think I will leave it. The point here is to alert the reader that we handle both cases. Oh, I wasn't asking you to remove it, just rewrite it ;-) A user agent can acquire a potential Zip archive both from data transfer protocols which label resources with media types (e.g. ) and from data transfer protocols which do not (e.g. ...). I think you already got rid of the e.g.+etc. pair.
Re: widgets feedback
Hi Josh,
Fixed issues below. If satisfied with the corrections, please give us
an OK for the DoC :)
On Thu, Jun 18, 2009 at 3:27 PM, timelesstimel...@gmail.com wrote:
http://dev.w3.org/2006/waf/widgets/
Date: Tue, Jun 16, 2009 at 2:52 AM
2:29 AM me: hey
suppose that times square becomes widget capable
2:30 AM and starts running widgets, like a Clock.wdgt
who's the end user? :){
I guess the person at Times Square that made the decision to activate
the widget.
9 minutes
2:40 AM me: Bluetooth is spelled as such, no capital T
(i.e., users can share widgets over non-HTTP distribution channels,
such as BlueTooth, a USB thumb drive, etc.).
Fixed
the idea of using both 'i.e.' and 'etc.' in the same parenthetical
scares me. although it might be correct in this instance
Dropped etc.; I've no intention of being a grammatical terrorist :)
2:41 AM Supported means that a user agent implements a said specification,
said - mentioned ?
a said sounds really odd
2:42 AM maybe listed, indicated, ... dunno
Fixed. Used mentioned
Initialization means a run through the steps for processing a widget
package post installation of a widget.
post = after ?
Used after.
2:43 AM As well as sections marked as non-normative, authoring
guidelines, diagrams, examples, and notes in this specification are
non-normative.
is hard to parse.
As well as sections marked as non-normative, authoring
guidelines, diagrams, examples, and notes in this specification are
non-normative.
2:44 AM In addition to (non-normative marked|marked non-normative)
sections, all authoring guidelines, ... and notes in this
specification are ... non-normative.
Made it:
[[
Some text in this specification is non-normative. Non-normative text includes:
* sections marked with the text This section is non-normative,
*authoring guidelines,
* examples, including sentences that contain the words for example,
* and notes.
Everything else in this specification is normative.
Please see the typographical conventions to see how authoring
guidelines, examples, and notes of this specification are stylized.
]]
There are no diagrams, so I removed that.
2:46 AM There are four classes of products that can claim conformance
to this specification:
2:47 AM that = which ?
(very uncertain about that)
AFAIK, that is correct here. But I can't be bothered looking up a
manual of style.
2:49 AM Other legacy/proprietary widget types can be supported by a
user agent, but a user agent must conform to this specification when
dealing with a widget package.
should this say:
2:52 AM While a conforming user agent may support other
legacy/proprietary widget types in order to conform to this
specification it must treat widget packages as according to this
specification.
Fixed.
--
Marcos Caceres
http://datadriven.com.au
Re: widgets feedback
Hi Josh, Fixed all editorial comments below for this third set of comments. If satisfied with the corrections, please give us an OK for the DoC :) On Thu, Jun 18, 2009 at 5:55 PM, timelesstimel...@gmail.com wrote: Date: Thu, Jun 18, 2009 at 6:48 PM 6:36 PM me: (e.g., a user agent could use an array, or an object, or a hash map, etc.). drop each or Fixed 6:41 PM For each element in the elements list, if the element is one of the following: A preference element: doesn't mention readonly (this might be ok, or maybe not...) Fixed. 6:48 PM 1. For each file name in the default start files table (from top to bottom) that has a media type that is supported by the user agent: 1. Let potential-start-file be the result of applying the rule for finding a file within a widget package to file name. 2. If potential-start-file is null or in error, ignore this file name and move onto the next file name in the default start files table. 3. If potential-start-file is a file, then: 1. Let widget start file be the value of potential-start-file. 2. Let start file content-type be the media type given in the media type column of the default start files table. 3. Terminate this algorithm and go to Step 9. I'm worried about the case where a package has two files: index.svg and index.xhtml. index.svg is 0 bytes and index.xhtml is a well formed xhtml file. The author developed this package using a user agent which doesn't support image/svg+xml and things worked well. A user unfortunately gets the widget and uses it with a user agent which does support image/svg+xml. I'm fairly certain what happens is that this process sends the user agent to step 9 with index.svg and the user ends up unhappy. This would be the author's fault for including an empty file. The UA still does the right thing (it loads the index.svg file and finds it is not well formed.) Kind regards, Marcos -- Marcos Caceres http://datadriven.com.au
Re: widgets feedback
Hi Josh, Addressed your second set of comments below. If satisfied with the corrections, please give us an OK for the DoC :) On Thu, Jun 18, 2009 at 3:27 PM, timelesstimel...@gmail.com wrote: Date: Tue, Jun 16, 2009 at 11:42 AM 8:42 AM me: A conformance checker (CC) is a user agent that verifies if a widget package and a configuration document conform to this specification. if = whether Fixed 56 minutes 9:38 AM me: liwhen the a class=no-toc no-num href=#rule-for-verifying-a-file-entry0rule for Verifying a File Entry/aspan/span is applied to the file, it returns the empty span is probably a bug Fixed. 9:39 AM 6.3 Reserved File and Folder Names Reserved File Names you need to change 'xml' to '.xml' and similar Fixed. 9:40 AM The [Widgets-DigSig] specification also defines the naming conventions for a distributor signature and the naming convention for an author signature. i think you want 'for distributor signatures' and 'for author signatures' (plural for both) There is only one author signature. I don't want to imply there there can be more. 19 minutes 10:00 AM me: via a an access control policy. drop a Fixed. 10:19 AM me: so, i'm not a fan of out of scope of (very few google hits), i prefer beyond the scope of (millions of hits) Fixed. 10:21 AM me: The start file of a widget package is a file that is used by the user agent when the widget is instantiated. kinda useless statement Used A start file designates the file from the widget package to be loaded by the user agent when it instantiates the widget. you use the configuration file when the widget is instantiated too Kinda... what you really use are the Configuration Defaults which are the result of processing the start file. 10:22 AM you kinda want to somehow explain that it's more than a file that's used. although w/o limiting things to DOM style :) 10:25 AM does Default Start File actually specify the order in which one is found Yes, in Step 8. For each file name in the default start files table (from top to bottom) that has a media type that is supported by the user agent:. and if so, does it define a name for the thing that's found? Not sure what you are asking here. The spec says the following in Step 8: If potential-start-file is a file, then: * Let widget start file be the value of potential-start-file. * Let start file content-type be the media type given in the media type column of the default start files table. Terminate this algorithm and go to Step 9. In other words, widget start file is stored in the configurations defaults, which is then initialized by the UA. When a start file is not explicitly declared via the content element, then start file will be one of the default start files. 10:26 AM it'd be better if you could just reference the algorithmically determined start file instead of hand waving at a list I have Note: See Step 8 for instructions on finding a default start file. The algorithm depends on the Default Start Files Table. I agree that it would be cleaner if everything was in one place, but I don't think we should bother moving it now (because we would need to fix all other places that use a similar table/lookup structure). I think it's clear enough. 31 minutes 10:58 AM me: might not be supported on all user agents. on = by Fixed then Make sure that the widget is labeled with an why is Make capitalized? Fixed. 11:00 AM me: you use case-sensitively 5 times and as case-sensitive 4 times i don't like the latter :) as case-sensitive = case-sensitively Fixed where appropriate. 17 minutes 11:19 AM me: feature name=http://example.com/camera; param name=autofocus value=true/ random blank line between those two? width = 200 viewmodes = application fullscreen 11:20 AM most things line up in this tag's attribute list, except viewmodes Fixed preference name =apikey 11:21 AM this tag doesn't get spaces after =,... if you're trying to demo lots of different styles, ok, but please note that somewhere, otherwise, ick :) Fixed. Made more consistent. Be sure to declare the widget namespace as part of the widget element. If the namespace is absent, then Zip archive will be treated as an invalid Zip archive. 11:22 AM it's odd to mark a zip file as invalid because of an error in the widget shouldn't the widget be invalid instead ? Correct. That is a bug. 11:24 AM Some general rule rules (plural) Fixed. 11:28 AM Keyword list attribute oh fun, this,is,forbidden It sure is. Unless that's a keyword, of course. 11:30 AM do we need to say that ., .., ..., are interesting? that is the domain of the Widgets URI spec 11:33 AM either by default as part of the [XML] specification (as is the case with xml:lang) or if the user agent implements the optional
Re: widgets feedback
Final hi! Josh,
Addressed your final set of editorial issues. If satisfied with the
corrections, please give us
an OK for the DoC :)
On Thu, Jun 18, 2009 at 5:54 PM, timelesstimel...@gmail.com wrote:
Date: Thu, Jun 18, 2009 at 4:52 PM
4:15 PM me: (e.g., floating and application mode)
either floating mode and application mode
or the floating and application modes
Removed the example text. The spec says that the Window Modes spec
specifies that. I don't want to make that normative in PC only to
have it replicated in the other spec (might cause issues).
The following example shows the usage of the name element.
widget xmlns=http://www.w3.org/ns/widgets;
name short=Weather
The Ultimate Weather Widget
probably indent The one more space :)
Fixed.
___
19 minutes
4:35 PM me: file identification table
has 3 columns, one is entirely empty
Anne wanted us to put something in there (waiting for him to tell us
what). I've removed it while we wait.
4:36 PM Step 1 - Acquire a Potential Zip Archive
Step 1 involves acquiring a potential Zip archive
-- Potential v. potential?
Heading convention. Will leave as is.
4:37 PM A user agent will acquire a potential Zip archive from a data
transfer protocol that either labels resources with a media type (e.g.
[HTTP]) or from a data transfer protocol that does not label resources
with a media type (e.g., BitTorrent, Bluetooth, etc.).
A tautology ...
(yes, i know we're trying to say this, but is there a better way to write
it?)
I think I will leave it. The point here is to alert the reader that we
handle both cases.
4:39 PM Step 2 - Verify the Zip archive
The previous step used more uppercase letters :)
Fixed.
4:41 PM must treat the value as null(i.e., not as empty string and not
as the text string null).
add a space between 'null' and '('
Fixed
4:42 PM Configuration Defaults
this table uses column headers and footers, the other ones don't. (just
noting)
True. The reason I added them is that when the spec is printed, this
table does not fit on one page. I will leave the others for now.
4:43 PM must attempt to locate digital signatures for the widget (step ).
step number missing
Fixed
4:44 PM So, for example, fr,en-us,en,en-au,en,fr,en would become
fr,en-us,en-au.
there should be an example of a tripple (zh-hans-cn)
added.
7 minutes
4:52 PM me: ignore means that a user agent must act as if the element,
or fileis not present.
add a space between 'file' and 'is'
Fixed.
--
Marcos Caceres
http://datadriven.com.au
