forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stev...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs/xml-site ack.xml communication.xml contact.xml cvs.xml decisions.xml guidelines.xml index.xml legal.xml library.xml mail.xml management.xml mission.xml news.xml overview.xml roles.xml source.xml whoweare.xml
Date Thu, 06 Jun 2002 14:32:41 GMT
stevenn     2002/06/06 07:32:41

  Modified:    src/documentation/content/xdocs contrib.xml document-v11.xml
                        dreams.xml howto-v10.xml index.xml license.xml
                        mail-lists.xml primer.xml who.xml
               src/documentation/content/xdocs/community/howto index.xml
               src/documentation/content/xdocs/community/howto/bugzilla-patch
                        howto-bugzilla-patch.xml
               src/documentation/content/xdocs/community/howto/cvs-ssh
                        howto-cvs-ssh.xml
               src/documentation/content/xdocs/community/howto/v10
                        howto-v10.xml
               src/documentation/content/xdocs/community/howto/xmlform
                        revision-howto-xmlform-2002-05-20.xml
                        revision-step1-2002-05-20.xml step1.xml step2.xml
                        step3.xml step4.xml step5.xml
               src/documentation/content/xdocs/xml-site ack.xml
                        communication.xml contact.xml cvs.xml decisions.xml
                        guidelines.xml index.xml legal.xml library.xml
                        mail.xml management.xml mission.xml news.xml
                        overview.xml roles.xml source.xml whoweare.xml
  Log:
  patched the existing docs according backwards-incompatible changes in doc-v11
  
  Revision  Changes    Path
  1.6       +74 -69    xml-forrest/src/documentation/content/xdocs/contrib.xml
  
  Index: contrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/contrib.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- contrib.xml	21 May 2002 21:16:16 -0000	1.5
  +++ contrib.xml	6 Jun 2002 14:32:39 -0000	1.6
  @@ -1,149 +1,154 @@
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  -<document> 
  -  <header> 
  -    <title>Contribution to Forrest</title> 
  +<document>
  +  <header>
  +    <title>Contributing to Forrest</title>
       <authors> <person name="Stefano Mazzocchi" email="stefano@apache.org"/>
  -      <person name="Nicola Ken Barozzi" email="nicolaken@apache.org"/> 
  -    </authors> 
  -  </header> 
  -  <body> 
  -    <section title="Introduction"> 
  -      <p> The Forrest Project is an <link
  -      href="http://www.opensource.org/">Open Source</link> volunteer project released
  +      <person name="Nicola Ken Barozzi" email="nicolaken@apache.org"/>
  +    </authors>
  +  </header>
  +  <body>
  +    <section>
  +      <title>Introduction</title>
  +      <p> The Forrest Project is an <link href="http://www.opensource.org/">Open Source</link> volunteer project released
         under a very open license. This means there are many ways to contribute to the
         project - either with direct participation (coding, documenting, answering
         questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by
         resource donations (money, time, publicity, hardware, software, conference
  -      presentations, speeches, etc...). </p> 
  +      presentations, speeches, etc...). </p>
         <p> To begin with, we suggest you to subscribe to the
           <link href="mail-lists.html">Forrest mailing lists</link> (follow the link for
         information on how to subscribe and to access the mail list archives).
  -      Listen-in for a while, to hear how others make contributions. </p> 
  +      Listen-in for a while, to hear how others make contributions. </p>
         <p>You can get your local working copy of the
           <link href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/Forrest">latest and
         greatest code</link> (which you find in the Forrest module in the CVS code
         repository. Review the todo list, choose a task (or perhaps you have noticed
         something that needs patching). Make the changes, do the testing, generate a
         patch, and post to the dev mailing list. (Do not worry - the process is easy
  -      and explained below.) </p> 
  +      and explained below.) </p>
         <p> Document writers are usually the most wanted people so if you like to
           help but you're not familiar with the innermost technical details, don't worry:
  -        we have work for you! </p> 
  -    </section> 
  -    <section title="Help Wanted Here"> 
  +        we have work for you! </p>
  +    </section>
  +    <section>
  +     <title>Help Wanted Here</title>
         <p> The rest of this document is mainly about contributing new or
           improved code and/or documentation, but we would also be glad to have extra
  -        help in any of the following areas: </p> 
  -      <ul> 
  +        help in any of the following areas: </p>
  +      <ul>
           <li>Answering questions on the <code>users</code> mailing list - there
             is often a problem of having too many questioners and not enough experts to
  -          respond to all the questions.</li> 
  +          respond to all the questions.</li>
           <li>Testing Forrest (especially its less-frequently-used features) on
  -          various configurations and reporting back.</li> 
  +          various configurations and reporting back.</li>
           <li>Debugging - producing reproduceable test cases and/or finding
             causes of bugs. Some known bugs are informally listed on To Do, and some are
             recorded in Bugzilla (see <link href="#procedure">explanation
  -      below</link>).</li> 
  +      below</link>).</li>
         <li>Specifying/analysing/designing new features - and beyond. (If you
           wish to get involved with this, please join <code>general Forrest mailing
           list</code>, install and try out Forrest and read some of the
           <link href="mail-lists.html">mail archives</link>. You should have a strong
         "fluency" in XML technologies, Java and a basic understanding of the Forrest
         architecture - don't just say "it should have XYZ" without reading anything
  -      first - because chances are, somebodies already thought of that feature!)</li> 
  +      first - because chances are, somebodies already thought of that feature!)</li>
         <li>Packaging easy-to-install packages (such as RPMs) for the myriad of
           possible configurations out there. (The project does not maintain anything but
           the basic <code>.zip</code> and <code>.tar.gz</code> packages, but anyone is
           welcome to build their own specific packages and announce them on the
  -        <code>general Forrest list</code>)</li> 
  +        <code>general Forrest list</code>)</li>
         <li>... and there is just one other thing - don't forget to tell everyone
           who asks, how great Forrest is! ;-) The more people that know about and start
           to use Forrest, the larger the pool of potential contributors there will be.
  -        </li> 
  -      </ul> 
  -    </section> <anchor id="cvshowto"/> 
  -    <section title="CVS Usage Precis"> 
  +        </li>
  +      </ul>
  +    </section> <anchor id="cvshowto"/>
  +    <section>
  +    <title>CVS Usage Precis</title>
         <p>An overview of how to use CVS to participate in Forrest development.
           Do not be afraid - you cannot accidently destroy the actual code repository,
           because you are working with a local copy as an anonymous user. Therefore, you
           do not have the system permissions to change anything. You can only update your
  -        local repository and compare your revisions with the real repository. </p> 
  +        local repository and compare your revisions with the real repository. </p>
         <p> (Further general CVS usage information is at
           <link href="http://www.cvshome.org/">www.cvshome.org</link> and your local
         <code>info cvs</code> pages or <code>man cvs</code> pages or user
  -      documentation.) </p> 
  +      documentation.) </p>
         <p> Let us lead by example. We will show you how to establish your local
           repository, how to keep it up-to-date, and how to generate the differences to
  -        create a patch. (The commands are for Linux.) </p> 
  -    </section> <anchor id="ssh"/> 
  -    <section title="CVS Committer with Secure Shell access"> 
  +        create a patch. (The commands are for Linux.) </p>
  +    </section> <anchor id="ssh"/>
  +    <section>
  +    <title>CVS Committer with Secure Shell access</title>
         <p>After a developer has consistently provided contributions (code,
           documentation and discussion), then the rest of the dev community may vote to
  -        grant this developer commit access to CVS. </p> 
  +        grant this developer commit access to CVS. </p>
         <p>You will need secure access to the repository to be able to commit
           patches. Here are some resources that help to get your machine configured to
  -        use the repository over SSH. </p> 
  -      <ul> 
  -        <li><link href="http://cvsbook.red-bean.com/">The CVS Book</link></li> 
  -      <li><link href="http://www.cvshome.org/">www.cvshome.org</link></li> 
  +        use the repository over SSH. </p>
  +      <ul>
  +        <li><link href="http://cvsbook.red-bean.com/">The CVS Book</link></li>
  +      <li><link href="http://www.cvshome.org/">www.cvshome.org</link></li>
         <li><link href="https://sourceforge.net/cvs/?group_id=32701"></link> -
         See the bottom of the page for links to tips for UNIX and Windows. Even if you
  -      are on UNIX, the Windows page will also help.</li> 
  -      </ul> 
  -    </section> <anchor id="procedure"/> 
  -    <section title="Procedure for Raising Development Issues"> 
  +      are on UNIX, the Windows page will also help.</li>
  +      </ul>
  +    </section> <anchor id="procedure"/>
  +    <section>
  +    <title>Procedure for Raising Development Issues</title>
         <p> There are two methods for discussing development and submitting
           patches. So that everyone can be productive, it is important to know which
           method is appropriate for a certain situation and how to go about it without
           confusion. This section explains when to use the <code>developer</code>
  -        <link href="mail-lists.html">mailing list</link> the bug database. </p> 
  +        <link href="mail-lists.html">mailing list</link> the bug database. </p>
         <p> Research your topic thoroughly before beginning to discuss a new
           development issue. Search and browse through the email archives - your issue
  -        may have been discussed before. Prepare your post clearly and concisely. </p> 
  +        may have been discussed before. Prepare your post clearly and concisely. </p>
         <p> Most issues will be discovered, resolved, and then patched quickly
           via the <code>developer</code> mailing list. Larger issues, and ones that are
  -        not yet fully understood or are hard to solve, are destined for Bugzilla. </p> 
  +        not yet fully understood or are hard to solve, are destined for Bugzilla. </p>
         <p> Experienced developers use Bugzilla directly, as they are very sure
           when they have found a bug and when not. However, less experienced users should
           first discuss it on the user or developer mailing list (as appropriate).
           Impatient people always enter everything into Bugzilla without caring if it is
           a bug of Forrest or their own installation/configuration mistake - please do
  -        not do this. </p> 
  +        not do this. </p>
         <p> As a rule-of-thumb, discuss an issue on the <code>developers</code>
           mailing list first to work out any details. After it is confirmed to be
           worthwhile, and you are clear about it, then submit the bug description or
  -        patch via Bug Tracking. </p> 
  +        patch via Bug Tracking. </p>
         <p> Perhaps you do not get any answer on your first reply, so just post
           it again until you get one. (But please not every hour - allow a few days for
           the list to deal with it.) Do not be impatient - remember that the whole world
           is busy, not just you. Bear in mind that other countries will have holidays at
           different times to your country and that they are in different time zones. You
           might also consider rewriting your initial posting - perhaps it was not clear
  -        enough and the readers eyes glazed over. </p> 
  -    </section> <anchor id="tips"/> 
  -    <section title="Contribution Notes and Tips"> 
  +        enough and the readers eyes glazed over. </p>
  +    </section> <anchor id="tips"/>
  +    <section>
  +     <title>Contribution Notes and Tips</title>
         <p> This is a collection of tips for contributing to the project in a
  -        manner that is productive for all parties. </p> 
  -      <ul> 
  +        manner that is productive for all parties. </p>
  +      <ul>
           <li> Every contribution is worthwhile. Even if the ensuing discussion
  -          proves it to be off-beam, then it may jog ideas for other people. </li> 
  +          proves it to be off-beam, then it may jog ideas for other people. </li>
           <li> Use sensible and concise email subject headings. Search engines,
             and humans trying to browse a voluminous list, will respond favourably to a
  -          descriptive title. </li> 
  +          descriptive title. </li>
           <li>Start new threads with new Subject for new topics, rather than
  -          reusing the previous Subject line. </li> 
  +          reusing the previous Subject line. </li>
           <li>Keep each topic focused. If some new topic arises then start a new
  -          discussion. This leaves the original topic to continue uncluttered. </li> 
  +          discussion. This leaves the original topic to continue uncluttered. </li>
           <li>Whenever you decide to start a new topic, then start with a fresh
             new email message window. Do not use the &quot;Reply to&quot; button, because
             threaded mail-readers get confused (they utilise the <code>In-reply-to</code>
             header). If so, then your new topic will get lost in the previous thread and go
  -          unanswered. </li> 
  +          unanswered. </li>
           <li> Prepend your email subject line with a marker when that is
             appropriate, e.g. <code>[Patch]</code>, <code>[Proposal]</code>,
             <code>[RT]</code> (Random Thought which quickly blossom into research topics
  -          :-), <code>[STATUS]</code> (development status of a certain facility). </li> 
  +          :-), <code>[STATUS]</code> (development status of a certain facility). </li>
           <li> When making changes to XML documentation, or any XML document for
             that matter, use a <link href="http://www.oasis-open.org/cover/">validating
         parser</link> (one that is tried and true is
  @@ -152,34 +157,34 @@
         docs</code> process to find them. Do not expect Forrest or the build system to
         detect the validation errors for you - they can do it, but that is not their
         purpose. (Anyway, nsgmls validation error messages are more informative.) </li>
  -      
  +
         <li> Remember that most people are participating in development on a
           volunteer basis and in their "spare time". These enthusiasts will attempt to
  -        respond to issues. It may take a little while to get your answers. </li> 
  +        respond to issues. It may take a little while to get your answers. </li>
         <li> Research your topic thoroughly before beginning to discuss a new
           development issue. Search and browse through the email archives - your issue
           may have been discussed before. Do not just perceive a problem and then rush
  -        out with a question - instead, delve. </li> 
  +        out with a question - instead, delve. </li>
         <li> Try to at least offer a partial solution and not just a problem
  -        statement. </li> 
  +        statement. </li>
         <li> Take the time to clearly explain your issue and write a concise
  -        email message. Less confusion facilitates fast and complete resolution. </li> 
  +        email message. Less confusion facilitates fast and complete resolution. </li>
         <li> Do not bother to send an email reply that simply says "thanks". When
           the issue is resolved, that is the finish - end of thread. Reduce clutter.
  -        </li> 
  +        </li>
         <li> You would usually do any development work against the HEAD branch of
  -        CVS. </li> 
  +        CVS. </li>
         <li> When sending a patch, you usually do not need to worry about which
           CVS branch it should be applied to. The maintainers of the repository will
  -        decide. </li> 
  +        decide. </li>
         <li> If an issue starts to get bogged down in list discussion, then it
           may be appropriate to go into private off-list discussion with a few interested
           other people. Spare the list from the gory details. Report a summary back to
  -        the list to finalise the thread. </li> 
  +        the list to finalise the thread. </li>
         <li> Become familiar with the mailing lists. As you browse and search,
           you will see the way other people do things. Follow the leading examples. </li>
  -      
  -      </ul> 
  -    </section> 
  +
  +      </ul>
  +    </section>
     </body>
   </document>
  
  
  
  1.8       +19 -20    xml-forrest/src/documentation/content/xdocs/document-v11.xml
  
  Index: document-v11.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/document-v11.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- document-v11.xml	3 Jun 2002 03:28:42 -0000	1.7
  +++ document-v11.xml	6 Jun 2002 14:32:39 -0000	1.8
  @@ -33,33 +33,28 @@
           <dl> 
             <dt><code>&lt;link href="faq.html"&gt;</code></dt> 
             <dd>Use this to
  -            <link href="faq.html"
  -             title="Example of a document via link">link</link>
  +            <link href="faq.html" title="Example of a document via link">link</link>
              to another document. As per normal, this will open the new document
              in the same browser window.</dd> 
   
             <dt><code>&lt;link href="#section"&gt;</code></dt> 
             <dd>Use this to
  -            <link href="#section"
  -             title="Example of a document via local anchor">link</link>
  +            <link href="#section" title="Example of a document via local anchor">link</link>
              to the named anchor in the current document.
             </dd> 
   
             <dt><code>&lt;link href="contrib.html#cvshowto"&gt;</code></dt> 
             <dd>Use this to
  -            <link href="contrib.html#cvshowto"
  -             title="Example of a document via link and anchor">link</link>
  +            <link href="contrib.html#cvshowto" title="Example of a document via link and anchor">link</link>
              to another document and go to the named anchor. This will open
              the new document in the same browser window.
             </dd> 
   
             <dt><code>&lt;jump href="contrib.html"&gt;</code></dt> 
             <dd>Use this to
  -            <jump href="contrib.html"
  -            title="Example of a document via jump">jump</jump>
  +            <jump href="contrib.html" title="Example of a document via jump">jump</jump>
              to another document and optionally go to a named
  -            <jump href="contrib.html#cvshowto"
  -            title="Example of a document via jump to anchor">anchor</jump>
  +            <jump href="contrib.html#cvshowto" title="Example of a document via jump to anchor">anchor</jump>
              within that document. This will open the new document in the same
              browser window. So what is the difference between link and jump?
              The jump behaves differently, in that it will replace any frames
  @@ -70,8 +65,7 @@
   
             <dt><code>&lt;fork href="faq.html"&gt;</code></dt> 
             <dd>Use this to
  -            <fork href="faq.html"
  -            title="Example of a document via fork">fork</fork>
  +            <fork href="faq.html" title="Example of a document via fork">fork</fork>
              your webbrowser to another document. This will open the document
              in a new, unnamed browser window.
              This is the equivalent of
  @@ -103,20 +97,24 @@
     </ol> 
   
     <anchor id="section"/>
  -  <section title="Using sections"> 
  +  <section> 
  +    <title>Using sections</title>
       <p>You can use sections to put some structure in your document. For some
         strange historical reason, the section title is an attribute of the
         <code>&lt;section&gt;</code> element.</p> 
     </section> 
  -  <section title="Sections, the sequel"> 
  +  <section>
  +    <title>Sections, the sequel</title>
       <p>Just some second section.</p> 
  -    <section title="Section 2.1"> 
  +    <section>
  +	   <title>Section 2.1</title>
         <p>Which contains a subsection (2.1).</p> 
       </section> 
     </section> 
   
     <anchor id="source"/>
  -  <section title="Showing preformatted source code"> 
  +  <section>
  +  <title>Showing preformatted source code</title> 
     <p>Enough about these sections. Let's have a look at more interesting
       elements, <code>&lt;source&gt;</code> for instance:</p> 
     <source>// This example is from the book _Java in a Nutshell_ by David Flanagan.
  @@ -139,7 +137,8 @@
     </section>
   
     <anchor id="table"/>
  -  <section title="Using tables"> 
  +  <section>
  +  <title>Using tables</title>
     <p>And now for a table:</p>
     <table> 
       <caption>Table caption</caption> 
  @@ -156,11 +155,11 @@
     </section>
   
     <anchor id="figure"/>
  -  <section title="Using figures"> 
  +  <section> 
  +   <title>Using figures</title>
     
     <p>And a figure to end all of this.</p>
  -  <figure src="images/project-logo.png"
  -          alt="The fine Forrest logo" width="220" height="65"/>	
  +  <figure src="images/project-logo.png" alt="The fine Forrest logo" width="220" height="65"/>	
     </section>
     </body> 
     <footer> 
  
  
  
  1.5       +4 -2      xml-forrest/src/documentation/content/xdocs/dreams.xml
  
  Index: dreams.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/dreams.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- dreams.xml	27 May 2002 02:03:09 -0000	1.4
  +++ dreams.xml	6 Jun 2002 14:32:39 -0000	1.5
  @@ -13,7 +13,8 @@
    </header>
   
    <body>
  - <section title="Introduction">
  + <section>
  +  <title>Introduction</title>
   
     <p>This is the initial attempt to give focus to the Forrest project. 
      This summary is a loose collection of items from the forrest-dev
  @@ -70,7 +71,8 @@
     </ul>
    </section>
   
  - <section title="Draft dream list">
  + <section>
  + <title>Draft dream list</title>
   
    <ul>
     <li>
  
  
  
  1.4       +24 -12    xml-forrest/src/documentation/content/xdocs/howto-v10.xml
  
  Index: howto-v10.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/howto-v10.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- howto-v10.xml	21 May 2002 21:16:16 -0000	1.3
  +++ howto-v10.xml	6 Jun 2002 14:32:39 -0000	1.4
  @@ -43,69 +43,80 @@
   <p>
   Here's how to proceed.</p>
   
  -  <section title="Write the Overview">
  +  <section>
  +  <title>Write the Overview</title>
   <p>
   An overview helps potential readers to determine quickly if a particular How-To matches their interests or needs. In a few sentences, summarize the main points of your How-To. Make sure to include any critical definitions which will help readers evaluate the utility of your How-To. Consider writing the overview last, after you have completed all other sections.
   </p>
     </section>
   
  -  <section title="Describe your Intended Audience">
  +  <section>
  +  <title>Describe your Intended Audience</title>
   <p>
   If your How-To is targeted at a specific audience, describe it here. For example, potential readers will have different levels of skill using Cocoon. They will also bring different areas of expertise and backgrounds to their How-To learning experience. When you clarify your target audience up front, you will save all other readers time and confusion. 
   </p> 
     </section>
   
  -  <section title="State the Purpose">
  +  <section>
  +  <title>State the Purpose</title>
   <p>
   State the purpose of your How-To. Explain how the reader will benefit by reading it. Give your reader an incentive or two to continue. 
   </p>
     </section>
   
  -  <section title="List any Prerequisites">
  +  <section>
  +  <title>List any Prerequisites</title>  
   <p>
   Inform your reader about any required knowledge, configuration, or resources they may need before stepping through your How-To. Assist them in this preparation by linking to other useful resources on the Cocoon site or the web. Helping your readers to prepare increases the likelihood that they will continue reading your How-To.
   </p>
     </section>
   
  -  <section title="Describe the Steps of your How-To">
  +  <section>
  +  <title>Describe the Steps of your How-To</title>  
   <p>
   In a precise, step-by-step approach, walk your reader through the process. Make sure your reader can reproduce your intended result by following your exact steps. Make the learning process efficient by supplying sample code snippets or configuration details as necessary.
   </p>
     </section>
   
  -  <section title="Extend the Learning">
  +  <section>
  +  <title>Extend the Learning</title>  
   <p>
   Provide your reader with a few real-world examples of how the techniques or capabilities gained from your How-To could be applied. Reward the reader for successfully completing the How-To with a few ideas about how it will pay off.
   </p>
     </section>
   
   
  -  <section title="Summarize the Entire Process">
  +  <section>
  +  <title>Summarize the Entire Process</title>
   <p>
   In a few sentences, remind the reader what they have just learned. This helps to reinforce the main points of your How-To.  
   </p>
     </section>
   
   
  -  <section title="Additional Tips or FAQs">
  +  <section>
  +  <title>Additional Tips or FAQs</title>
   <p>
   In some cases, step-by-step instructions simply aren't enough. Use this section to pass on any other tips or frequently asked questions. Anticipating the needs of your readers will increase the overall success of your writing effort.
   </p>
     </section>
   
  -  <section title="References">
  +  <section>
  +  <title>References</title>
   <p>
   Remember to acknowledge any third-party resources or individuals who contributed to the development of your How-To. Consider providing links for those motivated readers who want to learn more.
   </p>
     </section>
     
  -  <section title="Get some feedback">
  +  <section>
  +  <title>Get some feedback</title>
   <p>
   Ask a few other Cocoon users to proofread your How-To. Or, post a text version of it to the cocoon-user list, and ask for comments.
   </p> 
     </section>
     
  -  <section title="Submit via Bugzilla">
  +  <section>
  +  <title>Submit via Bugzilla</title>
   <p>
   Create an attachment for your How-To document, and submit it via Bugzilla. 
   <!-- link to How-To Bugzilla here -->
  @@ -148,7 +159,8 @@
     
     <tips title="Tips">
     
  -  <section title="How-To dtd">
  +  <section>
  +  <title>How-To dtd</title>
   <p>
   The document structure of Cocoons' How-To page is likely to change soon. Please note that this HOWTO page is likely to change as well.
   </p>
  
  
  
  1.7       +4 -2      xml-forrest/src/documentation/content/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/index.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- index.xml	22 May 2002 12:08:02 -0000	1.6
  +++ index.xml	6 Jun 2002 14:32:39 -0000	1.7
  @@ -7,7 +7,8 @@
       </authors> 
     </header> 
     <body> 
  -    <section title="Introduction"> 
  +    <section>
  +      <title>Introduction</title>
         <p>Forrest provides a sound technological infrastructure for open
           software development for the Apache Software Foundation based on ASF software,
           ASF practices and experience, and modern software design principles.</p> 
  @@ -24,7 +25,8 @@
           <link
          href="mailto:forrest-dev@xml.apache.org">forrest-dev@xml.apache.org</link></p> 
       </section> 
  -    <section title="Project Status"> 
  +    <section>
  +      <title>Project Status</title>
         <p>The Forrest project is new and needs your help to get started.</p>
         <ul>
           <li>Read our <link href="primer.html">Forrest Primer</link> to
  
  
  
  1.3       +1 -3      xml-forrest/src/documentation/content/xdocs/license.xml
  
  Index: license.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/license.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- license.xml	20 May 2002 18:23:27 -0000	1.2
  +++ license.xml	6 Jun 2002 14:32:39 -0000	1.3
  @@ -4,9 +4,7 @@
   <document>
    <header>
     <title>The Apache Software License, Version 1.1</title>
  -  <authors>
  -   <person name="Steven Noels" email="stevenn@apache.org"/>   
  -  </authors>
  +  
    </header>
   
   <body>
  
  
  
  1.4       +6 -3      xml-forrest/src/documentation/content/xdocs/mail-lists.xml
  
  Index: mail-lists.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/mail-lists.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mail-lists.xml	20 May 2002 18:23:27 -0000	1.3
  +++ mail-lists.xml	6 Jun 2002 14:32:39 -0000	1.4
  @@ -8,7 +8,8 @@
       </authors> 
     </header> 
     <body>
  -    <section title="Important Notice"> 
  +    <section>
  +      <title>Important Notice</title>
         <p><strong>IMPORTANT: Before posting a question or problem to any mailing
           list, </strong>please first look at the following resources in this order:</p> 
         <ol> 
  @@ -24,7 +25,8 @@
           high-volume lists, so we all needs ways to help us all work smarter. See tips
           for <link href="contrib.html#tips">Contributing</link> </p> 
       </section> 
  -    <section title="Forrest Dev"> 
  +    <section>
  +      <title>Forrest Dev</title>
         <p><link
         href="mailto:forrest-dev-subscribe@xml.apache.org">Subscribe</link>
         <link href="mailto:forrest-dev-unsubscribe@xml.apache.org">Unsubscribe</link>
  @@ -55,7 +57,8 @@
           engine), and full details of any errors encountered (including full error
           messages and stack traces).</p> 
       </section> 
  -    <section title="Related Mailing Lists"> 
  +    <section>
  +      <title>Related Mailing Lists</title>
         <p>(See also
           <link href="http://dmoz.org/Computers/Data_Formats/Markup_Languages/XML/"> ODP
         XML links</link> for related websites.)</p> 
  
  
  
  1.10      +26 -13    xml-forrest/src/documentation/content/xdocs/primer.xml
  
  Index: primer.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/primer.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- primer.xml	3 Jun 2002 03:31:56 -0000	1.9
  +++ primer.xml	6 Jun 2002 14:32:39 -0000	1.10
  @@ -21,7 +21,8 @@
         Forresteers. Please send all comments, patches and suggestions to
         <link href="mailto:forrest-dev@xml.apache.org">the Forrest
         developers</link>.</note> 
  -    <section title="History"> 
  +    <section>
  +      <title>History</title> 
         <p>Forrest has come into existence because of the abysmal state of the
           <link href="http://xml.apache.org/">xml.apache.org</link> website in comparison
         with other open source community sites such as Sourceforge. The old site had no
  @@ -45,7 +46,8 @@
         will become a true community website infrastructure for Apache open source
         development.</p> 
       </section> 
  -    <section title="What is Forrest"> 
  +    <section>
  +      <title>What is Forrest</title>
         <p>Forrest is a framework that supports the cross-project generation and
           management of development project websites using Cocoon as its XML publishing
           framework. It not only provides access to project documentation, but also to
  @@ -99,7 +101,8 @@
         <p>The Forrest website and the overall xml.apache.org website are
           maintained and published using the same mechanism.</p> 
       </section> 
  -    <section title="Forrest roles"> 
  +    <section>
  +      <title>Forrest roles</title>
         <p>Depending on your interests, your involvement with Forrest may vary,
           hence your <em>role</em>. We currently envision three different roles:</p> 
         <ul> 
  @@ -138,8 +141,10 @@
           </tr> 
         </table> 
       </section> 
  -    <section title="Getting your local copy of Forrest through CVS" id="cvs"> 
  -      <section title="System requirements"> 
  +    <section id="cvs">
  +      <title>Getting your local copy of Forrest through CVS</title> 
  +      <section>
  +        <title>System requirements</title>
           <p>Forrest requires the following systems to be already installed on
             your system:</p> 
           <ul> 
  @@ -147,12 +152,14 @@
               present. Forrest has been tested against the latest Sun 1.3 JDK.</li> 
           </ul> 
         </section> 
  -      <section title="Getting Forrest"> 
  +      <section>
  +        <title>Getting Forrest</title>
           <p>You need to retrieve Forrest from its CVS repository - there are no
             binary, nor source, nor snapshot distributions yet. Some help with CVS follows
             (courtesy of our friends of the Cocoon project).</p> 
         </section> 
  -      <section title="Step-by-step cvs instructions for Windows"> 
  +      <section>
  +        <title>Step-by-step cvs instructions for Windows</title>
           <ol> 
             <li>Download a recent release of WinCVS (homepage is
               <link href="http://www.wincvs.org/">http://www.wincvs.org/</link>); </li> 
  @@ -179,7 +186,8 @@
           <li>The Forrest source is now on your harddrive.</li> 
           </ol> 
         </section> 
  -      <section title="Step-by-step cvs instructions for Unix"> 
  +      <section>
  +        <title>Step-by-step cvs instructions for Unix</title>
           <ol> 
             <li>Make sure you have a CVS client package installed on your Unix
               system.</li> 
  @@ -199,7 +207,8 @@
             "<code>cvs -z3 update -d -P</code>".</p> 
         </section> 
       </section> 
  -    <section title="Forrest distribution"> 
  +    <section>
  +      <title>Forrest distribution</title>
         <p>Once you retrieved Forrest from its CVS repository, you will end up
           with a filesystem hierarchy similar to this inside the <code>xml-forrest</code>
           home directory:</p> 
  @@ -266,7 +275,8 @@
           directory. Forrest also creates a <code>tools/tmp/anttasks/</code> upon its
           first invocation. These are Centipede-specific compiled Ant tasks.</p> 
       </section> 
  -    <section title="The Forrest DTDs"> 
  +    <section>
  +      <title>The Forrest DTDs</title>
         <p>Forrest is the reference repository for the XML Apache documentation
           DTDs. Special care is taken to provide a set of modular, extensible and
           well-maintained DTDs for project documentation purposes. This modularity is
  @@ -307,7 +317,8 @@
           your document instances apart from your DTD files. Later on, the DTDs will be
           web-accessible from the Forrest website for your perusal.</p> 
       </section> 
  -    <section title="Forrest site generation using Cocoon"> 
  +    <section>
  +      <title>Forrest site generation using Cocoon</title>
         <p>The <code>docs</code> target of the Forrest build environment invokes
           Cocoon as a command-line application to generate an HTML rendition of the
           project's documentation. It is not within the scope of this document to explain
  @@ -399,7 +410,8 @@
           <code>book2menu</code>, <code>document2html</code> and
           <code>site2xhtml</code>.</p> 
       </section> 
  -    <section title="Where we are heading to"> 
  +    <section>
  +      <title>Where we are heading to</title>
         <p>We have been explaining so far where we are now and what already
           works. The purpose of this document however is to attract newcomers and entice
           them to start contributing to Forrest. We have a decent generation system for
  @@ -485,7 +497,8 @@
         </tr> 
         </table> 
       </section> 
  -    <section title="Where you can help"> 
  +    <section>
  +      <title>Where you can help</title> 
         <p>By now, you should have a better understanding of Forrest (if that is
           not the case, consider contributing clarifications to this document).
           We need more people to get the job done.
  
  
  
  1.7       +4 -2      xml-forrest/src/documentation/content/xdocs/who.xml
  
  Index: who.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/who.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- who.xml	25 May 2002 22:37:28 -0000	1.6
  +++ who.xml	6 Jun 2002 14:32:39 -0000	1.7
  @@ -8,7 +8,8 @@
       </authors>
     </header>
     <body>
  -    <section title="The Forrest Community">
  +    <section>
  +      <title>The Forrest Community</title>
         <p> The Forrest Project operates on a meritocracy: the more you do, the
           more responsibility you will obtain. This page lists all of the people who have
           gone the extra mile and are Committers. If you would like to get involved, the
  @@ -22,7 +23,8 @@
           where others can also learn from common mistakes and as a community we all grow
           together.</p>
       </section>
  -    <section title="Committers">
  +    <section>
  +      <title>Committers</title>
         <ul>
           <li>[NKB] - Nicola Ken Barozzi (nicolaken@apache.org)</li>
           <li>[DC] - David Crossley (crossley@apache.org)</li>
  
  
  
  1.4       +11 -8     xml-forrest/src/documentation/content/xdocs/community/howto/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/index.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- index.xml	27 May 2002 11:53:11 -0000	1.3
  +++ index.xml	6 Jun 2002 14:32:40 -0000	1.4
  @@ -11,7 +11,8 @@
     </header>
   
     <body>
  -    <section title="Status of DTD and stylesheet development"> 
  +    <section>
  +      <title>Status of DTD and stylesheet development</title>
         <p>
          The structure and presentation of the How-To documents are under
          development. The following documents and the associated DTDs,
  @@ -29,9 +30,10 @@
          <code>revision-howto-xmlform-YYYY-MM-DD.xml</code> is appended to the
          main page.
         </p>
  -	</section>
  +  </section>
   
  -    <section title="Sample How-Tos"> 
  +    <section>
  +    <title>Sample How-Tos</title>
   <p>
   These are demonstration documents to help with the current development work
   on the howto-v10 DTD and stylesheets. Please help to correct any deficiency.
  @@ -40,10 +42,11 @@
   <li><link href="v10/howto-v10.html">Single Page How-To</link></li>
   <li><link href="xmlform/howto-xmlform.html">Multi-Page How-To with Revisions</link></li>
   <li><link href="bugzilla-patch/howto-bugzilla-patch.html">How-To with Images</link></li>
  -	</ul>
  -	</section>
  +  </ul>
  +  </section>
   
  -    <section title="Real How-Tos"> 
  +    <section>
  +      <title>Real How-Tos</title> 
   <p>
   Even though the howto-v10 DTD is not yet stable, some important How-To
   documents are being developed now. Over time this community/howto/ area will
  @@ -51,9 +54,9 @@
   </p>
           <ul>
   <li><link href="cvs-ssh/howto-cvs-ssh.html">CVS through SSH</link></li>
  -	</ul>
  +  </ul>
   
  -	</section>
  +  </section>
     </body>
   
   </document>
  
  
  
  1.4       +84 -60    xml-forrest/src/documentation/content/xdocs/community/howto/bugzilla-patch/howto-bugzilla-patch.xml
  
  Index: howto-bugzilla-patch.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/bugzilla-patch/howto-bugzilla-patch.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- howto-bugzilla-patch.xml	27 May 2002 02:04:47 -0000	1.3
  +++ howto-bugzilla-patch.xml	6 Jun 2002 14:32:40 -0000	1.4
  @@ -53,14 +53,15 @@
   
   </prerequisites>
   
  -	<steps title="Steps">
  +  <steps title="Steps">
   <p>
   Here is how to proceed. Go to
   <fork href="http://nagoya.apache.org/bugzilla/">Bugzilla</fork>
   in another browser window.
   </p>
   
  -	<section title="1. Create your Bugzilla Account">
  +  <section>
  +  <title>1. Create your Bugzilla Account</title>
   <p>
   Follow the link the home page to &quot;Open a new Bugzilla account&quot;.
   Do not worry, you will not be sent spam email nor bombarded with advertisements
  @@ -73,10 +74,11 @@
   This ensures legitimacy. It also enables the system to send you
   email automatically when your patch is applied by a Cocoon committer.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="2. Enter a new bug report">
  -	
  +  <section>
  +  <title>2. Enter a new bug report</title>
  +  
   <p>
   Follow the "Enter a new bug report" link from the Bugzilla home page. First,
   you will be asked to select the relevant project ... choose Cocoon 2 of course.
  @@ -86,7 +88,8 @@
   
   <p><img src="my-images/bugzilla-screen.gif" alt="Bugzilla Screen" height="342" width="479" /></p>
   
  -	<section title="Specify Version">
  +  <section>
  +   <title>Specify Version</title>
   <p>
   This is the version of Cocoon that you prepared your patch against. Choose
   <code>Current CVS</code> if you have an up-to-date local working copy
  @@ -95,31 +98,35 @@
   committer if your changes do not match the repository. If you are unsure, then
   please say so in the description at step 12.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify Component">
  +  <section>
  +    <title>Specify Component</title>
   <p>
   Follow the &quot;Component&quot; link for description of the available
   components. If you do not know which component is relevant, then just use
   <code>core</code>.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify Platform">
  +  <section>
  +    <title>Specify Platform</title>
   <p>
   This is really meant for bug reporting. Perhaps it could be relevant for a
   patch. You would usually specify the <code>All</code> option.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify Operating System (OS)">
  +  <section>
  +    <title>Specify Operating System (OS)</title>
   <p>
   Really meant for bug reporting. Perhaps it could be relevant for a patch.
   You would usually specify the <code>All</code> option.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify Severity">
  +  <section>
  +    <title>Specify Severity</title>
   <p>
   The impact that would arise if your patch is not applied. For a documentation
   patch, the severity would usually be the default <code>Normal</code>.
  @@ -134,15 +141,17 @@
   intended for suggesting something that should be done. Use this option wisely.
   It would be better to discuss it on the mailing list first.)
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify Initial State">
  +  <section>
  +    <title>Specify Initial State</title>
   <p>
   Use the <code>New</code> option.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify Assigned To">
  +  <section>
  +    <title>Specify Assigned To</title>
   <p>
   Leave it blank. Your patch will be automatically assigned to the
   <code>cocoon-dev</code> mailing list. When a committer takes on your patch,
  @@ -155,17 +164,19 @@
   automatically to the <code>cocoon-dev</code> mailing list, so you do not need
   to Cc anyone there.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify URL">
  +  <section>
  +    <title>Specify URL</title>
   <p>
   If the patch refers to a particular document, then provide the website URL.
   If it refers to an issue with one of the local Cocoon Samples, then provide
   the localhost URL.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Carefully choose the Summary">
  +  <section>
  +    <title>Carefully choose the Summary</title>
   <p>
   The summary will become the all-important title of the bug. Use it wisely. You want
   to draw attention to your patch. Just as with posting email to the listervers,
  @@ -178,9 +189,10 @@
   lists. The patch queue summary reminds people what patches are pending. If you
   omit this tag, then your patch may easily be overlooked.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Description">
  +  <section>
  +   <title>Description</title>
   <p>
   Provide a brief explanation of what your patch does. Supply any instructions
   to help the committer apply your patch efficiently. Note any issues that may
  @@ -197,12 +209,13 @@
   <!--FIXME (DS): Do we need this? It's a patch, not a bug. It may be confusing. -->
   If this were a bug report, then it would need extensive description.
   </p>
  -	</section>
  -	
  -	</section>
  -	
  +  </section>
  +  
  +  </section>
  +  
   
  -	<section title="3. Send the patch report">
  +  <section>
  +    <title>3. Send the patch report</title>
   <p>
   Review your options, then press the <strong>Commit</strong> button. This will
   add an entry to the bug database and email a report to the 
  @@ -213,9 +226,10 @@
   The next steps will show you how to attach your patch to the report that you
   have just created ...
   </p>
  -	</section>
  +  </section>
   
  -	<section title="4. Create an attachment of the actual patch">
  +  <section>
  +    <title>4. Create an attachment of the actual patch</title>
   <p>
   You will be presented with a status screen saying that your bug report
   was accepted and that email was sent to <code>cocoon-dev</code> mailing list.
  @@ -230,21 +244,24 @@
   this bug&quot;.
   </p>
   
  -	<section title="Specify the file to be uploaded">
  +  <section>
  +    <title>Specify the file to be uploaded</title>
   <p>
   Provide the local pathname to your patchfile, e.g.
   <code>/home/me/work/cocoon/patch/howto-bugzilla.tar.gz</code>
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Describe the attachment">
  +  <section>
  +    <title>Describe the attachment</title>
   <p>
   Provide a concise one line description, e.g.
   <code>Gzipped TAR archive with new docs and diffs</code>
   </p>
  -	</section>
  +  </section>
   
  -	<section title="Specify the contentType of the attachment">
  +  <section>
  +    <title>Specify the contentType of the attachment</title>
   <p>
   If it is a Gzipped TAR archive (*.tar.gz) or a .zip archive, then select
   &quot;<code>Binary file (application/octet-stream)</code>&quot;.
  @@ -253,28 +270,31 @@
   If the patch is just a single diff file, then select
   &quot;<code>Patch file (text/plain, diffs)</code>&quot;.
   </p>
  -	</section>
  -	
  -	</section>
  +  </section>
  +  
  +  </section>
   
  -	<section title="5. Submit the attachment">
  +  <section>
  +    <title>5. Submit the attachment</title>
   <p>
   When you are ready, press the <strong>Submit</strong> button. As for Step 3,
   you will be presented with a status screen saying that your attachment
   was accepted and that email was sent to <code>cocoon-dev</code> mailing list.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="6. Be patient">
  +  <section>
  +    <title>6. Be patient</title>
   <p>
   Now your patch will wait inside Bugzilla until one of the Cocoon committers
   assigns the patch to their own email address and starts to process it to apply
   it to the master CVS repository. As the registered owner of the Bug, you will
   be sent an automatic email at each of these stages.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="7. Add more description or attachments if necessary">
  +  <section>
  +    <title>7. Add more description or attachments if necessary</title>
   <p>
   Until the patch is applied by the committer and the Bug report is closed, you
   can still add more to your bug report. However, only do this when
  @@ -285,52 +305,56 @@
   veto and may decide to make some slight modifications to your patch. So it
   is far better to wait.
   </p>
  -	</section>
  +  </section>
   
  -	<section title="8. Adding subsequent patches to the same document or program">
  +  <section>
  +    <title>8. Adding subsequent patches to the same document or program</title>
   <p>
   If you want to make more patches to the same file, then please open a new Bug
   rather than re-open the old one. After all, once the original patch is
   applied by the committer, its corresponding Bug report is closed.
   </p>
  -	</section>
  +  </section>
   
  -	</steps>
  +  </steps>
   
     <extension title="Real World Extension">
     <!--FIXME: (DS) The purpose of this is to provide examples of how they can use
                     the knowledge gained in this how-to -->
   <p>Contributing patches, in the form of documentation or code, is a vital way to give back to the Cocoon community. For example, you might consider contributing a timely patch in the form of a new FAQ, how-to, or tutorial. Or, you may also consider submitting a patch which updates Cocoon's existing user and developer guides. </p>
  -	</extension>
  +  </extension>
   
     <tips title="Tips">
   
  -  <section title="Setting user preferences">
  +  <section>
  +    <title>Setting user preferences</title>
   <p>
   You can configure certain preferences, though the Bugzilla defaults work just
   fine.
   </p>
  -	</section>
  +  </section>
   
  -  <section title="Review the bugzilla documentation">
  +  <section>
  +    <title>Review the bugzilla documentation</title>
   <p>
   There are various explanations of terminology and procedures ... follow the
   links should you need to know more.
   </p>
  -	</section>
  +  </section>
   
  -  <section title="Search Bugzilla">
  +  <section>
  +    <title>Search Bugzilla</title>
   <p>
   Bugzilla has a very powerful search interface. Now that you have a login
   account, Bugzilla can remember customized queries which you can run with a
   single click.
   </p>
  -	</section>
  +  </section>
   
  -	</tips>
  +  </tips>
   
     <references title="References">
  -	<ul>
  +  <ul>
   <li>
   Bugzilla is at 
   <link href="http://nagoya.apache.org/bugzilla/">http://nagoya.apache.org/bugzilla/</link>
  @@ -339,8 +363,8 @@
   Helpful Bug Writing Guidelines are available directly from the
   Bug entry interface.
   </li>
  -	</ul>
  -	
  -	</references>
  +  </ul>
  +  
  +  </references>
   
   </howto>
  
  
  
  1.5       +43 -36    xml-forrest/src/documentation/content/xdocs/community/howto/cvs-ssh/howto-cvs-ssh.xml
  
  Index: howto-cvs-ssh.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/cvs-ssh/howto-cvs-ssh.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- howto-cvs-ssh.xml	27 May 2002 13:35:50 -0000	1.4
  +++ howto-cvs-ssh.xml	6 Jun 2002 14:32:40 -0000	1.5
  @@ -30,21 +30,23 @@
       </prerequisites>
       <steps title="Steps">
           <p>How to proceed.</p>
  -        <section title="Terms">
  +        <section>
  +            <title>Terms</title>
               <dl>
  -		    <dt>SSH</dt>
  -		    <dd>Secure Shell. See <link href="http://www.openssh.org">OpenSSH</link></dd>
  -		    <dt>CVS</dt>
  -		    <dd>Concurrent Version System See <link href="http://www.cvshome.org" >CVS Home Page</link></dd>
  -	       </dl>		       					
  +        <dt>SSH</dt>
  +        <dd>Secure Shell. See <link href="http://www.openssh.org">OpenSSH</link></dd>
  +        <dt>CVS</dt>
  +        <dd>Concurrent Version System See <link href="http://www.cvshome.org" >CVS Home Page</link></dd>
  +         </dl>                    
           </section>
           <note><strong>$</strong> represents local, <strong>%</strong> remote machine.</note>                
  -        <section title="Setting up domain users">
  +        <section>
  +            <title>Setting up domain users</title>
               <note>This step is necessary only for Windows users. Linux users can happily skip this section and pass to <link href="#ssh_access">Setting up SSH access</link> section</note>
               <p>If you are a domain user then you should be added to Cygwin users list (See <code>[cygwin-dir]/etc/passwd</code>). 
               </p>
               <ul>
  -            	<li>Start Cygwin, then enter following commands:</li>
  +              <li>Start Cygwin, then enter following commands:</li>
               </ul>
               <source>
   $ whoami
  @@ -52,37 +54,39 @@
   $ mkgroup -d > /etc/group
   $ mkpasswd -d | grep 'userxxx' >> /etc/passwd
   $ exit
  -		</source>
  - 	     <note>Replace 'userxxx' by your account name</note>		
  -		<ul>
  -			<li>Start Cygwin/shell again and check that everything's Ok:</li>
  -		</ul>
  -		<source>
  +    </source>
  +       <note>Replace 'userxxx' by your account name</note>    
  +    <ul>
  +      <li>Start Cygwin/shell again and check that everything's Ok:</li>
  +    </ul>
  +    <source>
   $ whoami
   userxxx
               </source>
           </section>
  -        <section title="Setting up SSH access" id="ssh_access">
  +        <section id="ssh_access">
  +            <title>Setting up SSH access</title>
               <p>Start Cygwin/shell, then enter:</p>
               <source>
   $ ssh-user-config
  -	Shall I create an SSH1 RSA identity file for you? (yes/no) no
  -	Shall I create an SSH2 RSA identity file for you? (yes/no)  (yes/no) no
  -	Shall I create an SSH2 DSA identity file for you? (yes/no)  (yes/no) yes
  -	Generating /home/userxxx/.ssh/id_dsa
  -	Enter passphrase (empty for no passphrase):
  -	Enter same passphrase again:
  -	Do you want to use this identity to login to this machine? (yes/no) yes
  -	Adding to /home/userxxx/.ssh/authorized_keys2
  -	
  -	Configuration finished. Have fun!
  -		</source>
  -		<p>
  -			Now you have configured SSH on your machine. Next you have to setup access to the CVS machine.
  -		</p>
  -		<warning>Having an empty passphrase isn't recommended for security reasons. See <code>ssh-agent</code> documentation on how to configure automatic passphrase retaining.</warning>
  +  Shall I create an SSH1 RSA identity file for you? (yes/no) no
  +  Shall I create an SSH2 RSA identity file for you? (yes/no)  (yes/no) no
  +  Shall I create an SSH2 DSA identity file for you? (yes/no)  (yes/no) yes
  +  Generating /home/userxxx/.ssh/id_dsa
  +  Enter passphrase (empty for no passphrase):
  +  Enter same passphrase again:
  +  Do you want to use this identity to login to this machine? (yes/no) yes
  +  Adding to /home/userxxx/.ssh/authorized_keys2
  +  
  +  Configuration finished. Have fun!
  +    </source>
  +    <p>
  +      Now you have configured SSH on your machine. Next you have to setup access to the CVS machine.
  +    </p>
  +    <warning>Having an empty passphrase isn't recommended for security reasons. See <code>ssh-agent</code> documentation on how to configure automatic passphrase retaining.</warning>
           </section>
  -        <section title="Setting up passphrase access">
  +        <section>
  +            <title>Setting up passphrase access</title>
               <p>Perform the following:</p>
               <source>
   $ scp ~/.ssh/id_dsa.pub userxxx@cvs.apache.org:.
  @@ -105,15 +109,17 @@
               If now you are logged in to the to the CVS machine without entering the password then everything's Ok.
               </p>           
           </section>
  -        <section title="Getting the project from CVS">
  -        	  <p>Now you are ready to get a project from CVS using SSH connection.</p>
  -        	  <p>E.g. how it is done using Cygwin/shell</p>
  +        <section>
  +            <title>Getting the project from CVS</title>
  +            <p>Now you are ready to get a project from CVS using SSH connection.</p>
  +            <p>E.g. how it is done using Cygwin/shell</p>
               <source>
   $ export CVS_RSH=/bin/ssh
   $ cvs -d :ext:userxxx@cvs.apache.org:/home/cvs co xml-cocoon2            
               </source>
           </section>
  -        <section title="How to setup WinCVS">
  +        <section>
  +            <title>How to setup WinCVS</title>
               <ul>
                   <li>Add ssh.exe directory to your system PATH environment variable. Say: <br/>
                   <code>C:\>set PATH=%PATH%;C:\cygwin\bin</code></li>
  @@ -131,7 +137,8 @@
                   <li>Click Ok</li>
               </ul>
           </section>
  -        <section title="References">
  +        <section>
  +            <title>References</title>
               <p>
                   You can find more on CVS, SSH and WinCVS here:
               </p>
  
  
  
  1.2       +24 -12    xml-forrest/src/documentation/content/xdocs/community/howto/v10/howto-v10.xml
  
  Index: howto-v10.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/v10/howto-v10.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- howto-v10.xml	25 May 2002 07:29:52 -0000	1.1
  +++ howto-v10.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -43,69 +43,80 @@
   <p>
   Here's how to proceed.</p>
   
  -  <section title="Write the Overview">
  +  <section>
  +    <title>Write the Overview</title>
   <p>
   An overview helps potential readers to determine quickly if a particular How-To matches their interests or needs. In a few sentences, summarize the main points of your How-To. Make sure to include any critical definitions which will help readers evaluate the utility of your How-To. Consider writing the overview last, after you have completed all other sections.
   </p>
     </section>
   
  -  <section title="Describe your Intended Audience">
  +  <section>
  +    <title>Describe your Intended Audience</title>
   <p>
   If your How-To is targetted at a specific audience, describe it here. For example, potential readers will have different levels of skill using Cocoon. They will also bring different areas of expertise and backgrounds to their How-To learning experience. When you clarify your target audience up front, you will save all other readers time and confusion. 
   </p> 
     </section>
   
  -  <section title="State the Purpose">
  +  <section>
  +    <title>State the Purpose</title>
   <p>
   State the purpose of your How-To. Explain how the reader will benefit by reading it. Give your reader an incentive or two to continue. 
   </p>
     </section>
   
  -  <section title="List any Prerequsites">
  +  <section>
  +    <title>List any Prerequsites</title>
   <p>
   Inform your reader about any required knowledge, configuration, or resources they may need before stepping through your How-To. Assist them in this preparation by linking to other useful resources on the Cocoon site or the web. Helping your readers to prepare increases the likelihood that they will continue reading your How-To.
   </p>
     </section>
   
  -  <section title="Describe the Steps of your How-To">
  +  <section>
  +    <title>Describe the Steps of your How-To</title>
   <p>
   In a precise, step-by-step approach, walk your reader through the process. Make sure your reader can reproduce your intended result by following your exact steps. Make the learning process efficient by supplying sample code snippets or configuration details as necessary.
   </p>
     </section>
   
  -  <section title="Extend the Learning">
  +  <section>
  +    <title>Extend the Learning</title>
   <p>
   Provide your reader with a few real-world examples of how the techniques or capabilities gained from your How-To could be applied. Reward the reader for successfully completing the How-To with a few ideas about how it will pay off.
   </p>
     </section>
   
   
  -  <section title="Summarize the Entire Process">
  +  <section>
  +    <title>Summarize the Entire Process</title>
   <p>
   In a few sentences, remind the reader what they have just learned. This helps to reinforce the main points of your How-To.  
   </p>
     </section>
   
   
  -  <section title="Additional Tips or FAQs">
  +  <section>
  +    <title>Additional Tips or FAQs</title>
   <p>
   In some cases, step-by-step instructions simply aren't enough. Use this section to pass on any other tips or frequently asked questions. Anticipating the needs of your readers will increase the overall success of your writing effort.
   </p>
     </section>
   
  -  <section title="References">
  +  <section>
  +    <title>References</title>
   <p>
   Remember to acknowledge any third-party resources or individuals who contributed to the development of your How-To. Consider providing links for those motivated readers who want to learn more.
   </p>
     </section>
     
  -  <section title="Get some feedback">
  +  <section>
  +    <title>Get some feedback</title>
   <p>
   Ask a few other Cocoon users to proofread your How-To. Or, post a text version of it to the cocoon-user list, and ask for comments.
   </p> 
     </section>
     
  -  <section title="Submit via Bugzilla">
  +  <section>
  +    <title>Submit via Bugzilla</title>
   <p>
   Create an attachment for your How-To document, and submit it via Bugzilla. 
   <!-- link to How-To Bugzilla here -->
  @@ -148,7 +159,8 @@
     
     <tips title="Tips">
     
  -  <section title="How-To dtd">
  +  <section>
  +    <title>How-To dtd</title>
   <p>
   The document structure of Cocoon's How-To page is likely to change soon. Please note that this HOWTO page is likely to change as well.
   </p>
  
  
  
  1.2       +2 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/revision-howto-xmlform-2002-05-20.xml
  
  Index: revision-howto-xmlform-2002-05-20.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/revision-howto-xmlform-2002-05-20.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- revision-howto-xmlform-2002-05-20.xml	25 May 2002 07:29:52 -0000	1.1
  +++ revision-howto-xmlform-2002-05-20.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -11,7 +11,8 @@
     </header>
   
     <body>
  -    <section title="Some text here."> 
  +    <section>
  +      <title>Some text here</title>
         <p>There is a problem with this approach</p>
         <ul>
           <li>Problem A.</li>
  
  
  
  1.2       +2 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/revision-step1-2002-05-20.xml
  
  Index: revision-step1-2002-05-20.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/revision-step1-2002-05-20.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- revision-step1-2002-05-20.xml	25 May 2002 07:29:52 -0000	1.1
  +++ revision-step1-2002-05-20.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -11,7 +11,8 @@
     </header>
   
     <body>
  -    <section title="Other comments."> 
  +    <section>
  +      <title>Other comments</title>
         <p>There is a problem with this approach</p>
         <ul>
           <li>Problem d.</li>
  
  
  
  1.2       +81 -73    xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step1.xml
  
  Index: step1.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step1.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- step1.xml	25 May 2002 07:29:52 -0000	1.1
  +++ step1.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,5 +1,5 @@
   <?xml version="1.0" encoding="UTF-8"?>
  -<!DOCTYPE howto PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "howto-v10.dtd">
  +<!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.0//EN" "howto-v10.dtd">
   
   <howto>
   
  @@ -19,7 +19,8 @@
           <li>Copy the following xml files below and save them in the folder you created.</li>
         </ul>
   
  -      <section title="start.xml">
  +      <section>
  +        <title>start.xml</title>
         <p>Below is the first page which you can copy and save as start.xml in the folder src\scratchpad\webapp\mount\xmlform\howto</p>
         <source>
           <![CDATA[
  @@ -80,7 +81,8 @@
             <li>end.xml</li>          
         </ul>
         
  -      <section title="register.xml">
  +      <section>
  +      <title>register.xml</title>
         <p>Register.xml lets the user register their username, password and email address so they can join the mailing lists they will next choose.</p>
         <p>The important part of the form you will need to change in your own forms are inside the xf:form tag. The id attribute value should match the sitemaps xmlform-id parameters value:</p>
         <source>
  @@ -95,62 +97,63 @@
          <source>
           <![CDATA[
           <?xml version="1.0" ?>
  -	
  -	
  -	<!-- 
  -	
  -		XMLForm instance document for the Cocoon Feedback Wizard.
  -	
  -	 	Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  -	    Author: Ivelin Ivanov, ivelin@apache.org, April 2002
  -	
  -	-->
  -	
  -	<document xmlns:xf="http://xml.apache.org/cocoon/xmlform/2002">
  -	
  -	
  -	  <xf:form id="form-feedback" view="registration" action="howto-wizard.html">
  -	
  -	    <xf:caption>Registration</xf:caption>    
  -	
  -	    <error>
  -	      <xf:violations class="error"/>
  -	    </error>
  -	
  -	    <xf:textbox ref="/userName">
  -	        <xf:caption>Last Name</xf:caption>    
  -	        <xf:violations class="error"/>
  -	    </xf:textbox>
  -	
  -	    <xf:textbox ref="/email">
  -	        <xf:caption>Email</xf:caption>    
  -	        <xf:violations class="error"/>
  -	    </xf:textbox>
  -	
  -	    <xf:password ref="/password">
  -	        <xf:caption>Password</xf:caption>
  -	        <xf:violations class="error"/>
  -	    </xf:password>
  -	
  -	    <xf:submit id="next" class="button"> 
  -	      <xf:caption>Next</xf:caption>
  -	    </xf:submit>
  -	
  -	  </xf:form>
  -	  
  -	</document>
  +  
  +  
  +  <!-- 
  +  
  +    XMLForm instance document for the Cocoon Feedback Wizard.
  +  
  +    Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  +      Author: Ivelin Ivanov, ivelin@apache.org, April 2002
  +  
  +  -->
  +  
  +  <document xmlns:xf="http://xml.apache.org/cocoon/xmlform/2002">
  +  
  +  
  +    <xf:form id="form-feedback" view="registration" action="howto-wizard.html">
  +  
  +      <xf:caption>Registration</xf:caption>    
  +  
  +      <error>
  +        <xf:violations class="error"/>
  +      </error>
  +  
  +      <xf:textbox ref="/userName">
  +          <xf:caption>Last Name</xf:caption>    
  +          <xf:violations class="error"/>
  +      </xf:textbox>
  +  
  +      <xf:textbox ref="/email">
  +          <xf:caption>Email</xf:caption>    
  +          <xf:violations class="error"/>
  +      </xf:textbox>
  +  
  +      <xf:password ref="/password">
  +          <xf:caption>Password</xf:caption>
  +          <xf:violations class="error"/>
  +      </xf:password>
  +  
  +      <xf:submit id="next" class="button"> 
  +        <xf:caption>Next</xf:caption>
  +      </xf:submit>
  +  
  +    </xf:form>
  +    
  +  </document>
           ]]>
           </source>
  -	</section>
  +  </section>
           
  -        <section title="interest.xml">
  +        <section>
  +        <title>interest.xml</title>
           <p>This XML page lets the user select areas of interest and depending on their answers they will be shown a selection of mailing lists they can join. The intelligence for deciding which pages to show next are in a java file which we will show you how to write later.</p>
           <p>This page consists of tick boxes which are either true or false.</p>
           <source>
           <![CDATA[
           <xf:selectBoolean ref="/organicGardening">
  -	        <xf:caption>Organic Gardening</xf:caption>    
  -	    </xf:selectBoolean>
  +          <xf:caption>Organic Gardening</xf:caption>    
  +      </xf:selectBoolean>
            ]]>
            </source>
            <p>Below is the page which you can copy into the folder "howto".</p>
  @@ -162,9 +165,9 @@
   
   <!-- 
   
  -	XMLForm instance document for the Cocoon Feedback Wizard.
  +  XMLForm instance document for the Cocoon Feedback Wizard.
   
  - 	Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  +  Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
     Author: Ivelin Ivanov, ivelin@apache.org, April 2002
   
   -->
  @@ -200,9 +203,10 @@
   </document>     
           ]]>
           </source>
  -	</section>
  +  </section>
   
  -         <section title="organicGardening.xml">
  +         <section>
  +         <title>organicGardening.xml</title>
            <p>The next page is shown if the user ticked the organic gardening box in the previous page, interest.xml. This page consists a selection of mailing lists the user can chose. It is very similar to the previous page containing 3 tick boxes. The user has the choice of moving forward through the form or back to the previous page so they can alter their area of interest.</p>
            <source>
           <![CDATA[
  @@ -212,9 +216,9 @@
   
   <!-- 
   
  -	XMLForm instance document for the Cocoon Feedback Wizard.
  +  XMLForm instance document for the Cocoon Feedback Wizard.
   
  - 	Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  +  Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
     Author: Ivelin Ivanov, ivelin@apache.org, April 2002
   
   -->
  @@ -250,9 +254,10 @@
   </document>        
           ]]>
           </source>
  -	</section>
  +  </section>
           
  -        <section title="cooking.xml">
  +        <section>
  +        <title>cooking.xml</title>
           <p>The next page is a selection of cookery mailing lists, very similar to the organicGardening.xml page. This page will appear if the user ticked the organic gardening option on the interest.xml page.</p>
            <source>
           <![CDATA[
  @@ -262,9 +267,9 @@
   
   <!-- 
   
  -	XMLForm instance document for the Cocoon Feedback Wizard.
  +  XMLForm instance document for the Cocoon Feedback Wizard.
   
  - 	Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  +  Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
     Author: Ivelin Ivanov, ivelin@apache.org, April 2002
   
   -->
  @@ -300,9 +305,10 @@
   </document>        
           ]]>
           </source>
  -	</section>
  +  </section>
           
  -        <section title="smallholdingManagement.xml">
  +        <section>
  +        <title>smallholdingManagement.xml</title>
           <p>Again this page is similar to organicGardening.xml, cooking.xml as it gives the user a choice of mailing lists.  This page will only appear if the user selected Smallholding Management as an interest on the interest.xml page.</p>
           
           <source>
  @@ -313,9 +319,9 @@
   
   <!-- 
   
  -	XMLForm instance document for the Cocoon Feedback Wizard.
  +  XMLForm instance document for the Cocoon Feedback Wizard.
   
  - 	Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  +  Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
     Author: Ivelin Ivanov, ivelin@apache.org, April 2002
   
   -->
  @@ -354,9 +360,10 @@
           
           ]]>
           </source>
  -	</section>
  +  </section>
           
  -        <section title="confirm.xml">
  +        <section>
  +        <title>confirm.xml</title>
           <p>This page shows the user the data that has been collected from them. The JavaBean that stores all the data is queried and the information collected is displayed. This is done using the xf:output tag, specifying which value to display with the ref attribute. If they wish to change any of the information they can do this now by clicking the previous button and altering their answers.  Otherwise they can click the finish button which will take them to the end page, end.xml.</p>
           <source>
            <![CDATA[
  @@ -364,9 +371,9 @@
   
   <!-- 
   
  -	XMLForm instance document for the Cocoon Feedback Wizard.
  +  XMLForm instance document for the Cocoon Feedback Wizard.
   
  - 	Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
  +  Original Author: Torsten Curdt, tcurdt@dff.st, March 2002
     Author: Ivelin Ivanov, ivelin@apache.org, April 2002
   
   -->
  @@ -458,16 +465,17 @@
   
     </xf:form>
     
  -</document>	        
  +</document>         
            ]]>
           </source>
           </section>
   
  -        <section title="end.xml">
  +        <section>
  +        <title>end.xml</title>
           <p>This page displays the final page. It tells the reader they have succesfully filled in the form and gives them the option to return to the start.</p> 
           <source>
            <![CDATA[
  -	   <?xml version="1.0" ?>
  +     <?xml version="1.0" ?>
   <document>
       <br/><br/><br/>
       <table align="center" width="50%" cellspacing="20">
  @@ -500,7 +508,7 @@
        
            ]]>
           </source>
  -	</section>
  +  </section>
           <p><link href="step2.html">Step 2: Validation</link></p>
           
   
  
  
  
  1.2       +17 -17    xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step2.xml
  
  Index: step2.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step2.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- step2.xml	25 May 2002 07:29:52 -0000	1.1
  +++ step2.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,5 +1,5 @@
   <?xml version="1.0" encoding="UTF-8"?>
  -<!DOCTYPE howto PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "howto-v10.dtd">
  +<!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.0//EN" "howto-v10.dtd">
   
   <howto>
   
  @@ -29,18 +29,18 @@
   <?xml version="1.0" ?>
   <!--
   
  -	Validating Schematron schema for the xmlform example wizard
  +  Validating Schematron schema for the xmlform example wizard
     
     Schematron Schema language home page:
     http://www.ascc.net/xml/schematron/
     
  -	Author: Ivelin Ivanov, ivelin@apache.org, April 2002
  +  Author: Ivelin Ivanov, ivelin@apache.org, April 2002
   
   -->
   
   <schema ns="http://xml.apache.cocoon/xmlform"  xmlns="http://www.ascc.net/xml/schematron">
   
  -	<title>Schema for the XML Form example</title>
  +  <title>Schema for the XML Form example</title>
     
       <phase id="registration">
               <p>For user identity information.</p>
  @@ -55,29 +55,29 @@
       </phase>
   
       
  -	<pattern name="User Info Validation Pattern" id="reg">
  -		<rule context="/userName">
  -			<assert  test="string-length(.) &gt; 7" diagnostics="dname dcount">
  +  <pattern name="User Info Validation Pattern" id="reg">
  +    <rule context="/userName">
  +      <assert  test="string-length(.) &gt; 7" diagnostics="dname dcount">
           Username should be at least 8 characters.
         </assert>
  -			<assert  test="string-length(.) &lt; 20">
  +      <assert  test="string-length(.) &lt; 20">
           Username should be less than 20 characters.
         </assert>
  -		</rule>
  -		<rule context="/password">
  -			<assert  test="string-length(.) &gt; 7" diagnostics="dname dcount">
  +    </rule>
  +    <rule context="/password">
  +      <assert  test="string-length(.) &gt; 7" diagnostics="dname dcount">
           Password should be at least 8 characters.
         </assert>
  -			<assert  test="string-length(.) &lt; 20">
  +      <assert  test="string-length(.) &lt; 20">
           Password should be less than 20 characters.
         </assert>
  -		</rule>
  -		<rule context="/email">
  -			<assert test="contains( string(.),'@')">
  +    </rule>
  +    <rule context="/email">
  +      <assert test="contains( string(.),'@')">
           Email format is invalid.
         </assert>
  -		</rule>		
  -	</pattern>
  +    </rule>   
  +  </pattern>
   </schema>
   ]]>
         </source>  
  
  
  
  1.2       +3 -2      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step3.xml
  
  Index: step3.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step3.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- step3.xml	25 May 2002 07:29:52 -0000	1.1
  +++ step3.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,5 +1,5 @@
   <?xml version="1.0" encoding="UTF-8"?>
  -<!DOCTYPE howto PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "howto-v10.dtd">
  +<!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.0//EN" "howto-v10.dtd">
   
   <howto>
   
  @@ -13,7 +13,8 @@
     </header>
   
       <steps title="Step Three: JavaBean"> 
  -      <section title="HowToBean.java">
  +      <section>
  +        <title>HowToBean.java</title>
           <p>Next we create the simple JavaBean which holds the data filled in the form. Each value has a set and get method. Each value must map with the form data. This is done using JXPath.</p>
           <p>Copy the file below and save it as HowToBean.java in the folder \apache\xml-cocoon2\src\scratchpad\src\org\apache\cocoon\samples\xmlform</p>
           <source>
  
  
  
  1.2       +11 -7     xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step4.xml
  
  Index: step4.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step4.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- step4.xml	25 May 2002 07:29:52 -0000	1.1
  +++ step4.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,5 +1,5 @@
   <?xml version="1.0" encoding="UTF-8"?>
  -<!DOCTYPE howto PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "howto-v10.dtd">
  +<!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.0//EN" "howto-v10.dtd">
   
   <howto>
   
  @@ -15,7 +15,8 @@
       <steps title="Step Four: HowtoWizardAction.java"> 
   
         <p>This is based on the WizardAction.java.  The prepare, perform and reset methods need to be altered. Your XML pages also need to be defined.</p> 
  -      <section title="XML Pages defined"> 
  +      <section>
  +        <title>XML Pages defined</title>
           <source>
           <![CDATA[
     // different form views 
  @@ -32,7 +33,8 @@
           </source>
         </section>
         
  -      <section title="Prepare Method">
  +      <section>
  +      <title>Prepare Method</title>
         <p>This method prepares the form and the pages to be returned before the actual form population starts.</p>
         <p>The first time the URL http://localhost:8080/cocoon/mount/xmlform/howto-wizard.html is called there is no command passes so the if statement test is met and the start page is returned.</p>
         <p>After the start page has been viewed and the user clicks on "Start" the command start is passed so the else test is met and the registration page is returned. Any old forms are removed and a form listener is added to the form.</p>  
  @@ -80,7 +82,8 @@
         </section>
         
         
  -      <section title="Perform Method">
  +      <section>
  +      <title>Perform Method</title>
         <p>The perform method controls the logic of the forms pages to be displayed.</p>
         <p>First the model is saved to the JavaBean</p>
         <source>
  @@ -237,7 +240,8 @@
         </section>
         
         
  -      <section title="Reset Method">
  +      <section>
  +      <title>Reset Method</title>
         <p>The reset method is used to tidy up any checkboxes and can be used to reset other fields in the form.</p>
         <source>
           <![CDATA[
  @@ -303,8 +307,8 @@
   /*
    * $Header: /home/cvspublic/xml-cocoon2/src/scratchpad/src/org/apache/cocoon/samples/xmlform/HowtoWizardAction.java,
    v 1.2 2002/05/09 07:26:07 ivelin Exp $
  - * $Revision: 1.1 $
  - * $Date: 2002/05/25 07:29:52 $
  + * $Revision: 1.2 $
  + * $Date: 2002/06/06 14:32:40 $
    *
    * ====================================================================
    * The Apache Software License, Version 1.1
  
  
  
  1.2       +1 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step5.xml
  
  Index: step5.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step5.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- step5.xml	25 May 2002 07:29:52 -0000	1.1
  +++ step5.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,5 +1,5 @@
   <?xml version="1.0" encoding="UTF-8"?>
  -<!DOCTYPE howto PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "howto-v10.dtd">
  +<!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.0//EN" "howto-v10.dtd">
   
   <howto>
   
  
  
  
  1.2       +1 -1      xml-forrest/src/documentation/content/xdocs/xml-site/ack.xml
  
  Index: ack.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/ack.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ack.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ ack.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,6 +1,6 @@
   <?xml version="1.0"?>
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  -<document><header><title>Credits</title><authors><person name="unknown" email="unknown"/></authors></header><body>
  +<document><header><title>Credits</title></header><body>
     
       <p>
          A collaborative project like this doesn't exist in a vacuum. In order to keep project
  
  
  
  1.2       +9 -7      xml-forrest/src/documentation/content/xdocs/xml-site/communication.xml
  
  Index: communication.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/communication.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- communication.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ communication.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Communication</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
       <p>
  @@ -29,20 +27,23 @@
         <p>
         The Project's list fall into the following categories:
       </p>
  -    <section title="Announcement Lists">
  +    <section>
  +      <title>Announcement Lists</title>
         <p>
         Announcement lists are very low traffic designed to communicate 
         important information, such as final releases of a subproject's 
         code, to a wide audience.
       </p>
       </section>
  -    <section title="User Lists">
  +    <section>
  +      <title>User Lists</title>
         <p>
         User lists are for users of a product to converse about such things 
         as configuration and operating of the products of the Project.
       </p>
       </section>
  -    <section title="Developer Lists">
  +    <section>
  +      <title>Developer Lists</title>
         <p>
         Developer lists are for the developers of the project. On these 
         lists suggestions and comments for code changes are discussed and 
  @@ -51,7 +52,8 @@
         "action" is.
       </p>
       </section>
  -    <section title="Commit Lists">
  +    <section>
  +      <title>Commit Lists</title>
         <p>
         The commit lists are where all cvs code commit messages are sent. 
         All committers are required to subscribe to this list so that they 
  
  
  
  1.2       +1 -3      xml-forrest/src/documentation/content/xdocs/xml-site/contact.xml
  
  Index: contact.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/contact.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- contact.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ contact.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Contact Info</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
       
  
  
  
  1.2       +11 -8     xml-forrest/src/documentation/content/xdocs/xml-site/cvs.xml
  
  Index: cvs.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/cvs.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- cvs.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ cvs.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>CVS Repositories</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Web Access to the Repository">
  +    <section>
  +      <title>Web Access to the Repository</title>
         <p>You can browse the xml.apache.org workspaces via the web.
       </p>
         <ul>
  @@ -65,13 +64,15 @@
           </li>
         </ul>
       </section>
  -    <section title="Download the Source">
  +    <section>
  +      <title>Download the Source</title>
         <p> Most users of the source code probably don't need to have day to day access to
                      the source code as it changes. For these users we provide easy to unpack source
                      code downloads via our download pages.
       </p>
       </section>
  -    <section title="Access the Source Tree">
  +    <section>
  +      <title>Access the Source Tree</title>
         <p>
           So, you've decided that you need access to the source tree to see the latest and
                      greatest code. There's two different forms of CVS access. The first is anonymous
  @@ -79,7 +80,8 @@
                      development server. If you don't know what this means, join the mailing list and find
                      out.
           </p>
  -      <section title="AnonCVS">
  +      <section>
  +        <title>AnonCVS</title>
           <p> Anyone can checkout source code from our anonymous CVS server. To do so,
                      simply use the following commands (if you are using a GUI CVS client, configure it
                      appropriately):
  @@ -130,7 +132,8 @@
   checkout -d xerces1 -r xerces_j_1 xml-xerces</source>
         </section>
       </section>
  -    <section title="Other Ways to Access the Source Code">
  +    <section>
  +      <title>Other Ways to Access the Source Code</title>
         <p>
       For some, using CVS pserver might not be enough. You can access the
       xml.apache.org source modules via CVSup or Rsync. For more information about
  
  
  
  1.2       +17 -11    xml-forrest/src/documentation/content/xdocs/xml-site/decisions.xml
  
  Index: decisions.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/decisions.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- decisions.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ decisions.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>Decision Making</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Decision Making">
  +    <section>
  +      <title>Decision Making</title>
         <p>
         All <link href="roles.html">Developers</link> are encouraged to 
         participate in decisions, but the decision itself is made by those 
  @@ -57,7 +56,8 @@
         majority vote, depending on the type of action item.
       </p>
       </section>
  -    <section title="Action Items">
  +    <section>
  +      <title>Action Items</title>
         <p>
         All decisions revolve around "Action Items." Action Items consist of 
         the following:
  @@ -70,7 +70,8 @@
           <li>Showstoppers</li>
           <li>Product Changes</li>
         </ul>
  -      <section title="Long Term Plans">
  +      <section>
  +        <title>Long Term Plans</title>
           <p>
           Long term plans are simply announcements that group members are 
           working on particular issues related to the Project. These are not 
  @@ -79,7 +80,8 @@
           inform the group of their feelings.
         </p>
         </section>
  -      <section title="Short Term Plans">
  +      <section>
  +        <title>Short Term Plans</title>
           <p>
           Short term plans are announcements that a developer is working on a 
           particular set of documentation or code files with the implication 
  @@ -87,7 +89,8 @@
           changes.
         </p>
         </section>
  -      <section title="Release Plan">
  +      <section>
  +        <title>Release Plan</title>
           <p>
           A release plan is used to keep all Developers aware of when a 
           release is desired, who will be the release manager, when the 
  @@ -97,14 +100,16 @@
   
         </p>
         </section>
  -      <section title="Release Testing">
  +      <section>
  +        <title>Release Testing</title>
           <p>
           After a new release is built, it must be tested before being 
           released to the public. Majority approval is required before the 
           release can be made.
         </p>
         </section>
  -      <section title="Showstoppers">
  +      <section>
  +        <title>Showstoppers</title>
           <p>
           Showstoppers are issues that require a fix be in place before the 
           next public release. They are listed in the status file in order to 
  @@ -113,7 +118,8 @@
           so by lazy consensus.
         </p>
         </section>
  -      <section title="Product Changes">
  +      <section>
  +        <title>Product Changes</title>
           <p>
           Changes to the products of the Project, including code and 
           documentation, will appear as action items in the status file. All 
  
  
  
  1.2       +6 -2      xml-forrest/src/documentation/content/xdocs/xml-site/guidelines.xml
  
  Index: guidelines.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/guidelines.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- guidelines.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ guidelines.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,6 +1,9 @@
   <?xml version="1.0"?>
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  -<document><header><title>Project Guidelines</title><authors><person name="unknown" email="unknown"/></authors></header><body><section title="The xml.apache.org Project Guidelines"><p>
  +<document><header><title>Project Guidelines</title></header><body>
  +    <section>
  +      <title>The xml.apache.org Project Guidelines</title>
  +      <p>
         This document defines the guidelines of the <em>xml.apache.org</em> 
         project. It includes definitions of the various categories of 
         membership, who is able to vote, how conflicts are resolved by voting, 
  @@ -25,7 +28,8 @@
           Defines how the Project's source code is organized and developed.</li><li><link href="management.html">Project Management</link>
           Defines the roles and responsibilities of the Project Management
           Committee (PMC).</li><li><link href="mission.html">Our Mission / Charter</link>
  -        A copy of the Charter document for the xml.apache.org Project.</li></ul></section><section title="Website update guidelines"><warning>This is <strong>not</strong> valid for projects using Forrest for their documentation needs!</warning><p>
  +        A copy of the Charter document for the xml.apache.org Project.</li></ul></section>
  +        <section><title>Website update guidelines</title><warning>This is <strong>not</strong> valid for projects using Forrest for their documentation needs!</warning><p>
         As XML-oriented projects, so our website is also generated from 
         XML files.  While many similar websites may use servlets or a 
         system like Cocoon to generate their websites on-the-fly 
  
  
  
  1.2       +23 -12    xml-forrest/src/documentation/content/xdocs/xml-site/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/index.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ index.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -1,8 +1,9 @@
   <?xml version="1.0"?>
   <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  -<document><header><title>xml.apache.org</title><authors><person name="unknown" email="unknown"/></authors></header><body>
  +<document><header><title>xml.apache.org</title></header><body>
     
  -      <section title="Welcome to the Apache XML Project">
  +      <section>
  +       <title>Welcome to the Apache XML Project</title>
       <p>
         The goals of the <em>Apache XML Project</em> are:
       </p>
  @@ -55,7 +56,8 @@
           <em>Crimson</em> - A Java XML parser derived from the Sun Project X Parser.
         </li>
       </ul>
  -    <section title="Xerces: XML parsers in Java and C++ (plus Perl and COM)">
  +    <section>
  +      <title>Xerces: XML parsers in Java and C++ (plus Perl and COM)</title>
         <p>
           Xerces (named after the Xerces Blue butterfly) provides world-class
           XML parsing and generation. Fully-validating parsers are available for
  @@ -74,7 +76,8 @@
     A COM wrapper (also for Xerces-C) provides compatibility with the Microsoft MSXML parser.
         </p>
       </section>
  -    <section title="Xalan: XSL stylesheet processors in Java &amp; C++">
  +    <section>
  +      <title>Xalan: XSL stylesheet processors in Java &amp; C++</title>
         <p>
     Xalan (named after a rare musical instrument) provides high-performance
     XSLT stylesheet processing. Xalan fully implements the W3C XSLT and XPath
  @@ -88,14 +91,16 @@
     Xalan is currently available in Java, and available in Alpha form for C++.
         </p>
       </section>
  -    <section title="Cocoon: XML-based web publishing">
  +    <section>
  +      <title>Cocoon: XML-based web publishing</title>
         <p>
           Cocoon is a powerful framework for XML web publishing which brings a whole
           new world of abstraction and ease to consolidated web site creation and
           management based on the XML paradigm and related technologies.
         </p>
       </section>
  -    <section title="AxKit: XML-based web publishing in mod_perl">
  +    <section>
  +      <title>AxKit: XML-based web publishing in mod_perl</title>
         <p>
           AxKit brings the power of XML web publishing and dynamic
           XML based applications to the Apache web server using the
  @@ -103,7 +108,8 @@
           of XML with the performance of a native Apache solution.
         </p>
       </section>
  -    <section title="FOP: XSL Formatting Object processor in Java">
  +    <section>
  +      <title>FOP: XSL Formatting Object processor in Java</title>
         <p>
           FOP is the world's first print formatter driven by XSL formatting
           objects. It is a Java 1.2 application that reads a formatting object
  @@ -113,11 +119,13 @@
           the case of Xalan) SAX events.
         </p>
       </section>
  -    <section title="Forrest: Developer Community Portal">
  +    <section>
  +      <title>Forrest: Developer Community Portal</title>
         <p>
           Forrest is an XML/XSLT-based, skinable documentation publishing  environment that publishes documentation and vital stats of the xml.apache.org sub-projects. It sits underneath xml.apache.org: you're looking at the result of Forrest's work.</p>
       </section>
  -    <section title="Xang: Rapid development of dynamic server pages in JavaScript">
  +    <section>
  +      <title>Xang: Rapid development of dynamic server pages in JavaScript</title>
         <p>
     Apache Xang lets you quickly build data-driven, cross-platform Web
     applications that integrate disparate data sources. The Xang architecture
  @@ -125,7 +133,8 @@
     industry standards such as HTTP, XML, XSL, DOM and ECMAScript (JavaScript).
         </p>
       </section>
  -    <section title="SOAP: Simple Object Access Protocol">
  +    <section>
  +      <title>SOAP: Simple Object Access Protocol</title>
         <p>
     The Apache Soap project is an implementation of the draft W3C
     protocol by the same name.  It is based on, and supersedes, the
  @@ -141,14 +150,16 @@
     datatypes, and a convention for representing remote procedure calls
     and responses.</p>
       </section>
  -    <section title="Crimson: A Java XML parser derived from the Sun Project X Parser">
  +    <section>
  +      <title>Crimson: A Java XML parser derived from the Sun Project X Parser</title>
         <p>
         The source code for Crimson is available under the xml-crimson CVS
         module. Please visit the Crimson pages for more information.
         </p>
       </section>
     </section>
  -  <section title="Anyone Can Participate">
  +  <section>
  +    <title>Anyone Can Participate</title>
       <p>
         The <em>xml.apache.org</em> Project is composed of developers from all
         around the world, both individuals and engineers from major corporations.
  
  
  
  1.2       +1 -3      xml-forrest/src/documentation/content/xdocs/xml-site/legal.xml
  
  Index: legal.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/legal.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- legal.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ legal.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Legal Stuff</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
       <p>
  
  
  
  1.2       +9 -7      xml-forrest/src/documentation/content/xdocs/xml-site/library.xml
  
  Index: library.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/library.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- library.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ library.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>Reference Library</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Reference Library">
  +    <section>
  +      <title>Reference Library</title>
         <p>
       The <em>xml.apache.org</em> project lives or fails based on its human resources. Users and
       contributors alike help the project with ideas and brainpower. A common
  @@ -17,7 +16,8 @@
       and may be helpful to you:
       </p>
       </section>
  -    <section title="Technical Resources">
  +    <section>
  +      <title>Technical Resources</title>
         <p>
         These resources are required reading for anybody contributing source code to the
         project.
  @@ -50,7 +50,8 @@
         </li>
         </ul>
       </section>
  -    <section title="Source Code Philosophy Resources">
  +    <section>
  +      <title>Source Code Philosophy Resources</title>
         <p> 
           The following are a set of articles written about the recent source code movements
           that help illustrate some of the attributes of a collaborative project such as this. You
  @@ -74,7 +75,8 @@
         </li>
         </ul>
       </section>
  -    <section title="XML Resources">
  +    <section>
  +      <title>XML Resources</title>
         <p>A wide variety of XML-oriented resources are out on the net today.
         Just a few that we have found useful include:
         </p>
  
  
  
  1.2       +52 -31    xml-forrest/src/documentation/content/xdocs/xml-site/mail.xml
  
  Index: mail.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/mail.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mail.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ mail.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Mailing Lists</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
       <p>
  @@ -21,7 +19,8 @@
       probably read any FAQ postings or simply read a sampling of postings 
       on the list before posting your first question.
     </p>
  -    <section title="Usage Notes">
  +    <section>
  +      <title>Usage Notes</title>
         <p>
         Archives are generally named after the project they're about (duh!) 
         with a suffix that denotes the subjects covered.  Common suffixes are:
  @@ -46,7 +45,8 @@
           <code>*-help</code> get Help on mailing list commands
       </p>
       </section>
  -    <section title="Public archives">
  +    <section>
  +      <title>Public archives</title>
         <p>
         Archives of many of the most popular xml.apache.org mailing lists 
         are kept at <jump href="http://marc.theaimsgroup.com/">http://marc.theaimsgroup.com/</jump>,
  @@ -59,7 +59,8 @@
         <jump href="http://archive.covalent.net/">http://archive.covalent.net/</jump>
         </p>
       </section>
  -    <section title="The xml.apache.org Announcement List">
  +    <section>
  +      <title>The xml.apache.org Announcement List</title>
         <p>
           <em>Low Traffic</em>
           <jump href="mailto:announcements-subscribe@xml.apache.org">Subscribe</jump>
  @@ -73,7 +74,8 @@
         is kept.
       </p>
       </section>
  -    <section title="The xml.apache.org General Discussion List">
  +    <section>
  +      <title>The xml.apache.org General Discussion List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:general-subscribe@xml.apache.org">Subscribe</jump>
  @@ -89,7 +91,8 @@
         One exception is the xml-crimson codebase, which does not currently have it's own mailing list.
       </p>
       </section>
  -    <section title="The Xerces Developer List (obsolete)">
  +    <section>
  +      <title>The Xerces Developer List (obsolete)</title>
         <p>
           <em>Low Traffic - Obsolete</em>
         mailto:xerces-dev-subscribe@xml.apache.org
  @@ -100,7 +103,8 @@
         Everybody should switch to one of the specific mailing lists below.</em>
         </p>
       </section>
  -    <section title="The Xerces-J User List">
  +    <section>
  +      <title>The Xerces-J User List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:xerces-j-user-subscribe@xml.apache.org">Subscribe</jump>
  @@ -116,7 +120,8 @@
         mailing list are kept. 
       </p>
       </section>
  -    <section title="The Xerces-J Developer List">
  +    <section>
  +      <title>The Xerces-J Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:xerces-j-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -138,7 +143,8 @@
   
       </p>
       </section>
  -    <section title="The Xerces-C Developer List">
  +    <section>
  +      <title>The Xerces-C Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:xerces-c-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -161,7 +167,8 @@
         mailing lists are kept. 
       </p>
       </section>
  -    <section title="The Xerces-P Developer List">
  +    <section>
  +      <title>The Xerces-P Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:xerces-p-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -182,7 +189,8 @@
         mailing lists are kept. 
       </p>
       </section>
  -    <section title="The Xalan-J Users List">
  +    <section>
  +      <title>The Xalan-J Users List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:xalan-j-users-subscribe@xml.apache.org">Subscribe</jump>
  @@ -196,7 +204,8 @@
         Archives are kept at <jump href="http://marc.theaimsgroup.com/?l=xalan-j-users">http://marc.theaimsgroup.com/?l=xalan-j-users</jump>
         </p>
       </section>
  -    <section title="The Xalan-C Users List">
  +    <section>
  +      <title>The Xalan-C Users List</title>
         <p>
           <em>Low Traffic</em>
           <jump href="mailto:xalan-c-users-subscribe@xml.apache.org">Subscribe</jump>
  @@ -210,7 +219,8 @@
         Archives are kept at <jump href="http://marc.theaimsgroup.com/?l=xalan-c-users">http://marc.theaimsgroup.com/?l=xalan-c-users</jump> (may not be active yet)
       </p>
       </section>
  -    <section title="The Xalan Developer List">
  +    <section>
  +      <title>The Xalan Developer List</title>
         <p>
           <em>High Traffic</em>
           <jump href="mailto:xalan-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -233,7 +243,8 @@
         For user-oriented questions, please see the appropriate User list above.
       </p>
       </section>
  -    <section title="The Cocoon Users List">
  +    <section>
  +      <title>The Cocoon Users List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:cocoon-users-subscribe@xml.apache.org">Subscribe</jump>
  @@ -246,7 +257,8 @@
         is kept.
       </p>
       </section>
  -    <section title="The Cocoon Developer List">
  +    <section>
  +      <title>The Cocoon Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:cocoon-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -268,7 +280,8 @@
         mailing list is kept.
       </p>
       </section>
  -    <section title="The FOP User List">
  +    <section>
  +      <title>The FOP User List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:fop-user-subscribe@xml.apache.org">Subscribe</jump>
  @@ -280,7 +293,8 @@
         <jump href="http://marc.theaimsgroup.com/?l=fop-user">http://marc.theaimsgroup.com/?l=fo-user</jump>.
       </p>
       </section>
  -    <section title="The Forrest Developer List">
  +    <section>
  +      <title>The Forrest Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:forrest-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -291,7 +305,8 @@
         <p>
         This is the list where participating developers of Forrest meet and discuss issues, code 
         changes/additions, etc.</p>
  -    </section><section title="The FOP Developer List">
  +    </section><section>
  +      <title>The FOP Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:fop-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -314,7 +329,8 @@
         mailing list is kept.
       </p>
       </section>
  -    <section title="The Xang Developer List">
  +    <section>
  +      <title>The Xang Developer List</title>
         <p>
           <em>Low Traffic</em>
           <jump href="mailto:xang-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -329,9 +345,10 @@
         <p>
        There is no current Xang User mailing list, so all users can use this address until
        enough of a community forms to create a separate list.
  -	</p>
  +  </p>
       </section>
  -    <section title="The Soap Users List">
  +    <section>
  +      <title>The Soap Users List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:soap-user-subscribe@xml.apache.org">Subscribe</jump>
  @@ -342,7 +359,8 @@
         installation problems and what not.
       </p>
       </section>
  -    <section title="The Soap Developer List">
  +    <section>
  +      <title>The Soap Developer List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:soap-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -353,9 +371,10 @@
         discuss issues, code changes/additions, etc. Subscribers to this
         list also get notices of each and every code change, build 
         results, testing notices, etc. 
  -	</p>
  +  </p>
       </section>
  -    <section title="The Batik Users List">
  +    <section>
  +      <title>The Batik Users List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:batik-users-subscribe@xml.apache.org">Subscribe</jump>
  @@ -365,9 +384,10 @@
         This is the list for active users of the Batik project, where issues regarding
         installation and use of Batik are discussed. Also code changes and new
         releases are announced on this list.
  -	</p>
  +  </p>
       </section>
  -    <section title="The Batik Developers List">
  +    <section>
  +      <title>The Batik Developers List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:batik-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -376,9 +396,10 @@
         <p>
         This is the list for everyone interested and involved with the active
         development of  Batik.
  -	</p>
  +  </p>
       </section>
  -    <section title="The XML Security Developers List">
  +    <section>
  +      <title>The XML Security Developers List</title>
         <p>
           <em>Medium Traffic</em>
           <jump href="mailto:security-dev-subscribe@xml.apache.org">Subscribe</jump>
  @@ -387,7 +408,7 @@
         <p>
         This is the list for everyone interested and involved with the active
         development of XML Security.
  -	</p>
  +  </p>
       </section>
     </body>
   </document>
  
  
  
  1.2       +7 -6      xml-forrest/src/documentation/content/xdocs/xml-site/management.xml
  
  Index: management.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/management.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- management.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ management.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Project Management</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
       <p>
  @@ -15,7 +13,8 @@
         year. There is no term limit for members. The list of current members 
         can be found in our <link href="whoweare.html">Project Credits</link>.
       </p>
  -    <section title="Roles">
  +    <section>
  +      <title>Roles</title>
         <p>
           The PMC is responsible for the strategic direction and success of 
           the <em>xml.apache.org</em> Project. This governing body is expected 
  @@ -30,7 +29,8 @@
           as primary liaison.
         </p>
       </section>
  -    <section title="Meetings">
  +    <section>
  +      <title>Meetings</title>
         <p>
           The PMC meets monthly with a majority of its members to discuss 
           issues, determine strategic direction, and forward progress. These 
  @@ -40,7 +40,8 @@
           membership status.
         </p>
       </section>
  -    <section title="Membership">
  +    <section>
  +      <title>Membership</title>
         <p>
           PMC members may resign at any time. The Chairman may resign as 
           Chairman at any time without resigning membership to the PMC. The 
  
  
  
  1.2       +5 -5      xml-forrest/src/documentation/content/xdocs/xml-site/mission.xml
  
  Index: mission.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/mission.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mission.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ mission.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>Project Mission</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Mission/Charter">
  +    <section>
  +      <title>Mission/Charter</title>
         <p>
           <em>The most current copy of our charter can always be found 
         at </em>
  @@ -218,7 +217,8 @@
   and achieve a coherent architecture among xml.apache.org and these
   projects.</source>
       </section>
  -    <section title="Projects">
  +    <section>
  +      <title>Projects</title>
         <p>
         The <em>Apache XML Project</em> currently consists of a number of sub- 
         projects, each focused on a different aspect of XML:
  
  
  
  1.2       +36 -21    xml-forrest/src/documentation/content/xdocs/xml-site/news.xml
  
  Index: news.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/news.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- news.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ news.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,42 +3,46 @@
   <document>
     <header>
       <title>News and Status</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Current News">
  +    <section>
  +      <title>Current News</title>
         <p>Committers should feel free to update these pages with relevant
       news about their projects.  Be sure to see the information about updating
       the xml.apache.org website in the <link href="guidelines.html">guidelines</link>.
       </p>
  -      <section title="Forrest website launched (June 1, 2002)">
  +      <section>
  +        <title>Forrest website launched (June 1, 2002)</title>
           <p>
           The Forrest team will be gradually rebuilding the xml.apache.org website
           into a true developer community for Apache XML technology. <jump href="http://xml.apache.org/forrest/">Check us out</jump>.
          </p>
         </section>
  -      <section title="Cocoon 2.0.2 released (March 26, 2002)">
  +      <section>
  +        <title>Cocoon 2.0.2 released (March 26, 2002)</title>
           <p>
           The Apache Cocoon team is proud to announce the release of
           Cocoon 2.0.2. The distribution is available from the <jump href="http://xml.apache.org/dist/cocoon">download pages</jump>.
          </p>
         </section>
  -      <section title="Cocoon 2.0.1 released (January 31, 2002)">
  +      <section>
  +        <title>Cocoon 2.0.1 released (January 31, 2002)"</title>
           <p>
           The Apache Cocoon team is proud to announce the release of
           Cocoon 2.0.1. The distribution is available from the <jump href="http://xml.apache.org/dist/cocoon">download pages</jump>.
          </p>
         </section>
  -      <section title="Xerces 2.0.0 (beta) is released">
  +      <section>
  +        <title>Xerces 2.0.0 (beta) is released</title>
           <p>
           The beta release for Xerces2 marks the first step in producing the
           next generation of Xerces XML parser technology. Xerces2 beta is
           available from the <jump href="http://xml.apache.org/dist/">download pages</jump>.
          </p>
         </section>
  -      <section title="xml-commons subproject is formed! (Summer-01)">
  +      <section>
  +        <title>xml-commons subproject is formed! (Summer-01)</title>
           <p>
         A new subproject focusing on sharing common XML code and interfaces, etc.
         was formed recently.  For details, look in the xml-commons repository,
  @@ -46,7 +50,8 @@
         mailing list.
         </p>
         </section>
  -      <section title="Xalan-J was nominated for an award! (Summer-01)">
  +      <section>
  +        <title>Xalan-J was nominated for an award! (Summer-01)</title>
           <p>Dear Apache XML Project,<br/>
             <br/>
   Congratulations! JavaWorld has selected the Apache XML Project's Xalan-Java
  @@ -73,27 +78,32 @@
   415-975-2651<br/>
           </p>
         </section>
  -      <section title="Batik was nominated for an award! (Sep-01)">
  +      <section>
  +        <title>Batik was nominated for an award! (Sep-01)</title>
           <p>Some details were posted on<jump href="http://marc.theaimsgroup.com/?l=xml-apache-general&amp;m=99973420212175&amp;w=2">the general mailing list</jump>
           </p>
         </section>
       </section>
  -    <section title="Project Status">
  -      <section title="Batik Status: Source Code and Binaries Available">
  +    <section>
  +      <title>Project Status</title>
  +      <section>
  +        <title>Batik Status: Source Code and Binaries Available</title>
           <p>
         Batik, the Java Based toolkit for applications that want to use images in
         the Scalable Vector Graphics (SVG) format is finally available on our
  -      <jump href="http://xml.apache.org/dist/">download 		pages</jump>!
  +      <jump href="http://xml.apache.org/dist/">download pages</jump>!
       </p>
         </section>
  -      <section title="Xang - Source code for XPages from Datachannel released">
  +      <section>
  +        <title>Xang - Source code for XPages from Datachannel released</title>
           <p>
         Xang, the new code name of the XPages project from DataChannel is
         currently available in source form for download. Check out the
         <jump href="http://xml.apache.org/dist/">download pages</jump> for the source.
       </p>
         </section>
  -      <section title="Crimson - Source code for Project X from Sun released">
  +      <section>
  +        <title>Crimson - Source code for Project X from Sun released</title>
           <p>
         Crimson, the code name of the XML Parser Project X from Sun is
         currently available in source form for download.
  @@ -103,7 +113,8 @@
           <p>The current production release is Crimson 1.1.2beta2(Sep-01).
       Work on Crimson is mostly limited to bugfixing; discussions take place on general@xml.apache.org.</p>
         </section>
  -      <section title="Xerces status: Source Code and Binaries Available">
  +      <section>
  +        <title>Xerces status: Source Code and Binaries Available</title>
           <p>
         Xerces XML parsers in Java, C++, Perl, and COM are currently available in
         source code and binary form. Check out the
  @@ -114,7 +125,8 @@
       Work on 1.x is mostly limited to bugfixing; most of the Xerces community
       is moving forward with Xerces 2.x codebase.</p>
         </section>
  -      <section title="Xalan Status: Source Code and Binaries Available">
  +      <section>
  +        <title>Xalan Status: Source Code and Binaries Available</title>
           <p>
         Xalan XSLT stylesheet processor in Java is currently available in
         source code and binary form. Check out the
  @@ -122,14 +134,16 @@
         source!
       </p>
         </section>
  -      <section title="Cocoon Status: Source Code and Binaries Available">
  +      <section>
  +        <title>Cocoon Status: Source Code and Binaries Available</title>
           <p>
         Cocoon, the XML-based web publishing solution in Java, is available.
         Check out the <jump href="http://xml.apache.org/dist/cocoon">download pages</jump> for binaries
         and sources.
       </p>
         </section>
  -      <section title="FOP Status: Source Code and Binaries Available">
  +      <section>
  +        <title>FOP Status: Source Code and Binaries Available</title>
           <p>
         FOP, the XSL:FO formatting objects processor in Java, is currently available in
         source code and binary form. Check out the
  @@ -138,7 +152,8 @@
       </p>
         </section>
       </section>
  -    <section title="Past News">
  +    <section>
  +      <title>Past News</title>
         <ul>
           <li>
           Apache forms xml.apache.org --
  
  
  
  1.2       +5 -5      xml-forrest/src/documentation/content/xdocs/xml-site/overview.xml
  
  Index: overview.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/overview.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- overview.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ overview.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Get Involved!</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
       <p>
  @@ -18,7 +16,8 @@
         There are a variety of ways to participate. Regardless of how you choose 
         to participate, we suggest you join some or all of our <link href="mail.html">mailing lists</link>.
       </p>
  -    <section title="Use the Products and Give Us Feedback">
  +    <section>
  +      <title>Use the Products and Give Us Feedback</title>
         <p>
           Using the products,reporting bugs, making feature requests, etc. is by far 
           the most important role. It's your feedback that allows the technology to 
  @@ -36,7 +35,8 @@
           </li>
         </ul>
       </section>
  -    <section title="Contribute Code or Documentation Patches">
  +    <section>
  +      <title>Contribute Code or Documentation Patches</title>
         <p>
           In this role, you participate in the actual development of the code. If 
           this is the type of role you'd like to play, here are some steps (in 
  
  
  
  1.2       +11 -8     xml-forrest/src/documentation/content/xdocs/xml-site/roles.xml
  
  Index: roles.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/roles.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- roles.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ roles.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>Roles and Responsibilities</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Roles and Responsibilities">
  +    <section>
  +      <title>Roles and Responsibilities</title>
         <p>
         The roles and responsibilities that people can assume in the project 
         are based on merit. Everybody can help no matter what their role. 
  @@ -16,7 +15,8 @@
         obtain the right to vote and commit directly to the source repository.
       </p>
       </section>
  -    <section title="Users">
  +    <section>
  +      <title>Users</title>
         <p>
         Users are the people who use the products of the Project. People in 
         this role aren't contributing code, but they are using the products, 
  @@ -29,7 +29,8 @@
         become a developer.
       </p>
       </section>
  -    <section title="Developers">
  +    <section>
  +      <title>Developers</title>
         <p>
         Developers are the people who write code or documentation patches or 
         contribute positively to the project in other ways. A developer's 
  @@ -38,7 +39,8 @@
         authors for that file.
       </p>
       </section>
  -    <section title="Committers">
  +    <section>
  +      <title>Committers</title>
         <p>
         Developers who give frequent and valuable contributions to a 
         subproject of the Project can have their status promoted to that of 
  @@ -64,7 +66,8 @@
         <link href="whoweare.html">Project Credits</link>.
       </p>
       </section>
  -    <section title="Project Management Committee (PMC)">
  +    <section>
  +      <title>Project Management Committee (PMC)</title>
         <p>
         Committers who frequently participate with valuable contributions 
         may have their status promoted to that of a "Project Management 
  
  
  
  1.2       +13 -9     xml-forrest/src/documentation/content/xdocs/xml-site/source.xml
  
  Index: source.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/source.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- source.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ source.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>Source Repositories</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Source Repositories">
  +    <section>
  +      <title>Source Repositories</title>
         <p>
         The Project's codebase is maintained in shared information 
         repositories using CVS on the xml.apache.org machine. Only Committers 
  @@ -23,7 +22,8 @@
         Sun.
       </p>
       </section>
  -    <section title="License">
  +    <section>
  +      <title>License</title>
         <p>
         All source code committed to the Project's repositories must be 
         covered by the <em>Apache License version 1.1</em>
  @@ -31,7 +31,8 @@
         redistribution under the same conditions as the Apache License.
       </p>
       </section>
  -    <section title="Status Files">
  +    <section>
  +      <title>Status Files</title>
         <p>
         Each of the Project's active source code repositories contain a file 
         named <em>STATUS</em> which is used to keep track of the agenda and 
  @@ -47,14 +48,16 @@
         mailing lists three times per week.
       </p>
       </section>
  -    <section title="Branches">
  +    <section>
  +      <title>Branches</title>
         <p>
         Groups are allowed to create a branch for release cycles, etc. They 
         are expected to merge completely back with the main branch as soon as 
         their release cycle is complete.
       </p>
       </section>
  -    <section title="Changes">
  +    <section>
  +      <title>Changes</title>
         <p>
         Simple patches to fix bugs can be committed then reviewed. With a 
         commit-then-review process, the Committer is trusted to have a high 
  @@ -89,7 +92,8 @@
         before the change can be included in any public release.
       </p>
       </section>
  -    <section title="Patches">
  +    <section>
  +      <title>Patches</title>
         <p>
         When a specific change to a product is proposed for discussion or 
         voting on the appropriate development mailing list, it should be 
  
  
  
  1.2       +9 -7      xml-forrest/src/documentation/content/xdocs/xml-site/whoweare.xml
  
  Index: whoweare.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/xml-site/whoweare.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- whoweare.xml	4 Jun 2002 21:39:08 -0000	1.1
  +++ whoweare.xml	6 Jun 2002 14:32:40 -0000	1.2
  @@ -3,12 +3,11 @@
   <document>
     <header>
       <title>Who We Are</title>
  -    <authors>
  -      <person name="unknown" email="unknown"/>
  -    </authors>
  +    
     </header>
     <body>
  -    <section title="Who We Are">
  +    <section>
  +      <title>Who We Are</title>
         <p>
           The <em>xml.apache.org</em> project operates on a meritocracy: the more you do,
           the more
  @@ -18,7 +17,8 @@
           If you would like to get involved, the first step is to join the <link href="mail.html">mailing lists</link>.
       </p>
       </section>
  -    <section title="Project Management Committee">
  +    <section>
  +      <title>Project Management Committee</title>
         <ul>
           <li>Scott Boag
             <jump href="mailto:scott_boag@lotus.com">scott_boag@lotus.com</jump>
  @@ -37,7 +37,8 @@
           </li>
         </ul>
       </section>
  -    <section title="Committers">
  +    <section>
  +      <title>Committers</title>
         <p>
         Committers are people with write access to their project's CVS 
         repository.  New Committers to each project are nominated by and 
  @@ -45,7 +46,8 @@
         details on getting involved see the <link href="roles.html">roles</link>.
       </p>
       </section>
  -    <section title="Advisors">
  +    <section>
  +      <title>Advisors</title>
         <ul>
           <li>Brian Behlendorf<jump href="mailto:brian@behlendorf.com">brian@behlendorf.com</jump>
             <br/>
  
  
  

Mime
View raw message