draft-ietf-appsawg-about-uri-scheme-02.txt   draft-ietf-appsawg-about-uri-scheme-03.txt 
Applications Area WG (APPSAWG) L. Hunt, Ed. Applications Area WG (APPSAWG) L. Hunt, Ed.
Internet-Draft Opera Software, ASA. Internet-Draft Opera Software, ASA.
Intended Status: Standards Track M. Yevstifeyev, Ed. Intended Status: Standards Track M. Yevstifeyev, Ed.
Expires: September 4, 2012 March 3, 2012 Expires: September 5, 2012 March 4, 2012
The "about" URI Scheme The "about" URI Scheme
draft-ietf-appsawg-about-uri-scheme-02 draft-ietf-appsawg-about-uri-scheme-03
Abstract Abstract
This document specifies the "about" URI scheme, that is widely used This document specifies the "about" URI scheme, that is widely used
by Web browsers and some other applications to designate access to by Web browsers and some other applications to designate access to
their internal resources, such as settings, application information, their internal resources, such as settings, application information,
hidden built-in functionality, and so on. hidden built-in functionality, and so on.
Status of this Memo Status of this Memo
skipping to change at page 5, line 49 skipping to change at page 5, line 49
| blank | Used in "about" URIs to refer to | RFC xxxx | | blank | Used in "about" URIs to refer to | RFC xxxx |
| | blank page. | | | | blank page. | |
+------------------+------------------------------------+-----------+ +------------------+------------------------------------+-----------+
The registration procedures for this registry are "First Come First The registration procedures for this registry are "First Come First
Served", described in RFC 5226 [RFC5226], with supporting Served", described in RFC 5226 [RFC5226], with supporting
documentation meeting the requirements below. The registrant of the documentation meeting the requirements below. The registrant of the
token MUST provide the following registration template, which will be token MUST provide the following registration template, which will be
made available on IANA web site: made available on IANA web site:
[[for the WG discussion: I, as the WG participant, am convinced that
we do need Specification Required here. This is a burden, but this
(and the expert) will give us a warranty that the registered token is
really useful and is really part of some serious project, probably
standardization effort. I'd like this also would be discussed in the
WG, and the WG would change its mind. (Moreover, as I don't expect
the registrations to be very often, this won't take a great deal of
experts' time.)]]
o Registered Token: The desired special-purpose token to be used in o Registered Token: The desired special-purpose token to be used in
"about" URIs. "about" URIs.
o Intended usage: A short description of how "about" URIs with the o Intended usage: A short description of how "about" URIs with the
registered token must be handled; especially, what they must be registered token must be handled; especially, what they must be
resolved to, if resolvable. resolved to, if resolvable.
o Handling query component: It should be mentioned whether there are o Handling query component: It should be mentioned whether there are
some provisions on handling query components in the "about" URIs some provisions on handling query components in the "about" URIs
with the registered token. with the registered token.
 End of changes. 3 change blocks. 
11 lines changed or deleted 2 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/