[VCARDDAV] [Errata Held for Document Update] RFC6350 (4213)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 02 January 2015 17:06 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 9C3201A1B8E; Fri, 2 Jan 2015 09:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.413
X-Spam-Level:
X-Spam-Status: No, score=-104.413 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 aqIgnuzAvgfp; Fri, 2 Jan 2015 09:06:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC411A1BA4; Fri, 2 Jan 2015 09:06:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 879EF18047D; Fri, 2 Jan 2015 09:06:06 -0800 (PST)
To: evought@pobox.com, simon.perreault@viagenie.ca
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150102170606.879EF18047D@rfc-editor.org>
Date: Fri, 02 Jan 2015 09:06:06 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/vcarddav/9oYxl2aWM4CsZ14Q7vd5J7DJv1s
Cc: barryleiba@computer.org, iesg@ietf.org, vcarddav@ietf.org, rfc-editor@rfc-editor.org
Subject: [VCARDDAV] [Errata Held for Document Update] RFC6350 (4213)
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Jan 2015 17:06:25 -0000
The following errata report has been held for document update for RFC6350, "vCard Format Specification". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6350&eid=4213 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Eric Vought <evought@pobox.com> Date Reported: 2014-12-28 Held by: Barry Leiba (IESG) Section: 5.4 Original Text ------------- "Two property instances are considered alternative representations of the same logical property if and only if their names as well as the value of their ALTID parameters are identical. Property instances without the ALTID parameter MUST NOT be considered an alternative representation of any other property instance. Values for the ALTID parameter are not globally unique: they MAY be reused for different property names." Corrected Text -------------- "Two property instances are considered alternative representations of the same logical property if and only if their names as well as the value of their ALTID parameters are identical. Property instances without the ALTID parameter MUST NOT be considered an alternative representation of any other property instance. Values for the ALTID parameter are not globally unique: they MAY be reused for different property names. "Values for group and for the PREF parameter SHOULD be the same for all alternative representations of the same property. The values of group and PREF are not defined for a property if they differ among alternative representations of the same logical property." Notes ----- The corrected text "not defined" is intended as a literal statement of the consequences of the current specification and not a change to the meaning of the current specification. The submitter recommends that the text "Values for the group and for the PREF parameter MUST be the same..." be considered for future versions of this document. It is also requested that the example below be added to the "legal but questionable" list in section 5.4. Section 3.3 contains the text: "The group construct is used to group related properties together. The group name is a syntactic convention used to indicate that all property names prefaced with the same group name SHOULD be grouped together when displayed by an application." There is no valid interpretation available for an application if a logical property has more than one group (see example below) and clearly no way to display such properties together, therefore the group construct has no defined meaning for such a case. This is particularly troublesome when converting to formats such as the VCard XML Schema where the group is represented as an XML schema in which properties are contained. Also, Section 5.3 states in reference to the PREF parameter: "Note that the value of this parameter is to be interpreted only in relation to values assigned to other instances of the same property in the same vCard. A given value, or the absence of a value, MUST NOT be interpreted on its own." The meaning of "instances of the same property" is not decipherable with respect to logical properties which differ in their PREF parameter value, therefore application behavior is also not defined for this case. Example: volunteer.ORG;ALTID=1;PREF=1;LANGUAGE=en:Doctors Without Borders causes.ORG;ALTID=1;LANGUAGE=fr:Médecins Sans Frontières volunteer.ORG:Community Emergency Response Team;Some County\, Some State volunteer.ROLE:CERT Instructor ORG;TYPE=WORK:Sometown Medical Center The alternative representation of "Doctors Without Borders" is legal according to the current text but breaks the 'volunteer' grouping: the same logical property is requested by the VCard to appear in two places. Similarly, the PREF tag on "Doctors Without Borders" is legal but nonsensical. The logical application representation of the ORG properties with ALTID=1 as the same logical property breaks sort ordering or selection by PREF. Similarly, application representation of PREF as a priority queue of properties breaks for this case. The application is forced to drop consideration of PREF and group in these cases and should be explicitly allowed to do so (even though it may support PREF and grouping in the general case). ====================================== ====================================== Verifier notes: This is a complicated issue that needs discussion and that goes well beyond what errata can cover. I'm marking this as "held for document update" to leave the introduction to the issue here, because the confusion about how to interoperate here is real. But readers need to follow any subsequent discussion on the vcarddav mailing list. ====================================== -------------------------------------- RFC6350 (draft-ietf-vcarddav-vcardrev-22) -------------------------------------- Title : vCard Format Specification Publication Date : August 2011 Author(s) : S. Perreault Category : PROPOSED STANDARD Source : vCard and CardDAV Area : Applications Stream : IETF Verifying Party : IESG
- [VCARDDAV] [Technical Errata Reported] RFC6350 (4… RFC Errata System
- Re: [VCARDDAV] [Technical Errata Reported] RFC635… Barry Leiba
- Re: [VCARDDAV] [Technical Errata Reported] RFC635… Simon Perreault
- Re: [VCARDDAV] [Technical Errata Reported] RFC635… Barry Leiba
- Re: [VCARDDAV] [Technical Errata Reported] RFC635… Simon Perreault
- Re: [VCARDDAV] [Technical Errata Reported] RFC635… Barry Leiba
- [VCARDDAV] [Errata Held for Document Update] RFC6… RFC Errata System