RFC Errata
Found 2 records.
Status: Verified (2)
RFC 5005, "Feed Paging and Archiving", September 2007
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 1685
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Julian Reschke
Date Reported: 2009-02-18
Verifier Name: Alexey Melnikov
Date Verified: 2010-05-11
Section 4 says:
<entry>
<title>Atom-Powered Robots Scheduled To Run Amok</title>
<link href="http://example.org/2003/11/24/robots_coming"/>
| <id>urn:uuid:cdef5c6d5-gff8-4ebb-assa-80dwe44efkjo</id>
<updated>2003-11-24T12:00:00Z</updated>
<summary>Some text from an old, different entry.</summary>
</entry>
It should say:
<entry>
<title>Atom-Powered Robots Scheduled To Run Amok</title>
<link href="http://example.org/2003/11/24/robots_coming"/>
| <id>urn:uuid:2c355272-fd98-11dd-8474-0016415cd53f</id>
<updated>2003-11-24T12:00:00Z</updated>
<summary>Some text from an old, different entry.</summary>
</entry>
Notes:
The example UUID has the wrong number of characters in the first part, and non-hex digits in the last two parts (see http://intertwingly.net/blog/2009/02/17/White-House-FeedBack-Loop).
(The suggested replacement has a freshly minted UUID)
Errata ID: 1806
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Nottingham
Date Reported: 2009-07-12
Verifier Name: Alexey Melnikov
Date Verified: 2010-05-11
Throughout the document, when it says:
URI
It should say:
IRI
Notes:
Atom defines links as IRIs, not URIs; they should not be constrained to URIs.
Also implies a reference to RFC3987 (or successor).