W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2012

RE: Network Information API

From: Sun, Dan <Dan.Sun@VerizonWireless.com>
Date: Thu, 21 Jun 2012 15:51:53 -0400
To: "'SULLIVAN, BRYAN L'" <bs3131@att.com>, "'public-device-apis@w3.org'" <public-device-apis@w3.org>
Message-ID: <E1ShnQS-00016h-KC@lisa.w3.org>
Hi Bryan,

Thanks for the history!
It would be clear for people reading the Spec without history knowledge if the API Introduction can clarify the scope with this information.


From: SULLIVAN, BRYAN L [mailto:bs3131@att.com]
Sent: Thursday, June 21, 2012 3:22 PM
To: Sun, Dan; 'public-device-apis@w3.org'
Subject: RE: Network Information API

Those characteristics were originally in scope for the API (at least when it was part of the System Info API), but removed in the process of switching from the programmatic-style APIs (more focused on installed apps e.g. Widgets as in BONDI/WAC) to the browser-compatible APIs that we currently have (not needing a permissions framework, thus providing access to a much more limited set of attributes).

We believe those characteristics are still quite important and support their inclusion in some API, but that may have to occur through the SysApps WG now. For the meantime, the API initiatives outside W3C (e.g. WAC, Tizen, etc) continue to provide good examples of how those attributes can be exposed:
https://developer.tizen.org/documentation (see the SystemInfo API)

Bryan Sullivan

From: Sun, Dan [mailto:Dan.Sun@VerizonWireless.com]
Sent: Thursday, June 21, 2012 12:03 PM
To: 'public-device-apis@w3.org'
Subject: Network Information API


See two versions of this API [1] and [2]. What is the relation between these two?

[1] "The Network Information API", Suresh Chitturi, Robin Berjon, http://www.w3.org/TR/2011/WD-netinfo-api-20110607/
[2] "The Network Information API", Mounir Lamouri, http://dvcs.w3.org/hg/dap/raw-file/tip/network-api/Overview.html

Regardless, I would expect this API to expose the information of the camped network like MCC, MNC, signal strength, Roaming state, Cell ID, etc. besides the connection type (WiFi, GSM, UMTS, CDMA, LTE, etc.) as oppose to the Device Capabilities API to expose the network types supported by hosting device. Any thought?

Received on Thursday, 21 June 2012 19:52:24 UTC

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