Re: [contacts-manager-api] Preferred ContactField

Hi,

> But Christophe has a point that there needs to be a documentation that should only be one element of the array with its preferred value set to 'true'.


I agree with that point, except that the PREF parameter in vCard is optional[1]. If this attribute is determined as boolean, there should be one or no element with its preferred (or pref) attribute set to 'true'.

BTW, vCard v4 defines the PREF parameter as an integer between 1 and 100, which indicates the level of preference[1]. If we would follow it, 'pref' (or 'preferred') attribute should be defined as an integer in the same manner as vCard v4.

Any thoughts on this?

Regards,
Tomoyuki

[1] http://tools.ietf.org/html/rfc6350#section-5.3


On Mar 13, 2013, at 6:38 , Suresh Chitturi <schitturi@blackberry.com> wrote:

> 
>> -----Original Message-----
>> From: Tomoyuki SHIMIZU [mailto:tomoyuki.labs@gmail.com]
>> Sent: Monday, March 11, 2013 11:54 PM
>> To: public-sysapps@w3.org
>> Subject: Re: [contacts-manager-api] Preferred ContactField
>> 
>> Hi Christophe,
>> 
>>> I see 2 potential alternatives:
>>> 1. Add a "preferred" boolean attribute to ContactField interface 2.
>>> Document that the first element in the array is always the preferred
>>> one
>> 
>> ContactField interface in Pick Contacts Intent [1] has 'pref' boolean attribute
>> equivalent to 1.
> 
> Right, this was done to keep it separate from 'type' attribute.
> But Christophe has a point that there needs to be a documentation that should only be one element of the array with its preferred value set to 'true'.
> 
> Regards,
> Suresh
> 
> ---------------------------------------------------------------------
> 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 Wednesday, 13 March 2013 01:45:19 UTC