RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (1)

RFC 3470, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", January 2003

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

Errata ID: 268

Status: Verified
Type: Technical

Reported By: Larry Masinter
Date Reported: 2003-04-25

Section 4.13 says:

   "numeric entity reference"  

It should say:

   "numeric character reference"

Notes:

Section 4.16:
"In XML instances all white space is considered significant and
is by default visible to processing applications."
Should be:
"In XML instances, white space is often significant and visible
to processing applications."

Status: Held for Document Update (1)

RFC 3470, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", January 2003

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

Errata ID: 3789

Status: Held for Document Update
Type: Editorial

Reported By: Erik Wilde
Date Reported: 2013-11-07
Held for Document Update by: Barry Leiba
Date Held: 2014-01-14

Section 4.2 says:

It some cases, protocols have been defined

It should say:

In some cases, protocols have been defined

Notes:

Simple typo

----- Verifier notes -----
Simple typos just go into "hold for document update". Best to resist the urge to submit them, unless they're likely to cause confusion.

Status: Rejected (1)

RFC 3470, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", January 2003

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

Errata ID: 3790

Status: Rejected
Type: Technical

Reported By: Erik Wilde
Date Reported: 2013-11-07
Rejected by: Barry Leiba
Date Rejected: 2013-11-07

Section 4.2 says:

n/a

It should say:

n/a

Notes:

While at the time of writing the Infoset was the most relevant spec, now there's XDM, which is more relevant now.

It also might make sense to describe the differences between XML syntax and the more abstract view of Infoset/XML in detail, in particular when it comes to nasty edge cases such as unserializable Infosets, and the fact that some information present in the XML syntax gets lost in the more abstract view.
--VERIFIER NOTES--
As the report says,"at the time of writing the Infoset was the most relevant spec" -- and errata are here to report things that would have been considered errors at the time of writing, but they got missed. This isn't that.

Report New Errata



Search RFCs
Advanced Search
×