RFC Errata System | 2 Feb 15:56 2016

[Editorial Errata Reported] RFC6352 (4610)

The following errata report has been submitted for RFC6352,
"CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6352&eid=4610

--------------------------------------
Type: Editorial
Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>

Section: 8.7

Original Text
-------------
The request MUST include a Depth: 0 header; however, the actual
      scope of the REPORT is determined as described above.

Corrected Text
--------------
The request MUST include a Depth: 1 header; however, the actual
      scope of the REPORT is determined as described above.

Notes
-----
All examples of a addressbook-multiget query use Depth: 1 header, but the 8.7 section says it must be Depth:
0. I believe the mistake is in the documentation.

Instructions:
-------------
(Continue reading)

RFC Errata System | 12 Dec 15:17 2015

[Errata Verified] RFC6474 (4556)

The following errata report has been verified for RFC6474,
"vCard Format Extensions: Place of Birth, Place and Date of Death". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6474&eid=4556

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>
Date Reported: 2015-12-07
Verified by: Barry Leiba (IESG)

Section: 2.3

Original Text
-------------
DEATHDATE;19531015T231000Z

Corrected Text
--------------
DEATHDATE:19531015T231000Z

Notes
-----
A typo when declaring the third DEATHDATE property example: It is a colon, not a semi-colon.

--------------------------------------
(Continue reading)

RFC Errata System | 12 Dec 15:15 2015

[Errata Verified] RFC6474 (4559)

The following errata report has been verified for RFC6474,
"vCard Format Extensions: Place of Birth, Place and Date of Death". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6474&eid=4559

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>
Date Reported: 2015-12-07
Verified by: Barry Leiba (IESG)

Section: 2.2

Original Text
-------------
DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833

Corrected Text
--------------
DEATHPLACE;VALUE=uri:geo:41.731944\\\\,-49.945833

Notes
-----
Section 3.4 in RFC 6350 states that all property values must have COMMA characters escaped with a BACKSLASH
character. The DEATHPLACE property value in the example contains a comma. Therefore it must be escaped
with a backslash.
(Continue reading)

RFC Errata System | 12 Dec 15:14 2015

[Errata Verified] RFC6474 (4557)

The following errata report has been verified for RFC6474,
"vCard Format Extensions: Place of Birth, Place and Date of Death". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6474&eid=4557

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>
Date Reported: 2015-12-07
Verified by: Barry Leiba (IESG)

Section: 2.1

Original Text
-------------
BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079

Corrected Text
--------------
BIRTHPLACE;VALUE=uri:geo:46.769307\\\\,-71.283079

Notes
-----
Section 3.4 in RFC 6350 states that all property values must have COMMA characters escaped with a BACKSLASH
character. The BIRTHPLACE property value in the example contains a comma. Therefore it must be escaped
with a backslash.
(Continue reading)

Simon Perreault | 7 Dec 15:25 2015
Gravatar

Re: [Technical Errata Reported] RFC6474 (4557)

Le 2015-12-07 09:18, Sylvain Berfini a écrit :
> Actually I only set one when I submitted the errata. I don't know why it
> put it twice (also on errata 4559).

Ah, probably just a bug in the mailer then.

A single backslash would be correct. No impact on interop either because
this is example text. Same for errata 4559.

Simon

> Le 07/12/2015 15:17, Simon Perreault a écrit :
>> Le 2015-12-07 06:22, RFC Errata System a écrit :
>>> Original Text
>>> -------------
>>> BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079
>>>
>>> Corrected Text
>>> --------------
>>> BIRTHPLACE;VALUE=uri:geo:46.769307\\,-71.283079
>>>
>>> Notes
>>> -----
>>> Section 3.4 in RFC 6350 states that all property values must have
>>> COMMA characters escaped with a BACKSLASH character. The BIRTHPLACE
>>> property value in the example contains a comma. Therefore it must be
>>> escaped with a backslash.
>> Why two backslashes?
>>
>> Simon
(Continue reading)

RFC Errata System | 7 Dec 12:23 2015

[Technical Errata Reported] RFC6474 (4559)

