Found 2 records.

Status: Verified (2)

RFC 5023, "The Atom Publishing Protocol", October 2007

Note: This RFC has been updated by RFC 8996

Errata ID: 1304
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Julian Reschke
Date Reported: 2008-01-29
Verifier Name: Alexey Melnikov
Date Verified: 2010-05-21

Section 5.3 says:

   2.  If the Member Resource was created successfully, the server
       responds with a status code of 201 and a Location header that
       contains the IRI of the newly created Entry Resource.  Media
       Resources could have also been created and their IRIs can be
       found through the Entry Resource.  See Section 9.6 for more
       details.

It should say:

   2.  If the Member Resource was created successfully, the server
       responds with a status code of 201 and a Location header that
       contains the URI of the newly created Entry Resource.  Media
       Resources could have also been created and their IRIs can be
       found through the Entry Resource.  See Section 9.6 for more
       details.

Notes:

The Location header (as defined in HTTP/1.1) contains a URI, not a IRI.

Errata ID: 3207
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Rushforth
Date Reported: 2012-05-01
Verifier Name: Barry Leiba
Date Verified: 2012-05-04

Section p51 says:

   anyForeignElement =
       element * - atom:* {
          (attribute * { text }
           | text
           | anyElement)*
       }

It should say:

   anyForeignElement =
       element * - app:* {
          (attribute * { text }
           | text
           | anyElement)*
       }

Notes:

I believe the schema unintentionally prohibits atom:link from being included in the categories document. Given that in another schema in the same appendix it is allowed, and going by the text in the normative sections, I believe this must be a cut and paste error.

Report New Errata