Re: Promises - review of use in Network Service Discovery draft?

Hi Frederick, Rich,  
Quick update, though not particularly helpful right now: the TAG will write a "how to use Promises in specs" in the coming weeks. Please subscribe yourself to watch the following repo on GH:

https://github.com/w3ctag/promises-spec-text

This will hopefully help all working groups in a scalable manner!  

-- 
Marcos Caceres


On Wednesday, July 24, 2013 at 5:02 PM, Marcos Caceres wrote:

> Hi Frederick, 
> 
> On Wednesday, July 24, 2013 at 4:13 PM, Frederick.Hirsch@nokia.com (mailto:Frederick.Hirsch@nokia.com) wrote:
> 
> > Dear TAG members (cc'd DAP):
> > 
> > The Device API working group (DAP) is working on a specification 'Network Service Discovery'.
> > 
> > "This specification defines a mechanism for an HTML document to discover and subsequently communicate with HTTP-based services advertised via common discovery protocols within the current network."
> > 
> > <https://dvcs.w3.org/hg/dap/raw-file/tip/discovery-api/Overview.html>
> > 
> > Rich Tibbett, the editor, has updated the editors draft to use 'Promises' as noted in his message below.
> > 
> > Would members of the TAG that have experience with Promises please (if possible) review the Promises usage in this editors draft and let the DAP WG know of any concerns or best practices that we need to consider (or confirm that our usage looks good)?
> 
> The best list for that feedback is actually public-script-coord@w3.org (mailto:public-script-coord@w3.org). I would recommend you start there. Otherwise, please see the Task Scheduler API Specification [1], which has been reviewed by both Alex and Annevk - and they said that the way that spec uses promises in prose and in WebIDL is correct. 
> 
> Regardless, I've added the Network Discovery spec to the TAG's spec review list. Thanks for bringing it to the TAG's attention:
> https://github.com/w3ctag/spec-reviews/issues/8
> 
> 
> [1] http://web-alarms.sysapps.org/

Received on Thursday, 25 July 2013 17:26:35 UTC