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). However, URI's need some (minimal) parsing, and since this is a system level API, one might just prefer the explicit objects for telephony services (which generalize the current Telephony object). We need decision on this. It also affects other API's (e.g. Messaging). BTW the W3C Messaging API [3] wrongly assumes that the IANA mms:// URI is registered with MMS: it is for Windows media streaming (Microsoft Media Server) [2]. [1] http://tools.ietf.org/html/rfc3966 [2] http://en.wikipedia.org/wiki/URI_scheme [3] http://www.w3.org/TR/messaging-api/ Regards, Zoltan
Received on Tuesday, 23 October 2012 18:09:08 UTC