canmove, Confirmed users
2,887
edits
WebAPI/ContactsAPI: Difference between revisions
Jump to navigation
Jump to search
→Priority 6 feature requests: note current recommendation
(→Priority 6 feature requests: Possible workaround for 'carrier', add id for referencing.) |
(→Priority 6 feature requests: note current recommendation) |
||
| Line 230: | Line 230: | ||
*** Rates in Brazil depend a lot on the carrier of the person you are communicating with. | *** Rates in Brazil depend a lot on the carrier of the person you are communicating with. | ||
** Is this a "nice to have" stretch innovative feature or is it a competitive parity feature? In which case... | ** Is this a "nice to have" stretch innovative feature or is it a competitive parity feature? In which case... | ||
*** What existing device address books have a field in the UI? | *** What existing device(s) address books have a field in the UI? As of now there no known devices / address books that support a "carrier" designation on "tel" values. | ||
**** A quick search didn't turn up any prior art or devices. | **** A quick search didn't turn up any prior art or devices. If anyone knows of ANY device or address book software that supports a "carrier" designation on a per phone number basis, please provide the specific name of the device and a URL to its description on the web (e.g. at a place where you can buy it). | ||
**** When found, what do they export in vCards when such a field is used? | **** When found, what do they export in vCards when such a field is used? | ||
** Can this information be automatically determined rather than user-entered? | ** Can this information be automatically determined rather than user-entered? | ||
| Line 238: | Line 238: | ||
*** E.g. in the US we have no idea if the cell phone numbers of friends are serviced by AT&T, Verizon, Sprint, T-Mobile, Virgin Mobile etc. and frankly, don't (and shouldn't) care, since the functionality is equivalent. | *** E.g. in the US we have no idea if the cell phone numbers of friends are serviced by AT&T, Verizon, Sprint, T-Mobile, Virgin Mobile etc. and frankly, don't (and shouldn't) care, since the functionality is equivalent. | ||
** Possible workaround: one way to implement a "carrier" designation on telephone numbers would be to use custom machine-types on the phone number, that is, along with "home", "work", "pref" etc. standard types, we can use custom machine-types of the form: "label:value", e.g. "carrier:tmobile". | ** Possible workaround: one way to implement a "carrier" designation on telephone numbers would be to use custom machine-types on the phone number, that is, along with "home", "work", "pref" etc. standard types, we can use custom machine-types of the form: "label:value", e.g. "carrier:tmobile". | ||
** '''Current recommendation:''' strongly recommend we postpone "carrier" to after v1. If no one else in the market has this feature, then it shouldn't be a blocker for us to ship v1. | |||
=== Out of scope === | === Out of scope === | ||