W3C home > Mailing lists > Public > public-sysapps@w3.org > October 2012

Re: Telephony API draft

From: Göran Eriksson <gaperik@gmail.com>
Date: Wed, 24 Oct 2012 15:27:55 +0200
Message-Id: <9F07EA5A-01D7-4185-BFFB-167EAA07891C@gmail.com>
Cc: "public-sysapps@w3.org" <public-sysapps@w3.org>
To: Mounir Lamouri <mounir@lamouri.fr>
Hi

Perhaps a stupid question but may I ask about the assumptions around the implementation of the API: do You assume it to be directly tied to the telephony stack on the modem- be that a CS Telephony stack or an IMS based- or will there be a layer beneath allowing the user/ developer to pick underlying provider, similar to the approach in some Android API's?

Regards
GE

Sent from my iPad

On 24 okt 2012, at 13:46, Mounir Lamouri <mounir@lamouri.fr> wrote:

> On 10/22/2012 03:53 PM, Kis, Zoltan wrote:
>> Hello,
>> 
>> A side-question. Can implementations use telephony URI's [1][2] or just
>> phone numbers?
>> 
>> This is more of an implementation issue, since the signature for both is
>> the same (DOMString).
>> However, the spec should be explicit about allowing it or not.
>> 
>> I vote for allowing it, as it would help handling telephony services and
>> conference calls with a much simpler API (I have made an experimental
>> draft with both tel:// URI's and explicit objects).
> 
> I'm not sure why tel:// should be accepted in the API. As far as I see
> it, the API should be used to call real phone numbers.
> 
> The only way I see tel:// being related to this API is if there is a
> tel:// link on a web page. Then, a user could click on it and somehow
> the system could open an app that would parse the link and do what
> should be done with the number. However, the API would only get the raw
> number.
> 
> --
> Mounir
> 
Received on Wednesday, 24 October 2012 13:28:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 24 October 2012 13:28:29 GMT