Becky wrote: > Yes, I've worked in W3C working groups I'm glad you do, I'm concerned about messaging - that others might not understand what it means. I've seen various groups really fail to understand such a detail.
> - I know the risks of implementing too early in the process! > However, when we wanted to add an API for contacts into PhoneGap we needed > a place to start so we used the W3C working draft available at the time. > We realized that it would likely change but at least gave us a starting point. > We been trying to keep track of the W3C updates and changes so we can > decide when to update the Cordova version. Right, and appreciated. > When we implemented an earlier Contacts API working draft for Cordova we added > a remove functionality to provide the ability to delete a contact. > It just seemed to make sense that if add is being provided that there > should also be a way to remove a contact as well. So, this symmetry is interesting. One thing I don't think Cordova (or pretty much most other projects have) is any metrics showing how often/much use a given API has. Does Cordova/PhoneGap know if remove() is used and if so by whom and if by whom, why? I know of a few rather rare instances where it might theoretically be possible for someone to want to have a remove, but I think they're either theoretical or indicate a need for something drastically different (which is the reason why I was working on a Pick-Contact API). > Since not all of the platforms provide a native "view" for accessing the > contacts > (similar to camera access) we decided to implement full functionality of > create, > find and remove. Camera access doesn't usually let one delete a picture, does it? (I understand that Gallery access would.) p.s., sysapps is having a F2F soon, I hope you're planning to attend :). --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
