You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2014/02/19 21:48:47 UTC

w3c network information api shelved

http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0042.html

our repo: https://github.com/apache/cordova-plugin-network-information

Good thing we never updated it...

Re: w3c network information api shelved

Posted by Shazron <sh...@gmail.com>.
Actually with iOS 7 CTTelephonyNetworkInfo.currentRadioAccessTechnology
(their API docs haven't been updated yet, strange, but it is in the public
header) you can discern which type of cellular radio signal it is now. We
haven't updated our implementation because it is iOS 7 only.

currentRadioAccessTechnology (NSString*) - The current radio access
technology the device is registered with. May be NULL if device is not
registered on any network.

³you¹re on cellular (unspecified type)² on most of the platforms.
>
> Everyone was demanding something more specific than that, and yet none of
> the OS vendors are offering it, and in reality nothing useful can be done
> w/ it.
>

Re: w3c network information api shelved

Posted by Ken Wallis <kw...@blackberry.com>.
Standards are certainly valuable, when bolstered by real world use cases
and data.

Specifically in relation to the networking API, it really is of somewhat
dubious value even if reporting everything correctly, as connectivity at
any given instant has no real bearing on connectivity status in the next
instant (the classic elevator example). It can be used for heuristics but
isn’t necessarily reliable in the mobile world.

-- 
Ken Wallis
Senior Product Manager - WebWorks
BlackBerry
650-620-2404





-----Original Message-----
From: Brian LeRoux <b...@brian.io>
Reply-To: "dev@cordova.apache.org" <de...@cordova.apache.org>
Date: Wednesday, February 19, 2014 at 2:26 PM
To: "dev@cordova.apache.org" <de...@cordova.apache.org>
Subject: Re: w3c network information api shelved

>Josh I appreciate your perspective but getting more inputs and outputs
>from
>Cordova and W3C is not a bad thing. Certainly there is a perception of how
>standards work.  would argue they haven't been working very well: big up
>front designs usually fail. Anyhow I welcome prototyping and discussion to
>make them, and us, better.
>
>
>On Wed, Feb 19, 2014 at 1:45 PM, Josh Soref <js...@blackberry.com> wrote:
>
>> Shazron wrote:
>>  >
>> http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0042.html
>>  >
>>  > our repo: 
>>https://github.com/apache/cordova-plugin-network-information
>>  >
>> > Good thing we never updated itŠ
>>
>> Based on the quirks in the documentation, it looks like the API is
>>mostly
>> useless.
>>
>>
>> ³you¹re on cellular (unspecified type)² on most of the platforms.
>>
>> Everyone was demanding something more specific than that, and yet none
>>of
>> the OS vendors are offering it, and in reality nothing useful can be
>>done
>> w/ it.
>>
>> Removing it is the right things.
>>
>>
>> On Wed, Feb 19, 2014 at 1:00 PM, Brian LeRoux <b...@brian.io> wrote:
>> > I've been encouraging w3c members to bring these issue to us and to
>>help
>> >us
>> > work through implementation. The relationship so far has been more
>>onus
>> >on
>> > us and that was probably not optimal for getting things done.
>>Hopefully
>> >we
>> > see them chime in.
>>
>>
>> Brian, that isn¹t how it works. To have a specification, you have to
>>have
>> real use cases, and real implementations, not toy use cases and not toy
>> implementations.
>>
>> The forum for discussing standards is W3C. It¹s an open email list. It¹s
>> more responsive than the Cordova project (where pull requests often get
>> lost for months). And all feedback is tracked and will be addressed.
>>
>> On 2/19/14, 4:05 PM, "Shazron" <sh...@gmail.com> wrote:
>>
>> > From that w3c thread, I came across this w3c github org:
>> > https://github.com/w3c-webmob
>> >
>> > Seems they are gathering data on what's out there (including Cordova
>> >APIs).
>>
>> Sure. If someone can come up with actual Use Cases, perhaps an API might
>> need to be created, but it¹s most likely the case that other APIs
>>already
>> exist (Video, Streaming, WebPerf) or will be created in those areas for
>> 80-90% of the real Use Cases, and in general specifications and software
>> should cover the 80-90%, not the 1%.
>>
>>


Re: w3c network information api shelved

Posted by Brian LeRoux <b...@brian.io>.
Josh I appreciate your perspective but getting more inputs and outputs from
Cordova and W3C is not a bad thing. Certainly there is a perception of how
standards work.  would argue they haven't been working very well: big up
front designs usually fail. Anyhow I welcome prototyping and discussion to
make them, and us, better.


On Wed, Feb 19, 2014 at 1:45 PM, Josh Soref <js...@blackberry.com> wrote:

