Re: [VCARDDAV] Upload of SCIM/vCard mapping draft

Bert Greevenbosch <> Fri, 21 September 2012 06:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4B2E121F84F3; Thu, 20 Sep 2012 23:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CcXrkzOGKHuB; Thu, 20 Sep 2012 23:14:22 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9466621F8639; Thu, 20 Sep 2012 23:14:21 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.5-GA FastPath queued) with ESMTP id AJW51145; Fri, 21 Sep 2012 06:14:20 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Sep 2012 07:13:41 +0100
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Sep 2012 07:14:17 +0100
Received: from ([]) by ([]) with mapi id 14.01.0323.003; Fri, 21 Sep 2012 14:14:07 +0800
From: Bert Greevenbosch <>
To: "" <>, "" <>, "" <>
Thread-Topic: Upload of SCIM/vCard mapping draft
Thread-Index: AQHNlX3P+qo+TKEJ9EuMcAMkwpiVzJeUSfqA
Date: Fri, 21 Sep 2012 06:14:07 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB6290D5011@szxeml509-mbs>
References: <> <29195_1347959585_50583B21_29195_10300_1_ef6d99e0-25ee-4eb9-8e6e-267b3be182d9@PEXCVZYH01.corporate.adroot.infra.ftgroup>
In-Reply-To: <29195_1347959585_50583B21_29195_10300_1_ef6d99e0-25ee-4eb9-8e6e-267b3be182d9@PEXCVZYH01.corporate.adroot.infra.ftgroup>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [VCARDDAV] Upload of SCIM/vCard mapping draft
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 21 Sep 2012 06:14:23 -0000

Hello Dany,

Thank you for your comments. I have added the references to RFC 6473, RFC 6474 and RFC 6715 to the draft, and updated the vCard -> SCIM table. I haven't found strong matches in SCIM for the new vCard properties, so I have not yet defined mappings for them.

Both typos have been fixed too.

I will upload a new version of the draft in due time, but first wait a while for possibly more comments.

Thanks again and best regards,

-----Original Message-----
From: [] 
Sent: 18 September 2012 17:13
To:;; Bert Greevenbosch
Cc: Likepeng; MIENVILLE Thibaud OLNC/NAD
Subject: Upload of SCIM/vCard mapping draft

Hi all,

Here are my comments :

1) To be complete, in its sections 4 and 9, this document will have to take into account other RFCs like :

		- RFC 6473
		- RFC 6474
		- RFC 6715

2) I noted 2 typos in section 4 : 

   1.  Fwd: [scim] Upload of SCIM/vCard mapping draft
      (Peter Saint-Andre)


Message: 1
Date: Thu, 13 Sep 2012 19:15:29 -0600
From: Peter Saint-Andre <>
Subject: [VCARDDAV] Fwd: [scim] Upload of SCIM/vCard mapping draft
Message-ID: <>
Content-Type: text/plain; charset="utf-8"

Of interest.

-------- Original Message --------
Subject: 	[scim] Upload of SCIM/vCard mapping draft
Date: 	Fri, 14 Sep 2012 01:08:18 +0000
From: 	Bert Greevenbosch <>
To: <>

Hi all,

Yesterday I uploaded a draft that provides mapping between SCIM and
vCard. It is available under the following link:

The draft provides the mapping in two directions: from SCIM to vCard and
from vCard to SCIM.

Open issues include the conversion method between SCIM ids and vCard
UIDs. When that is done, it should be easy to port the grouping function.

I think the draft is also very useful for the discussion on the format
to use for SCIM, and in which extent it will be related to vCard.

I look forward to your comments and suggestions!

Best regards,


-------------- next part --------------
scim mailing list


VCARDDAV mailing list

End of VCARDDAV Digest, Vol 61, Issue 23


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.