Re: [VCARDDAV] Questions about vCard 4.0 (draft rev-11)

Simon Perreault <simon.perreault@viagenie.ca> Wed, 23 June 2010 12:32 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C79A3A6A09 for <vcarddav@core3.amsl.com>; Wed, 23 Jun 2010 05:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLfiq3Z4DevJ for <vcarddav@core3.amsl.com>; Wed, 23 Jun 2010 05:32:14 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by core3.amsl.com (Postfix) with ESMTP id E1FC23A69F2 for <vcarddav@ietf.org>; Wed, 23 Jun 2010 05:32:12 -0700 (PDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5175820DC3; Wed, 23 Jun 2010 08:32:20 -0400 (EDT)
Message-ID: <4C21FED3.3020808@viagenie.ca>
Date: Wed, 23 Jun 2010 08:32:19 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: Javier Godoy <rjgodoy@fich.unl.edu.ar>
References: <AANLkTiniY60njEGixPGeKvs_m1LE_uVrvtnDQuXrP7jV@mail.gmail.com><4C20B501.6030802@viagenie.ca> <AANLkTikd9ni-iCI2tIaGi803AEDjtKXE9PEIsJsONdCO@mail.gmail.com> <AE51FE4DF2604D0A9D2697A8438376E2@Javier2>
In-Reply-To: <AE51FE4DF2604D0A9D2697A8438376E2@Javier2>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] Questions about vCard 4.0 (draft rev-11)
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 12:32:22 -0000

On 2010-06-23 03:43, Javier Godoy wrote:
> Since ORG is (0,n) now it makes sense to define SORT-STRING as (0,n),

I disagree. FN is (1,n). We're still in the same situation.

Suppose you have multiple FN properties. Which one are you going to use
for sorting? The first one? It wouldn't make sense to pick e.g. the
second one because there's nothing guaranteeing that all second FN
properties in all vCards have anything in common. Also, the order of
properties can be changed by any intermediate system since order doesn't
matter.

Since we're in the same situation with ORG, I don't see why we wouldn't
solve it exactly in the same way with a separate property, e.g.
ORG-SORT-STRING.

Now, one thing that I like about your example is the use of the LANGUAGE
tag. We need to at least add an example where the LANGUAGE tag is also
applied to the SORT-STRING property.

Example:

ORG;LANGUAGE=ja:日本の組織  # "Japanese organization"
ORG;LANGUAGE=en:Japanese organization
ORG-SORT-STRING;LANGUAGE=ja:にほんのそしき

(I'll figure out an equivalent example in French since we can't have
Japanese characters in RFCs...)

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org