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

Telephony API proposal from Intel

From: Kis, Zoltan <zoltan.kis@intel.com>
Date: Mon, 31 Dec 2012 16:46:12 +0200
Message-ID: <CANrNqUc1PTOGjVdWO4ZfV07M6OpPr6TY9PgDLY-shbqQf8bVKw@mail.gmail.com>
To: public-sysapps@w3.org
Hello,

Intel's proposal for the Telephony API (as a show case for what use
cases we would like to discuss), can be found on

http://htmlpreview.github.com/?https://github.com/otcshare/sysapps/blob/master/proposals/Telephony_Intel/Telephony.html
(until the pull request is merged into https://github.com/sysapps/sysapps ).

As the Abstract tells it, it is based on [1] and adds support for for
multiple telephony services, video calls, conference calls, call
migration between services, audio and video control, etc.

The goal is to discuss about these use cases and proposed solution
patterns, and get as much consensus as possible.

Main topics of discussion:
- One point of disagreement in [1] was how to (if at all) handle call
state transitions in the API implementation. After 40+ emails we
decided to bring it to public discussion... This is an evergreen
discussion between dialer implementers and telephony HW/middleware
developers, and I have seen similar discussions a few times. It will
not be easy. This proposal states my take on this (from the side of
having experience on telephony middleware and native dialers),
supported by the telephony experts I have asked, but it would be good
to know other opinions, too.

- Supporting multiple SIM and conference calls brings in the topic of
telephony services, which overlaps with messaging services.

- How audio and video should be controlled from this API (from the
dialer user interface handling point of view), if at all. Even if
decided it should not be handled from here, we need to discuss where
it will be. It is needed for implementing dialers. Also, audio and
video policies vs notifications popped up in earlier discussions,
which raises the question to Adam and Wonsuk if should we also target
designing a Notification API? At least Mozilla and Intel seem to be
interested in it (and working on it, apparently along similar design
objectives).

Happy New Year to everyone!

[1] http://sysapps.github.com/sysapps/proposals/Telephony/Telephony.html

Best regards,
Zoltan
Received on Monday, 31 December 2012 14:46:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 31 December 2012 14:46:41 GMT