Re: [VCARDDAV] vCard revision - AN (anniversary)

[Joseph Smarr <[e-mail]>]

If there's a well-defined 1:1 mapping between vCard and PoCo, that's fine by
me, assuming there are good reasons for not doing exactly the same thing
(which in this case it sounds like there may be due to consistency
constraints). Thanks, js

On Thu, Jun 11, 2009 at 11:28 AM, Javier Godoy <[e-mail]>wrote:

> Hi Joseph,
>
> On  Thursday, June 11, 2009 11:57 AM  Joseph Smarr wrote:
>
>> Yeah, and not surprisingly this is how I think vCard should handle this
>> value too! :) Thanks, js
>>
>
> Since draft -07 date values may be truncated (i.e. --mmdd and ---dd)  when
> the
> higher order components are not available, or the vCard author does not
> want
> to disclose them.
>
> The truncation feature was borrowed from ISO 8601:2000. Truncation is
> preferable to using 0000, because the latter is a valid year number
> according
> to ISO 8601:2004.
>
> The date value 0000-02-14 in Portable Contacts should be mapped to --0214
> in
> vCard. The the year component in vCard date value 00000214 represents a
> known year, which cannot
> be represented in Portable Contacts without loss of information.
>
>
> Regards
>
> Javier
>
>
>  On Wed, Jun 10, 2009 at 2:25 PM, Andy Mabbett <[e-mail]>
>> wrote:
>>
>>  In message <[e-mail]>, Sly Gryphon
>>> <[e-mail]> writes
>>>
>>>
>>>  Additional attribute proposal for AN (anniversary)
>>>>
>>>
>>>
>>> It's worth noting that Portable Contacts has an anniversary property:
>>>
>>>   The wedding anniversary of this contact. The value MUST be a
>>>   valid xs:date (e.g. 1975-02-14. The year value MAY be set to
>>>   0000 when the year is not available.
>>>
>>>      http://portablecontacts.net/draft-spec.html#anchor16
>>>
>>
>
>
>
>
>
>