Upgrading to JAXP 1.3 APIs.

git-svn-id: https://svn.apache.org/repos/asf/xml/commons/trunk@226184 13f79535-47bb-0310-9956-ffa450edef68

java/external/src/org/xml/sax/ext/package.html

@@ -1,33 +1,36 @@
 <HTML><HEAD>
-
+<!-- $Id$ -->
 </HEAD><BODY>
 
 <p>
-This package contains interfaces to optional SAX2 handlers.
+This package contains interfaces to SAX2 facilities that
+conformant SAX drivers won't necessarily support.
 
 <p>See <a href='http://www.saxproject.org'>http://www.saxproject.org</a>
 for more information about SAX.</p>
 
-<p>
-The package is independent of the SAX2 core, though the functionality
-exposed generally needs to be implemented within a parser.
+<p> This package is independent of the SAX2 core, though the functionality
+exposed generally needs to be implemented within a parser core.
 That independence has several consequences:</p>
 
 <ul>
 
-<li>SAX2 drivers are <em>not</em> required to recognize these handlers,
-and you cannot assume that the class files will be present in every SAX2
+<li>SAX2 drivers are <em>not</em> required to recognize these handlers.
+</li>
+
+<li>You cannot assume that the class files will be present in every SAX2
 installation.</li>
 
 <li>This package may be updated independently of SAX2 (i.e. new
-handlers may be added without updating SAX2 itself).</li>
+handlers and classes may be added without updating SAX2 itself).</li>
 
-<li>The handlers are not implemented by the SAX2
+<li>The new handlers are not implemented by the SAX2
 <code>org.xml.sax.helpers.DefaultHandler</code> or
 <code>org.xml.sax.helpers.XMLFilterImpl</code> classes.
-You can subclass these if you need such behaviour.</li>
+You can subclass these if you need such behavior, or
+use the helper classes found here.</li>
 
-<li>The handlers need to be registered differently than regular SAX2
+<li>The handlers need to be registered differently than core SAX2
 handlers.</li>
 
 </ul>
@@ -37,13 +40,7 @@ designed both to allow SAX parsers to pass certain types of information
 to applications, and to serve as a simple model for other SAX2 parser
 extension packages.  Not all such extension packages should need to
 be recognized directly by parsers, however.
-As an example, most schema systems can be cleanly layered on top
+As an example, most validation systems can be cleanly layered on top
 of parsers supporting the standardized SAX2 interfaces.  </p>
 
-<p><strong>NOTE:</strong> this package alone does add any
-functionality; it simply provides optional interfaces for SAX2 drivers
-to use.  You must use a SAX2 driver that recognizes these interfaces if
-you actually want to have access to lexical and declaration
-information.</p>
-
 </BODY></HTML>