Update docs for 1.0.b1 release

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

README.html

@@ -98,8 +98,32 @@ xml.apache.org subprojects.</p>
   <div class="category"><div class="label"><a name="guidelines">Commons Guidelines</a></div><div class="content">
 <p>As the community forms, we need to formalize these guidelines, especially to differentiate 
 'requirements' from suggested 'guidelines'.</p>
-<p>Shane's starting proposals:</p>
+<p>Shane's starting proposals:
-<p>Directory tree (preliminary)</p>
+<br>xml-commons is an unusual project in several ways.  
+First, it encompasses two kinds of code: external and apache.  
+<br>Secondly, 
+xml-commons mainly focuses on providing code and services to other 
+xml.apache.org projects instead of shipping it's own 'standalone' project.  
+<br>Third, it will also tend to be more focused on smaller, interoperable modules of 
+code and a very high degree of stability.</p>
+<p>In some ways, the forming of 
+xml-commons is the seed of a catalyst to improve cross-project coordination 
+throughout xml.apache.org.  One potential goal is to get all xml.apache.org 
+projects to take their xml standards oriented code - like DOM, SAX and JAXP - 
+from specific marked builds of xml-commons, instead of each project 
+using different versions of these files.</p>
+<p><b>External code:</b> xml-commons will serve as an Apache-controlled 
+copy of externally-defined standards-based files.  This way, we can try 
+to manage common versions of these important xml standards-based files
+and interfaces. Read more <a href="#external">here</a>.</p>
+<p><b>Apache code:</b> xml-commons will serve as a shared repository for 
+common xml-oriented utilities or building blocks that several other 
+xml.apache.org projects wish to use.  The first example is org.apache.env.Which, 
+and environment checking utility that scans your environment and reports common 
+versions of xml-related files.  The next likely submission is an entity resolver 
+that could be plugged into any xml parsing, transforming, or processing 
+project.  Read more <a href="#java">here</a>.</p>
+<p>Directory tree (proposed)</p>
 <pre>
 xml-commons/
     README.html - this file
@@ -194,8 +218,35 @@ xml-related items in your JVM's environment: see xml-commons/java/which.xml</li>
 
 
   <div class="category"><div class="label"><a name="releases">Where can I download releases?</a></div><div class="content">
-<p>Our first 'preview' release is planned for early January-2002. 
+<p>The xml-commons-1.0.b1 release 11-Jan-02 is available in our 
-We'll certainly announce our first releases over general@xml.apache.org as well as our <a href="#mailing">project mailing list</a>.</p>
+<a href="http://xml.apache.org/dist/commons/">distribution directory</a> and includes the following code:
+<ul>
+<li>java/build/which.jar containing:</li>
+<li>org.apache.env.Which - a simple environment check utility for 
+xml-related items in your JVM's environment: 1.0 funtionality working</li>
+<li>java/external/build/xml-apis.jar containing:</li>
+<li>DOM Level 2 including all base files and HTML and CSS DOMs; from <a href="http://www.w3.org/DOM/">w3c.org</a></li>
+<li>JAXP code roughly equivalent to JAXP 1.1.3; for reference releases 
+from Sun, see <a href="http://java.sun.com/xml/">java.sun.com/xml</a></li>
+<li>SAX 2.0-r2-prerelease and SAX2-ext-1.0; plus bugfixes to 
+org.xml.sax.helpers.ParserAdapter (make compile in JDK 1.1.x) and AttributesImpl (minor 
+removeAttribute bug); from megginson.com although SAX maintenance has 
+now moved to <a href="http://sax.sourceforge.net/">sax.sourceforge.net</a></li>
+</ul>
+</p>
+<p>Future 'b' or beta releases leading up to a gold 1.0 release will 
+be discussed on our <a href="#mailing">mailing list</a>.  Likely releases 
+might address points like:
+<ul>
+<li>Improvements or submissions to org.apache.env.Which</li>
+<li>A new submission of an entity resolver from Norman Walsh</li>
+<li>A specific version of backlevel JAXP 1.1 that will work with 
+Sun's J2EE CTS conformance tests, if enough people request it</li>
+<li>Specific versions of SAX, if the xml.apache.org community 
+requests it and wants to update to a newer shipped release of SAX, perhaps 
+SAX 2R2pre3 or later</li>
+</ul>
+</p>
   </div></div>
 
   <div class="category"><div class="label"><a name="mailing">How can I find out more?</a></div><div class="content">