On Mon, Feb 23, 2009 at 12:42 AM, Francis Irving <[email protected]>wrote:
> This is interesting, but I'm confused a bit here... > > For location information, how does this compare to the W3C spec? Which > I'm hoping will soon be implemented on phone browsers. > > http://dev.w3.org/geo/api/spec-source.html > I honestly don't know, and I struggle to see how a browser spec intersects with SS7-speaking application servers other than through GET requests, or really where W3C comes in. Is the OneAPI for use from normal websites, or more for use from > mobile phone appliations (in Java, or whatever)? It's a RESTful Web service - it shouldn't matter. It should provide data to anything that authenticates validly to a registered endpoint. There's a SOAP interface as well if you care. > Can you give examples for each of the main capabilities of > the API? > Location - get location of (e164 phone number) and do stuff with it charging - could a normal website, say, charge somebody asking it from > a mobile phone to use a particular feature? This is very much TODO at the moment as it involves interoperator settlement. > messaging - can a website send an SMS from the user's phone if they > are browsing from the phone? Yes > location - (presumably answered above) > user context - what is this? > Things like what device/capabilities/recent calls - big privacy and operational issues yet to work out. > > When will it likely work on most GSM operators? > Already operational on VF, Telenor, Telefonica/O2, TIM and some others, plus an emulator sandbox.
_______________________________________________ Mailing list [email protected] Archive, settings, or unsubscribe: https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
