- From: Josh Soref <jsoref@rim.com>
- Date: Mon, 4 Jul 2011 13:57:49 -0400
- To: Dominique Hazael-Massieux <dom@w3.org>
- CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
> That's exactly what the contacts API provide. Basically, the Web site > asks what fields it would needs, and the user agent lets the user pick > what she wants to expose to the site (using some pre-filtering based on > what the site requested). Somewhere in Section 5 (Contact Search Processing), should be advice to: * show the user the general contact query * show the user which fields are being requested * show the user see a preview of the resulting data Note that this is probably RFC "should", it is definitely not an RFC "must", as a trusting agent should be allowed to skip this step. Somewhere in the steps for Section 5 (which don't really have wonderful "steps"), should be a phase in which the user can create synthetic cards in order to make the application happy. > Again, that's fully the intent of the Contacts API; if that intent > isn't > clear in the specification, suggested wording improvement would be > welcome. Having done this, one can drop the entire security consideration junk relating to URIs. --------------------------------------------------------------------- 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.
Received on Monday, 4 July 2011 17:58:29 UTC