- From: timeless <timeless@gmail.com>
- Date: Thu, 18 Jun 2009 16:27:22 +0300
- To: public-webapps <public-webapps@w3.org>
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"? :){
________________________________
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.).
the idea of using both 'i.e.' and 'etc.' in the same parenthetical
scares me. although it might be correct in this instance
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
Initialization means a run through the steps for processing a widget
package post installation of a widget.
post => 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.
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)
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.
Received on Thursday, 18 June 2009 13:27:54 UTC