Subject: Re: [VCARDDAV] New Version Notification fordraft-ietf-vcarddav-oma-cab-extensions-00.txt

From: <[email-masked]>
Date: Wed, 30 Nov 2011 10:17:23 +0100

Hello,

Please find some comments about "comments in draft-ietf-vcarddav-oma-cab-extensions-00.txt"

Anchor 3 in section 2 : May be we can add something in this section in order to explain what OMA CAB does. Something like : 
The Converged Address Book (CAB) Enabler provides consistent mechanisms to manage contact information in both user facing applications as well as in support of network facing activities.  At the core of this enabler is a network-based contact repository which a user can use to store contact information which can be retrieved by any CAB-enabled device.  The network-based repository is also able to provide specific contact information to other users and to keep them up-to-date whenever the data is updated.
The CAB Enabler provides synchronization of the contact information available in the user device(s) with the network-based contact repository.
The CAB Enabler is also managing the distribution of user’s own contact information.  In essence, a user fills out a Personal Contact Card which includes all the information a user wishes to store about him or herself.
Since systems that are supporting the CAB Enabler are likely supporting multiple users, the CAB Enabler also defines a search paradigm which permits other users to query such a system to locate information about the available users.
As the CAB Enabler supports many different types of information it has a data model that is flexible and extensible.  It manages traditional types of contact information (e.g. name, address, email, phone number, mobile number, etc.) as well as new types of information (e.g. websites, blogs, presence subscription references, etc.).  

Anchors 6, 7, 8, 9 in section 2.1 : as the vCard 4.0 doesn't include parameters as LANGUAGE-PROFICIENCY-TYPE, LANGUAGE-FLUENCY-TYPE
 Then this property definition is fine in this extension document.

Anchors 11,12,13,14 in section 2.2 : to me, the SERVICE definition is fine as it is. It is different from URL in vCard spec and from SOCIALPROFILE in draft-george (which doesn't include Label) 

Anchors 17,18,19,20 in section 2.6 : PUBLICNOTE is useful as OMA-CAB defines NOTE as "a note for me and my friends" and PUBLIC-NOTE as "a note for all others"

Hope these comments will help to get a final version of this document by the end of 2011 as planned.

Regards
Dany 

-----Message d'origine-----
De : [email-masked] [mailto:[email-masked]] 
Envoyé : vendredi 21 octobre 2011 14:42
À : [email-masked]
Cc : [email-masked]; [email-masked]; CAUCHIE Dany RD-MAPS-LAN
Objet : New Version Notification fordraft-ietf-vcarddav-oma-cab-extensions-00.txt

A new version of I-D, draft-ietf-vcarddav-oma-cab-extensions-00.txt has been successfully submitted by Barry Leiba and posted to the IETF repository.

Filename:	 draft-ietf-vcarddav-oma-cab-extensions
Revision:	 00
Title:		 vCard Format extension : represent vCard extensions defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) group
Creation date:	 2011-10-20
WG ID:		 vcarddav
Number of pages: 16

Abstract:
   This document defines extensions to the vCard data format for
   representing and exchanging certain contact information.  The
   properties covered here have been defined by the Open Mobile Alliance
   Converged Address Book group, in order to synchronize, using OMA Data
   Synchronization, important contact fields that were not already
   defined in the base vCard 4.0 specification.

The IETF Secretariat