Return-Path: X-Original-To: vcarddav@ietfa.amsl.com Delivered-To: vcarddav@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1451B1AE219 for ; Tue, 7 Jan 2014 14:23:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.738 X-Spam-Level: X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mx3mHf4bhJln for ; Tue, 7 Jan 2014 14:22:58 -0800 (PST) Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 4542F1AE216 for ; Tue, 7 Jan 2014 14:22:58 -0800 (PST) Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id s07MMmcL004814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Jan 2014 22:22:49 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s07MMlud014741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2014 22:22:48 GMT Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s07MMlj6018938; Tue, 7 Jan 2014 22:22:47 GMT Received: from [10.159.114.174] (/10.159.114.174) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 07 Jan 2014 14:22:46 -0800 Message-ID: <52CC7E0D.50506@oracle.com> Date: Tue, 07 Jan 2014 15:22:05 -0700 From: Erwin Rehme User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: vcarddav@ietf.org Content-Type: multipart/alternative; boundary="------------040203050105020904030808" X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Mailman-Approved-At: Wed, 08 Jan 2014 05:27:45 -0800 Subject: [VCARDDAV] Question about SOURCE property in RFC 6350 X-BeenThere: vcarddav@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF vcarddav wg mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 22:25:43 -0000 This is a multi-part message in MIME format. --------------040203050105020904030808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In RFC 6350 is says: 6.1.3 . SOURCE Purpose: To identify the source of directory information contained in the content type. Value type: uri Cardinality: * Special notes: The SOURCE property is used to provide the means by which applications knowledgable in the given directory service protocol can obtain additional or more up-to-date information from the directory service. It contains a URI as defined in [RFC3986 ] *and/or other information referencing the vCard to which the information pertains.* When directory information is available from more than one source, the sending entity can pick what it considers to be the best source, or multiple SOURCE properties can be included. Does the "and/or other information..." statement mean that the value is can be "free form" text and not just a uri? -- Erwin Rehme --------------040203050105020904030808 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In RFC 6350 is says:

6.1.3.  SOURCE


   Purpose:  To identify the source of directory information contained
      in the content type.

   Value type:  uri

   Cardinality:  *

   Special notes:  The SOURCE property is used to provide the means by
      which applications knowledgable in the given directory service
      protocol can obtain additional or more up-to-date information from
      the directory service.  It contains a URI as defined in [RFC3986]
      and/or other information referencing the vCard to which the
      information pertains.  When directory information is available
      from more than one source, the sending entity can pick what it
      considers to be the best source, or multiple SOURCE properties can
      be included.
Does the "and/or other information..." statement mean that the value is can be "free form" text and not just a uri?

-- Erwin Rehme
--------------040203050105020904030808--