W3C home > Mailing lists > Public > public-coremob@w3.org > July 2012

RE: Network Information Use Cases

From: Josh Soref <jsoref@rim.com>
Date: Thu, 5 Jul 2012 21:26:30 +0000
To: Core Mobile <public-coremob@w3.org>
Message-ID: <957F1ECDA90E004B8DBDE23CFC94E3A33A4CD64A@XMB103ECNC.rim.net>
Dan Sun wrote:
> Please refer to SysApps WG Charter [1] about Network Interface API or do I
> misunderstand it?

You're referencing a vaporware specification. Core Mob has agreed to only reference W3 Specifications that are published (or very close to published).
The Network API that people are talking about is a DAP deliverable that's very close to done, not a SysApps Charter potential deliverable for a WG that's merely nascent.

> Forget the Adaptive Video Streaming, I was a little hesitate to use that term in
> the use case too ... The point is Network Information API can enable or improve
> certain implementations. In above use cases, it improves user experience
> before the real Adaptive streaming API is available.

The video APIs will exist before anything is published by SysApps. So you'll need another use case.

And note that we're only asking for UCs to justify referencing existing specifications. You can't reference non-existent specifications, such as SysApps deliverables. You can certainly take those UCs to SysApps and work to ensure that their deliverables address them.

> Why not expose this simple API to do so? Native apps have relied on such API.

To do which? And where. CoreMob is interested in suggesting browsers implement standards that have been standardized.

If you want DNS lookups, or reverse DNS, then sure, you could ask SysApps for that feature. And I'd hope they'd provide it, it's certainly a reasonable request.

However, today, for most purposes a simple WebService can expose the necessary API to the WebApp. If you show actual Web Applications using that feature, then it's an easier sell to provide a browser API for it...

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Thursday, 5 July 2012 21:27:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 April 2013 17:36:47 UTC