RE: Telephony API, new version

Hi. Zoltan, editors and all.

> -----Original Message-----
> From: Kis, Zoltan [mailto:zoltan.kis@intel.com]
> Sent: Friday, March 29, 2013 4:15 AM
> To: public-sysapps@w3.org
> Subject: Telephony API, new version
> 
> Hello,
> 
> A new version of the Telephony API can be found at
> http://telephony.sysapps.org/ .
> The old repository at https://github.com/sysapps/ is not used any more.
> 
> This is really a working draft, and a few details will certainly change
> next week after the holidays.

It seems that Telephony API spec is going to be ready for FPWD. It would be
better to go there after updated next week. What do you think?


> The main change is the way how multiparty (conference) calls are handled,
> as now there is a separate object for controlling multiparty calls, and
> managing the now explicit participating call objects.
> Previously conference calls were exposed via a single call object with an
> array of participants.
> This version is better aligned with 3GPP specifications, but is still
> compatible with IMS/VoIP. Also, it is still forward compatible with
> specifying the functionality which is currently not covered by this
> specification (e.g. supplementary services other than multiparty calls).
> The editors have discussed multiple ways to achieve the functionality, so
> this version should be considered as one way of doing it.
> Your comments may help the editors in considering and deciding between
> possible solutions, therefore all comments are welcome.
>

Do you think all of functions you mentioned are mandatory and basic features
for Telephony API? It would be better if we can develop a spec with only
mandatory function first and then other functions are covered by second
round.

Best regards,
Wonsuk.

>
> Best regards,
> Zoltan

Received on Friday, 29 March 2013 00:20:36 UTC