--- 1/draft-ietf-appsawg-about-uri-scheme-02.txt	2012-03-04 06:13:57.390672532 +0100
+++ 2/draft-ietf-appsawg-about-uri-scheme-03.txt	2012-03-04 06:13:57.406670941 +0100
@@ -1,18 +1,18 @@
 
 Applications Area WG (APPSAWG)                              L. Hunt, Ed.
 Internet-Draft                                      Opera Software, ASA.
 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
-                 draft-ietf-appsawg-about-uri-scheme-02
+                 draft-ietf-appsawg-about-uri-scheme-03
 
 Abstract
 
    This document specifies the "about" URI scheme, that is widely used
    by Web browsers and some other applications to designate access to
    their internal resources, such as settings, application information,
    hidden built-in functionality, and so on.
 
 Status of this Memo
 
@@ -228,29 +228,20 @@
    | blank            | Used in "about" URIs to refer to   | RFC xxxx  |
    |                  | blank page.                        |           |
    +------------------+------------------------------------+-----------+
 
    The registration procedures for this registry are "First Come First
    Served", described in RFC 5226 [RFC5226], with supporting
    documentation meeting the requirements below.  The registrant of the
    token MUST provide the following registration template, which will be
    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
      "about" URIs.
 
    o Intended usage:  A short description of how "about" URIs with the
      registered token must be handled; especially, what they must be
      resolved to, if resolvable.
 
    o Handling query component:  It should be mentioned whether there are
      some provisions on handling query components in the "about" URIs
      with the registered token.