RE: Is Quota Management API ready for First Public Working Draft?

2012-05-31 Thread SULLIVAN, BRYAN L
I support the FPWD publication.

Thanks,
Bryan Sullivan 

-Original Message-
From: Arthur Barstow [mailto:art.bars...@nokia.com] 
Sent: Tuesday, May 29, 2012 6:40 AM
To: ext Kinuko Yasuda; WebApps WG
Subject: Is Quota Management API ready for First Public Working Draft?

Hi Kinuko, All - what are people's thoughts on whether or not the Quota 
Management API spec is ready for First Public Working Draft?

A rule of thumb for FPWD is that the ED's scope should cover most of 
the expected functionality although the depth of some functionality may 
be very shallow, and it is OK if there are open bugs/issues.

-Thanks, Art

On 5/29/12 12:30 AM, ext Kinuko Yasuda wrote:
 On Wed, May 23, 2012 at 9:32 PM, Anne van Kesteren ann...@annevk.nl 
 mailto:ann...@annevk.nl wrote:

 On Wed, May 23, 2012 at 2:05 PM, Kinuko Yasuda
 kin...@chromium.org mailto:kin...@chromium.org wrote:
  https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html

 I noticed something else. StorageInfo is marked as Supplemental and
 NoInterfaceObject, but I do not think either is meant to be used here.
 Supplemental has been replaced by partial interface (rather than
 [Supplemental] interface), but is only supposed to be used if this
 is not the original definition (and I do not think StorageInfo is
 defined elsewhere). NoInterfaceObject is used prevent certain
 interfaces from being prototyped, but I do not think we want that here
 either.


 Oops.. thanks very much for pointing out those mistakes.
 You're right, neither Supplemental nor NoInterfaceObject look 
 appropriate here.
 I dropped them from the draft.

 https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html

 Thanks!





Is Quota Management API ready for First Public Working Draft?

2012-05-29 Thread Arthur Barstow
Hi Kinuko, All - what are people's thoughts on whether or not the Quota 
Management API spec is ready for First Public Working Draft?


A rule of thumb for FPWD is that the ED's scope should cover most of 
the expected functionality although the depth of some functionality may 
be very shallow, and it is OK if there are open bugs/issues.


-Thanks, Art

On 5/29/12 12:30 AM, ext Kinuko Yasuda wrote:
On Wed, May 23, 2012 at 9:32 PM, Anne van Kesteren ann...@annevk.nl 
mailto:ann...@annevk.nl wrote:


On Wed, May 23, 2012 at 2:05 PM, Kinuko Yasuda
kin...@chromium.org mailto:kin...@chromium.org wrote:
 https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html

I noticed something else. StorageInfo is marked as Supplemental and
NoInterfaceObject, but I do not think either is meant to be used here.
Supplemental has been replaced by partial interface (rather than
[Supplemental] interface), but is only supposed to be used if this
is not the original definition (and I do not think StorageInfo is
defined elsewhere). NoInterfaceObject is used prevent certain
interfaces from being prototyped, but I do not think we want that here
either.


Oops.. thanks very much for pointing out those mistakes.
You're right, neither Supplemental nor NoInterfaceObject look 
appropriate here.

I dropped them from the draft.

https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html

Thanks!