Re: [VCARDDAV] updating vCard 3.0 to vCard 4.0

Daisuke Miyakawa <d.miyakawa@gmail.com> Fri, 16 July 2010 00:27 UTC

Return-Path: <d.miyakawa@gmail.com>
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 900373A681D for <vcarddav@core3.amsl.com>; Thu, 15 Jul 2010 17:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.441
X-Spam-Level:
X-Spam-Status: No, score=-0.441 tagged_above=-999 required=5 tests=[AWL=1.557, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6]
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 srboB95qP0KB for <vcarddav@core3.amsl.com>; Thu, 15 Jul 2010 17:27:45 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 155C83A67D4 for <vcarddav@ietf.org>; Thu, 15 Jul 2010 17:27:45 -0700 (PDT)
Received: by gxk1 with SMTP id 1so732114gxk.31 for <vcarddav@ietf.org>; Thu, 15 Jul 2010 17:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=GmdlPz56s6+RZEG/S+XDBSgY716CQLnkXHe+cn/t1kg=; b=Hfmw7g8WKQ5OEZO79ibsTJTS2QmyWFt1IjRc5qTB+XOkmXswJT0mSLtnOFuBD+9+dA ala5PmQsAJGrvyuMyQbxEI9vj9ULK2T/sEeeK918cbin6tz1PhabmqzL81O9UXU67f/r /bW+GM3oKQmHk7ooRWWSaqxfQObGeXLGBthaE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZDcntqFXX9tnGE3nYfQqP3Vqd4Why3M/PSN7B0B4DCvbhkmpV1PwxdNpnsofOpu48U mpIvLBcR0j0DFRc/pLM2BOalhqGGW2/L9fC5Mv++azQMgn9bZI0T8HEN+Aj6bDqn90tM DW2qaBpKOnioUlm0c0u7XDzJninjIgzOFlTOE=
MIME-Version: 1.0
Received: by 10.90.73.10 with SMTP id v10mr406966aga.94.1279240073290; Thu, 15 Jul 2010 17:27:53 -0700 (PDT)
Received: by 10.90.35.14 with HTTP; Thu, 15 Jul 2010 17:27:53 -0700 (PDT)
In-Reply-To: <85421D6B55DD4BC18C9FB8105F4D66DD@Javier2>
References: <85421D6B55DD4BC18C9FB8105F4D66DD@Javier2>
Date: Fri, 16 Jul 2010 09:27:53 +0900
Message-ID: <AANLkTik07FG0DP21XS85ZIflhfVEQjXnlKDmEureV09c@mail.gmail.com>
From: Daisuke Miyakawa <d.miyakawa@gmail.com>
To: Javier Godoy <rjgodoy@fich.unl.edu.ar>
Content-Type: multipart/alternative; boundary=00163630ef8926a6db048b764a04
Cc: vcarddav@ietf.org
Subject: Re: [VCARDDAV] updating vCard 3.0 to vCard 4.0
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: Fri, 16 Jul 2010 00:27:46 -0000

Hi,

Interesting. I'd like to have some documentation describing relation between
vCard 3.0 and 4.0, while I don't know there's any draft for it.

As for the mapping from 3.0 to 4.0, however, I have some concerns.

vCard 3.0 just recommends UTF-8. It is not MUST. Actually I've seen some
device emitted vCard with Japanese local charset called Shift_JIS.
One-to-One mapping from Shift_JIS to UTF-8 is sometimes impossible, as far
as I rember.
There are some other examples I can find which makes the migration
difficult.

>From the actual usage, I personally want such documentation anyway.
I think we don't need to have a strict mapping but some guideline, though I
agree it won't be a formal "specification".
For example, now we have SORT-AS parameter instead of vCard 3.0's
SORT-STRING, strings for sort should be composed differently.

BEGIN:VCARD
VERSION:3.0
N:宮川;大輔;;;
SORT-STRING:みやかわ だいすけ
NOTE:My name
END:VCARD


This should be...

BEGIN:VCARD
VERSION:4.0
N;SORT-AS="みやかわ;だいすけ":宮川;大輔;;;
NOTE:My name
END:VCARD


Thanks,

2010/7/15 Javier Godoy <rjgodoy@fich.unl.edu.ar>

>
> ¿Will be there a WG draft about updating from vCard 3.0 to vCard 4.0?
>
> I'm concerned that, after the publication of vcardrev, systems supporting
> vCard 4.0 would have to interoperate with systems supporting vCard
> 3.0-only. .
>
> Besides, since RFC 2425 and RFC 2426 will be obsolete, the requirement of
> "supporting both vCard 3.0 and vCard 4.0" will imply references to the
> obsolete and current standards, on an equal footing. Instead, I would like
> to
> require "mapping from vCard 3.0 to vCard 4.0", and have such mapping
> reviewed
> by the same people who participated in the discussion about vcardrev.
>
> Interoperability with older systems may also require exporting vCard 4.0
> instances as vCard 3.0. Later, the downgraded instance might be converted
> back
> to vCard 4.0. I would like to provide a mechanism for preserving as much
> information as possible during this mapping.
>
> I think the community would benefit and feel more confident if some
> broadly-discussed guidelines are provided, instead of asking each
> implementor
> to reinvent the wheel.
>
> If this is not in the schedule, and if you think it might be usefeul, I
> would
> like to take this responsability.
>
>
> Best Regards
>
> Javier
>
>
> _______________________________________________
> VCARDDAV mailing list
> VCARDDAV@ietf.org
> https://www.ietf.org/mailman/listinfo/vcarddav
>



-- 
Daisuke Miyakawa (宮川大輔)
d.miyakawa@gmail.com