> Shazron wrote:
>  >
> http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0042.html
>  >
>  > our repo: https://github.com/apache/cordova-plugin-network-information
>  >
> > Good thing we never updated itŠ
>
> Based on the quirks in the documentation, it looks like the API is mostly
> useless.
>
>
> ³you¹re on cellular (unspecified type)² on most of the platforms.
>
> Everyone was demanding something more specific than that, and yet none of
> the OS vendors are offering it, and in reality nothing useful can be done
> w/ it.
>
> Removing it is the right things.
>
>
> On Wed, Feb 19, 2014 at 1:00 PM, Brian LeRoux <b...@brian.io> wrote:
> > I've been encouraging w3c members to bring these issue to us and to help
> >us
> > work through implementation. The relationship so far has been more onus
> >on
> > us and that was probably not optimal for getting things done. Hopefully
> >we
> > see them chime in.
>
>
> Brian, that isn¹t how it works. To have a specification, you have to have
> real use cases, and real implementations, not toy use cases and not toy
> implementations.
>
> The forum for discussing standards is W3C. It¹s an open email list. It¹s
> more responsive than the Cordova project (where pull requests often get
> lost for months). And all feedback is tracked and will be addressed.
>
> On 2/19/14, 4:05 PM, "Shazron" <sh...@gmail.com> wrote:
>
> > From that w3c thread, I came across this w3c github org:
> > https://github.com/w3c-webmob
> >
> > Seems they are gathering data on what's out there (including Cordova
> >APIs).
>
> Sure. If someone can come up with actual Use Cases, perhaps an API might
> need to be created, but it¹s most likely the case that other APIs already
> exist (Video, Streaming, WebPerf) or will be created in those areas for
> 80-90% of the real Use Cases, and in general specifications and software
> should cover the 80-90%, not the 1%.
>
>

Re: w3c network information api shelved

Posted by Josh Soref <js...@blackberry.com>.
Shazron wrote:
 > http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0042.html
 >
 > our repo: https://github.com/apache/cordova-plugin-network-information
 >
> Good thing we never updated itŠ

Based on the quirks in the documentation, it looks like the API is mostly
useless.


³you¹re on cellular (unspecified type)² on most of the platforms.

Everyone was demanding something more specific than that, and yet none of
the OS vendors are offering it, and in reality nothing useful can be done
w/ it.

Removing it is the right things.


On Wed, Feb 19, 2014 at 1:00 PM, Brian LeRoux <b...@brian.io> wrote:
> I've been encouraging w3c members to bring these issue to us and to help
>us
> work through implementation. The relationship so far has been more onus
>on
> us and that was probably not optimal for getting things done. Hopefully
>we
> see them chime in.


Brian, that isn¹t how it works. To have a specification, you have to have
real use cases, and real implementations, not toy use cases and not toy
implementations.

The forum for discussing standards is W3C. It¹s an open email list. It¹s
more responsive than the Cordova project (where pull requests often get
lost for months). And all feedback is tracked and will be addressed.

On 2/19/14, 4:05 PM, "Shazron" <sh...@gmail.com> wrote:

> From that w3c thread, I came across this w3c github org:
> https://github.com/w3c-webmob
>
> Seems they are gathering data on what's out there (including Cordova
>APIs).

Sure. If someone can come up with actual Use Cases, perhaps an API might
need to be created, but it¹s most likely the case that other APIs already
exist (Video, Streaming, WebPerf) or will be created in those areas for
80-90% of the real Use Cases, and in general specifications and software
should cover the 80-90%, not the 1%.


Re: w3c network information api shelved

Posted by Shazron <sh...@gmail.com>.
>From that w3c thread, I came across this w3c github org:
https://github.com/w3c-webmob

Seems they are gathering data on what's out there (including Cordova APIs).


On Wed, Feb 19, 2014 at 1:00 PM, Brian LeRoux <b...@brian.io> wrote:

> I've been encouraging w3c members to bring these issue to us and to help us
> work through implementation. The relationship so far has been more onus on
> us and that was probably not optimal for getting things done. Hopefully we
> see them chime in.
>
>
> On Wed, Feb 19, 2014 at 12:48 PM, Shazron <sh...@gmail.com> wrote:
>
> > http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0042.html
> >
> > our repo: https://github.com/apache/cordova-plugin-network-information
> >
> > Good thing we never updated it...
> >
>

Re: w3c network information api shelved

Posted by Brian LeRoux <b...@brian.io>.
I've been encouraging w3c members to bring these issue to us and to help us
work through implementation. The relationship so far has been more onus on
us and that was probably not optimal for getting things done. Hopefully we
see them chime in.


On Wed, Feb 19, 2014 at 12:48 PM, Shazron <sh...@gmail.com> wrote:

> http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0042.html
>
> our repo: https://github.com/apache/cordova-plugin-network-information
>
> Good thing we never updated it...
>