W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2014

[network info] CfC to Shelve Network Information API concluded; plan to publish W3C Note, also Requirements Note publication?

From: <Frederick.Hirsch@nokia.com>
Date: Tue, 18 Mar 2014 20:49:11 +0000
To: <public-device-apis@w3.org>, <w3c@marcosc.com>, <mounir@lamouri.fr>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <579014FA-ABD3-4CF3-AD12-8F8AB4AD7D3F@nokia.com>
The CfC to shelve the Network Information API has concluded without objection, so we are now Resolved to shelve this specification.

To be clear, this means we will publish a W3C note, that does not have the specification content, but does have the links to the previous version, and a status section that clearly states the document is shelved.
An example is the messaging API shelving publication at http://www.w3.org/TR/messaging-api/

For the status section, apart from the ReSpec generated content, I suggest the following text (with appropriate links).

[[

The Network Information API is intended to provide information to web applications regarding the underlying network connection to enable a variety of use cases, such as enabling user control over activities based on network cost or performance, for example. The working group does not have consensus on the appropriate model, whether it should attempt to estimate bandwidth or indicate the type of network, for example. The Device APIs Working Group has agreed to discontinue work on this API until new input regarding the requirements and technical approach are available. 

The Charter of the Device APIs Working Group continues to include this work as "in scope", so the working group may decide to resume work if warranted by new information.

]]

I suggest we plan to publish on 27 March. 

Mounir, are you able to prepare a shelving publication draft? Please let me know - if not, I’ll do it.

I also think this might be a good time to publish a W3C Note in TR space for the requirements draft that Marcos created at  http://w3c-webmob.github.io/netinfo-usecases/ . If we do so, then the shelved Network Information API could reference it.  Marcos, do you agree with DAP publishing the requirements document  as a W3C Note in TR space, and if so can you please prepare a publication draft?

All, Please indicate any comment on the shelving text above as well as publication plans, on the list please.

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group


On Feb 18, 2014, at 2:47 PM, Hirsch Frederick (Nokia-CTO/Boston) <Frederick.Hirsch@nokia.com> wrote:

> 
> This is a Call for Consensus (CfC) to shelve the Network Information API specification.
> 
> Shelving in this case means that we are not sure the specification will advance along the lines the draft indicates. As a result we want to be clear to everyone that we may not advance the specification or that we may change the approach.  This does not mean that we have decided not to ever advance the specification, just that there is a question as to the direction and/or progression at this point. 
> 
> To shelve we will publish a W3C Note indicating that the document is shelved, with the following Status Section text and with all specification detail removed (consistent with earlier shelving, see http://www.w3.org/TR/messaging-api/ but taking into account AC forum feedback)
> 
> [[
> 
> Work on this document has been discontinued and it should not be referenced or used as a basis for implementation.
> 
> The Network Information API was defined to enable API access to network information. While working on this specification the Device APIs Working Group encountered issues related to estimating network bandwidth and with providing useful information, deciding to discontinue work until better understanding of the use cases, requirements and approach are available.
> 
> The Charter of the Device APIs Working Group continues to include this work as "in scope", so the working group could decide to resume work if warranted by new information.
> 
> The previous published version containing the most recent content is available at the “Previous Version” link noted above.
> 
> This document was published by the Device APIs Working Group as a Working Group Note. If you wish to make comments regarding this document, please send them to public-device-apis@w3.org (subscribe, archives). All comments are welcome.
> 
> Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
> 
> This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
> 
> ]]
> 
> Proposed publication date, Thursday 27 February 2014.
> 
> Please respond to this CfC (including the proposed status text above) to the public-device-apis@w3.org mail list by 25 February 2014 (next Tuesday).   Silence will be considered as agreement with the proposal. If you support this CfC, a positive response is preferred and encouraged, even if a +1.
> 
> If there is  agreement, the following steps will be next
> 
> 1. Editors (Mounir) to prepare draft Note for publication, including validity and link checks. Proposed publication date - 27 February 2014
> 
> 2. On DAP home page move from active roadmap [1]  to the list of shelved specifications [2].
> 
> 3 On the TR page, this document should be listed under the "Obsolete" section with status “Retired"
> 
> 
> Thanks
> 
> regards, Frederick
> 
> Frederick Hirsch, Nokia
> Chair, W3C DAP Working Group
> 
> 
> [1] http://www.w3.org/2009/dap/#roadmap
> 
> [2] http://www.w3.org/2009/dap/#shelved
> 
> 
> 
> 
Received on Tuesday, 18 March 2014 20:50:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:02 UTC