RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 7 records.

Status: Verified (3)

RFC 4480, "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", July 2006

Source of RFC: simple (rai)

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

Reported By: Raphael Bossek
Date Reported: 2011-09-07
Verifier Name: Robert Sparks
Date Verified: 2012-02-08

Section 7.2. says:

7.2. Schema Registration for Schema ............................32
     'urn:ietf:params:xml:ns:pidf:status:rpid'

----on the page 32----

7.2.  Schema Registration for Schema
      'urn:ietf:params:xml:ns:pidf:status:rpid'

   URI:  urn:ietf:params:xml:ns:pidf:status:rpid

It should say:

7.2. Schema Registration for Schema ............................32
     'urn:ietf:params:xml:schema:pidf:status:rpid'

----on the page 32----

7.2.  Schema Registration for Schema
      'urn:ietf:params:xml:schema:pidf:status:rpid'

   URI:  urn:ietf:params:xml:schema:pidf:status:rpid

Notes:

The XML Schema sub-namespace is 'urn:ietf:params:xml:schema:pidf:status:rpid' (instead of 'urn:ietf:params:xml:ns:pidf:status:rpid') as registered in the IANA maintained registry at http://www.iana.org/assignments/xml-registry/schema.html

RFC 3688: The IETF XML Registry; Syntax for XML schema sub-namespace define the XML Schema namespace syntax as "urn:ietf:params:xml:schema:<id>".

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

Reported By: Ben Campbell
Date Reported: 2013-04-17
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-04-17

Section 5.1 says:

[There are 8 occurrences of the following element in the schema in section 5.1]   

      <xs:attributeGroup ref="fromUntil"/>

It should say:

[Each occurrence should be replaced with the following]

     <xs:attributeGroup ref="dm:fromUntil"/>

Notes:

fromUntil is imported from the presence data model namespace "urn:ietf:params:xml:ns:pidf:data-model". This schema imports that namespace with a prefix of "dm". (see beginning of section 5.1) The prefix was left off of the "fromUntil" entries.

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

Reported By: John Huang
Date Reported: 2007-09-07

The header on every page says:

RFC 4480                          RIPD                         July 2006

It should say:

RFC 4480                          RPID                         July 2006

Status: Held for Document Update (3)

RFC 4480, "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", July 2006

Source of RFC: simple (rai)

Errata ID: 2961
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Raphael Bossek
Date Reported: 2011-09-07
Held for Document Update by: Robert Sparks

Section 4. says:

<rpid:sphere>bowling league</rpid:sphere>

It should say:

<rpid:sphere><bowlingleague/></rpid:sphere>

Notes:

The <sphere> content type is 'element-only'; it's not valid to use tokens. It's possible to use XML elements from other XML namespace (e.g. <bowlingleague/>) or choose one of the following: <rpid:work/>, <rpid:home/>, <rpid:unknown/>

Errata ID: 2962
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Raphael Bossek
Date Reported: 2011-09-08
Held for Document Update by: Robert Sparks

Section 4. says:

<dm:deviceID>urn:device:0003ba4811e3</dm:deviceID>
...
<dm:deviceID>urn:x-mac:0003ba4811e3</dm:deviceID>
...
<dm:deviceID>urn:device:0003ba4811e3</dm:deviceID>

It should say:

Replace all three with

<dm:deviceID>urn:uuid:698137d0-b395-11e0-aff2-0800200c9a66</dm:deviceID>

Notes:

"urn:device" is a not registered URN namespace as defined by RFC3406: Uniform Resource Names (URN) Namespace Definition Mechanisms. "urn:x-mac" is an experimental URN namespace. All <dm:deviceID> address point to the same device.
RFC 4479 in section 3.4. Device RECOMMENDS version 1 UUIDs for the <deviceID> element: "For devices with a MAC address, version 1 UUIDs are RECOMMENDED, as they result in a time-based identifier that makes use of the MAC address."

Errata ID: 3121
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Peter Saint-Andre
Date Reported: 2012-02-14
Held for Document Update by: Richard Barnes
Date Held: 2013-04-16

Section 7.2 says:

                 <xs:element name="looking-for-work"
                   type="empty" />
                 <xs:element name="meal"
                   type="empty" />

It should say:

                 <xs:element name="looking-for-work"
                   type="empty" />
                 <xs:element name="lunch"
                   type="empty" />
                 <xs:element name="meal"
                   type="empty" />

Notes:

Erratum #2959 claimed that the element "lunch" needs to be removed from the specification since it is not included in the schema. However, the schema was in error. This erratum corrects the schema so that, if approved, IANA can update the information at http://www.iana.org/assignments/xml-registry/schema/pidf/status/rpid.xsd

Implementors using the schema as updated by this erratum should note that if they produce documents that include the "lunch" element, then these documents might be rejected as invalid by implementations using the original schema.

Status: Rejected (1)

RFC 4480, "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", July 2006

Source of RFC: simple (rai)

Errata ID: 2959
Status: Rejected
Type: Technical
Publication Format(s) : TEXT

Reported By: Raphael Bossek
Date Reported: 2011-09-07
Rejected by: Richard Barnes
Date Rejected: 2013-04-16

Section 3.2. says:

Activities such as <appointment>, <breakfast>, <dinner>, <holiday>,
<lunch>, <meal>, <meeting>, <performance>, <travel>, or <vacation>
can often be derived from calendar information.

----on the next page----

lunch:  The person is eating his or her midday meal.

It should say:

Activities such as <appointment>, <breakfast>, <dinner>, <holiday>,
<meal>, <meeting>, <performance>, <travel>, or <vacation>
can often be derived from calendar information.

----on the next page----

(delete this line)

Notes:

The <lunch> activity is not allowed because not defined by the XML Schema in section in section 5.1. Because the XML Schema is immutable the documentation should be corrected.

--VERIFIER NOTES--
This erratum had previously been held for document update, but has since been rejected in favor of Erratum 3121. Please see that erratum at <http://www.rfc-editor.org/errata_search.php?eid=3121>

Report New Errata



Advanced Search