[VCARDDAV] updating vCard 3.0 to vCard 4.0
"Javier Godoy" <rjgodoy@fich.unl.edu.ar> Thu, 15 July 2010 12:20 UTC
Return-Path: <rjgodoy@fich.unl.edu.ar>
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 E15873A6898 for <vcarddav@core3.amsl.com>; Thu, 15 Jul 2010 05:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.195
X-Spam-Level:
X-Spam-Status: No, score=0.195 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_50=0.001, STOX_REPLY_TYPE=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 6lnJNH8BKA-L for <vcarddav@core3.amsl.com>; Thu, 15 Jul 2010 05:20:32 -0700 (PDT)
Received: from fich.unl.edu.ar (fich.unl.edu.ar [168.96.132.90]) by core3.amsl.com (Postfix) with ESMTP id 757B33A6903 for <vcarddav@ietf.org>; Thu, 15 Jul 2010 05:20:31 -0700 (PDT)
Received: from Javier2 ([190.193.109.175]) (authenticated user rjgodoy@fich.unl.edu.ar) by fich.unl.edu.ar (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits)) for vcarddav@ietf.org; Thu, 15 Jul 2010 09:20:45 -0300
Message-ID: <85421D6B55DD4BC18C9FB8105F4D66DD@Javier2>
From: Javier Godoy <rjgodoy@fich.unl.edu.ar>
To: vcarddav@ietf.org
Date: Thu, 15 Jul 2010 09:20:22 -0300
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
Subject: [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: Thu, 15 Jul 2010 12:20:34 -0000
¿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] updating vCard 3.0 to vCard 4.0 Javier Godoy
- Re: [VCARDDAV] updating vCard 3.0 to vCard 4.0 Daisuke Miyakawa
- Re: [VCARDDAV] updating vCard 3.0 to vCard 4.0 Javier Godoy