Re: [VCARDDAV] IETF79 vcarddav wg meeting notes

[Simon Perreault <[e-mail]>]

On 2010-11-28 06:00, Andy Mabbett wrote:
> hCard currently uses LABEL for non-granular addresses. How will they
> be catered for if this change occurs?

How about this?

ADR;LABEL="My non-granular address":;;;;;;

> What use is SEX="Ada Lovelace"?

I think that's the wrong question to ask. It has been made very clear on
this mailing list that people want this. At this point, it's better to
ask "Why not allow it?"

>> - CALSCALE parameter
>>  - Problem: Having only a single pre-defined value makes this parameter
>> useless.
>>  - Resolution: Refer to iCalendar and create an IANA registry for calendar
>> types.
> 
> It does *not* make the parameter useless, it makes it extendable.
> 
> It is not clear from the wording of the proposed resolution that the
> new parameter will be kept. Is that the case?

It will be kept.

>> - Case sensitivity
>>  - Problem: Case causes interoperability issues in practice.
>>  - Resolution: Output SHOULD be upper-case. Accept both.
> 
> Why upper-case? [Genuine question;  not meaning to challenge]

Because that's what is most commonly used in practice right now.
Ensuring that your output is upper-case (we're talking about property
and parameter names here) is a way to avoid some interoperability issues.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca