W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2011

Editorial feedback for Contacts API

From: Josh Soref <jsoref@rim.com>
Date: Tue, 21 Jun 2011 11:26:07 -0400
To: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <6A252AE18765C3468EF06946F24F0B571FFBF8F801@XCH102CNC.rim.net>
http://www.w3.org/TR/2011/WD-contacts-api-20110616/


Sorry for the delay in providing feedback. I was transitioning for the past few months and didn't have any time to review the DAP work items. I'm now trying to focus on them as part of my new job. 

I can't tell if the document is en-GB or en-US. The API itself is en-US.

[en-GB]> ... utilising existing web platform APIs. 
[en-GB]> ... authorise the retrieval of contact information.
[en-GB]> ... "favourite", "cryptozoologists".
[en-US]> ... utilizing all of the parameters provided in the find() operation as follows: 
[en-US]> ... utilizing all of the parameters provided in the find() operation as follows: 
[en-US]> ... minimize the data that needs to be shared
[en-US]> ... to let that application fulfill

Here are the en-US/en-GB terms:
* authorize/authorise
* favorite/favourite
* fulfill/fulfil
* minimize/minimize
* utilizing/utilizing

Personally, I'd prefer en-US. Originally I was going to suggest selecting en-GB, because I thought that was the dominant form, however, I think that en-US is dominant, so the items I've identified as [en-GB] should be changed.

Other editorial comments...

> ... a user agent must respect revoked permissions. 

"revoked permissions" seems awkward, how about one of: permission revocation / revocation of permissions.

> This in turn often leads to disjointed and inconsistent information 
> being stored across a user's address book providers. 

s/disjointed/disjoint/

> A set of Security and Privacy Considerations are presented for the 
> discretion of both implementors
> 3.1 Privacy considerations for implementors of the Contacts API 
> Further to the requirements listed in the previous section, 
> implementors ... extended by implementors of this specification.

s/implementors/implementers/g

-- according to dictionaries, however it seems w3 isn't very good at getting this right...

> formatted for display (e.g. Mr. Joe Smith Jr). 
> This attribute contains the honorific suffix of this Contact. E.g. Jr, III, Sr. 

s/Jr/Jr./g
s/Sr/Sr./g


> paradigms in order to acheive add and update functionality. 

s/acheive/achieve/

> (i.e MatchedContact is not-null)

s/i.e/i.e./

---------------------------------------------------------------------
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 Sunday, 26 June 2011 12:38:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:21 GMT