Re: New Progress Events editor's draft

2008-06-17 Thread Michael(tm) Smith
Sam Weinig <[EMAIL PROTECTED]>, 2008-06-17 07:34 -0700: > On Jun 17, 2008, at 3:45 AM, Michael(tm) Smith wrote: >> Note that all of the Web API WG drafts are in this tree: >> >> http://dev.w3.org/2006/webapi/ >> >> And the WAF WG drafts (including Access-Control spec) are here: >> >> http://dev.

Re: New Progress Events editor's draft

2008-06-17 Thread Sam Weinig
On Jun 17, 2008, at 3:45 AM, Michael(tm) Smith wrote: Hi Mark, You can find the editor's draft of the progress-events doc here: http://dev.w3.org/2006/webapi/progress/Progress.html That's actually a direct link to the latest CVS source, so if/when it gets updated, it'll be immediately avai

Re: New Progress Events editor's draft

2008-06-17 Thread Mark Birbeck
Many thanks, Mike. 2008/6/17 Michael(tm) Smith <[EMAIL PROTECTED]>: > Hi Mark, > > You can find the editor's draft of the progress-events doc here: > > http://dev.w3.org/2006/webapi/progress/Progress.html > > That's actually a direct link to the latest CVS source, so if/when > it gets updated, i

Re: New Progress Events editor's draft

2008-06-17 Thread Michael(tm) Smith
Hi Mark, You can find the editor's draft of the progress-events doc here: http://dev.w3.org/2006/webapi/progress/Progress.html That's actually a direct link to the latest CVS source, so if/when it gets updated, it'll be immediately available there. Note that all of the Web API WG drafts are i

Re: New Progress Events editor's draft

2008-06-17 Thread Mark Birbeck
Hi Chaals, Would you mind providing the link? I'm sure it's in an easy to find place, but I'm not yet familiar with the spec locations yet. Thanks. Mark On Tue, Jun 17, 2008 at 10:45 AM, Charles McCathieNevile <[EMAIL PROTECTED]> wrote: > > Hi folks, > > I have produced a new editor's draft [1

New Progress Events editor's draft

2008-06-17 Thread Charles McCathieNevile
Hi folks, I have produced a new editor's draft [1] that incorporates a bunch of the feedback I have on the Public Working Draft. It notes, rather than provides a resolution for, the new (or recycled) issues I raised on defining an eventType for document.createEvent and on where to define w