Bommels05/commons-xml
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
commons-xml/README.html

509 lines
24 KiB
HTML
Raw Blame History

<?xml version="1.0"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en">
<!-- Using XHTML in the README just for fun; the rest of the docs should be in stylebook or other formats -->
<!-- @author shane_curcuru@lotus.com -->
<!-- Copyright (c) 2001-2002 The Apache Software Foundation. All rights reserved. -->
<head>
<title>xml-commons README homepage</title>
<style>
body { font-family: verdana,arial,helvetica,sans-serif; font-size: 10px; }
form { margin: 0px; padding: 0px; border: 0px; }
ul { margin: 0px 5px 0px 25px; padding: 0px; }
li { margin: 2px 0px 2px 0px; }
table { border: 0px; width: 100%; }
img { border: 0px; }
a:link { color: #0F3660 }
a:visited { color: #880000 }
a:active { font-weight: bold }
a:hover { color: #880000; }
.path { font-size: 10px; background-color: #CFDCED; border-bottom-color: #4A6D8C; border-bottom-style: solid; border-bottom-width: 2px; padding: 2px; }
.path .current { font-weight: bold; }
.top { background-color: #294563; }
.top img { margin: 5px; }
.search { font-size: 13px; color: #ffffff; margin-right: 10px; padding: 10px 5px 3px 5px; background-color: #4A6D8C; }
.tabs { font-size: 12px; background-color: #294563; padding: 2px 7px 5px 7px; }
.tabs .tab { background-color: #CFDCED; padding: 4px 6px 4px 6px;}
.tabs .current { background-color: #FFFFFF; font-weight: bold; padding: 5px 6px 6px 6px; }
.copyright { text-align: center; font-size: 10px; background-color: #CFDCED; border-top-color: #4A6D8C; border-top-style: solid; border-top-width: 1px; padding: 2px; }
.category { width: 100%; margin-bottom: 5px; }
.category .label { font-weight: bold; font-size: 11px; background-color: #7099C5; color: #ffffff; }
.category .content { margin: 0px; }
.software { margin: 0px 0px 3px 0px; }
.software .name { font-weight: bold; font-size: 13px; }
.software .languages { color: #7099C5; font-size: 13px; }
.software .desc { font-size: 11px; }
.frame { width: 100%; margin-bottom: 10px; font-size: 11px; background-color: #f0f0ff; border: solid 1px #7099C5; }
.frame .label { background-color: #7099C5; color: #ffffff; }
.frame .content { margin: 3px; }
.news { margin-bottom: 10px; }
.news .title { font-size: 13px; font-weight: bold; }
.news .by { font-size: 9px; color: #7099C5; }
.news .by a { color: #7099C5; }
.news .text { margin: 5px 0px 0px 0px; }
.news img { float: left; margin: 5px 5px 5px 5px; border: 0px; width: 35px; height: 35px; }
</style>
</head>
<body alink="#ff0000" bgcolor="#ffffff" link="#0000ff" text="#000000" vlink="#0000aa" >
<div class="path">
<a href="http://www.apache.org/">www.apache.org</a>&nbsp;&gt;&nbsp;
<span class="current"><a href="http://xml.apache.org/">xml.apache.org</a></span>&nbsp;&gt;&nbsp; commons
</div>
<p><!-- spacer --></p>
<!-- Steal look and feel of Forrest 1.5 by copy & paste -->
<div class="category">
<div class="label"><a name="welcome">Welcome to xml-commons!</a></div>
<div class="content">
<h3>xml-commons is a new xml.apache.org subproject!</h3>
<p>xml-commons is focused on common code and guidelines for xml projects.
It's first focus will be to organize and have common packaging for the various externally-defined
standards code relating to XML - things like the DOM, SAX, and JAXP interfaces.</p>
<p>As the xml-commons community forms, we also hope to serve as a holding area
for other common xml-related utilities and code, and to help promulgate common
packaging, testing, documentation, and other guidelines across all
xml.apache.org subprojects.</p>
</span>
</div>
</div>
<div class="category"><div class="label"><a name="TOC">In this document:</a></div><div class="content">
<ul>
<li><a href="#guidelines">Guidelines</a></li>
<li><a href="#releases">Releases</a></li>
<li><a href="#external">DOM, SAX, and JAXP code</a></li>
<li><a href="#java">Apache-defined code: org.apache.env.Which</a></li>
<li><a href="#mailing">Mailing list</a></li>
<li><a href="#cvs">Get source code</a></li>
<li><a href="#proposal">xml-subproject-proposal-commons-v1.1</a></li>
<li><a href="#proposal-votes">xml-subproject-proposal-commons-v1.1-vote-count-26-Apr-01</a></li>
<li><a href="#info-about">Info About This Document</a></li>
</ul>
</div></div>
<div class="category"><div class="label"><a name="guidelines">Commons Guidelines</a></div><div class="content">
<p>As the community forms, we need to formalize these guidelines, especially to differentiate
'requirements' from suggested 'guidelines'.</p>
<p>Shane's starting proposals:
<br>xml-commons is an unusual project in several ways.
First, it encompasses two kinds of code: external and apache.
<br>Secondly,
xml-commons mainly focuses on providing code and services to other
xml.apache.org projects instead of shipping it's own 'standalone' project.
<br>Third, it will also tend to be more focused on smaller, interoperable modules of
code and a very high degree of stability.</p>
<p>In some ways, the forming of
xml-commons is the seed of a catalyst to improve cross-project coordination
throughout xml.apache.org. One potential goal is to get all xml.apache.org
projects to take their xml standards oriented code - like DOM, SAX and JAXP -
from specific marked builds of xml-commons, instead of each project
using different versions of these files.</p>
<p><b>External code:</b> xml-commons will serve as an Apache-controlled
copy of externally-defined standards-based files. This way, we can try
to manage common versions of these important xml standards-based files
and interfaces. Read more <a href="#external">here</a>.</p>
<p><b>Apache code:</b> xml-commons will serve as a shared repository for
common xml-oriented utilities or building blocks that several other
xml.apache.org projects wish to use. The first example is org.apache.env.Which,
and environment checking utility that scans your environment and reports common
versions of xml-related files. The next likely submission is an entity resolver
that could be plugged into any xml parsing, transforming, or processing
project. Read more <a href="#java">here</a>.</p>
<p>Directory tree (proposed)</p>
<pre>
xml-commons/
README.html - this file
build.xml - overall build file for top-level items
xdocs/ - top-level xml format docs about this project itself and our guidelines
(in whatever format xml.apache.org uses for site)
docs/ - (not checked in) html format docs created by 'build docs' from xdocs
java/ - root of all java-related files
external/ - src root of all source files in java that come from external sources
for example: the DOM, SAX, and JAXP files
org/xml/sax/*
org/w3c/dom/*
javax/xml/*
external/build.xml - Ant build file for all external sources
xdocs/ - xml format docs describing any java files, as needed
{name}.xml - Ant build file for Apache-defined subproject(s)
future: resolver.xml: for Norm Walsh's entity resolver submission, when done
src/ - root of Apache-defined Java code
src/org/apache/... etc
which.xml - Ant build file for org.apache.env.Which utility
c/ - root of all C/C++ related files
external/ - root of all externally-owned C/C++ sources
perl/ - root of all Perl related files
etc.
</pre>
<ul>
<li>We should consider adopting those guidelines from the <a href="http://jakarta.apache.org/commons/">jakarta-commons</a>
project that make sense for our xml projects - keeping in mind that both the kind of
projects we build are different than jakarta, and some of our goals are a
little bit different.</li>
<li>Dicsussion and buy-in should happen on the project mailing list
<b>before</b> checking in new modules.</li>
<li>New modules generally shouldn't go in until at least two separate
other projects express interest in using the module. I think this is an
important difference from jakarta-commons that makes sense in our world.
I.e. I'd rather not just throw something in because it seems like it might
be useful, I'd rather only put things in that we know will be shared among
multiple projects.</li>
<li>The xml-commons community should come up with guidelines for other
xml.apache.org subprojects to use the code that commons has. I.e. suggestions
and ways to package this code vis-a-vis the other project's code in a common way.</li>
<li>Other shared xml.apache.org guidelines? Like documentation format, testing techniques/policies, etc.</li>
</ul>
</div></div>
<div class="category"><div class="label"><a name="external">DOM, SAX, and JAXP code</a></div><div class="content">
<p>xml-commons primary goal is to provide Apache projects with a stable version of
XMl-related externally-defined standards-based code. This is mainly the various
interfaces that you use when programming XML from JAVA: DOM, SAX and JAXP for now.</p>
<p>This tree is rooted at xml-commons/java/external, and has a build.xml file.
Basic documentation from each external project is also checked in.</p>
<ul>
<li>Current (Jan-02) status:</li>
<li>DOM L2 - full set of interfaces (including HTML stuff) from w3c.org</li>
<li>SAX 2.0 from megginson.com, plus minor bugfixes (note that SAX
is currently maintained at <a href="http://sax.sourceforge.net/">http://sax.sourceforge.net/</a>,
we need to update and cross-check with them soon!)</li>
<li>JAXP 1.1.3-HEAD from Sun, with current bugfixes by edwingo@apache.org</li>
</ul>
<p>Issues Jan-02: our current SAX and JAXP code may not pass the current
J2EE CTS test suite, since we have bugfixes above what those CTS tests
mandate. If you don't know what that is, you don't care; otherwise ask
on commons-dev for an update.</p>
</div></div>
<div class="category"><div class="label"><a name="java">Apache-authored code: org.apache.env.Which, more?</a></div><div class="content">
<p>xml-commons' secondary goal is to provide a project space for small
XML-related utilities that are being used in <b>multiple</b> other xml.apache.org
projects. In an effort to simplify and reduce dependency headaches, we'll
probably accept new projects only fairly slowly (this is in contrast to
the much more open <a href="http://jakarta.apache.org/commons/">jakarta-commons</a> project).
In particular, code submitted here should probably have minimal dependencies:
possibly only depending on DOM/SAX/JAXP and Ant (for builds).</p>
<ul>
<li>Current (Jan-02) status:</li>
<li>org.apache.env.Which - a simple environment check utility for
xml-related items in your JVM's environment: see xml-commons/java/which.xml</li>
<li>(to be submitted) Norm Walsh's entity resolver utility</li>
<li>(to be voted in) Jeff Turner's DOCTYPE changer</li>
</ul>
</div></div>
<div class="category"><div class="label"><a name="releases">Where can I download releases?</a></div><div class="content">
<p>The xml-commons-1.0.b1 release 11-Jan-02 is available in our
<a href="http://xml.apache.org/dist/commons/">distribution directory</a> and includes the following code:
<ul>
<li>java/build/which.jar containing:</li>
<li>org.apache.env.Which - a simple environment check utility for
xml-related items in your JVM's environment: 1.0 funtionality working</li>
<li>java/external/build/xml-apis.jar containing:</li>
<li>DOM Level 2 including all base files and HTML and CSS DOMs; from <a href="http://www.w3.org/DOM/">w3c.org</a></li>
<li>JAXP code roughly equivalent to JAXP 1.1.3; for reference releases
from Sun, see <a href="http://java.sun.com/xml/">java.sun.com/xml</a></li>
<li>SAX 2.0-r2-prerelease and SAX2-ext-1.0; plus bugfixes to
org.xml.sax.helpers.ParserAdapter (make compile in JDK 1.1.x) and AttributesImpl (minor
removeAttribute bug); from megginson.com although SAX maintenance has
now moved to <a href="http://sax.sourceforge.net/">sax.sourceforge.net</a></li>
</ul>
</p>
<p>Future 'b' or beta releases leading up to a gold 1.0 release will
be discussed on our <a href="#mailing">mailing list</a>. Likely releases
might address points like:
<ul>
<li>Improvements or submissions to org.apache.env.Which</li>
<li>A new submission of an entity resolver from Norman Walsh</li>
<li>A specific version of backlevel JAXP 1.1 that will work with
Sun's J2EE CTS conformance tests, if enough people request it</li>
<li>Specific versions of SAX, if the xml.apache.org community
requests it and wants to update to a newer shipped release of SAX, perhaps
SAX 2R2pre3 or later</li>
</ul>
</p>
</div></div>
<div class="category"><div class="label"><a name="mailing">How can I find out more?</a></div><div class="content">
<p>We have a project mailing list setup - commons-dev@xml.apache.org</a>.
Ask your questions or bring your suggestions there, or to general@xml.apache.org.
<br><a href="mailto:commons-dev@xml.apache.org">Send an email to commons-dev</a>
<br><a href="mailto:commons-dev-subscribe@xml.apache.org">Subscribe to commons-dev</a>
<br><a href="mailto:commons-dev-unsubscribe@xml.apache.org">Unsubscribe from commons-dev</a>
</p>
</div></div>
<div class="category"><div class="label"><a name="cvs">Where can I get the code/CVS?</a></div><div class="content">
<p>The xml-commons repository is available thru normal and anonymous CVS, or through
this <a href="http://xml.apache.org/websrc/cvsweb.cgi/xml-commons/">nifty web interface</a>.</p>
<p>See <a href="http://xml.apache.org/cvs.html">xml.apache.org CVS overview</a>.</p>
</div></div>
<div class="category"><div class="label"><a name="proposal">xml-subproject-proposal-commons-v1.1</a></div><div class="content">
<pre>
List: xml-apache-general
Subject: [VOTE] Proposal: new xml-commons subproject for standards-based files
From: Shane_Curcuru@lotus.com
Date: 2001-04-17 16:08:07
I propose a new xml.apache.org/xml-commons subproject to fulfill the need
for a central repository for various XML standards-based files and common
tools.
COMMITTERS-PLEASE-VOTE! Although I'm not sure of the exact voting procedure
for creating whole new subprojects, I'm hoping to see a bunch of +1's to
start with; feel free to either reply-to or use the handy mini-xml ballot
below.
NON-COMMITTERS-PLEASE-DISCUSS! While votes from non-committers are not
binding your discussion and insights are very valuable!
Key: committer="your_apache_login" email="your@preferred.email.address"
Leave committer blank if you aren't; vote must be +1 | 0 | -1
Add comment(s) if you like on specific issues
ballot committer="" email=""
vote issue="xml-subproject-proposal-commons-v1.1" vote
=""comment/comment/vote
vote issue="xml-subproject-proposal-commons-v1.1-committers" vote
=""comment/comment/vote
/ballot
xml-subproject-proposal-commons-v1.1
Proposal: form a new xml.apache.org subproject called xml-commons to
fulfill the below needs.
(0) Rationale:
Many xml.apache.org projects use and ship with sets of similar
externally-defined standards-based code; differences in versioning and
configuration of this code often make developing and using our projects
more difficult. A common place for all xml.apache.org projects to get DOM,
SAX, JAXP, and other externally-defined code would be a fairly low-cost and
low-maintenance way to alleviate these difficulties. Having a subproject
and a community focused on cross-xml-subproject issues will also help drive
better cross-project coordination and tooling.
(0.1) Programming Languages: While the coding details of Java/C/Perl/etc
are obviously different, the core concept is the same: a central repository
for all xml.apache.org projects to share common interfaces and utilities.
We should start with xml-commons/java, xml-commons/c, and xml-commons/perl
since these languages are in current use in various xml.apache.org
subprojects today.
(1) Scope of this subproject:
(1.1) Common externally-defined standards:
This includes the packages: org.w3c.dom.**, org.xml.sax.**, and javax.xml.
** This is designed to essentially be an xml.apache.org-specific holding
place for commonly-used interfaces/headers that are created outside of
Apache. This subproject should provide guidelines and build scripts to aid
xml.apache.org groups to easily use these common files in a common manner
across all subprojects. This subproject should provide some basic
versioning abilities so that xml.apache.org projects temporarily using
new/beta/updated/proposed versions of these specs can continue to get their
code from this area.
(1.2) Common xml-oriented utilities:
We should also include additional utilities/common code in this subproject,
like current copies of bsf.jar, stylebook, servlet API classes, etc. This
could also include code that did originate in an Apache project, that we
wanted to centralize the use of: SystemIDResolver, XML Serializers, etc.
(1.3) General project starting guidelines for future directions/scope:
While the details of guidelines for this work should be finalized by the
community that forms it (along with input from the other xml.apache.org
projects who will be using this code), there are some basics to start with:
- Communicate status regularly with general@xml.apache.org and with other
subprojects
- Clearly document and checkin 'best practices' for usage of xml-commons
code in other subprojects
- Proactively work with other subprojects to implement and improve our
'best practices'
- Provide upgrade paths and help; deprecate (or equivalent) old API's
before removing, so other subprojects have ample time to upgrade.
- Test and document all non-standards-based code; provide tests/additional
documentation for standards-based code
(1.4) General guidelines for future directions/scope:
Note this is firstly a subproject to make life inside of xml.apache.org
easier, to enable us to more efficiently develop nifty XML projects. As we
gain experience in developing this subproject, an obvious future direction
for this community will be to work on a potential AXDK (Apache XML
Development Kit) that would be a meta-packaging-project composed out of
several xml projects together. The AXDK would be a way to make life for
end-users easier: a single package of various Apache XML tools that works
'out of the box'. (AXDK naming credit to kellyc I think?)
(1.5) Interaction with other subprojects
Additional guidelines can be drawn up on general@xml.apache.org for this
subproject, and then documented and checked in. These should include both
how other xml subprojects should use these resources in their development
cycles, as well as how all xml subprojects should package these resources
when creating public, shipped distributions (to avoid version conflicts,
etc.) This subproject's community, along with general@xml.apache.org, will
need to draw up guidelines for code within this subproject as well.
(2) Identify the initial source from which the subproject is to be
populated:
Standards-based sources would be obtained from the relevant owners/creators
and checked into the project repository. A basic build.xml file and apache
project usage guidelines would need to be created. Possible legal review
would be needed for licensed files (one solution might be to waive the
Apache license on these files). For common xml-oriented utilities, the
initial sources can be moved in from other xml.apache.org subprojects (cf.
potential org.apache.xml.utils.SystemIdResolver from xml-xalan).
(3) Identify the xml.apache.org resources to be created
(3.1) mailing list(s)
xml-commons-dev
(ed note: added xml-commons-cvs as well -Shane)
(3.2) CVS repositories
xml-commons
(3.3) Bugzilla
program: Commons
components: External Standards, Common XML Utils
xml-subproject-proposal-commons-v1.1-committers
A sub-issue that I'd like people to vote on separately for whichever of the
below option(s) they like best.
(4) Identify the initial set of committers
(4.a) [vote-multiple] kellyc, curcuru, rubys
(4.b) [vote-multiple] one committer from each xml.apache.org subproject
that wants to volunteer, plus at least one PMC member (for projects that
don't get someone volunteered)
(4.c) [vote-multiple] all current xml.apache.org committers
/xml-subproject-proposal-commons-v1.1-committers
/xml-subproject-proposal-commons-v1.1
(*) Important cross-reference:
http://jakarta.apache.org/commons/index.html
Jakarta is currently working on a similar, yet different, tool/util/common
code area. While we can steal a lot of their ideas, I think the needs of
xml.apache.org will be different than Jakarta, so we should make our own
community decision on how to do this. Many thanks to the nice format for a
proposal that I plagarized. 8-)
- Shane shane_curcuru@lotus.com curcuru@apache.org
</pre>
</div></div>
<div class="category"><div class="label"><a name="proposal-votes">xml-subproject-proposal-commons-v1.1-vote-count-26-Apr-01</a></div><div class="content">
<p>Below follows the votes cast to create this subproject</p>
<p>---- From open general@xml.apache.org mailing list through 3pm 26-Apr-01 ----
<br />Original proposal at: http://marc.theaimsgroup.com/?l=xml-apache-general&m=98752444702386&w=2
<br />---- 17 Total committer +1 votes, plus 13 +1's for 4.c (allow all xml committers) ----
</p>
<ul>
<li>+1 4.c Shane Curcuru curcuru@apache.org (my implicit vote with the proposal)</li>
<li>+1 and 4c Kelly Campbell camk@channelpoint.com</li>
<li>+1 4.c Arnaud Le Hors lehors@us.ibm.com</li>
<li>+1, and 4c Tinny Ng tng-xml@ca.ibm.com</li>
<li>+1, and 4c "Ted Leung" twleung@sauria.com</li>
<li>+1 (4.c) Elena Litani elena@apache.org</li>
<li>+1, 4.c Vincent Hardy vhardy@eng.sun.com</li>
<li>ballot committer="arved" email="asandstrom@accesswave.ca"
vote issue="xml-subproject-proposal-commons-v1.1" vote="+1"
comment/
/vote
vote issue="xml-subproject-proposal-commons-v1.1-committers"
vote="+1"
comment4.(c)/comment
/vote
/ballot
</li>
<li>+1 and 4c. Andy Clark andyc@apache.org</li>
<li>+1 4.c "Jeffrey Rodriguez" jeffreyr_97@hotmail.com</li>
<li>+1, I vote for the least restrictive option, 4.c. Edwin.Goei@sun.com</li>
<li>+1 for the proposal. +1 for 4.d - all current xml.apache.org and jakarta.apache.org :-) ( but I can settle for 4.c :-) cmanolache@yahoo.com</li>
<li>+1 for 4c Donald_Leslie@lotus.com</li>
<li>+1. Scott Sanders satan@totalsync.com (jakarta committer, don't know if he's an xml committer, but he volunteered to work on coordination with jakarta-commons)</li>
<li>+1, 4.c Thierry Kormann tkormann@sophia.inria.fr</li>
<li>+1 from me. Davanum Srinivas dims@yahoo.com</li>
<li>+1 Scott_Boag@lotus.com</li>
</ul>
<ul>
<li>---- Other comments and non-committer votes ----</li>
<li>ballot committer="" email="shugal@gmx.de"
vote issue="xml-subproject-proposal-commons-v1.1" vote="+1"
commentA good and necessary idea! I'd like to contribute here.
Also see below./comment
/vote
vote issue="xml-subproject-proposal-commons-v1.1-committers"
vote="4.b or 4.a"
commentI'm no committer, but I think we should get the
number of committers low at least a this initial stage. Everyone is
free to contribute code to one of the actual committers who will
check it into CVS if they think it's useful./comment
/vote
/ballot
</li>
<li>"Once the /xml-commons repository is set up, I volunteer to check in the
latest JAXP code into /xml-commons. Right now there are 3 different
projects with 3 different versions. It'd be nice to have just one." Edwin
Goei edwingo@sun.com
</li>
</ul>
<p>/xml-subproject-proposal-commons-v1.1-vote-count-26-Apr-01</p>
</div></div>
<div class="category"><div class="label"><a name="info-about">Info About This Document</a></div><div class="content">
<ul>
<li>Version: $Id$</li>
<li>Contributors:</li>
<li><a href="mailto:curcuru@apache.org">Shane Curcuru</a></li>
<li>This document is currently a hand-coded HTML file for reasons of simplicity; we plan to use whatever xml format the xml.apache.org website uses in the future.</li>
<li>This document is stored in the xml-commons CVS repository</li>
<li>Checked in: /home/cvs/xml-commons/README.html</li>
<li>Live on xml.apache.org site: http://xml.apache.org/commons/index.html</li>
<li><a href="http://xml.apache.org/websrc/cvsweb.cgi/xml-commons/README.html">View with CVSWEB</a></li>
</ul>
</div></div>
<br><br>
<div class="copyright">
Copyright &copy; 1999-2001 <a href="http://www.apache.org/">Apache Software Foundation</a>. All Rights Reserved.
<br/>
For more information about licensing please see README.txt
</div>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink