You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

508 lines
47 KiB

  1. <HTML><HEAD><META content="text/html; charset=utf8" http-equiv="Content-Type"><SCRIPT language="JavaScript" src="resources/script.js" type="text/javascript"></SCRIPT><TITLE>Xerces-C++ XML Parser</TITLE></HEAD><BODY alink="#ff0000" bgcolor="#ffffff" leftmargin="4" link="#0000ff" marginheight="4" marginwidth="4" text="#000000" topmargin="4" vlink="#0000aa"><TABLE border="0" cellpadding="0" cellspacing="0" width="620"><TR><TD align="left" height="60" rowspan="3" valign="top" width="135"><IMG border="0" height="60" hspace="0" src="resources/logo.gif" vspace="0" width="135"></TD><TD align="left" colspan="4" height="5" valign="top" width="456"><IMG border="0" height="5" hspace="0" src="resources/line.gif" vspace="0" width="456"></TD><TD align="left" height="60" rowspan="3" valign="top" width="29"><IMG border="0" height="60" hspace="0" src="resources/right.gif" vspace="0" width="29"></TD></TR><TR><TD align="left" bgcolor="#0086b2" colspan="4" height="35" valign="top" width="456"><IMG alt="" border="0" height="35" hspace="0" src="graphics/charter-header.jpg" vspace="0" width="456"></TD></TR><TR><TD align="left" height="20" valign="top" width="168"><IMG border="0" height="20" hspace="0" src="resources/bottom.gif" vspace="0" width="168"></TD><TD align="left" height="20" valign="top" width="96"><A href="http://xml.apache.org/" onMouseOut="rolloverOff('xml');" onMouseOver="rolloverOn('xml');" target="new"><IMG alt="http://xml.apache.org/" border="0" height="20" hspace="0" name="xml" onLoad="rolloverLoad('xml','resources/button-xml-hi.gif','resources/button-xml-lo.gif');" src="resources/button-xml-lo.gif" vspace="0" width="96"></A></TD><TD align="left" height="20" valign="top" width="96"><A href="http://www.apache.org/" onMouseOut="rolloverOff('asf');" onMouseOver="rolloverOn('asf');" target="new"><IMG alt="http://www.apache.org/" border="0" height="20" hspace="0" name="asf" onLoad="rolloverLoad('asf','resources/button-asf-hi.gif','resources/button-asf-lo.gif');" src="resources/button-asf-lo.gif" vspace="0" width="96"></A></TD><TD align="left" height="20" valign="top" width="96"><A href="http://www.w3.org/" onMouseOut="rolloverOff('w3c');" onMouseOver="rolloverOn('w3c');" target="new"><IMG alt="http://www.w3.org/" border="0" height="20" hspace="0" name="w3c" onLoad="rolloverLoad('w3c','resources/button-w3c-hi.gif','resources/button-w3c-lo.gif');" src="resources/button-w3c-lo.gif" vspace="0" width="96"></A></TD></TR></TABLE><TABLE border="0" cellpadding="0" cellspacing="0" width="620"><TR><TD align="left" valign="top" width="120"><IMG border="0" height="14" hspace="0" src="resources/join.gif" vspace="0" width="120"><BR>
  2. <A href="../index.html" onMouseOut="rolloverOff('side-ext-2');" onMouseOver="rolloverOn('side-ext-2');"><IMG alt="Xerces Project" border="0" height="12" hspace="0" name="side-ext-2" onLoad="rolloverLoad('side-ext-2','graphics/ext-2-label-2.jpg','graphics/ext-2-label-3.jpg');" src="graphics/ext-2-label-3.jpg" vspace="0" width="120"></A><BR>
  3. <IMG border="0" height="6" hspace="0" src="resources/separator.gif" vspace="0" width="120"><BR>
  4. <A href="index.html" onMouseOut="rolloverOff('side-index');" onMouseOver="rolloverOn('side-index');"><IMG alt="Overview" border="0" height="12" hspace="0" name="side-index" onLoad="rolloverLoad('side-index','graphics/index-label-2.jpg','graphics/index-label-3.jpg');" src="graphics/index-label-3.jpg" vspace="0" width="120"></A><BR>
  5. <IMG alt="Charter" border="0" height="12" hspace="0" src="graphics/charter-label-1.jpg" vspace="0" width="120"><BR>
  6. <A href="releases.html" onMouseOut="rolloverOff('side-releases');" onMouseOver="rolloverOn('side-releases');"><IMG alt="Release Info" border="0" height="12" hspace="0" name="side-releases" onLoad="rolloverLoad('side-releases','graphics/releases-label-2.jpg','graphics/releases-label-3.jpg');" src="graphics/releases-label-3.jpg" vspace="0" width="120"></A><BR>
  7. <A href="secadv.html" onMouseOut="rolloverOff('side-secadv');" onMouseOver="rolloverOn('side-secadv');"><IMG alt="Advisories" border="0" height="12" hspace="0" name="side-secadv" onLoad="rolloverLoad('side-secadv','graphics/secadv-label-2.jpg','graphics/secadv-label-3.jpg');" src="graphics/secadv-label-3.jpg" vspace="0" width="120"></A><BR>
  8. <A href="http://xerces.apache.org/xerces-c/download.cgi" onMouseOut="rolloverOff('side-ext-18');" onMouseOver="rolloverOn('side-ext-18');"><IMG alt="Download" border="0" height="12" hspace="0" name="side-ext-18" onLoad="rolloverLoad('side-ext-18','graphics/ext-18-label-2.jpg','graphics/ext-18-label-3.jpg');" src="graphics/ext-18-label-3.jpg" vspace="0" width="120"></A><BR>
  9. <IMG border="0" height="6" hspace="0" src="resources/separator.gif" vspace="0" width="120"><BR>
  10. <IMG alt="Xerces-C++ 3.1.2" border="0" height="17" hspace="0" name="side-sect-24" src="graphics/sect-24-label.jpg" vspace="0" width="120"><BR>
  11. <A href="install-3.html" onMouseOut="rolloverOff('side-install-3');" onMouseOver="rolloverOn('side-install-3');"><IMG alt="Installation" border="0" height="12" hspace="0" name="side-install-3" onLoad="rolloverLoad('side-install-3','graphics/install-3-label-2.jpg','graphics/install-3-label-3.jpg');" src="graphics/install-3-label-3.jpg" vspace="0" width="120"></A><BR>
  12. <A href="build-3.html" onMouseOut="rolloverOff('side-build-3');" onMouseOver="rolloverOn('side-build-3');"><IMG alt="Build Instructions" border="0" height="12" hspace="0" name="side-build-3" onLoad="rolloverLoad('side-build-3','graphics/build-3-label-2.jpg','graphics/build-3-label-3.jpg');" src="graphics/build-3-label-3.jpg" vspace="0" width="120"></A><BR>
  13. <IMG border="0" height="6" hspace="0" src="resources/separator-space.gif" vspace="0" width="120"><BR>
  14. <A href="program-3.html" onMouseOut="rolloverOff('side-program-3');" onMouseOver="rolloverOn('side-program-3');"><IMG alt="Programming" border="0" height="12" hspace="0" name="side-program-3" onLoad="rolloverLoad('side-program-3','graphics/program-3-label-2.jpg','graphics/program-3-label-3.jpg');" src="graphics/program-3-label-3.jpg" vspace="0" width="120"></A><BR>
  15. <A href="samples-3.html" onMouseOut="rolloverOff('side-samples-3');" onMouseOver="rolloverOn('side-samples-3');"><IMG alt="Samples" border="0" height="12" hspace="0" name="side-samples-3" onLoad="rolloverLoad('side-samples-3','graphics/samples-3-label-2.jpg','graphics/samples-3-label-3.jpg');" src="graphics/samples-3-label-3.jpg" vspace="0" width="120"></A><BR>
  16. <A href="faqs-3.html" onMouseOut="rolloverOff('side-faqs-3');" onMouseOver="rolloverOn('side-faqs-3');"><IMG alt="FAQs" border="0" height="12" hspace="0" name="side-faqs-3" onLoad="rolloverLoad('side-faqs-3','graphics/faqs-3-label-2.jpg','graphics/faqs-3-label-3.jpg');" src="graphics/faqs-3-label-3.jpg" vspace="0" width="120"></A><BR>
  17. <IMG border="0" height="6" hspace="0" src="resources/separator-space.gif" vspace="0" width="120"><BR>
  18. <A href="api-3.html" onMouseOut="rolloverOff('side-api-3');" onMouseOver="rolloverOn('side-api-3');"><IMG alt="API Reference" border="0" height="12" hspace="0" name="side-api-3" onLoad="rolloverLoad('side-api-3','graphics/api-3-label-2.jpg','graphics/api-3-label-3.jpg');" src="graphics/api-3-label-3.jpg" vspace="0" width="120"></A><BR>
  19. <A href="ApacheDOMC++Binding.html" onMouseOut="rolloverOff('side-ext-84');" onMouseOver="rolloverOn('side-ext-84');"><IMG alt="DOM C++ Binding" border="0" height="12" hspace="0" name="side-ext-84" onLoad="rolloverLoad('side-ext-84','graphics/ext-84-label-2.jpg','graphics/ext-84-label-3.jpg');" src="graphics/ext-84-label-3.jpg" vspace="0" width="120"></A><BR>
  20. <A href="migrate-3.html" onMouseOut="rolloverOff('side-migrate-3');" onMouseOver="rolloverOn('side-migrate-3');"><IMG alt="Migration Guide" border="0" height="12" hspace="0" name="side-migrate-3" onLoad="rolloverLoad('side-migrate-3','graphics/migrate-3-label-2.jpg','graphics/migrate-3-label-3.jpg');" src="graphics/migrate-3-label-3.jpg" vspace="0" width="120"></A><BR>
  21. <IMG border="0" height="6" hspace="0" src="resources/separator.gif" vspace="0" width="120"><BR>
  22. <A href="feedback.html" onMouseOut="rolloverOff('side-feedback');" onMouseOver="rolloverOn('side-feedback');"><IMG alt="Feedback" border="0" height="12" hspace="0" name="side-feedback" onLoad="rolloverLoad('side-feedback','graphics/feedback-label-2.jpg','graphics/feedback-label-3.jpg');" src="graphics/feedback-label-3.jpg" vspace="0" width="120"></A><BR>
  23. <A href="bug-report.html" onMouseOut="rolloverOff('side-bug-report');" onMouseOver="rolloverOn('side-bug-report');"><IMG alt="Bug-Reporting" border="0" height="12" hspace="0" name="side-bug-report" onLoad="rolloverLoad('side-bug-report','graphics/bug-report-label-2.jpg','graphics/bug-report-label-3.jpg');" src="graphics/bug-report-label-3.jpg" vspace="0" width="120"></A><BR>
  24. <A href="mailing-lists.html" onMouseOut="rolloverOff('side-mailing-lists');" onMouseOver="rolloverOn('side-mailing-lists');"><IMG alt="Mailing Lists" border="0" height="12" hspace="0" name="side-mailing-lists" onLoad="rolloverLoad('side-mailing-lists','graphics/mailing-lists-label-2.jpg','graphics/mailing-lists-label-3.jpg');" src="graphics/mailing-lists-label-3.jpg" vspace="0" width="120"></A><BR>
  25. <IMG border="0" height="6" hspace="0" src="resources/separator.gif" vspace="0" width="120"><BR>
  26. <A href="source-repository.html" onMouseOut="rolloverOff('side-source-repository');" onMouseOver="rolloverOn('side-source-repository');"><IMG alt="Source Repository" border="0" height="12" hspace="0" name="side-source-repository" onLoad="rolloverLoad('side-source-repository','graphics/source-repository-label-2.jpg','graphics/source-repository-label-3.jpg');" src="graphics/source-repository-label-3.jpg" vspace="0" width="120"></A><BR>
  27. <A href="applications.html" onMouseOut="rolloverOff('side-applications');" onMouseOver="rolloverOn('side-applications');"><IMG alt="Applications" border="0" height="12" hspace="0" name="side-applications" onLoad="rolloverLoad('side-applications','graphics/applications-label-2.jpg','graphics/applications-label-3.jpg');" src="graphics/applications-label-3.jpg" vspace="0" width="120"></A><BR>
  28. <IMG border="0" height="14" hspace="0" src="resources/close.gif" vspace="0" width="120"><BR></TD><TD align="left" valign="top" width="500"><TABLE border="0" cellpadding="3" cellspacing="0"><TR><TD>
  29. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>Xerces Project Charter</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  30. <P>
  31. The following charter applies to all Xerces projects.
  32. </P>
  33. </FONT></TD></TR></TABLE><BR>
  34. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>1 INTRODUCTION</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  35. <P>
  36. 1.1 Apache Xerces is a collaborative software development project
  37. dedicated to providing robust, full-featured, commercial-quality, and
  38. freely available XML parsers and closely related technologies
  39. on a wide variety of platforms supporting several languages. This
  40. project is managed in cooperation with various individuals worldwide
  41. (both independent and company-affiliated experts), who use the
  42. Internet to communicate, plan, and develop XML software and related
  43. documentation.
  44. </P>
  45. <P>
  46. 1.2 This charter briefly describes the mission, history, organization, and
  47. processes of the project.
  48. </P>
  49. </FONT></TD></TR></TABLE><BR>
  50. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>2 MISSION</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  51. <P>
  52. 2.1 Apache Xerces exists to promote the use of XML. We view XML as a
  53. compelling paradigm that structures data as information, thereby
  54. facilitating the exchange, transformation, and presentation of
  55. knowledge. The ability to transform raw data into usable information
  56. has great potential to improve the functionality and use of
  57. information systems. We intend to build freely available XML
  58. parsers and closely related technologies in order to engender such
  59. improvements.
  60. </P>
  61. <P>
  62. 2.2 The Apache Xerces parsers support standard APIs (formal, de facto,
  63. or proposed).
  64. They are designed to be high performance, reliable, and easy to use.
  65. To facilitate easy porting of ideas between languages, the API's supported
  66. should be as similar as possible, given the constraints of the languages
  67. and existing architectures. Apache Xerces parsers should also be designed
  68. to work efficiently with other Apache projects that deal
  69. with XML whenever possible.
  70. </P>
  71. <P>
  72. 2.3 We believe that the best way to further these goals
  73. is by having both individuals and corporations
  74. collaborate on the best possible infrastructure, APIs, code, testing,
  75. and release cycles. Components must be vendor neutral and usable as
  76. core components for all.
  77. </P>
  78. <P>
  79. 2.4 In order to achieve a coherent architecture between Apache Xerces
  80. parsers
  81. and other components and applications, standards (formal or
  82. de facto) will be used as much as possible for both protocols and
  83. APIs. Where appropriate, experiences and lessons learned will be fed
  84. back to standards bodies in an effort to assist in the development of
  85. those standards. We will also encourage the innovation of new
  86. protocols, APIs, and components in order to seed new concepts not
  87. yet defined by standards.
  88. </P>
  89. </FONT></TD></TR></TABLE><BR>
  90. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>3 HISTORY</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  91. <P>
  92. 3.1 The code base which formed the foundations of both the
  93. Xerces-Java and Xerces-C++ subprojects of the Apache XML Project
  94. was originally donated to Apache by IBM in 1999. Xerces-Perl
  95. came into existence as a subproject of the Apache XML project
  96. after the Xerces-C++ community had already matured to a
  97. significant extent. All three were subprojects of the Apache XML
  98. Project until late 2004. At this time, reflecting the growth in
  99. the Apache XML project and these communities themselves, Apache
  100. Xerces became a top-level Project of the Apache Software
  101. Foundation. Apache Xerces still shares much infrastructure with
  102. the Apache XML project and the other former subprojects of Apache
  103. XML that have become projects in their own right.
  104. </P>
  105. </FONT></TD></TR></TABLE><BR>
  106. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>4 TERMS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  107. <P>
  108. 4.1 The ASF Board. The management board of the Apache Software
  109. Foundation.
  110. </P>
  111. <P>
  112. 4.2 The Project. The Apache Xerces Project; intended
  113. to refer to the source code, website and community that are Apache Xerces.
  114. </P>
  115. <P>
  116. 4.3 Subproject. Apache Xerces is composed of a number of subprojects
  117. which fit into one of two categories:
  118. </P>
  119. <P>
  120. a) An XML parser implementation in some particular programming
  121. language. There may be multiple parsers for a given
  122. language, if the API's the parsers support are sufficiently
  123. dissimilar. At the time of writing, there is one parser for
  124. each of Java, C/C++ and Perl.
  125. </P>
  126. <P>
  127. b) A set of components serving some purpose not directly
  128. pertinent to XML parsing, but which are used in related
  129. applications and are tightly bound, usually through internal
  130. API's, to one (or more) of the parser subprojects.
  131. </P>
  132. <P>
  133. 4.4 Product. Some deliverable (usually a binary or source
  134. package) that a subproject releases to the public. Subprojects
  135. may have multiple products.
  136. </P>
  137. <P>
  138. 4.5 Contributor. Anyone who makes a contribution to the development
  139. of the Apache Xerces project or a subproject.
  140. </P>
  141. <P>
  142. 4.6 Committer. Apache Xerces has a set of committers. Committers
  143. are contributors who have read/write access to the source code
  144. repository.
  145. </P>
  146. </FONT></TD></TR></TABLE><BR>
  147. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>5 THE PROJECT MANAGEMENT COMMITTEE</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  148. <P>
  149. 5.1 The Apache Xerces project is managed by a core group of
  150. committers known as the Project Management Committee [PMC],
  151. which is composed of volunteers from among the active committers
  152. (see 8.3 below) from all subprojects. Each subproject must have
  153. at least one representative on the PMC, to ensure active
  154. supervision of the subproject.
  155. </P>
  156. <P>
  157. 5.2 The activities of the PMC are coordinated by the Chairperson,
  158. who is an officer of the corporation and reports to the Apache
  159. Board. The Chairperson will, on the request of the Apache Board,
  160. provide reports to the Board on issues related to the running of
  161. the Apache Xerces project.
  162. </P>
  163. <P>
  164. 5.3 The PMC has the following responsibilities:
  165. </P>
  166. <P>
  167. a) Accepting new subproject proposals, voting on these
  168. proposals and creating the
  169. subproject (see SUBPROJECTS below). This is done in collaboration
  170. with the Incubator (see http://incubator.apache.org).
  171. </P>
  172. <P>
  173. b) Facilitating code or other donations by individuals or companies,
  174. in collaboration with the Incubator.
  175. </P>
  176. <P>
  177. c) Resolving license issues and other legal issues in conjunction with
  178. the ASF board.
  179. </P><P>
  180. d) Ensuring that administrative and infrastructure work is completed.
  181. </P><P>
  182. e) Facilitating relationships among subprojects and other Apache projects.
  183. </P><P>
  184. f) Facilitating relationships between Apache Xerces and the external
  185. world.
  186. </P><P>
  187. g) Overseeing Apache Xerces to ensure that the mission defined in
  188. this document is being fulfilled.
  189. </P><P>
  190. h) Resolving conflicts within the project.
  191. </P><P>
  192. i) Reporting to the ASF board (through the Chair) on the progress
  193. of the project.
  194. </P><P>
  195. 5.4 In cases where the sub-project is unable to directly provide
  196. at least one representative on the PMC--implying that there are no
  197. active committers on that code base--then the subproject should
  198. be considered dormant, and any relevant Apache policies for dormant
  199. projects should be implemented. At the least, the subproject's status
  200. should
  201. be updated on its website.
  202. </P><P>
  203. 5.5 Every 12 months, or at the request of the Board, the PMC will provide
  204. a recommendation to the Apache Board for the position of Chairperson
  205. of the PMC.
  206. </P><P>
  207. 5.6 This recommendation will be made on the basis of an election held
  208. within the PMC. The election will be performed using a simple
  209. majority vote of PMC members.
  210. </P><P>
  211. 5.7 Upon agreement by the Apache Board, the recommended Chairperson will,
  212. if they are not already, be appointed an officer of the corporation.
  213. See http://www.apache.org/foundation/bylaws.html for more information.
  214. </P><P>
  215. 5.8 In the unlikely event that a member of the PMC becomes disruptive to
  216. the process, ceases to make codebase contributions for an extended
  217. period, or ceases to take part in PMC votes for an extended period of
  218. time, said member may be removed by unanimous vote of remaining PMC
  219. members.
  220. </P><P>
  221. 5.9 The PMC is responsible for maintaining and updating this
  222. charter. Development must follow the process outlined below, so any
  223. change to the development process necessitates a change to the
  224. charter. Changes must be approved by a two-thirds majority of all members
  225. of the PMC.
  226. </P>
  227. </FONT></TD></TR></TABLE><BR>
  228. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>6 SUBPROJECTS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  229. <P>
  230. 6.1 When a new subproject proposal is submitted to the PMC, it
  231. may be accepted by a two-thirds vote of the PMC.
  232. </P><P>
  233. 6.2 A subproject may be removed by unanimous vote of the PMC, subject to
  234. the
  235. approval of the ASF board.
  236. </P>
  237. </FONT></TD></TR></TABLE><BR>
  238. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>7 CONTRIBUTORS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  239. <P>
  240. 7.1 Like all Apache projects, the Apache Xerces project is a meritocracy
  241. --
  242. the more work you do, the more you are allowed to do. Contributions
  243. will include participating in mailing lists, reporting bugs, providing
  244. patches and proposing changes to a product.
  245. </P><P>
  246. 7.2 In order to ensure that all code contained in the Apache
  247. Xerces project's code repository is free of licensing,
  248. intellectual property and patent issues, any developer wishing
  249. to contribute a new feature to Xerces must either sign:
  250. </P><P>
  251. a) If contributing as an individual, sign the &quot;Individual
  252. Contributor License Agreement (CLA)&quot;
  253. (http://www.apache.org/licenses/icla.txt) and file a copy with
  254. the Secretary of the Corporation; or
  255. </P><P>
  256. b) If making the contribution as part of their employment
  257. responsibilities, sign the &quot;Corporate CLA (CCLA)&quot;,
  258. (http://www.apache.org/licenses/cla-corporate.txt) and file a
  259. copy with the Secretary of the Corporation.
  260. </P><P>
  261. 7.3 If the contribution in question is a small bugfix, the
  262. contributor need not sign a CLA, but need only provide the
  263. following information, attaching it to the communication
  264. containing the patch:
  265. </P><P>
  266. a) Name and employer
  267. </P><P>
  268. b) Are you the author of the code being contributed?
  269. </P><P>
  270. c) Do you have the right to grant the copyright and patent
  271. licenses for the contribution that are set forth in the ASF v.2.0
  272. license (http://www.apache.org/licenses/LICENSE-2.0)?
  273. </P><P>
  274. d) Does your employer have any rights to code that you have
  275. written, for example, through your contract for employment? If
  276. so, has your employer given you permission to contribute the code
  277. on its behalf or waived its rights in the code?
  278. </P><P>
  279. e) Are you aware of any third-party licenses or other
  280. restrictions (such as related patents or trademarks) that could
  281. apply to your contribution? If so, what are they?
  282. </P><P>
  283. 7.4 Contributors who make regular and substantial contributions may become
  284. committers as described below.
  285. </P>
  286. </FONT></TD></TR></TABLE><BR>
  287. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>8 COMMITTERS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  288. <P>
  289. 8.1 Each subproject has a set of committers. Committers are
  290. contributors who have read/write access to the source code
  291. repository.
  292. </P><P>
  293. 8.2 Normally, a new committer is added after a contributor has
  294. been nominated by a committer and approved by at least 50 percent
  295. of the active committers for that subproject with no opposing
  296. votes. In the case that a subproject has a very small number of
  297. active committers, the PMC may choose to require a PMC resolution
  298. to approve the nomination of a contributor by one of the active
  299. committers in that subproject. All committers must have a signed
  300. Contributor License Agreement on file with the Secretary of the
  301. Corporation. Since, in most cases, contributors will already
  302. have contributed significant amounts of code, this should usually
  303. have been done before nomination.
  304. </P><P>
  305. 8.3 Although committers have write access to all Apache Xerces
  306. subprojects,
  307. they are only permitted to make changes to the subprojects to which they
  308. have been elected committers. A committer may be elected to multiple
  309. subprojects, but, except that no new access need be granted, the
  310. process is the same as for any other contributor.
  311. </P><P>
  312. 8.4 For the purposes of voting, committers will be classed as &quot;active&quot; or
  313. &quot;inactive&quot;. Only active committers will be included in the totals used to
  314. determine the success or failure of a particular vote, and
  315. only active committers are part of the PMC.
  316. </P><P>
  317. 8.5 Committers remain active as long as they are contributing code or
  318. posting to the subproject mailing lists. If a committer has neither
  319. contributed code nor posted to the subproject mailing lists in 3
  320. months, the PMC chair may e-mail the
  321. committer, the subproject development list, and the PMC mailing list
  322. notifying the committer that they are going to be moved to inactive
  323. status. If there is no response in 72 hours, the committer will become
  324. inactive, and may be removed from the PMC mailing list.
  325. </P><P>
  326. 8.6 An inactive status will not prevent a committer committing new code
  327. changes or posting to the mailing lists. Either of these activities will
  328. automatically re-activate the committer for the purposes of
  329. voting, and necessitate their addition to the PMC mailing list.
  330. </P>
  331. </FONT></TD></TR></TABLE><BR>
  332. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>9 INFRASTRUCTURE</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  333. <P>
  334. 9.1 The Apache Xerces project relies on the Apache XML project
  335. and the Apache Infrastructure project for the following:
  336. </P><P>
  337. a) Bug Database -- This is a system for tracking bugs and feature
  338. requests.
  339. </P><P>
  340. b) Subproject Source Repositories -- These are several repositories
  341. containing both the source code and documentation for the
  342. subprojects.
  343. </P><P>
  344. c) Website -- A xerces.apache.org website will contain information about
  345. the Apache Xerces project, including documentation, downloads of
  346. releases, and this charter. Each subproject will have its own website
  347. with subproject information.
  348. </P><P>
  349. d) PMC Mailing List -- This list is for PMC business requiring
  350. confidentiality, particularly when an individual or company requests
  351. discretion. All other PMC business should be done on the general
  352. mailing list.
  353. </P><P>
  354. e) General Mailing List -- This mailing list is open to the public. It is
  355. intended for discussions that cross subprojects.
  356. </P><P>
  357. f) Subproject Mailing Lists -- Each subproject should have at least one
  358. devoted mailing
  359. list. Many subprojects may wish to have both user and development
  360. lists. The individual subprojects may decide on the exact structure of
  361. their mailing lists.
  362. </P>
  363. </FONT></TD></TR></TABLE><BR>
  364. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>10 LICENSING</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  365. <P>
  366. 10.1 All contributions to the Apache Xerces project adhere to the
  367. Apache Software Foundation License, v.2.0
  368. (http://www.apache.org/licenses/LICENSE-2.0)?
  369. All further contributions must be made under the
  370. same terms.
  371. </P><P>
  372. 10.2 When a committer is considering integrating a contribution
  373. from a contributor who has no CLA on file with the Corporation,
  374. it is the responsibility of the committer, in consultation with
  375. the PMC, to conduct due diligence on the pedigree of the
  376. contribution under consideration; see sections 7.2 and 7.3.
  377. </P>
  378. </FONT></TD></TR></TABLE><BR>
  379. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>11 THE DEVELOPMENT PROCESS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  380. <P>
  381. 11.1 The development process is intentionally lightweight; like other
  382. Apache projects, the committers decide which changes may be committed
  383. to the repository. Three +1 ('yes' votes) with no -1 ('no' votes or
  384. vetoes) are needed to approve a significant code change. For
  385. efficiency, some code changes from some contributors (e.g.
  386. feature additions, bug fixes) may be approved in advance, in
  387. which case they may be committed first and changed as needed,
  388. with conflicts resolved by majority vote of the committers.
  389. </P>
  390. </FONT></TD></TR></TABLE><BR>
  391. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>12 SUBPROJECT REQUIREMENTS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  392. <P>
  393. 12.1 Each subproject should have a set of requirements as well as an
  394. up-to-date release plan and design document on its dedicated web page.
  395. </P><P>
  396. 12.2 It is recommended that each subproject have a smoke-test system
  397. that works at least as a basic integration test.
  398. </P>
  399. </FONT></TD></TR></TABLE><BR>
  400. <TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="ffffff" colspan="2" width="494"><TABLE border="0" cellpadding="0" cellspacing="0" width="494"><TR><TD bgcolor="#039acc" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#039acc" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#039acc" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#0086b2" width="492"><FONT color="#ffffff" face="arial,helvetica,sanserif" size="+1"><IMG border="0" height="2" hspace="0" src="resources/void.gif" vspace="0" width="2"><B>13 RELATIONSHIP TO OTHER APACHE PROJECTS</B></FONT></TD><TD bgcolor="#017299" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR><TR><TD bgcolor="#0086b2" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD><TD bgcolor="#017299" height="1" width="492"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="492"></TD><TD bgcolor="#017299" height="1" width="1"><IMG border="0" height="1" hspace="0" src="resources/void.gif" vspace="0" width="1"></TD></TR></TABLE></TD></TR><TR><TD width="10">&nbsp;</TD><TD width="484"><FONT color="#000000" face="arial,helvetica,sanserif">
  401. <P>
  402. 13.1 The Apache Xerces project should work closely with other Apache
  403. projects, such as XML, Jakarta and the Apache Server, to avoid redundancy
  404. and achieve a coherent architecture among Apache Xerces and these
  405. projects.
  406. </P>
  407. </FONT></TD></TR></TABLE><BR>
  408. </TD></TR></TABLE></TD></TR></TABLE><BR><TABLE border="0" cellpadding="0" cellspacing="0" width="620"><TR><TD bgcolor="#0086b2"><IMG height="1" src="resources/dot.gif" width="1"></TD></TR><TR><TD align="center"><FONT color="#0086b2" size="-1"><I>
  409. Copyright &copy; 1999-2015 The Apache Software Foundation.
  410. All Rights Reserved.
  411. </I></FONT></TD></TR></TABLE></BODY></HTML>