RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 8 records.

Status: Verified (5)

RFC 6351, "xCard: vCard XML Representation", August 2011

Note: This RFC has been updated by RFC 6868

Source of RFC: vcarddav (app)

Errata ID: 2994
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Simon Perreault
Date Reported: 2011-10-12
Verifier Name: Peter Saint-Andre
Date Verified: 2011-10-17

Section Appendix A says:

# 6.1.3
property-source = element source {
    element parameters { param-altid, param-pid, param-pref,
                         param-mediatype },
    value-uri
  }

It should say:

# 6.1.3
property-source = element source {
    element parameters { param-altid, param-pid, param-pref,
                         param-mediatype }?,
    value-uri
  }

Notes:

Parameters are optional, so there needs to be a ? at the end.

Errata ID: 3047
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Christian Mollekopf
Date Reported: 2011-12-08
Verifier Name: Peter Saint-Andre
Date Verified: 2011-12-09

Section Appendix A. says:

# 6.4.1
property-tel = element tel {
    element parameters {
      param-altid,
      param-pid,
      param-pref,
      element type {
        element text { "work" | "home" | "text" | "voice"
                     | "fax" | "cell" | "video" | "pager"
                     | "textphone" }+
      }?,
      param-mediatype
    }?,
    (value-text | value-uri)
  }

It should say:

# 6.4.1
property-tel = element tel {
    element parameters {
      param-altid,
      param-pid,
      param-pref,
      element type {
        element text { "work" | "home" | "text" | "voice"
                     | "fax" | "cell" | "video" | "pager"
                     | "textphone" | x-name | iana-token }+
      }?,
      param-mediatype
    }?,
    (value-text | value-uri)
  }

Notes:

x-name and iana-token is missing in a couple of explicit listings of values, the above is just an example. RFC6350 allows extending these values with own x-names though.

This should be corrected in:
param-type
param-calscale
property-tel

Errata ID: 4241
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Ivan Enderlin
Date Reported: 2015-01-26
Verifier Name: Barry Leiba
Date Verified: 2015-01-26

Section 5 says:

     BEGIN:VCARD
     VERSION:4.0
     contact.FN=...
     contact.EMAIL=...
     media.PHOTO=...
     CATEGORIES=...
     END:VCARD

It should say:

     BEGIN:VCARD
     VERSION:4.0
     contact.FN:...
     contact.EMAIL:...
     media.PHOTO:...
     CATEGORIES:...
     END:VCARD

Notes:

Property names and values are separated by a colon, not an equal sign.

Errata ID: 4243
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Ivan Enderlin
Date Reported: 2015-01-27
Verifier Name: Barry Leiba
Date Verified: 2015-01-27

Section 5.1 says:

   Examples:

     <x-my-prop>
       <parameters>
         <pref><integer>1</integer></pref>
       </parameters>
       <text>value goes here</text>
     </x-my-prop>

     <ext:my-prop
         ext:xmlns="http://example.com/extensions/my-vcard">
       <parameters>
         <pref><integer>1</integer></pref>
       </parameters>                 <!-- Core vCard elements  -->
       <text>value goes here</text>  <!-- are still accessible -->
     </ext:my-prop>

It should say:

   Examples:

     <x-my-prop>
       <parameters>
         <pref><integer>1</integer></pref>
       </parameters>
       <text>value goes here</text>
     </x-my-prop>

     <ext:my-prop
         xmlns:ext="http://example.com/extensions/my-vcard">
       <parameters>
         <pref><integer>1</integer></pref>
       </parameters>                 <!-- Core vCard elements  -->
       <text>value goes here</text>  <!-- are still accessible -->
     </ext:my-prop>

Notes:

The correct declaration of the "ext" namespace is "xmlns:ext", not "ext:xmlns".

Errata ID: 4247
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Ivan Enderlin
Date Reported: 2015-01-28
Verifier Name: Barry Leiba
Date Verified: 2015-02-01

Section Appendix A says:

# 4.3.2
value-time = element time {
    xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)"
                         ~ "(Z|[+\-]\d\d(\d\d)?)?" }
  }

It should say:

# 4.3.2
value-time = element time {
    xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d)?|--\d\d)"
                         ~ "(Z|[+\-]\d\d(\d\d)?)?" }
  }

Notes:

The second element of the first disjunction is -\d\d(\d\d)?, not -\d\d(\d\d?) (the question mark is not well placed).

Status: Reported (2)

RFC 6351, "xCard: vCard XML Representation", August 2011

Note: This RFC has been updated by RFC 6868

Source of RFC: vcarddav (app)

Errata ID: 6577
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Sergei S. Betke
Date Reported: 2021-05-08

Section Appendix A says:

# 6.2.7
property-gender = element gender {
    element sex { "" | "M" | "F" | "O" | "N" | "U" },
    element identity { text }?
  }

It should say:

# 6.2.7
property-gender = element gender {
    element sex { "M" | "F" | "O" | "N" | "U" }?,
    element identity { text }?
  }

Notes:

RFC 6350: The components correspond, in sequence, to the sex (biological), and gender identity. Each component is OPTIONAL.

Errata ID: 6578
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Sergei S. Betke
Date Reported: 2021-05-08

Section Appendix A says:

# 6.3.1
param-label = element label { value-text }?
property-adr = element adr {
    element parameters { param-language, param-altid, param-pid,
                         param-pref, param-type, param-geo, param-tz,
                         param-label }?,
    element pobox { text }+,
    element ext { text }+,
    element street { text }+,
    element locality { text }+,
    element region { text }+,
    element code { text }+,
    element country { text }+
  }

It should say:

# 6.3.1
param-label = element label { value-text }?
property-adr = element adr {
    element parameters { param-language, param-altid, param-pid,
                         param-pref, param-type, param-geo, param-tz,
                         param-label }?,
    element pobox { text }?,
    element ext { text }?,
    element street { text }?,
    element locality { text }?,
    element region { text }?,
    element code { text }?,
    element country { text }?
  }

Notes:

Multiply values for one address component does not allowed!

RFC 6350: Special notes: The structured type value consists of a sequence of address components. The component values MUST be specified in their corresponding position.
When a component value is missing, the associated component separator MUST still be specified.

Status: Held for Document Update (1)

RFC 6351, "xCard: vCard XML Representation", August 2011

Note: This RFC has been updated by RFC 6868

Source of RFC: vcarddav (app)

Errata ID: 3008
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Torsten Fusswinkel
Date Reported: 2011-10-31
Held for Document Update by: Peter Saint-Andre

Section Appendix A says:

### Section 3.3: vCard Format Specification
#
# 3.3
iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" }
x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" }

It should say:

### Section 3.3: vCard Format Specification
#
# 3.3
iana-token = xsd:string { pattern = "[a-zA-Z0-9\-]+" }
x-name = xsd:string { pattern = "x-[a-zA-Z0-9\-]+" }

Notes:

The minus sign has to be escaped with a backslash.

Report New Errata



Advanced Search