UserPreferences

PaceUriOrItsSuccessor


Abstract

[MarkPilgrim] Make all references to RFC 2396 into "RFC 2396 or its successor" so that when [WWW]RFC 2396bis is done, Atom can inherit it without revving the spec.

Status

Open

Rationale

RFC 2396bis slightly improves internationalization support for URIs (it is somewhat clearer than RFC 2396 that using UTF-8 for encoding character into octets is a good thing. It also contains a new section explaining encoding issues in much more detail. But it doesn't allow using non-ASCII characters, that's what the IRI spec is for.). The BNF has been carefully revised and tested, and can be used to create a parser. A coherent discussion of how to compare two URIs has been added. There is a better explanation of when to percent-encode and when to not percent-encode. It will become the new standard for URIs (it is already the de facto standard in modern browsers). Atom should plan for its arrival by referencing "RFC 2396 or its successor" to define URIs.

Proposal

In section 3.2.2, change "The content of atom:url in a Person construct MUST be a URI [RFC2396]." to "The content of atom:url in a Person construct MUST be a URI [RFC2396 or its successor]."

In section 3.4.3, change "Link constructs MUST have a href attribute, whose value MUST be a URI [RFC2396]." to "Link constructs MUST have a href attribute, whose value MUST be a URI [RFC2396 or its successor]."

In section 4.8, change "The content of this element, when present, MUST be a URI." to "The content of this element, when present, MUST be a URI [RFC2396 or its successor]."

In section 4.9, change "The atom:generator element MAY have a "url" attribute whose value MUST be a URI" to "The atom:generator element MAY have a "url" attribute whose value MUST be a URI [RFC 2396 or its successor]"

Impacts

Unknown (FIXME)

Notes

See also PaceIRI.


CategoryProposals