Re: Issue 12: Javascript API to return promises instead of nothing.

On Tuesday, January 24, 2017 8:45:56 AM CET Schunter, Matthias wrote:
> Hi Roy,
> 
> PS: As far as I know, W3C now allows to change the spec while iterating
> in the candidate recommendation state. I.e. no need to go back to WD
> even if we introduce changes to the API.

Yes, but the exact process depends on the kind of changes:

Republishing a CR with only editorial changes simply requires a WG 
decision and can be done as often as the WG wishes. It needs the 
Webmaster's help, so only on Tuesdays and Thursdays, but otherwise no 
need to talk to anybody.

The same holds for republishing a CR after removing features that were 
already marked explicitly as "at risk".

The WG can also decide at any time to republish the CR as a WD.

But republishing a CR with "substantive changes" requires writing a new 
Transition Request (with all the usual things that go into such a 
request) and waiting for Director's approval. If the changes are small, 
such approval is likely to be quick, though.

"Substantive changes" are changes that affect conformance or add new 
features: i.e., any changes that can make an implementation that used to 
be conforming now non-conforming, or vice-versa.


I haven't looked at the change itself, but based on Roy's e-mail below, 
it seems to be a change that affects conformance. And so it requires 
writing a new Transition Request if we want the updated spec to be a CR.

I can help writing such a Transition Request, but I can't do it on my 
own. I don't know enough about the history of the spec and its 
implementations yet.

> 
> -----Original Message-----
> From: Roy T. Fielding [mailto:fielding@gbiv.com]
> Sent: Tuesday, January 24, 2017 9:15 AM
> To: Matthias Schunter (Intel Corporation) <mts-std@schunter.org>
> Cc: public-tracking@w3.org (public-tracking@w3.org)
> <public-tracking@w3.org> Subject: Re: Issue 12: Javascript API to
> return promises instead of nothing.
> 
> Umm, the downside is that it is a normative change to the API, which
> means we go back to WD status and have zero implementations.
> 
> I want commitments from browsers to implement this change before we
> make it. Right now we should assume the entire API will be removed.
> 
> ....Roy
> 
> > On Jan 24, 2017, at 3:20 AM, Matthias Schunter (Intel Corporation)
> > <mts-std@schunter.org> wrote:
> > 
> > Hi Folks,
> > 
> > 
> > Sites can use our javascript API to register site-wide and web-wide
> > exceptions. Currently the corresponding calls do not return any
> > results.
> > 
> > Mike proposed to return promises. These would allow the engine to
> > call-back to a site once it has processed a javascript request.  This
> > renders our API more asynchronous.
> > 
> > IMHO there does not be a downside to this proposal. Mike posted the
> > changed javascript API here: https://github.com/w3c/dnt/issues/12
> > 
> > 
> > Unless somebody objects before our next call, I suggest to introduce
> > this change to our API.
> > 
> > 
> > Regards,
> > 
> > matthias
> 
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928



Bert
-- 
  Bert Bos                                ( W 3 C ) http://www.w3.org/
  http://www.w3.org/people/bos                               W3C/ERCIM
  bert@w3.org                             2004 Rt des Lucioles / BP 93
  +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France