Closed marcoscaceres closed 10 years ago
We need to specify the valid formats with references. In this version of the spec we support GSM and CDMA. In subsequent versions SIP and XMPP calls may be supported. All this have well defined remote party formats (will need to find the exact references).
I tried feeding the iOS a random string... it converts it all to numbers :) Weird.
OK, some implementations may want to add skype, too. Other formats may be supported by some implementation, but that is the decision of the implementation, and it would not be compliant. Such apps may fail on other implementations.
I think this is then best left to the backend, right?
The advantage of tel URI's is that all this is standardized.
Excuse my ignorance, but what does an XMPP number(?) look like?
I think this is then best left to the backend, right?
It depends whether do we require implementations to validate user strings for security reasons, or do we push that to the backends. We could do a pre-validation (length, encoding etc), and leave the rest to the backends.
I think for V1 we should just leave it all to the backends and see how we go... if people complain during review, we can start imposing rules.
OK. We can create a note, eventually.
Closing.
In the dial method, it's not well defined that it's the telephony service that handles invalid phone numbers.