You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by st...@apache.org on 2002/06/04 23:39:09 UTC
cvs commit: xml-forrest/src/documentation/content/xdocs/xml-site ack.xml book.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
stevenn 2002/06/04 14:39:09
Added: src/documentation/content/xdocs/xml-site ack.xml book.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:
added xml.apache.org main site content to forrest as a testcase
Revision Changes Path
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/ack.xml
Index: ack.xml
===================================================================
<?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>
<p>
A collaborative project like this doesn't exist in a vacuum. In order to keep project
like this running, you need support and help. The <em>xml.apache.org</em> project has been
fortunate to have the support of the following:
</p>
<ul>
<li>
<jump href="http://www.apache.org">The Apache Group</jump><br/>
The xml.apache.org project operates as an Official Project under the Apache
umbrella. It abides by the same principles and operating procedures as the parent
organization.
</li>
<li>
<jump href="http://www.ibm.com">IBM</jump>
<br/>
IBM provided the initial code base for Xerces (Java, C++, Perl and COM versions), as
well as ongoing support for this and other Apache projects (e.g. the Apache HTTP server).
</li>
<li>
<jump href="http://www.lotus.com">Lotus</jump>
<br/>
Lotus provided the initial code base for Xalan (Java and C++ versions).
</li>
<li>
<jump href="http://www.exoffice.com">Exoffice</jump>
<br/>
Exoffice has contributed their OpenXML and XSL:P technologies.
</li>
<li>
<jump href="http://www.datachannel.com">DataChannel</jump>
<br/>
DataChannel has contributed their XPages technologies.
</li>
<li>
<jump href="http://www.sun.com">Sun Microsystems, Inc.</jump>
<br/>
Sun has contributed their ProjectX and XHTML parser technologies.
</li>
<li>
<jump href="http://www.hyperreal.com">Hyperreal</jump>
Hyperreal is the server that this site is served from.
</li>
<li>
<jump href="http://www.above.net">Above.Net</jump>
Above.Net provides the network bandwidth for the Apache websites.
</li>
</ul>
</body></document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/book.xml
Index: book.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "book-cocoon-v10.dtd">
<book software="xml.apache.org"
title="The Apache XML Project"
copyright="@year@ The Apache Foundation"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="About">
<menu-item label="Index" href="index.html"/>
<menu-item label="News" href="news.html"/>
<menu-item label="Mission" href="mission.html"/>
<menu-item label="Guidelines" href="guidelines.html"/>
<menu-item label="Roles" href="roles.html"/>
<menu-item label="Communication" href="communication.html"/>
<menu-item label="Decisions" href="decisions.html"/>
<menu-item label="Conventions" href="source.html"/>
<menu-item label="Management" href="management.html"/>
</menu>
<menu label="Projects">
<menu-item href="http://xml.apache.org/xerces-j/index.html" label="Xerces Java 1" />
<menu-item href="http://xml.apache.org/xerces2-j/index.html" label="Xerces Java 2" />
<menu-item href="http://xml.apache.org/xerces-c/index.html" label="Xerces C++" />
<menu-item href="http://xml.apache.org/xerces-p/index.html" label="Xerces Perl" />
<menu-item href="http://xml.apache.org/xalan-j/index.html" label="Xalan Java 2" />
<menu-item href="http://xml.apache.org/xalan-c/index.html" label="Xalan C++" />
<menu-item href="http://xml.apache.org/fop/index.html" label="FOP" />
<menu-item href="http://xml.apache.org/forrest/index.html" label="Forrest" />
<menu-item href="http://xml.apache.org/cocoon/index.html" label="Cocoon" />
<menu-item href="http://xml.apache.org/xang/index.html" label="Xang" />
<menu-item href="http://xml.apache.org/soap/index.html" label="SOAP" />
<menu-item href="http://xml.apache.org/batik/index.html" label="Batik" />
<menu-item href="http://xml.apache.org/crimson/index.html" label="Crimson" />
<menu-item href="http://xml.apache.org/axis/index.html" label="Axis" />
<menu-item href="http://xml.apache.org/security/index.html" label="XML Security" />
<menu-item href="http://xml.apache.org/xmlrpc/" label="XML-RPC"/>
<menu-item href="http://www.dbxml.org" label="Xindice" />
<menu-item href="http://axkit.org" label="AxKit" />
</menu>
<menu label="Resources">
<menu-item label="Downloads" href="http://xml.apache.org/dist/"/>
<menu-item label="Bug Database" href="http://nagoya.apache.org/bugzilla/"/>
<menu-item label="Gump" href="http://jakarta.apache.org/gump/"/>
</menu>
<menu label="Information">
<menu-item label="Get Involved" href="overview.html"/>
<menu-item label="Repositories" href="cvs.html"/>
<menu-item label="Mailing Lists" href="mail.html"/>
<menu-item label="Reference" href="library.html"/>
</menu>
<menu label="Community">
<menu-item label="Who We Are" href="whoweare.html"/>
<menu-item label="Credits" href="ack.html"/>
</menu>
<menu label="Resources">
<menu-item label="Legal Stuff" href="legal.html"/>
<menu-item label="Contact Info" href="contact.html"/>
</menu>
</book>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/communication.xml
Index: communication.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Communication</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<p>
The Project obtains its strength from the communication of its
members. In order for members to easily communicate with each other,
the Project has a variety of mailing lists. These lists, with the
exception of the announcement lists, are not moderated and anybody is
more than welcome to join them. However, you must be subscribed to
post to a list.
</p>
<p>
To reduce the bandwidth demands on everyone, mail should not contain
attachments. It is recommended that you place interesting material
(such as patches) either within the body of the message or provide a
URL for retrieval.
</p>
<p>
To join the mailing lists, see our <link href="mail.html">Mailing List</link>
page.
</p>
<p>
The Project's list fall into the following categories:
</p>
<section title="Announcement Lists">
<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">
<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">
<p>
Developer lists are for the developers of the project. On these
lists suggestions and comments for code changes are discussed and
action items are raised and voted on. For the developer community,
these lists are the very center of the project where all the
"action" is.
</p>
</section>
<section title="Commit Lists">
<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
can stay aware of changes to the repository.
</p>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/contact.xml
Index: contact.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Contact Info</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<p>
If you have questions or comments about this site, please send email to:
<jump href="mailto:webmaster@xml.apache.org">webmaster@xml.apache.org</jump>
</p>
<p>
The xml.apache.org project is an effort of the Apache Software Foundation. The
address for general ASF correspondence and licensing questions is:
<jump href="mailto:apache@apache.org">apache@apache.org</jump>
You can find more contact information for the Apache Software Foundation on the
contact page of the <jump href="http://www.apache.org/">main Apache site</jump>.
</p>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/cvs.xml
Index: cvs.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>CVS Repositories</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Web Access to the Repository">
<p>You can browse the xml.apache.org workspaces via the web.
</p>
<ul>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-axis">xml-axis</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-batik">xml-batik</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon">xml-cocoon</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon2">xml-cocoon2</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-commons">xml-commons</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-contrib">xml-contrib</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-crimson">xml-crimson</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-fop">xml-fop</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-forrest">xml-forrest</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-rpc">xml-rpc</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-site">xml-site</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-soap">xml-soap</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-stylebook">xml-stylebook</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xalan">xml-xalan</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xang">xml-xang</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xerces">xml-xerces</jump>
</li>
<li>
<jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-security">xml-security</jump>
</li>
</ul>
</section>
<section title="Download the Source">
<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">
<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
and anybody can use it. The second is not and you must have a login to the
development server. If you don't know what this means, join the mailing list and find
out.
</p>
<section title="AnonCVS">
<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):
</p>
<source>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic
login
password: anoncvs
cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic
checkout [module-name]</source>
<p>
Modules available for access are:
</p>
<ul>
<li>xml-axis</li>
<li>xml-batik</li>
<li>xml-cocoon</li>
<li>xml-cocoon2</li>
<li>xml-commons</li>
<li>xml-contrib (so-called "whiteboard" area)</li>
<li>xml-crimson</li>
<li>xml-fop</li>
<li>xml-forrest</li>
<li>xml-rpc</li>
<li>xml-site</li>
<li>xml-soap</li>
<li>xml-stylebook</li>
<li>xml-xalan</li>
<li>xml-xang</li>
<li>xml-xerces</li>
<li>xml-security</li>
</ul>
<p>
The Xerces2 project has been merged into the main trunk of
the xml-xerces module. The Xerces 1.x codebase has been
moved to a branch of the CVS module. In
order to extract the Xerces 1.x code, you must specify the
"xerces_j_1" branch using the "-r" option. For example, to
extract the Java sources for Xerces 1.x in a directory called
"xerces1", enter the following commands: (each "cvs" command
is entered on a single line)
</p>
<source>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic
login
password: anoncvs
cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic
checkout -d xerces1 -r xerces_j_1 xml-xerces</source>
</section>
</section>
<section title="Other Ways to Access the Source Code">
<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
how to use these tools with the Apache CVS tree,
see the <jump href="http://www.apache.org/info/how-to-mirror.html">Apache Mirroring Document</jump>.</p>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/decisions.xml
Index: decisions.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Decision Making</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Decision Making">
<p>
All <link href="roles.html">Developers</link> are encouraged to
participate in decisions, but the decision itself is made by those
that have <link href="roles.html">Committer</link> status in the Project.
In other words, the Project is a "Minimum Threshold Meritocracy".
</p>
<p>
Any Developer may vote on any issue or action item. However, the only
binding votes are those cast by a Committer. If the vote is about a
change to the source code or documentation and the primary author is a
Developer and not a Commiter, the primary author of what is being
changed may also cast a binding vote on that issue.
</p>
<p>
The act of voting carries certain obligations. Voting members are not
only stating their opinion, they are also agreeing to help do the
work.
</p>
<p>
Each vote can be made in one of three flavors:
</p>
<ul>
<li>
<em>+1</em> - "Yes," "Agree," or "the action should be performed."
On some issues this is only binding if the voter has tested the action
on their own system(s).</li>
<li>
<em>+/-0</em> - "Abstain," "no opinion". An abstention may have
detrimental effects if too many people abstain.</li>
<li>
<em>-1</em> - "No." On issues where consensus is required, this
vote counts as a <em>veto</em>. All vetos must contain an explanation
of why the veto is appropriate. Vetos with no explanation are void. No
veto can be overruled. If you disagree with the veto, you should lobby
the person who cast the veto. Voters intending to veto an action item
should make their opinions known to the group immediately so that the
problem can be remedied as early as possible.</li>
</ul>
<p>
An action requiring consensus approval must receive at least <em>3
binding +1</em> votes and no binding <em>vetos</em>. An action
requiring majority approval must receive at least <em>3 binding +1
votes</em> and <em>more +1</em> votes than -1 votes. All other action
items are considered to have lazy approval until somebody votes <em>-
1</em>, after which point they are decided by either consensus or
majority vote, depending on the type of action item.
</p>
</section>
<section title="Action Items">
<p>
All decisions revolve around "Action Items." Action Items consist of
the following:
</p>
<ul>
<li>Long Term Plans</li>
<li>Short Term Plans</li>
<li>Release Plan</li>
<li>Release Testing</li>
<li>Showstoppers</li>
<li>Product Changes</li>
</ul>
<section title="Long Term Plans">
<p>
Long term plans are simply announcements that group members are
working on particular issues related to the Project. These are not
voted on, but Developers who do not agree with a particular plan, or
think that an alternative plan would be better, are obligated to
inform the group of their feelings.
</p>
</section>
<section title="Short Term Plans">
<p>
Short term plans are announcements that a developer is working on a
particular set of documentation or code files with the implication
that other developers should avoid them or try to coordinate their
changes.
</p>
</section>
<section title="Release Plan">
<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
repository will be frozen to create a release, and other assorted
information to keep Developers from tripping over each other. Lazy
majority decides each issue in a release plan.
</p>
</section>
<section title="Release Testing">
<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">
<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
focus special attention on these problems. An issue becomes a
showstopper when it is listed as such in the status file and remains
so by lazy consensus.
</p>
</section>
<section title="Product Changes">
<p>
Changes to the products of the Project, including code and
documentation, will appear as action items in the status file. All
product changes to the currently active repository are subject to
lazy consensus.
</p>
</section>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/guidelines.xml
Index: guidelines.xml
===================================================================
<?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>
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,
and the procedures to follow for proposing and making changes to the
codebase of the Project.
</p><note>
Note that our sister project, jakarta.apache.org, is formulating
a number of other project-wide guidelines that the xml community may
wish to copy or modify. In Sept-2001 there are also a number of
discussions on the general@xml.apache.org and commons-dev@xml.apache.org
mailing lists about other cross-project guidelines that we hope will
standardize our projects and make developing and using them easier.
Stay tuned!
</note><p>
This is a living document. Changes can be made by the Project
Management Committee.
</p><ul><li><link href="roles.html">Roles and Responsibilities</link>
Defines the recognized roles in the project.</li><li><link href="communication.html">
Communication</link>
Defines how users and developers communicate.</li><li><link href="decisions.html">Decision Making</link>
Defines how action items are proposed and voted on.</li><li><link href="source.html">Source Repositories</link>
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>
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
from XML documents, we currently checkin source .xml files
of the documentation and then generate a static set of .html
files for most of this website.
</p><p>
Briefly: the entire xml.apache.org website is stored in CVS repositories.
Both the source .xml documents and the generated .html docs are checked in,
and the actual website itself is simply a checked-out copy of the repository.
</p><p>
While each subproject's individual areas may be managed separately
(by that subproject's committers) the top-level of the website
should be managed through the xml-site repository. Thus to change
any of the files at the root of http://xml.apache.org you should
first check out the xml-site repository from cvs.apache.org
</p><p>
(for updating the top-level docs)
<br/>Checkout the xml-site module (you only actually need a few subdirs; it's quite large)
<br/>Make updates to the .xml files in the xml-site/sources/website directory
<br/>Go to the xml-site/sources directory locally and run website.bat
<br/>Check that the .html structure in your local targets directory is built correctly
<br/>Checkin both your updated sources/ and targets/ trees as needed
<br/>Login to xml.apache.org and cd to /www/xml.apache.org
<br/>Do an update of directories there as needed
</p></section></body></document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/index.xml
Index: index.xml
===================================================================
<?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>
<section title="Welcome to the Apache XML Project">
<p>
The goals of the <em>Apache XML Project</em> are:
</p>
<ul>
<li>
to provide commercial-quality standards-based XML solutions that are
developed in an open and cooperative fashion,
</li>
<li>
to provide feedback to standards bodies (such as IETF and W3C) from an
implementation perspective, and
</li>
<li>
to be a focus for XML-related activities within Apache projects
</li>
</ul>
<p>
The <em>Apache XML Project</em> currently consists of the following sub-
projects, each focused on a different aspect of XML:
</p>
<ul>
<li>
<em>Xerces</em> - XML parsers in Java, C++ (with Perl and COM bindings)
</li>
<li>
<em>Xalan</em> - XSLT stylesheet processors, in Java and C++
</li>
<li>
<em>Cocoon</em> - XML-based web publishing, in Java
</li>
<li>
<em>AxKit</em> - XML-based web publishing, in mod_perl
</li>
<li>
<em>FOP</em> - XSL formatting objects, in Java
</li>
<li>
<em>Forrest</em> - XML/XSLT-based developers community website foundation, using Cocoon
</li>
<li>
<em>Xang</em> - Rapid development of dynamic server pages, in JavaScript
</li>
<li>
<em>SOAP</em> - Simple Object Access Protocol
</li>
<li>
<em>Batik</em> - A Java based toolkit for Scalable Vector Graphics (SVG)
</li>
<li>
<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)">
<p>
Xerces (named after the Xerces Blue butterfly) provides world-class
XML parsing and generation. Fully-validating parsers are available for
both Java and C++, implementing the W3C XML and DOM (Level 1 and 2)
standards, as well as the de facto SAX (version 2) standard. The
parsers are highly modular and configurable. Initial support for XML
Schema (draft W3C standard) is also provided.
</p>
<p>
A Perl wrapper is provided for the C++ version of Xerces, which allows
access to a fully validating DOM XML parser from Perl. It also
provides for full access to Unicode strings, since Unicode is a key
part of the XML standard.
</p>
<p>
A COM wrapper (also for Xerces-C) provides compatibility with the Microsoft MSXML parser.
</p>
</section>
<section title="Xalan: XSL stylesheet processors in Java & C++">
<p>
Xalan (named after a rare musical instrument) provides high-performance
XSLT stylesheet processing. Xalan fully implements the W3C XSLT and XPath
recommendations. The stylesheet processor is feature-rich and robust. The
XPath Processor is useable as a stand-alone unit. Xalan uses the Bean
Scripting Framework (BSF) to implement Java or script extensions, features
multiple document output extensions, and we are working on data-binding
extensions for SQL/JDBC and other data providers.
</p>
<p>
Xalan is currently available in Java, and available in Alpha form for C++.
</p>
</section>
<section title="Cocoon: XML-based web publishing">
<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">
<p>
AxKit brings the power of XML web publishing and dynamic
XML based applications to the Apache web server using the
mod_perl framework and the Apache C API to combine the power
of XML with the performance of a native Apache solution.
</p>
</section>
<section title="FOP: XSL Formatting Object processor in Java">
<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
tree and then turns it into a PDF document. The formatting object
tree, can be in the form of an XML document (output by an XSLT
engine like Xalan) or can be passed in memory as a DOM Document or (in
the case of Xalan) SAX events.
</p>
</section>
<section title="Forrest: Developer Community Portal">
<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">
<p>
Apache Xang lets you quickly build data-driven, cross-platform Web
applications that integrate disparate data sources. The Xang architecture
cleanly separates data, logic and presentation. It is based on open
industry standards such as HTTP, XML, XSL, DOM and ECMAScript (JavaScript).
</p>
</section>
<section title="SOAP: Simple Object Access Protocol">
<p>
The Apache Soap project is an implementation of the draft W3C
protocol by the same name. It is based on, and supersedes, the
IBM SOAP4J implementation.
</p>
<p>
From the draft W3C specification:
SOAP is a lightweight protocol for exchange of information in a
decentralized, distributed environment. It is an XML based protocol
that consists of three parts: an envelope that defines a framework
for describing what is in a message and how to process it, a set of
encoding rules for expressing instances of application-defined
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">
<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">
<p>
The <em>xml.apache.org</em> Project is composed of developers from all
around the world, both individuals and engineers from major corporations.
All interested developers are welcome to join and participate. Learn more
about <link href="overview.html">how to get involved</link>.
</p>
</section>
</body></document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/legal.xml
Index: legal.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Legal Stuff</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<p>
All material on this website is Copyright (c) 1999 The Apache Software Foundation.
All Rights Reserved.
</p>
<p>
For details look at the file:
<jump href="http://xml.apache.org/dist/LICENSE.txt">License.txt</jump>.
</p>
<p>
IBM is a trademark of International Business Systems, Inc. Lotus is a trademark of
Lotus Development Corporation. Sun and Sun Microsystems are trademarks or
registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in
the United States and other countries, exclusively licensed through X/Open
Company, Ltd. Windows, WindowsNT, and Win32 are registered trademarks of
Microsoft Corp. All other product names mentioned herein and throughout the
entire web site are trademarks of their respective owners.
</p>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/library.xml
Index: library.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Reference Library</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Reference Library">
<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
foundation of knowledge is required to effectively participate in this virtual
community. The following is a list of documents that we have found helpful for us
and may be helpful to you:
</p>
</section>
<section title="Technical Resources">
<p>
These resources are required reading for anybody contributing source code to the
project.
</p>
<ul>
<li>
<jump href="http://java.sun.com/docs/books/jls/index.html">The Java Language Specification</jump>
<br/>
Written by the creators of the Java Programming Language, this online book is
considered by many to be the bible for programming in Java. A must read.
</li>
<li>
<jump href="http://java.sun.com/products/jdk/javadoc/index.html">Javadoc</jump>
<br/>
Javadoc is the automatic software documentation generator used by Java since it
was first released. All Java code written for this project must be documented using
Javadoc conventions.
</li>
<li>
<jump href="http://www.cvshome.org/docs/blandy.html">Introduction to CVS</jump>
<br/>
Written by Jim Blandy, this brief introduction gives a first look into CVS. If you
have never used CVS before, you'll want to start here.
</li>
<li>
<jump href="http://www.cvshome.org/docs/cederqvist.html">Version Management with CVS</jump>
<br/>
Written by Per Cederqvist at al, this is the main manual for CVS. It provides details
on all documented CVS features.
</li>
</ul>
</section>
<section title="Source Code Philosophy Resources">
<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
may not agree with all of the points of these articles, but an understanding of them
will help in communicating with everyone on the project.
</p>
<ul>
<li>
<jump href="http://www.tuxedo.org/%7Eesr/writings/cathedral-bazaar/index.html">The Cathedral and the Bazaar</jump>
<br/>
Written by Eric S. Raymond, this is a must read for anyone willing to join or
support a volunteer project.
</li>
<li>
<jump href="http://www.tuxedo.org/%7Eesr/writings/homesteading/index.html">Homesteading the Noosphere</jump>
<br/>
Written by Eric S. Raymond, this is a sequel to "The Cathedral and the Bazaar". It
details the property and ownership customs of the open-source culture. This
analysis has larg implications for anyone interested in organizing large-scale
intellectual collaborations such as this project.
</li>
</ul>
</section>
<section title="XML Resources">
<p>A wide variety of XML-oriented resources are out on the net today.
Just a few that we have found useful include:
</p>
<ul>
<li>
<jump href="http://xml.org/">xml.org</jump>
<br/>
An industry-sponsored portal with links, news, and a wide variety of resources
</li>
<li>
<jump href="http://xmlhack.com/">xmlhack </jump>
<br/>
Find all the latest XML-related news stories here
</li>
<li>
<jump href="http://www.oasis-open.org/cover/">The XML Cover pages</jump>
<br/>
Robin Cover's long-standing overview of all things XML
</li>
<li>
<jump href="http://www.xmlsoftware.com/">XMLSOFTWARE</jump>
<br/>
A listing of various XML-related tools with brief reviews
</li>
</ul>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/mail.xml
Index: mail.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Mailing Lists</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<p>
Every volunteer project obtains its strength from the people involved in
it. Mailing lists provide a simple and effective communication
mechanism.
</p>
<p>
You are welcome to join any of these mailing lists (or all of them if
you wish). You can choose to lurk, or actively participate. It's up to
you. Before you join these lists, you should look over the resources in
the Reference Library section. As with any mailing list, you should
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">
<p>
Archives are generally named after the project they're about (duh!)
with a suffix that denotes the subjects covered. Common suffixes are:
<br/>
<code>*-dev</code> Developer list - for technical questions about
the product, code patches, bug submissions about advanced functionality, etc.
<br/>
<code>*-user, *-users</code> Users list - for general usage questions
about the product from an end-users perspective
<br/>
<code>*-cvs</code> CVS commit list - this is a read-only list that
sends out email with details of all checkins to that project's CVS repository
</p>
<p>
The ezmlm mailing list controller accepts commands by sending emails
to <code>listname-command</code>, generally like the following:
<br/>
<code>*-subscribe</code> Subscribe your current email address to the list
<br/>
<code>*-unsubscribe</code> UnSubscribe your *current* email address from the list
<br/>
<code>*-help</code> get Help on mailing list commands
</p>
</section>
<section title="Public archives">
<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>,
which are organized by month and include search features for both subjects
and message text. Many lists are also archived by other large
mailing list archive sites as well.
</p>
<p>
Many mailing lists are also archived at
<jump href="http://archive.covalent.net/">http://archive.covalent.net/</jump>
</p>
</section>
<section title="The xml.apache.org Announcement List">
<p>
<em>Low Traffic</em>
<jump href="mailto:announcements-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:announcements-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
If you want to keep informed about what we are up to but you do not
have the time to read all the messages on the other mailing lists,
subscribe to this moderated list to get general announcements. An
<jump href="http://xml-archive.webweaving.org/xml-archive-announcements">archive</jump>
is kept.
</p>
</section>
<section title="The xml.apache.org General Discussion List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:general-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:general-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This list is for issues that span across all xml.apache.org projects,
whether technical or organizational.
Discussions about specific code bases should be redirected to one of
the codebase-specific lists below. An
<jump href="http://xml-archive.webweaving.org/xml-archive-general">archive</jump>
is kept.
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)">
<p>
<em>Low Traffic - Obsolete</em>
mailto:xerces-dev-subscribe@xml.apache.org
mailto:xerces-dev-unsubscribe@xml.apache.org
</p>
<p>
<em>This list has now been split into separate lists for Java, C++, and Perl parser efforts.
Everybody should switch to one of the specific mailing lists below.</em>
</p>
</section>
<section title="The Xerces-J User List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:xerces-j-user-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-j-user-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
</p>
<p>
This is the list where users of the Xerces-J Java XML parser
can meet and discuss questions, raise issues, etc.
Archives of the
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-j-user/">Xerces-J Users</jump>
mailing list are kept.
</p>
</section>
<section title="The Xerces-J Developer List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:xerces-j-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-j-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
<em>CVS Commit (Xerces-J/C/P)</em>
<jump href="mailto:xerces-cvs-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of the Xerces-J Java XML
parser meet and discuss issues, code changes/additions, etc.
Archives of the
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-j-dev/">Xerces-J developers</jump>
and
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-cvs">Xerces-* commit</jump>
mailing lists are kept.
</p>
</section>
<section title="The Xerces-C Developer List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:xerces-c-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-c-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
<em>CVS Commit (Xerces-J/C/P)</em>
<jump href="mailto:xerces-cvs-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of the Xerces-C C++ XML
parser meet and discuss issues, code changes/additions, etc. This list currently
also discusses the COM bindings to the Xerces-C parser as well. The Perl
binding now has a separate mailing list (see below).
Archives of the
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-c-dev/">Xerces-C developers</jump>
and
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-cvs">Xerces-* commit</jump>
mailing lists are kept.
</p>
</section>
<section title="The Xerces-P Developer List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:xerces-p-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-p-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
<em>CVS Commit (Xerces-J/C/P)</em>
<jump href="mailto:xerces-cvs-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xerces-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of the Xerces-P perl binding for XML
parsing meet and discuss issues, code changes/additions, etc.
Archives of the
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-p-dev/">Xerces-P developers</jump>
and
<jump href="http://xml-archive.webweaving.org/xml-archive-xerces-cvs">Xerces-* commit</jump>
mailing lists are kept.
</p>
</section>
<section title="The Xalan-J Users List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:xalan-j-users-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xalan-j-users-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where all users can discuss general usage questions
about the <jump href="xalan-j/">java version of Xalan</jump>. For detailed technical questions,
please see the developer list below.
<br/>
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">
<p>
<em>Low Traffic</em>
<jump href="mailto:xalan-c-users-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xalan-c-users-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where all users can discuss general usage questions
about the <jump href="xalan-c/">C++ version of Xalan</jump>. For detailed technical questions,
please see the developer list below.
<br/>
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">
<p>
<em>High Traffic</em>
<jump href="mailto:xalan-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xalan-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
<em>CVS Commit (read-only)</em>
<jump href="mailto:xalan-cvs-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xalan-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of the Xalan XSLT
stylesheet processor meet and discuss issues, code changes/additions,
etc. Subscribers to the -cvs list get notices of each and every code
change, build results, testing notices, etc. Both of these lists
pertain to both the Java and C++ versions
<br/>
Archives are kept at <jump href="http://marc.theaimsgroup.com/?l=xalan-dev">http://marc.theaimsgroup.com/?l=xalan-dev</jump>
and at <jump href="http://marc.theaimsgroup.com/?l=xalan-cvs">http://marc.theaimsgroup.com/?l=xalan-cvs</jump>
<br/>
For user-oriented questions, please see the appropriate User list above.
</p>
</section>
<section title="The Cocoon Users List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:cocoon-users-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:cocoon-users-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where active users of Cocoon meet and discuss issues,
installation problems and what not. An
<jump href="http://xml-archive.webweaving.org/xml-archive-cocoon-users">archive</jump>
is kept.
</p>
</section>
<section title="The Cocoon Developer List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:cocoon-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:cocoon-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
<em>CVS Commit</em>
<jump href="mailto:cocoon-cvs-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:cocoon-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of Cocoon meet and
discuss issues, code changes/additions, etc. Subscribers to the CVS
commit list also get notices of each and every code change, build
results, testing notices, etc. You are strongly adviced to subcribe to
both lists if you want to follow what is happening. An archive of the
<jump href="http://xml-archive.webweaving.org/xml-archive-cocoon">developers</jump>
and
<jump href="http://xml-archive.webweaving.org/xml-archive-cocoon-cvs">commit</jump>
mailing list is kept.
</p>
</section>
<section title="The FOP User List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:fop-user-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:fop-user-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where users of FOP meet and discuss issues,
installation problems and more. An archive is available at
<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">
<p>
<em>Medium Traffic</em>
<jump href="mailto:forrest-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:forrest-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<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">
<p>
<em>Medium Traffic</em>
<jump href="mailto:fop-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:fop-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
<br/>
<em>CVS Commit</em>
<jump href="mailto:fop-cvs-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:fop-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of FOP XSL-FO
Formatting Objects processor meet and discuss issues, code
changes/additions, etc. Subscribers to the CVS commit list also get
notices of each and every code change, build results, testing notices,
etc. You are strongly adviced to subcribe to both lists if you want
to follow what is happening. An archive of the
<jump href="http://xml-archive.webweaving.org/xml-archive-fop">developers</jump>
and
<jump href="http://xml-archive.webweaving.org/xml-archive-fop-cvs">commit</jump>
mailing list is kept.
</p>
</section>
<section title="The Xang Developer List">
<p>
<em>Low Traffic</em>
<jump href="mailto:xang-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:xang-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of Xang meet and
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>
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>
</section>
<section title="The Soap Users List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:soap-user-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:soap-user-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where active users of Soap meet and discuss issues,
installation problems and what not.
</p>
</section>
<section title="The Soap Developer List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:soap-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:soap-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list where participating developers of Soap meet and
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>
</section>
<section title="The Batik Users List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:batik-users-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:batik-users-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
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>
</section>
<section title="The Batik Developers List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:batik-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:batik-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list for everyone interested and involved with the active
development of Batik.
</p>
</section>
<section title="The XML Security Developers List">
<p>
<em>Medium Traffic</em>
<jump href="mailto:security-dev-subscribe@xml.apache.org">Subscribe</jump>
<jump href="mailto:security-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
</p>
<p>
This is the list for everyone interested and involved with the active
development of XML Security.
</p>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/management.xml
Index: management.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Project Management</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<p>
The Project Management Committee (PMC) was formed by the Apache Board
in September 1999. This Committee consists of X founding members, one
of whom is the founding Chairman. The term of the Chairman is one
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">
<p>
The PMC is responsible for the strategic direction and success of
the <em>xml.apache.org</em> Project. This governing body is expected
to ensure the project's welfare and guide its overall direction. The
PMC may not necessarily participate in the day-to-day coding but is
involved in the overall development plans, the alleviation of any
bottlenecks, the resolution of conflicts, and the overall technical
success of the project.
</p>
<p>
The PMC is answerable to the Apache Board with its Chairman serving
as primary liaison.
</p>
</section>
<section title="Meetings">
<p>
The PMC meets monthly with a majority of its members to discuss
issues, determine strategic direction, and forward progress. These
meetings may take place online, via teleconference, or via other
means deemed effective by the PMC. The PMC has an annual meeting at
which time a new Chairman is elected. The old Chairman maintains
membership status.
</p>
</section>
<section title="Membership">
<p>
PMC members may resign at any time. The Chairman may resign as
Chairman at any time without resigning membership to the PMC. The
Chairman or any member may be removed from the PMC by a 3/4 vote of
the PMC.
</p>
</section>
<p>
New members may be elected to the PMC. In order to be elected, a
person must have served as a Committer and be nominated by a PMC
Member. Once nominated, all of the PMC will vote and those receiving a
3/4 positive vote will become a member.
</p>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/mission.xml
Index: mission.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Project Mission</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Mission/Charter">
<p>
<em>The most current copy of our charter can always be found
at </em>
<jump href="http://cvs.apache.org/viewcvs.cgi/xml-admin/charter.txt">http://cvs.apache.org/viewcvs.cgi/xml-admin/charter.txt</jump>;
however a recent copy is included herein.</p>
<source>xml.apache.org is a collaborative software development project
dedicated to providing robust, full-featured, commercial-quality, and
freely available XML support on a wide variety of platforms. This
project is managed in cooperation with various individuals worldwide
(both independent and company-affiliated experts), who use the
Internet to communicate, plan, and develop XML software and related
documentation.
This charter briefly describes the mission, history, organization, and
processes of the project.
MISSION
=======
xml.apache.org exists to promote the use of XML. We view XML as a
compelling paradigm that structures data as information, thereby
facilitating the exchange, transformation, and presentation of
knowledge. The ability to transform raw data into usable information
has great potential to improve the functionality and use of
information systems. We intend to build freely available XML
processing components in order to engender such improvements.
xml.apache.org defines a set of components that exchange or deal with
XML information sets. These components plug into each other using
standard APIs (formal, de facto, or proposed). The components must be
high performance, reliable, and easy to use. The components must be
part of an underlying architectural orchestration that will allow them
to work together without major negotiations or breakage.
We believe that the best way to define this XML information exchange
architecture is by having both individuals and corporations
collaborate on the best possible infrastructure, APIs, code, testing,
and release cycles. Components must be vendor neutral and usable as
core components for all.
In order to achieve a coherent architecture between xml.apache.org
components and other components and applications, standards (formal or
de facto) will be used as much as possible for both protocols and
APIs. We will also allow the innovation of new protocols, APIs, and
components in order to seed new concepts not yet defined by standards.
HISTORY
=======
This project was established under the direction of the newly-formed
Apache Software Foundation in August 1999 to facilitate joint
open-source development.
THE PROJECT MANAGEMENT COMMITTEE
================================
The xml.apache.org project is managed by a small, core group of
contributors known as the Project Management Committee [PMC]. The PMC
must have at least one officer from the Apache Board, who will be the
Chairperson and report to the Apache Board. See
http://www.apache.org/foundation/bylaws.html for reference.
The PMC has the following responsibilities:
1) Accepting new subproject proposals, formally submitting these
proposals for committer vote, and creating the subproject (see
SUBPROJECTS below).
2) Facilitating code or other donations by individuals or companies.
3) Resolving license issues and other legal issues.
4) Approving new committers.
5) Ensuring that administrative and infrastructure work is completed.
6) Facilitating relationships among projects.
7) Facilitating relationships between xml.apache.org and the external
world.
8) Overseeing xml.apache.org to ensure that the mission defined in
this document is being fulfilled.
9) Resolving conflicts within the project.
To become a member of the PMC, an individual must be nominated by a
contributor, unanimously approved by all PMC members, and approved by
a two-thirds majority of committers. In most cases, developers will
have actively contributed to development for at least six months
before being considered for membership on the PMC. The goal is to keep
the membership of the core group at four to seven people in order to
minimize the bureaucratic overhead required to keep the project
operational.
In the unlikely event that a member of the PMC becomes disruptive to
the process or ceases to contribute for an extended period, said
member may be removed by unanimous vote of remaining PMC members.
The PMC is responsible for maintaining and updating this
charter. Development must follow the process outlined below, so any
change to the development process necessitates a change to the
charter. Changes must be unanimously approved by all members of the
PMC. A contributor may challenge a change to the charter at any time
and ask for a vote of all committers, in which case a two-thirds
majority must approve the change.
SUBPROJECTS
===========
xml.apache.org is comprised of subprojects; a subproject is a
component whose scope is well defined. Each subproject has its own
set of developers.
A new subproject proposal is submitted to the PMC, accepted by majority
committer vote, and then subject to final approval by the PMC.
COMMITTERS
==========
Each subproject has a set of committers. Committers are developers who
have read/write access to the source code repository. New committers
are added when a developer is nominated by a committer and approved by
at least 50 percent of the committers for that subproject with no
opposing votes. In most cases, new committers will already be
participating in the development process by submitting suggestions
and/or fixes via the bug report page or mailing lists.
CONTRIBUTORS
============
Like all Apache projects, the XML project is a meritocracy -- the more
work you do, the more you are allowed to do. Occasional contributors
will be able to report bugs and participate in the mailing lists.
Specific changes to a product proposed for discussion or voting on the
appropriate development mailing list should be presented in the form
of input to the patch command. When sent to the mailing list, the
message should contain a subject beginning with [PATCH] and including
a distinctive one-line summary that corresponds to the action item for
that patch.
Use the diff -u command from the original software file(s) to the
modified software file(s) to create the patch. Patches should be
submitted against the latest CVS versions of the software to avoid
conflicts and ensure that you are not submitting a patch for a problem
that has already been resolved.
Developers who make regular and substantial contributions may become
committers as described above.
INFRASTRUCTURE
==============
The xml.apache.org project site must provide the following:
Bug Database -- This is a system for tracking bugs and feature
requests.
Subproject Source Repositories -- These are several CVS repositories
containing both the source code and documentation for the
subprojects. Each subproject will have a set of committers to its
repository.
Website -- An xml.apache.org website will contain information about
the xml.apache.org project, including documentation, downloads of
releases, and this charter. Each subproject will have its own website
with subproject information.
PMC Mailing List -- This list is for PMC business requiring
confidentiality, particularly when an individual or company requests
discretion. All other PMC business should be done on the general
mailing list.
General Mailing List -- This mailing list is open to the public. It is
intended for discussions that cross subprojects.
Subproject Mailing Lists -- Each subproject should have a devoted mailing
list. Many subprojects may wish to have both user and development
lists. The individual subprojects may decide on the exact structure of
their mailing lists.
LICENSING
=========
All contributions to the xml.apache.org project adhere to the "ASF
Source Code License." All further contributions must be made under the
same terms. All contributions must contain the following copyright
notice: [This changes now that the license is available]
Copyright (c) {date} {name of contributor} and others. All rights
reserved. This program and the accompanying materials are made
available under the terms of the ASF Source Code License, as found in
the file ASF.code.license.html that is included in this distribution.
THE DEVELOPMENT PROCESS
=======================
The development process is intentionally lightweight; like other
Apache projects, the committers decide which changes may be committed
to the repository. Three +1 ('yes' votes) with no -1 ('no' votes or
vetoes) are needed to approve a code change. For efficiency, some code
changes from some contributors (e.g. feature additions, bug fixes) may
be approved in advance, in which case they may be committed first and
changed as needed, with conflicts resolved by majority vote of the
committers.
SUBPROJECT REQUIREMENTS
=======================
Each subproject must have a set of requirements as well as an
up-to-date release plan and design document on its dedicated web page.
It must be possible for each subproject to plug into the Gump nightly
build system (see http://jakarta.apache.org/builds/gump). It is
recommended that each subproject have a smoke-test system that works at
least as a basic integration test.
RELATIONSHIP TO OTHER APACHE PROJECTS
=====================================
The xml.apache.org project should work closely with other Apache
projects, such as Jakarta and the Apache Server, to avoid redundancy
and achieve a coherent architecture among xml.apache.org and these
projects.</source>
</section>
<section title="Projects">
<p>
The <em>Apache XML Project</em> currently consists of a number of sub-
projects, each focused on a different aspect of XML:
</p>
<ul>
<li>
<em>Xerces</em> - XML parsers in Java, C++ (with Perl and COM bindings)
</li>
<li>
<em>Xalan</em> - XSLT stylesheet processors, in Java and C++
</li>
<li>
<em>Cocoon</em> - XML-based web publishing, in Java
</li>
<li>
<em>FOP</em> - XSL formatting objects, in Java
</li><li><em>Forrest</em> - XML/XSLT project community websites</li>
<li>
<em>Xang</em> - Rapid development of dynamic server pages, in JavaScript
</li>
<li>
<em>SOAP</em> - Simple Object Access Protocol
</li>
<li>
<em>Batik</em> - A Java based toolkit for Scalable Vector Graohics (SVG)
</li>
<li>
<em>Axis</em> - A Java based implementation of SOAP
</li>
<li>
<em>Commons</em> - A meta-project of common XML-oriented code
</li>
</ul>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/news.xml
Index: news.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>News and Status</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Current News">
<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)">
<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)">
<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)">
<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">
<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)">
<p>
A new subproject focusing on sharing common XML code and interfaces, etc.
was formed recently. For details, look in the xml-commons repository,
in the general@xml.apache.org mailing list, or the commons-dev@xml.apache.org
mailing list.
</p>
</section>
<section title="Xalan-J was nominated for an award! (Summer-01)">
<p>Dear Apache XML Project,<br/>
<br/>
Congratulations! JavaWorld has selected the Apache XML Project's Xalan-Java
1.2.2 as a finalist in the Best Java-XML Application category of our
Editors' Choice Awards. Established in 1997, the awards recognize those innovative companies,
organizations, and individuals committed to developing new Java tools and
technologies that drive the platform forward. More than 100 products and
technologies were nominated by vendors, readers, as well as JavaWorld
editors and writers. We'll publish the complete list of finalists in each
category by 5 p.m. PDT on Friday, May 4 (go to:
http://www.javaworld.com/jw-05-2001/jw-0504-finalists.html).
</p>
<p>
As a finalist, members of your product team will be invited to attend
JavaWorld's Editors' Choice Awards ceremony at the JavaOne Conference and
Expo from June 4-8 in San Francisco, where a winner in each category will
be announced.
</p>
<p>
Regards, Scott Plamondon<br/>
Senior Editor<br/>
JavaWorld<br/>
scott_plamondon@itworld.com<br/>
415-975-2651<br/>
</p>
</section>
<section title="Batik was nominated for an award! (Sep-01)">
<p>Some details were posted on<jump href="http://marc.theaimsgroup.com/?l=xml-apache-general&m=99973420212175&w=2">the general mailing list</jump>
</p>
</section>
</section>
<section title="Project Status">
<section title="Batik Status: Source Code and Binaries Available">
<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>!
</p>
</section>
<section title="Xang - Source code for XPages from Datachannel released">
<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">
<p>
Crimson, the code name of the XML Parser Project X from Sun 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>
<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">
<p>
Xerces XML parsers in Java, C++, Perl, and COM are currently available in
source code and binary form. Check out the
<jump href="http://xml.apache.org/dist/">download pages</jump> for binaries
and source!
</p>
<p>The current production release is Xerces-J 1.4.3 (Sep-01).
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">
<p>
Xalan XSLT stylesheet processor in Java is currently available in
source code and binary form. Check out the
<jump href="http://xml.apache.org/dist/">download pages</jump> for binaries and
source!
</p>
</section>
<section title="Cocoon Status: Source Code and Binaries Available">
<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">
<p>
FOP, the XSL:FO formatting objects processor in Java, is currently available in
source code and binary form. Check out the
<jump href="http://xml.apache.org/dist/">download pages</jump> for binaries and
source!
</p>
</section>
</section>
<section title="Past News">
<ul>
<li>
Apache forms xml.apache.org --
<jump href="http://xml.apache.org/pr/0001.txt">PRESS RELEASE</jump>
</li>
<li>
CNet Article on xml.apache.org --
<jump href="http://news.cnet.com/news/0-1003-200-1431504.html?tag=st.ne.1002.thed.1003-200-1431504">ARTICLE</jump>
</li>
<li>
SlashDOT comments on xml.apache.org --
<jump href="http://www.slashdot.org/index.pl?section=apache">COMMENTS</jump>
</li>
<li>
The Batik announcement --
<jump href="#N/A">PRESS RELEASE</jump>
<!--must fix this--></li>
</ul>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/overview.xml
Index: overview.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Get Involved!</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<p>
Every volunteer project obtains its strength from the people involved in
it. We invite you to participate as much or as little as you choose. The
roles and responsibilities that people can assume in the project are based
on merit. Everybody's input matters!
</p>
<p>
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">
<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
evolve.
</p>
<ul>
<li>
<link href="mail.html">Mailing lists</link>
</li>
<li>
<jump href="http://xml.apache.org/dist/">Download binary builds</jump>
</li>
<li>
<jump href="http://nagoya.apache.org/bugzilla/">Report bugs/Request additional features</jump>
</li>
</ul>
</section>
<section title="Contribute Code or Documentation Patches">
<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
addition to the ones above) to get you started:
</p>
<ul>
<li>
<link href="guidelines.html">Read Guidelines</link>
</li>
<li>
<link href="library.html">Review Reference Library</link>
</li>
<li>
<jump href="http://xml.apache.org/dist/">Download the source code</jump>
</li>
<li>
<link href="cvs.html">
Access the CVS repository</link>
</li>
</ul>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/roles.xml
Index: roles.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Roles and Responsibilities</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Roles and Responsibilities">
<p>
The roles and responsibilities that people can assume in the project
are based on merit. Everybody can help no matter what their role.
Those who have been long term or valuable contributors to the project
obtain the right to vote and commit directly to the source repository.
</p>
</section>
<section title="Users">
<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,
reporting bugs, making feature requests, and such. This is by far
the most important category of people as, without users, there is no
reason for the Project.
</p>
<p>
When a user starts to contribute code or documentation patches, they
become a developer.
</p>
</section>
<section title="Developers">
<p>
Developers are the people who write code or documentation patches or
contribute positively to the project in other ways. A developer's
contribution is always recognized. In source code, all developers
who contribute to a source file may add their name to the list of
authors for that file.
</p>
</section>
<section title="Committers">
<p>
Developers who give frequent and valuable contributions to a
subproject of the Project can have their status promoted to that of
a "Committer" for that subproject. A Committer has write access to
the source code repository and gains voting rights allowing them to
affect the future of the subproject.
</p>
<p>
In order for a Developer to become a Committer, another Committer
can nominate that Developer or the Developer can ask for it. Once a
Developer is nominated, all of the Committers for a subproject will
vote. If there are at least 3 positive votes and no negative votes,
the Developer is converted into a Committer and given write access
to the source code repository for that subproject.
</p>
<p>
At times, Committers may go inactive for a variety of reasons. A
Committer that has been inactive for 6 months or more may lose his
or her status as a Committer.
</p>
<p>
A list of our current Committers can be found in our
<link href="whoweare.html">Project Credits</link>.
</p>
</section>
<section title="Project Management Committee (PMC)">
<p>
Committers who frequently participate with valuable contributions
may have their status promoted to that of a "Project Management
Committee Member". This committee is the official managing body of
the xml.apache.org Project and is responsible for setting overall
project direction. In order to become a Member, someone on the PMC
must nominate the Committer. The individual may then be approved
with a 3/4 majority of the PMC.
</p>
<p>
To view the Project Management Committee bylaws,
<link href="management.html">click here</link>.
</p>
<p>
A list of our current PMC Members can be found in our
<link href="whoweare.html">Project Credits</link>.
</p>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/source.xml
Index: source.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Source Repositories</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Source Repositories">
<p>
The Project's codebase is maintained in shared information
repositories using CVS on the xml.apache.org machine. Only Committers
have write access to these repositories. Everyone has read access via
anonymous CVS.
</p>
<p>
All Java Language source code in the repository must be written in
conformance to the
<jump href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code
Conventions for the Java Programming Language</jump> as published by
Sun.
</p>
</section>
<section title="License">
<p>
All source code committed to the Project's repositories must be
covered by the <em>Apache License version 1.1</em>
or contain a copyright and license that allows
redistribution under the same conditions as the Apache License.
</p>
</section>
<section title="Status Files">
<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
plans for work within that repository. The status file includes
information about release plans, a summary of code changes committed
since the last release, a list of proposed changes that are under
discussion, brief notes about items that individual developers are
working on or want discussion about, and anything else that may be
useful to help the group track progress.
</p>
<p>
The active status files are automatically posted to the developer
mailing lists three times per week.
</p>
</section>
<section title="Branches">
<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">
<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
degree of confidence in the change.
</p>
<p>
Doubtful changes, new features, and large scale overhauls need to be
discussed before committing them into the repository. Any change that
affects the semantics of an existing API function, the size of the
program, configuration data formats, or other major areas must receive
consensus approval before being committed.
</p>
<p>
Related changes should be committed as a group, or very closely
together. Half complete projects should never be committed to the main
branch of a development repository. All code changes must be
successfully compiled on the developer's platform before being
committed.
</p>
<p>
The current source code tree for a subproject should be capable of
complete compilation at all times. However, it is sometimes impossible
for a developer on one platform to avoid breaking some other platform
when a change is committed. If it is anticipated that a given change
will break the build on some other platform, the committer must
indicate that in the commit message.
</p>
<p>
A committed change must be reversed if it is vetoed by one of the
voting members and the veto conditions cannot be immediately satisfied
by the equivalent of a "bug fix" commit. The veto must be rescinded
before the change can be included in any public release.
</p>
</section>
<section title="Patches">
<p>
When a specific change to a product is proposed for discussion or
voting on the appropriate development mailing list, it should be
presented in the form of input to the patch command. When sent to the
mailing list, the message should contain a Subject beginning with
[PATCH] and a distinctive one-line summary corresponding to the action
item for that patch.
</p>
<p>
The patch should be created by using the diff -u command from the
original software file(s) to the modified software file(s). For
example:
</p>
<p>
<code>diff -u Main.java.orig Main.java >> patchfile.txt</code>
</p>
<p>
or
</p>
<p>
<code>cvs diff -u Main.java >> patchfile.txt</code>
</p>
<p>
All patches necessary to address an action item should be
concatencated within a single patch message. If later modification to
the patch proves necessary, the entire new patch should be posted and
not just the difference between the two patches.
</p>
</section>
</body>
</document>
1.1 xml-forrest/src/documentation/content/xdocs/xml-site/whoweare.xml
Index: whoweare.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Who We Are</title>
<authors>
<person name="unknown" email="unknown"/>
</authors>
</header>
<body>
<section title="Who We Are">
<p>
The <em>xml.apache.org</em> project operates on a meritocracy: the more you do,
the more
responsibility you can obtain. This page lists all of the people who have gone
the
extra mile and are Committers or members of the Project Management Committee.
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">
<ul>
<li>Scott Boag
<jump href="mailto:scott_boag@lotus.com">scott_boag@lotus.com</jump>
</li>
<li>Ted Leung
<jump href="mailto:twl@apache.org">twl@apache.org</jump>
</li>
<li>Sam Ruby
<jump href="mailto:rubys@ibm.com">rubys@ibm.com</jump>
[<jump href="http://radio.weblogs.com/0101679/">WebLog</jump>]</li>
<li>Davanum Srinivas
<jump href="mailto:dims@apache.org">dims@apache.org</jump>
</li>
<li>Dirk-Willem Van Gulik
<jump href="mailto:dirkx@webweaving.org">dirkx@webweaving.org</jump>
</li>
</ul>
</section>
<section title="Committers">
<p>
Committers are people with write access to their project's CVS
repository. New Committers to each project are nominated by and
voted into a project by that project's current committers. For more
details on getting involved see the <link href="roles.html">roles</link>.
</p>
</section>
<section title="Advisors">
<ul>
<li>Brian Behlendorf<jump href="mailto:brian@behlendorf.com">brian@behlendorf.com</jump>
<br/>
Brian is a co-founder of the Apache html HTTP Server Project.
He is co-founder and CTO of <jump href="http://www.collab.net/">Collab.Net
</jump>.
</li>
</ul>
</section>
</body>
</document>