The following errata report has been submitted for RFC6474,
"vCard Format Extensions: Place of Birth, Place and Date of Death".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6474&eid=4559

--------------------------------------
Type: Technical
Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>

Section: 2.2

Original Text
-------------
DEATHPLACE;VALUE=uri:geo:41.731944,-49.945833

Corrected Text
--------------
DEATHPLACE;VALUE=uri:geo:41.731944,\\-49.945833

Notes
-----
Section 3.4 in RFC 6350 states that all property values must have COMMA characters escaped with a BACKSLASH
character. The DEATHPLACE property value in the example contains a comma. Therefore it must be escaped
with a backslash.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
(Continue reading)

RFC Errata System | 7 Dec 12:22 2015

[Technical Errata Reported] RFC6474 (4557)

The following errata report has been submitted for RFC6474,
"vCard Format Extensions: Place of Birth, Place and Date of Death".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6474&eid=4557

--------------------------------------
Type: Technical
Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>

Section: 2.1

Original Text
-------------
BIRTHPLACE;VALUE=uri:geo:46.769307,-71.283079

Corrected Text
--------------
BIRTHPLACE;VALUE=uri:geo:46.769307\\,-71.283079

Notes
-----
Section 3.4 in RFC 6350 states that all property values must have COMMA characters escaped with a BACKSLASH
character. The BIRTHPLACE property value in the example contains a comma. Therefore it must be escaped
with a backslash.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
(Continue reading)

RFC Errata System | 7 Dec 12:18 2015

[Editorial Errata Reported] RFC6474 (4556)

The following errata report has been submitted for RFC6474,
"vCard Format Extensions: Place of Birth, Place and Date of Death".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6474&eid=4556

--------------------------------------
Type: Editorial
Reported by: Sylvain Berfini <sylvain.berfini <at> belledonne-communications.com>

Section: 2.3

Original Text
-------------
DEATHDATE;19531015T231000Z

Corrected Text
--------------
DEATHDATE:19531015T231000Z

Notes
-----
A typo when declaring the third DEATHDATE property example: It is a colon, not a semi-colon.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
(Continue reading)

RFC Errata System | 3 Mar 01:25 2015

[Errata Held for Document Update] RFC6350 (4261)

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=4261

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Ivan Enderlin <ivan.enderlin <at> fruux.com>
Date Reported: 2015-02-05
Held by: Barry Leiba (IESG)

Section: 4.3

Original Text
-------------
In RFC6351 (Appendice A), we have a Relax NG Schema defining date and
time format:

# 4.3.1
value-date = element date {
    xsd:string { pattern = "\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d" }
  }

# 4.3.2
value-time = element time {
    xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)"
(Continue reading)

RFC Errata System | 3 Mar 01:22 2015

[Errata Held for Document Update] RFC6350 (4245)

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=4245

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Ivan Enderlin <ivan.enderlin <at> fruux.com>
Date Reported: 2015-01-27
Held by: Barry Leiba (IESG)

Section: 6.7.7

Original Text
-------------
   Value type:  A semicolon-separated pair of values.  The first field
      is a small integer corresponding to the second field of a PID
      parameter instance.  The second field is a URI.  The "uuid" URN
      namespace defined in [RFC4122] is particularly well suited to this
      task, but other URI schemes MAY be used.

Corrected Text
--------------
   Value type:  A single structured text value consisting of components
      separated by the SEMICOLON character (U+003B). The first
      component is a small integer corresponding to the second
(Continue reading)

RFC Errata System | 5 Feb 10:42 2015

[Technical Errata Reported] RFC6350 (4261)

The following errata report has been submitted for RFC6350,
"vCard Format Specification".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6350&eid=4261

--------------------------------------
Type: Technical
Reported by: Ivan Enderlin <ivan.enderlin <at> fruux.com>

Section: 4.3

Original Text
-------------
In RFC6351 (Appendice A), we have a Relax NG Schema defining date and
time format:

# 4.3.1
value-date = element date {
    xsd:string { pattern = "\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d" }
  }

# 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)?)?" }
  }

# 4.3.3
(Continue reading)


Gmane