Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.39 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Mon, 12 Mar 2012 11:56:07 -0700
Subject: Re: Unified JS Contact object
Thread-Topic: Unified JS Contact object
Thread-Index: Ac0AgcIq+i55cPghTzyI3+TjEWatSg==
Message-ID: <CB8394C3.15D4%fil@adobe.com>
In-Reply-To: 
 <CADjNb+=DiUG6TVPgV5bU_j8r+ymS5TsFL8u=-qB1=Y+X5+-O9g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Let's make the change and I can test it out on Android on my end - just
ping me.

On 3/12/12 10:22 AM, "Becky Gibson" <gibson.becky@gmail.com> wrote:

>The unified JS contact object initializes the contact object incorrectly.
>Base on the June, 2011 and March, 2012 definition for the contact object,
> parameters that are not defined should have the initial value of null:
>
>All Contact <http://w3c-test.org/dap/contacts/#idl-def-Contact> objects *
>must* include all attributes supported by the implementation, regardless
>of
>whether these attributes have been assigned a null value or not. If a
>supported attribute has not been assigned a value by the user or the
>implementation, then this attribute *must* still be present in the
>resulting Contact <http://w3c-test.org/dap/contacts/#idl-def-Contact>
>object
>and *must* have a value of null.
>
>The current implementation initializes all of the array fields to an empty
>array rather than null if no value is provided.   The iOS code relies on
>the distinction between null and empty array during an update of a
>contact.
> If an array value is null, that parameter is ignored (not changed), if it
>is an empty array and data exists, the stored date for that parameter is
>removed.
>
>Not sure if changing this back to the spec will affect the other
>platforms?
>
>-becky