le" section of the
Requirements document. Please expand on R52-54, if possible.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
On Fri, May 22, 2009 at 11:29 AM, Marcos Caceres wrote:
> On Fri, May 22, 2009 at 11:17 AM, Scott Wilson
> wrote:
>> Is there a particular preferred format for submitting use cases?
>
> Not really, but it's best if it's something that we can include into:
>
>
of the above applies. However, it would be great to
get your thoughts on what is now in the spec.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
On 5/24/09 7:25 AM, timeless wrote:
On Tue, May 19, 2009 at 12:18 PM, Marcos Caceres wrote:
1. If no element is used, the application type (e.g., HTML,
Flash, whatever) is responsible for providing the security
context/rules under which the widget runs. For HTML this means that a
widget
On Mon, May 25, 2009 at 11:15 PM, Adam Barth wrote:
> On Sun, May 24, 2009 at 4:18 AM, Marcos Caceres wrote:
>> I should have made myself more clear. I meant that the widget would behave
>> as if it had been dragged from the hard-drive with respect to access to HTTP
>>
On Tue, May 26, 2009 at 12:01 AM, Adam Barth wrote:
> On Mon, May 25, 2009 at 2:34 PM, Marcos Caceres wrote:
>> should the following inline resources load?
>>
>>
>> http://foo.com"/</a>>
>> http://foo.com/image";>
>> http://bar.com
The Widgets 1.0: Packaging and Configuration will go to second last call
tomorrow (28th of May). Effectively, the spec is feature complete but
desperately needs review: it will have a 3 week review period (which is
very short, but we want to get this to CR quickly!).
Spec is available at:
http
Hi Marcin,
On 5/29/09 4:26 PM, Marcin Hanclik wrote:
Hi Marcos,
The following typo has been found by BONDI contributors.
The example in http://dev.w3.org/2006/waf/widgets/#the-feature-element now
specified as:
http://www.w3.org/ns/widgets";>
http://example.org/api.geolocation";
For the sake of the disposition of comment, please verify that you are
satisfied with the changes and response below.
On 5/29/09 4:55 PM, Marcin Hanclik wrote:
Hi Marcos,
Thanks.
Your proposal is generally ok me, feature name is just IRI.
I have, however, 2 arguments to change your proposal
To avoid semantic collisions with other W3C standards, I suggest changing
> "version" to e.g. "docversion".
> 2. The text similar to the one from DigSig spec could be put to P&C 8.1, just
> to show roadmap and intentions.
>
I don't agree with your conclusion. Versioning in the P&C is
understood in the context of the widget element. That is, the widget's
version is X. What version of the configuration document format is
denoted by the namespace.
--
Marcos Caceres
http://datadriven.com.au
e notify us promptly by
> responding to this e-mail. Thank you.
>
>
--
Marcos Caceres
http://datadriven.com.au
mum version supported version
> should be
> minimum supported version
fixed.
> the the CC MUST
> should be
> the CC MUST
fixed.
> 5.3
> it is recommended that a user agent internally treat all zip-relative
> should be
> it is recommended that a user agent internally treats all zip-relative
fixed.
--
Marcos Caceres
http://datadriven.com.au
educe the number of ...
Fixed.
> In this case, to find find the ...
> should be
> In this case, to find the ...
Fixed.
> 7.3
> whose folder-name case-sensitively match the string ...
> should be
> whose folder-name case-sensitively matches the string ...
Fixed.
--
Marcos Caceres
http://datadriven.com.au
as to what minimum version of the
> language is required for the content to work properly. No difference
> in processing is required for differently specified version="" and
> baseProfile="" attributes.
>
See also the link below for a detailed discussion as to why you are
suggesting in not ideal:
http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html
--
Marcos Caceres
http://datadriven.com.au
d to by the src attribute is a vector graphic format ...
> could be
> If the file pointed to by the src attribute contains an icon in a vector
> graphic format ...
Having the word icon in there doen't make sense as an icon is a
concept, not a tangible object. I added the word "of" to try to make
it more clear:
"is of a vector graphic format"
> 8.11
> The allowed values are any name of a character set listed in ...
> should be
> The allowed value is any name of a character set from those listed in ...
fixed
> (a user agent are required ...
> should be
> (the user agents are required ...
Fixed.
--
Marcos Caceres
http://datadriven.com.au
e
> string of the specifiers of the feature itself just meant it to be available
> to Web content unconditionally and didn't bother to mint a widget feature
> string?
Like I said, feature was originally intended to request access to
proprietary features designed for widgets (namely BONDI). If the API
just becomes available in the browser, then no feature string is
needed. But yes, we have a potential problem here until we settle on
the security model.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
then it should be free to
do so; if not, it can impose its own constraints so not to crash.
--
Marcos Caceres
http://datadriven.com.au
On 6/1/09 4:40 PM, Henri Sivonen wrote:
On Jun 1, 2009, at 16:44, Marcos Caceres wrote:
On Mon, Jun 1, 2009 at 1:25 PM, Henri Sivonen wrote:
Using a feature element denotes that, at runtime, a widget may
attempt to
access the feature identified by the feature element's name attr
%x4-4FFFD / %x5-5FFFD / %x6-6FFFD
/ %x7-7FFFD / %x8-8FFFD / %x9-9FFFD
/ %xA0000-AFFFD / %xB-BFFFD / %xC-CFFFD
/ %xD-DFFFD / %xE1000-EFFFD
> Authors need to keep path lengths below 250 bytes. Unicode code points can
> require more than one byte to encode, which can result in
> a path whose length is less than 250 characters.
> should be
> Authors need to keep path lengths below 250 bytes. Unicode code points may
> require more than one byte to encode a character, which
> can result in a path whose length is less than 250 characters to be
> represented in more than 250 bytes.
fixed.
> UTF8-chars
> should be
> utf8-chars or utf8-char or something new (after the ABNF is updated) .
Fixed.
--
Marcos Caceres
http://datadriven.com.au
-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
Marcos Caceres
Sent: Monday, June 01, 2009 12:18 PM
To: Marcin Hanclik; public-webapps@w3.org
Subject: Re: [widgets] P&C Last Call comments, versioning
On Mon, Jun 1, 2009 at 12:00 PM, Cameron McCormack
On 6/2/09 12:18 PM, Marcin Hanclik wrote:
Hi Marcos,
No, they are different...
From the interoperability perspective both are "potential interoperability
issues".
You can't dictate those rules in the spec because they are based on
the capability of the device.
Of course, not everything
On 6/2/09 11:39 AM, Marcin Hanclik wrote:
Hi Marcos,
What version of the configuration document format is
denoted by the namespace.
So there is versioning, but it is based on namespace and not on version
attribute.
This is just syntactical issue.
It's more of a conceptual issue with _real
it is too pedantic, but I found this:
> http://dictionary.reference.com/help/faq/language/g58.html
> in
> http://en.wikipedia.org/wiki/Ex_officio#cite_note-3
>
Thanks for the links. I've checked all e.g., and i.e., and all conform
to us-en as required by the w3c.
--
Marcos Caceres
http://datadriven.com.au
widget) may access the API.
> http://bondi.omtp.org/1.0/security/BONDI_Architecture_and_Security_Appendices_v1.0.pdf,
> section B.4.(1|2).
>
Right. This is applicable for BONDI user agents, but not necessarily
user agents that use the W3C's DAP-WG APIs. It is unlikely that Web
Bro
k the user agent ignore an object (e.g., a file or a DOM node)."
> Not sure what it means.
Let me try that again,
"The term in error is used in this Step to mean that an element, or
attribute, or file in a configuration document is non-conforming to
the rules of this specification. How an element, or attribute, or file
is to be treated when it is in error is always given when the term is
used; but will generally require the user agent to ignore any element,
attribute, or file that is in error. To ignore means user agent must
act as if the element, or attribute, or file is not present."
Is that any better?
--
Marcos Caceres
http://datadriven.com.au
elements of the gadget. If it isn't declared, it isn't
> injected, and if you try calling those functions they just aren't there.
>
> What this does make less clear for me is in W:A&E why you'd ever want to
> call "hasFeature()"?
>
I agree.
> To ignore means that the user agent must act as if the element, or attribute,
> or file is not present."
>
Fixed! thanks again Marcin for the detailed review!
--
Marcos Caceres
http://datadriven.com.au
le-extension, attempt ...
I think file is correct here.
> attempt to match the file-extension to one in the first column
> should be
> attempt to match the file-extension to one of the strings in the first column
Fixed
> Comments as above for "Rule for Identifying the media type of a file".
>
As above.
--
Marcos Caceres
http://datadriven.com.au
hink a consistent definition, at least within one document would help in
> comprehending the topic.
I've just made it: "The value of a version attribute is an arbitrary
string (possibly empty)." That's all it is.
--
Marcos Caceres
http://datadriven.com.au
lt start files table.
>
> How to choose the item from that columnt?
I moved the following text from the Default Start Files section, down to step 8:
"When attempting to locate a default start file, a user agent must
attempt to locate a file entry whose file-name matches one of the
default start files based on the order they appear in the default
start files table (from top to bottom). File names must be treated as
case-sensitive."
>
>
> Stopped at Step 8. To be continued.
>
Nice one! nearly at the end :)
--
Marcos Caceres
http://datadriven.com.au
declare a feature, e.g., , and then you can
ask for an pointer to it at runtime:
var foobarator = Bondi.getFeature("foo:bar");
foobarator.crush().kill().destroy();
var barfoo = Bondi.getFeature("bar:foo");
barfoo === underfined; // true
--
Marcos Caceres
http://datadriven.com.au
t is correct. The same would hold for required="TRUE", which would
be "false". Not sure if we should change this or not, or keep it
strict.
> /5/ Rule for Parsing a Non-negative Integer
>
> Couldn't we just refer to some well-established definition, if there is one
> handy? Seems like this must have been done many times before. And what about
> those negative numbers, then? Not needed? :-)
The algorithm is based on HTML5's, but modified to handle " 100px" or
"100 200" (where 100 would be returned). It's how browses handle
i...@width and i...@height. I also don't want to reference more specs,
it's a pain to have to jump around different specs looking for
definitions... especially for little ones like this one.
--
Marcos Caceres
http://datadriven.com.au
. [Widgets-Views]
>
> Widgets 1.0: Media Query Extensions. A. Bersvendsen and M. Caceres.
> Unpublished editors' draft.
>
> Is this the correct reference in terms of the naming (views vs. MQE)?
It's ok for now... we will sort out that mess in the next few weeks.
It's really nothing to worry about.
> I think everything a
I'm going to assume "a" is "awesome" :)
--
Marcos Caceres
http://datadriven.com.au
orry for this. My problem.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
Marcos
iew-diff.html
I made the publication date the 12th of June... though that is highly
optimistic :) Anyway, we can update that when we have a firm date.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
s a blank paragraph between it and
> the 3. number, this differs from 6.
I could not replicate this?
> -
> If the signatures list is not empty, sort the list of signatures by
> the file name field in ascending numerical order (e.g. signature1.xml
> followed by signature2.xml followed by signature3.xml etc).
>
> change "xml etc" to "xml, etc."
Fixed.
--
Marcos Caceres
http://datadriven.com.au
t; XXX algorithms", which seems to be in conflict with section 7 that
> states the algorithm used must be one of algorithms listed in section 6.
> This seems to be an open ended requirement.
I agree.
> Suggestion - Remove the statements in section 7.1. It is down to the
> signer to choose the algorithm to use. If they choose to use a
> non-recommended algorithm they should understand that user agent support
> cannot be guaranteed.
Right. Frederick, wdyt?
--
Marcos Caceres
http://datadriven.com.au
GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org
] On Behalf Of Marcos Caceres
Sent: Monday, June 08, 2009 1:08 PM
To: P
e.,
widget.preference just references whatever the Window storage object
is... I don't have the spec Web Storage spec handy, so I can't
remember what it is called (window.storage?)).
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
to progress the
> collaboration/shared state Widget extensions?
>
I've not looked at this enough to comment, but can you describe what
you have in mind in a bit more detail. Nice work on integrating the
Wave stuff so quickly, btw.
--
Marcos Caceres
http://datadriven.com.au
On Thu, May 7, 2009 at 12:33 PM, wrote:
> On 5.5.2009 13.16, "ext Marcos Caceres" wrote:
>> On Wed, Apr 29, 2009 at 4:16 PM, Robin Berjon wrote:
>>> Assume we have two localisation subdirectories:
>>>
>>> locales/en/
>>> locales/EN/
>
_Security_Appendices_v1.0.pdf
> B.2 specifies more details.
>
I still have no clue what requestFeature() does/means. The again, I
have not read the Bondi spec regarding that.
--
Marcos Caceres
http://datadriven.com.au
e References - This section will be completed as the document
> matures.
>
> Other than the above, what else must be done before we can publish a LCWD of
> the A&E spec?
Need to sort out how Preferences work. Need to also define how read
only preferences work (i.e., what happens when an author tries to set
a preference that is read only).
--
Marcos Caceres
http://datadriven.com.au
sounds a bit prescriptive. We
need to rework this a bit if we want to include it in the
requirements. I think we should discuss this during the F2F.
--
Marcos Caceres
http://datadriven.com.au
other thread Marcos stated that one of the
> benefits of was that if a widget gets exploited, the
> exploited code couldn't get access to any features that the widget
> hadn't enabled using . However this does not seem to be true
> if the exploited code could simply call
27;ve
>>>already launched.
> There is an ongoing debate about requestFeature().
> BONDI spec is approaching both widgets and websites and basically
> requestFeature() is planned to be primarily used only by websites.
>
Ok, that makes sense; but I have serious doubts anyone will implement that.
--
Marcos Caceres
http://datadriven.com.au
n't been activated
> with ? Should there be no function object for frob()? Or should it
> be there but throw upon calling? Or something else.
>
Not there.
> Please specify this.
Right, I think this needs to be specified in the A&E spec but not in packaging.
--
Marcos Caceres
http://datadriven.com.au
ussing this if, as you
said before, it has no relevance to widgets.
--
Marcos Caceres
http://datadriven.com.au
Hi Marcin,
I missed the following:
>
> … ignore this element/attribute. Stop processing this element …
>
> Here, better linking to the preceding “if” could add clarity. A “.” (dot)
> and imperative mode may result in misunderstanding (there are many instances
> of this case).
Can you clarify wha
hem.
>
Understood, but isn't there some way to load them dynamically even if
they are declared?
--
Marcos Caceres
http://datadriven.com.au
On 6/8/09 11:20 PM, Anne van Kesteren wrote:
On Mon, 08 Jun 2009 20:34:14 +0200, Marcos Caceres wrote:
I still have no clue what requestFeature() does/means. The again, I
have not read the Bondi spec regarding that.
On Mon, 08 Jun 2009 20:34:19 +0200, Marcos Caceres wrote:
Yes, that was
2009/6/9 Anne van Kesteren :
> On Tue, 09 Jun 2009 01:38:14 +0200, Marcos Caceres wrote:
>> On 6/8/09 11:20 PM, Anne van Kesteren wrote:
>>> On Mon, 08 Jun 2009 20:34:19 +0200, Marcos Caceres
>>> wrote:
>>>> Yes, that was the design. If requestFeature() i
On 6/9/09 11:58 AM, Anne van Kesteren wrote:
On Tue, 09 Jun 2009 11:32:49 +0200, Marcos Caceres wrote:
Like I said, as far as WebApps is concerned requestFeature() does not
exists. What I meant was the requestFeature() undermines
without addressing the security issues.
I'm getting mor
ll discuss this as part of DAP.
--
Marcos Caceres
http://datadriven.com.au
that
> requestFeature() will be applicable also to widgets. The detailed discussion
> is planned anyway.
>
BONDI is not WebApps. What BONDI decides to do has no bearing here
until it is formally proposed as an input.
--
Marcos Caceres
http://datadriven.com.au
morrow.
Obviously, that won't be in the final draft.
[1] http://www.w3.org/TR/widgets/
--
Marcos Caceres
http://datadriven.com.au
I'm forwarding the following comments on behalf of Martin Nilsson, of
Opera Software, with his permission, to be addressed as part of the LC
review.
Kind regards,
Marcos
==
Section 5.3: Why not mandate all paths to be UTF-8? I really hate the
notion of "If an author chooses to use cp437-c
e, we will assume you have accepted the comments and no
further action is needed. If further action or clarification is needed
on your part, then please let us know ASAP.
Kind regards,
Marcos
On Tue, Jun 2, 2009 at 1:19 PM, Marcos Caceres wrote:
>
>
> On 6/2/09 11:39 AM, Marcin Hanclik w
ifications
> shouldn't try to define conformance beyond what implementers are likely to
> do, it's just a waste of good pixels.
>
> --
> Robin Berjon - http://berjon.com/
> Feel like hiring me? Go to http://robineko.com/
>
>
>
>
>
>
>
--
Marcos Caceres
http://datadriven.com.au
> From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
> Marcos Caceres
> Sent: Tuesday, June 02, 2009 6:47 PM
> To: Marcin Hanclik
> Cc: public-webapps@w3.org
> Subject: Re: [widgets] P&C Last Call comments, 3
>
> On Tue, Jun 2, 2009 at 12:01 PM, Marci
; Could we agree that I will send my confirmations to all my P&C LC emails we
> exchanged and with which I am ok by this Thursday, 18.06?
>
Sure! otherwise, expect an email flood :)
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
e and Robin's additional feedback, I've added the
following to the spec as part of "The Feature Element" section:
"How a user agent makes use of features depends on the user agent's
security policy, hence activation and authorization requirements for
features are beyond the scope of this specification."
Is that satisfactory?
--
Marcos Caceres
http://datadriven.com.au
r specification that is not public and it is not very clear
> what it will include.
>
> Of course, I will wait until ViewModes appears and comment then, since
> currently my input may double someone else's input.
>
I'm unsure how to proceed here. Until we publish a FPWD
On Thu, Jun 4, 2009 at 3:26 PM, wrote:
> On 3.6.2009 18.29, "ext Marcos Caceres" wrote:
> On Wed, Jun 3, 2009 at 12:50 PM, wrote:
>>> "A user agent MAY support the [Widgets-DigSig] specification ..."
>>> And would have written it as:
>>> &q
e those aliases marked as "preferred MIME
name".
>> - Suggest to replace "(a user agent are REQUIRED to support [UTF-8])" with
>> "User agents MUST support [UTF-8]."
I had missed this in the last set of comments. Fixed.
--
Marcos Caceres
http://datadriven.com.au
Just a gentle reminder that the P&C Last Call period ends on 19 June.
Comments after the deadline will not be considered until we are in CR
(or in another Last Call, if need be).
Spec is at:
http://dev.w3.org/2006/waf/widgets/
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
that as everyone seems to converge on HTML as
> the core of their systems, reuse gets easier and easier. If somebody
> did want to repackage an extension as a widget, it should be possible
> to reuse a lot of the code directly.
Yes, I can certainly see that on the code path there would not be much
problem (aside from the proprietary bookmarks, history, etc. APIs).
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
ed to keep
path lengths below 250 bytes. Unicode code points may require more
than one byte to encode a character, which can result in a path whose
length is less than 250 characters but whose size is greater than 250
bytes."
--
Marcos Caceres
http://datadriven.com.au
ns are all in the document and explicitly marked as
definitions (using the dfn tag). I'm going on vacation in 50 mins, so
I don't have time to extract them. Maybe someone on the BONDI side can
write some XSLT magic to extract them out?
--
Marcos Caceres
http://datadriven.com.au
ease provide a URL?
Ah, sorry. I got confused (reading the title of the of the email would
have helped! Thanks a lot GMail!).
The only definition we have is:
"Initialization means a run through the steps for processing a widget
package post installation of a widget."
I'm not sur
On Mon, Jun 15, 2009 at 2:54 PM, Dominique Hazael-Massieux wrote:
> Hi,
>
> I have also noted that the two examples in 7.2 use a wrong namespace
> (w3.org instead of www.w3.org).
Fixed.
--
Marcos Caceres
http://datadriven.com.au
for the
availability of a feature will be required (like testing if an object
is available in JS, etc.). The WG will not be defining what those
methods are, however.
> Without hasFeature(), what does P&C mean?
The definition given in the spec still holds. hasFeature() and the
semanti
st align the text to be either descriptive or all imperative for
> consistency.
>
If you can live with it, I think I will leave this as is.
--
Marcos Caceres
http://datadriven.com.au
ess-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.
>
>
--
Marcos Caceres
http://datadriven.com.au
update the acknowledgments before we republish.
--
Marcos Caceres
http://datadriven.com.au
t of the
preference element, then please send it to the WG for consideration.
--
Marcos Caceres
http://datadriven.com.au
Call:
>> http://www.w3.org/2009/04/16-uwawg-minutes.html#item01
>>
>> No patent disclosures have been made [4].
>>
>> Thank you!
>>
>> Matt Womer
>> UWA Activity Lead
>>
>> [1] http://www.w3.org/2007/uwa/
>> [2] http://www.w3.org/TR/2009/WD-dcontology-20090616/
>> [3]
>> http://www.w3.org/TR/2009/WD-dcontology-20090616/Overview.html#sec-summary-changes
>> [4] http://www.w3.org/2004/01/pp-impl/40755/status
>
>
>
--
Marcos Caceres
http://datadriven.com.au
Comments from Josh Soref (18 June; 18:55:10 +0300 aka #1102)
>
> http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/1102.html
>
> 4. Widgets A&E spec: status; plans for LCWD publication
>
> http://dev.w3.org/2006/waf/widgets-api/
>
> 5. Widgets Update spec: PAG status
>
> http://dev.w3.org/2006/waf/widgets-updates/
>
> 6. AOB
>
>
>
>
--
Marcos Caceres
http://datadriven.com.au
ce between:
{'hello': 'value'}
Or
But using (DOM3) textContent on this would be useless as information
is lost in the following case ('fasdfasd'):
1234 54321
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
Hi Marcin,
For the LC DoC, can I get a quick confirmation that you are satisfied
with the responses of the WG for this thread.
Kind regards,
Marcos
On Fri, May 29, 2009 at 5:17 PM, Marcos Caceres wrote:
>
> For the sake of the disposition of comment, please verify that you are
> satis
e changed the "normalization" behavior so
that the result would now be: "en-us,en-au,en" (i.e., repetitions are
removed from left to right, not from right to left).
> Would 'canonicalization' be a more suitable term here than
> 'decomposition'?
I think both of those terms are scary, so I've just said "would
become" instead of "would decompose".
> /6/ Runtime resolution of localized resources
>
> What specification should describe how a reference to a resource (which
> could be in a localized folder) is resolved at runtime, based on the user's
> language range?
Sorry, I don't understand this question. Can you please rephrase it?
> That is not quite in the domain of the packaging
> specification, given that it is runtime behavior. This functionality is
> sketched in the fallback behavior example, but it is non-normative.
As above.
> Thanks for considering these comments.
Thanks for the detailed review.
--
Marcos Caceres
http://datadriven.com.au
ion where localized and unlocalized elements are gathered in 9.7):
http://dev.w3.org/2006/waf/widgets/
However, can you please confirm that it is all consistent now?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
of processing rules
to include your more precise suggestion:
"This section defines various processing rules, which are a set of
common algorithms used by the steps for processing a widget package."
For the sake of the DoC, please confirm if you are satisfied with the
responses above.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
I
removed 2119 terminology.
> I also think it is bad form to put security precautions in a note.
I understand, but making the security precaution normative would also
result in a non-testable assertion. Do you have a better suggestion as
to what I should do here or should I leave it as is (that is, leave it
as a note)?
--
Marcos Caceres
http://datadriven.com.au
where localized and unlocalized elements are gathered in 9.7):
http://dev.w3.org/2006/waf/widgets/
However, can you please confirm that it is all consistent now?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
d
also have included the following code points as they are not allowed
in file names:
U+000A LINE FEED (LF),
U+000B LINE TABULATION,
U+000C FORM FEED (FF),
U+000D CARRIAGE RETURN (CR).
I've added them.
For the sake of the DoC, is that satisfactory?
--
Marcos Caceres
http://datadriven.com.au
ser that the widget
has been updated.
11. End-User restarts the widget.
So, I don't what would be achieved by removing widget.update() as it
doesn't actually do any "updating". If anything, we need to redefine
widget.update() to make it more useful and powerful.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
hy I thought audio/x-wav would be more appropriate. WDYT?
> An additional column mentioning the format might be nice for readers.
Sorry, by "mentioning the format" do you mean a link to the
specification that defines the format?
--
Marcos Caceres
http://datadriven.com.au
On Wed, Jun 10, 2009 at 5:24 PM, Anne van Kesteren wrote:
> On Wed, 10 Jun 2009 17:20:25 +0200, Marcos Caceres wrote:
>> On Wed, Jun 10, 2009 at 4:57 PM, Anne van Kesteren
>> wrote:
>>> "TO BE WRITTEN, PLEASE IGNORE" if normative material is yet to be
>>&
t would be a
nice feature, it was not identified by the WG as a requirement [1].
For the DoC, please indicate if you are satisfied with this response
from the WG.
[1] http://www.w3.org/TR/widgets-reqs/
--
Marcos Caceres
http://datadriven.com.au
etAttention() could perhaps
> be clarified a little
>
> I'll work on some of those tomorrow, feedback is welcome in the meantime.
>
> --
> Robin Berjon - http://berjon.com/
> Feel like hiring me? Go to http://robineko.com/
>
>
>
>
>
>
>
--
Marcos Caceres
http://datadriven.com.au
t string, or file-name, or
folder-name is not reserved for the purpose of this specification.
]]
Is that not clear enough? Can you help me make that more clear?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
On 6/30/09 7:49 PM, timeless wrote:
On Tue, Jun 30, 2009 at 4:24 PM, Marcos Caceres wrote:
Or use index.html in other directories?
Nothing. Treated as an arbitrary file - this was already implied in
the spec. To make this explicitly clear, I've added:
speaking of which,
do
message. The means of notifying the end-user, and the wording of the
localized error message, is left to the discretion of implementers.
In the case the UA is a CC, it must inform the author that the Zip
archive is an invalid Zip archive.
]]
Is that any better?
--
Marcos Caceres
http://datadriven.com.au
lace any sequences of space characters (in any order)
with a single U+0020 SPACE character."
Functionally, I don't believe this change either algorithm, so this
will be treated as an editorial comment.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
way than the algorithm
> just before it. This would also do well with a consistent style I think.
>
I tried to make it more consistent with the previous algorithm. Please
let me know if it is ok now. If not, please feel free to suggest
better wording.
--
Marcos Caceres
http://datadriven.com.au
wed in the process document). If no one implements it, then we
will remove it.
> textContent is an attribute, not a property. In bindings it might turn into a
> property, but that is not relevant I think.
>
Fixed.
--
Marcos Caceres
http://datadriven.com.au
ear or close enough?
> Also, following the definition of file-extension _none_ of the entries in the
> table would be matched. I.e. file-extension requires a leading dot.
>
Fixed.
--
Marcos Caceres
http://datadriven.com.au
2009/6/10 Anne van Kesteren :
> I think the first paragraph here can be dropped as you cannot test it.
> Optionally you could rephrase it as a non-normative note.
>
Changed this to a note.
--
Marcos Caceres
http://datadriven.com.au
used for that
> purpose,
> specifically because hasFeature() is used in DOM to check for - static IMHO -
> existence of some module/functionality/feature, and feature loading that is
> meant within P&C is of dynamic nature.
>
hasFeature was dropped at the F2F.
> So I suggest removing that sentence from the note in order not to create a
> de-facto standard.
Agreed. What do you think of the text above?
--
Marcos Caceres
http://datadriven.com.au
901 - 1000 of 1416 matches
Mail list logo
