RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (3)

RFC 6715, "vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group", August 2012

Source of RFC: vcarddav (app)

Errata ID: 3342
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Michael Angstadt
Date Reported: 2012-09-08
Verifier Name: Barry Leiba
Date Verified: 2012-09-08

Section 3.1 says: 

Description:

When a property is multi-valued, INDEX can be used to indicate an ordering or sequence of the values.  INDEX values must be strictly positive.  Zero is not allowed.

It should say:

Description:

When a property is multi-valued, INDEX can be used to indicate an ordering or sequence of the values.  INDEX values must be strictly positive.  Zero is not allowed.

If an instance of a multi-valued property does not have an INDEX value, then it is included at the end of the ordered sequence, as if it had a very high INDEX value. 

Notes:

It is not clear how a list of properties should be sorted if some of them have INDEX parameters and others do not.  This errata submission proposes that properties without an INDEX parameter be pushed to the end of the sorted list, as if they had a very high INDEX value.

For example, the ordering of the following properties is very clear, since they all have INDEX parameters:

INTEREST;INDEX=3:art
INTEREST;INDEX=2:baseball
INTEREST;INDEX=4:music
INTEREST;INDEX=1:hockey

The above example would be sorted as follows:

INTEREST;INDEX=1:hockey
INTEREST;INDEX=2:baseball
INTEREST;INDEX=3:art
INTEREST;INDEX=4:music

However, the spec does not provide guidance on how to sort a list of properties if some properties have INDEX parameters and others do not.  This errata submission suggests that the properties missing the INDEX parameter be pushed to the end of the sorted list.  For example:

Unsorted:

INTEREST:art
INTEREST;INDEX=2:baseball
INTEREST:music
INTEREST;INDEX=1:hockey

Sorted:

INTEREST;INDEX=1:hockey
INTEREST;INDEX=2:baseball
INTEREST:art
INTEREST:music

...OR...

INTEREST;INDEX=1:hockey
INTEREST;INDEX=2:baseball
INTEREST:music
INTEREST:art

Verifier note:
Something like this was meant to be in the document, but was left out.

Errata ID: 3340
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Angstadt
Date Reported: 2012-09-08
Verifier Name: Barry Leiba
Date Verified: 2012-09-08

Section 3.1 says: 

Examples:
ORG-URI;INDEX=1:http://mycompany.example1.com
ORG-URI;PREF=1;INDEX=2:http://mycompany.example2.com

It should say:

Examples:
ORG-DIRECTORY;INDEX=1:http://mycompany.example1.com
ORG-DIRECTORY;PREF=1;INDEX=2:http://mycompany.example2.com

Notes:

In the examples, the ORG-DIRECTORY property is incorrectly referred to as ORG-URI.

Errata ID: 3341
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Angstadt
Date Reported: 2012-09-08
Verifier Name: Barry Leiba
Date Verified: 2012-09-08

Section 5 says: 

     +-------+------------------------+------------------------+
     | Name- |                        |                        |
     | space | Property               | Reference              |
     +-------+------------------------+------------------------+
     |       | EXPERTISE              | RFC 6715, Section 2.1  |
     |       | HOBBY                  | RFC 6715, Section 2.2  |
     |       | INTEREST               | RFC 6715, Section 2.3  |
     |       | ORG-URI                | RFC 6715, Section 2.4  |
     +-------+------------------------+------------------------+

It should say:

     +-------+------------------------+------------------------+
     | Name- |                        |                        |
     | space | Property               | Reference              |
     +-------+------------------------+------------------------+
     |       | EXPERTISE              | RFC 6715, Section 2.1  |
     |       | HOBBY                  | RFC 6715, Section 2.2  |
     |       | INTEREST               | RFC 6715, Section 2.3  |
     |       | ORG-DIRECTORY          | RFC 6715, Section 2.4  |
     +-------+------------------------+------------------------+

Notes:

The ORG-DIRECTORY property is incorrectly referred to as ORG-URI.

Report New Errata



Advanced Search