errata logo graphic

Found 9 records.

Status: Verified (5)

RFC6321, "xCal: The XML Format for iCalendar", August 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 3042

Status: Verified
Type: Technical

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

Section Appendix A says:

  # 3.6.6 Alarm Component

  component-valarm = element valarm {
       audioprop | dispprop | emailprop
   }

   type-audioprop = element properties {
       property-action &

       property-trigger &

       (property-duration, property-repeat)? &

       property-attach?
   }

   type-dispprop = element properties {
       property-action &
       property-description &
       property-trigger &
       property-summary &

       property-attendee+ &

       (property-duration, property-repeat)? &

       property-attach*
   }

   type-emailprop = element properties {
       property-action &
       property-description &
       property-trigger &

       (property-duration, property-repeat)?
   }

It should say:

  # 3.6.6 Alarm Component

  component-valarm = element valarm {
       type-audioprop | type-dispprop | type-emailprop
   }

   type-audioprop = element properties {
       property-action &

       property-trigger &

       (property-duration, property-repeat)? &

       property-attach?
   }

   type-emailprop = element properties {
       property-action &
       property-description &
       property-trigger &
       property-summary &

       property-attendee+ &

       (property-duration, property-repeat)? &

       property-attach*
   }

   type-dispprop = element properties {
       property-action &
       property-description &
       property-trigger &

       (property-duration, property-repeat)?
   }

Notes:

* the alarm properties lack the "type-"
* dispprop and emailprop have been exchanged


Errata ID: 3050

Status: Verified
Type: Technical

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

Section Appendix A says:

   type-bysecond = element bysecond {
       xsd:positiveInteger
   }

   type-byminute = element byminute {
       xsd:positiveInteger
   }

   type-byhour = element byhour {
       xsd:positiveInteger
   }

It should say:

type-bysecond = element bysecond {
       xsd:nonNegativeInteger
   }

   type-byminute = element byminute {
       xsd:nonNegativeInteger
   }

   type-byhour = element byhour {
       xsd:nonNegativeInteger
   }

Notes:

Those values can be 0 (per RFC 5545) and xsd:positiveInteger doesn't allow that.


Errata ID: 3679

Status: Verified
Type: Technical

Reported By: Michael Angstadt
Date Reported: 2013-07-11
Verifier Name: Barry Leiba
Date Verified: 2013-08-21

Section B.2.2 says:

<tzid>US/Eastern</tzid>

It should say:

<tzid><text>US/Eastern</text></tzid>

Notes:

The "tzid" property in the second example (p.51) is not formatted correctly. The property value should be enclosed in a "<text>" element.


Errata ID: 2929

Status: Verified
Type: Editorial

Reported By: Philipp Kewisch
Date Reported: 2011-08-10
Verifier Name: Peter Saint-Andre
Date Verified: 2011-08-12

Section B.2.1. says:

VERSION:2.0
PRODID:-//Example Corp.//Example Client//EN
BEGIN:VTIMEZONE

It should say:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Example Inc.//Example Client//EN
BEGIN:VTIMEZONE

Notes:

Example Inc. is used in all examples, especially in Section B.2.2, the matching XML Data. Also, the BEGIN:VCALENDAR is missing.


Errata ID: 3892

Status: Verified
Type: Editorial

Reported By: Clement Pellerin
Date Reported: 2014-02-14
Verifier Name: Barry Leiba
Date Verified: 2014-02-14

Section B.1.1 says:

   BEGIN:VCALENDAR
   CALSCALE:GREGORIAN
   PRODID:-//Example Inc.//Example Calendar//EN
   VERSION:2.0
   BEGIN:VEVENT
   DTSTAMP:20080205T191224Z
   DTSTART:20081006
   SUMMARY:Planning meeting
   UID:4088E990AD89CB3DBB484909
   END:VEVENT
   END:VCALENDAR

It should say:

   BEGIN:VCALENDAR
   CALSCALE:GREGORIAN
   PRODID:-//Example Inc.//Example Calendar//EN
   VERSION:2.0
   BEGIN:VEVENT
   DTSTAMP:20080205T191224Z
   DTSTART;VALUE=DATE:20081006
   SUMMARY:Planning meeting
   UID:4088E990AD89CB3DBB484909
   END:VEVENT
   END:VCALENDAR


Notes:

The default value type of DTSTART is DATE-TIME. The definition of DATE-TIME makes the time portion mandatory. By declaring the value type explicitly, this solution makes the value legal and matches the xCal sample in B.1.2

Another solution is to change the property value to match the default DATE-TIME type
DTSTART:20081006T191224Z
and adjust the xCal example in B.1.2 to match
<dtstart>
<date-time>2008-10-06T19:12:24Z</date-time>
</dtstart>


Status: Held for Document Update (4)

RFC6321, "xCal: The XML Format for iCalendar", August 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 3315

Status: Held for Document Update
Type: Technical

Reported By: Norman Walsh
Date Reported: 2012-08-12
Held for Document Update by: Barry Leiba

Section Appendix A says:

   type-until = element until {
       type-date |
       type-date-time
   }

It should say:

???

Notes:

The type-date and type-date-time patterns are undefined in the schema.


Errata ID: 3316

Status: Held for Document Update
Type: Technical

Reported By: Norman Walsh
Date Reported: 2012-08-12
Held for Document Update by: Barry Leiba

Section Appendix A says:

   type-byday = element byday {
       xsd:integer?,
       type-weekday
   }

It should say:

???

Notes:

That's not a valid RELAX NG pattern. It's an attempt to group "string" and "data" patterns.


Errata ID: 2938

Status: Held for Document Update
Type: Editorial

Reported By: Hamish Lawson
Date Reported: 2011-08-15
Held for Document Update by: Peter Saint-Andre

Section 3.4.1.2 says:

These are an IC:latitude element and an IC:longitude
element, each of which contains float values.

It should say:

 These are an IC:latitude element and an IC:longitude
 element, each of which contains a float value.

Notes:

The existing text erroneously suggests that multiple values could be contained by each element.


Errata ID: 3314

Status: Held for Document Update
Type: Editorial

Reported By: Norman Walsh
Date Reported: 2012-08-12
Held for Document Update by: Barry Leiba

Section Appendix A says:

   # 3.6.5 Time Zone Component

   component-vtimezone = element vtimezone {
       element properties {
           property-tzid &

           property-last-mod? &
           property-tzuurl?
       },

It should say:

   # 3.6.5 Time Zone Component

   component-vtimezone = element vtimezone {
       element properties {
           property-tzid &

           property-last-mod? &
           property-tzurl?
       },

Notes:

The property-tzurl pattern name is misspelled.


Report New Errata