Author: scantor
Date: Wed Jun 21 17:18:13 2017
New Revision: 1799488
URL: http://svn.apache.org/viewvc?rev=1799488&view=rev
Log:
Merge over doc changes from 3.1 branch.
Added:
xerces/c/trunk/doc/applications.xml (with props)
xerces/c/trunk/doc/bug-report.xml (with props)
xerces/c/trunk/doc/charter.xml (with props)
xerces/c/trunk/doc/download.xml (with props)
xerces/c/trunk/doc/feedback.xml (with props)
xerces/c/trunk/doc/html/secadv/
xerces/c/trunk/doc/html/secadv/CVE-2015-0252.txt (with props)
xerces/c/trunk/doc/html/secadv/CVE-2016-0729.txt (with props)
xerces/c/trunk/doc/html/secadv/CVE-2016-4463.txt (with props)
xerces/c/trunk/doc/mailing-lists.xml (with props)
xerces/c/trunk/doc/releases.xml (with props)
xerces/c/trunk/doc/releases_archive.xml (with props)
xerces/c/trunk/doc/releases_plan.xml (with props)
xerces/c/trunk/doc/secadv.xml (with props)
xerces/c/trunk/doc/source-repository.xml (with props)
Modified:
xerces/c/trunk/doc/apidocs.xml (props changed)
xerces/c/trunk/doc/build.xml (contents, props changed)
xerces/c/trunk/doc/createdoc.xml (props changed)
xerces/c/trunk/doc/domcount.xml (props changed)
xerces/c/trunk/doc/domprint.xml (props changed)
xerces/c/trunk/doc/enumval.xml (props changed)
xerces/c/trunk/doc/faq-build.xml (props changed)
xerces/c/trunk/doc/faq-contributing.xml (props changed)
xerces/c/trunk/doc/faq-distrib.xml (props changed)
xerces/c/trunk/doc/faq-other.xml (props changed)
xerces/c/trunk/doc/faq-parse.xml (props changed)
xerces/c/trunk/doc/html/ (props changed)
xerces/c/trunk/doc/html/ApacheDOMC++Binding.html
xerces/c/trunk/doc/html/apiDocs-3/ (props changed)
xerces/c/trunk/doc/install.xml (contents, props changed)
xerces/c/trunk/doc/memparse.xml (props changed)
xerces/c/trunk/doc/migration.xml (contents, props changed)
xerces/c/trunk/doc/migration_archive.xml (contents, props changed)
xerces/c/trunk/doc/pparse.xml (props changed)
xerces/c/trunk/doc/program-dom.xml (props changed)
xerces/c/trunk/doc/program-others.xml (props changed)
xerces/c/trunk/doc/program-sax.xml (props changed)
xerces/c/trunk/doc/program-sax2.xml (props changed)
xerces/c/trunk/doc/program.xml (props changed)
xerces/c/trunk/doc/psviwriter.xml (props changed)
xerces/c/trunk/doc/readme.xml (contents, props changed)
xerces/c/trunk/doc/redirect.xml (props changed)
xerces/c/trunk/doc/samples.xml (props changed)
xerces/c/trunk/doc/sax2count.xml (props changed)
xerces/c/trunk/doc/sax2print.xml (props changed)
xerces/c/trunk/doc/saxcount.xml (props changed)
xerces/c/trunk/doc/saxprint.xml (props changed)
xerces/c/trunk/doc/schema.xml (props changed)
xerces/c/trunk/doc/scmprint.xml (props changed)
xerces/c/trunk/doc/senumval.xml (props changed)
xerces/c/trunk/doc/stdinparse.xml (props changed)
xerces/c/trunk/doc/style/dtd/blocks.ent
xerces/c/trunk/doc/style/dtd/entities.ent
xerces/c/trunk/doc/xerces-c_book.xml (contents, props changed)
xerces/c/trunk/doc/xinclude.xml (props changed)
Propchange: xerces/c/trunk/doc/apidocs.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: xerces/c/trunk/doc/applications.xml
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/applications.xml?rev=1799488&view=auto
==============================================================================
--- xerces/c/trunk/doc/applications.xml (added)
+++ xerces/c/trunk/doc/applications.xml Wed Jun 21 17:18:13 2017
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
+
+<s1 title="Applications">
+
+ <s2 title="Overview">
+ <p>This page lists popular application and libraries that
+ are based on or provide an additional functionality on
+ top of &XercesCName;. If you know of an application that
+ you feel should be listed here, send an email with all the
+ relevant information to one of the <jump href="mailing-lists.html">
+ &XercesCName; mailing lists</jump>.</p>
+
+ <s3 title="CodeSynthesis XSD">
+ <p><jump href="http://www.codesynthesis.com/products/xsd/";>CodeSynthesis
+ XSD</jump> is an open-source XML Schema to C++ data
+ binding compiler that uses &XercesCName; as the underlying XML
+ parser. Provided with an XML instance specification (XML Schema), XSD
+ generates C++ classes that represent the given vocabulary as well
+ as parsing and serialization code. You can then access the data
+ stored in XML using types and functions that semantically
+ correspond to your application domain rather than dealing with
+ direct representations of XML such as DOM and SAX.</p>
+ </s3>
+
+ <s3 title="Xalan-C++">
+ <p><jump href="http://xml.apache.org/xalan-c/";>Xalan-C++</jump>
+ is an open-source XSLT processor for transforming XML documents
+ into HTML, text, or other XML document types. It implementes the W3C
+ recommendations for XSL Transformations (XSLT) and the XML Path
+ Language (XPath) and is based on &XercesCName;.</p>
+ </s3>
+
+ <s3 title="XQilla">
+ <p><jump href="http://xqilla.sourceforge.net";>XQilla</jump>
+ is an open-source XQuery and XPath 2.0 implementation based
+ on &XercesCName;. It implements the DOM 3 XPath API and conforms
+ to the W3C proposed recommendation of XQuery and XPath 2.0.</p>
+ </s3>
+
+ <s3 title="XML Security for C++">
+ <p><jump href="http://santuario.apache.org/";>XML Security
+ for C++</jump> is an open-source implementation of the XML
+ Digital Signature and Encryption specifications and is based
+ on &XercesCName;. The library also provides support for
+ serializing XML in the canonical form.</p>
+ </s3>
+
+ <s3 title="Shibboleth and OpenSAML">
+ <p><jump href="http://shibboleth.net/";>Shibboleth</jump> is
+ an open source Web Single Sign-On and Federation implementation
+ that supports the SAML 2.0 and SAML 1.1 standards, among other
+ capabilities. The Service Provider and underlying OpenSAML
+ library use &XercesCName;.</p>
+ </s3>
+
+ </s2>
+</s1>
Propchange: xerces/c/trunk/doc/applications.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: xerces/c/trunk/doc/bug-report.xml
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/bug-report.xml?rev=1799488&view=auto
==============================================================================
--- xerces/c/trunk/doc/bug-report.xml (added)
+++ xerces/c/trunk/doc/bug-report.xml Wed Jun 21 17:18:13 2017
@@ -0,0 +1,82 @@
+<?xml version="1.0" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
+
+<s1 title="Bug Reporting">
+
+<s2 title="How to report bugs">
+<p> Please report bugs to <jump href="&JiraURL;">Jira</jump>,
+the Apache bug database. Pick the product "Xerces-C++"
+using the following components:
+</p>
+<table>
+<tr><th><em>Component</em></th><th><em>Description</em></th></tr>
+<tr><td>DOM</td><td>Items specific to DOM</td></tr>
+<tr><td>SAX/SAX2</td><td>Items specific to SAX or SAX2</td></tr>
+<tr><td>Non-Validating Parser</td><td>General Parsing Problem</td></tr>
+<tr><td>Validating Parser (DTD)</td><td>DTD related parser issue</td></tr>
+<tr><td>Validating Parser (Schema)</td><td>Schema related parser
issue</td></tr>
+<tr><td>Utilities</td><td>Items related to utilities like MessageLoader,
Transcoder, NetAccessors, Platform specific utilities</td></tr>
+<tr><td>Build</td><td>Problem with build, makefile, project files</td></tr>
+<tr><td>Documentation</td><td>Documentation bugs such as FAQ, Programming
Guide</td></tr>
+<tr><td>Samples/Tests</td><td>Samples or test cases related issues</td></tr>
+<tr><td>Miscellaneous</td><td>Items not covered in other categories</td></tr>
+</table>
+<p>A copy of your bug report is sent automatically to the
+<jump href="mailing-lists.html">&XercesCName; development mailing list</jump>.
+</p>
+</s2>
+<s2 title="Search first">
+<p> Check the <jump href="&JiraURL;">Jira</jump> database
+before submitting your bug report to avoid creating a duplicate report.
+Even the bug has been reported already, you may add a comment to the existing
report
+since your contribution may lead to a quicker identification/resolution to the
bug reported.
+</p>
+<p> Here is the list of
+<jump href=
+"http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10510&statusIds=1">
+outstanding bugs</jump> that are currently reported in Jira.
+</p>
+</s2>
+<s2 title="Write a good bug report">
+<p> Writing a useful bug report, which makes the bug reproducible, is the
first step
+towards the resolution of the bug. Specifics about the bug, like
+</p>
+<ul>
+<li>&XercesCName; version number</li>
+<li>Platform</li>
+<li>Operating system and version number</li>
+<li>Compiler and version number</li>
+<li>The XML document (or excerpt) that failed</li>
+<li>The C++ application code that failed</li>
+<li>Whether you built the &XercesCName; library yourself or used the
+binary distribution</li>
+<li>What happened</li>
+</ul>
+<p>
+are all necessary information to allow developer to reproduce,
+identify, evaluate and eventually, fix the bug, which is the very
+purpose of your reporting of the bug.
+</p>
+<p>If you are providing a patch please review the information in
+<jump href="faq-contributing-&XercesC3Series;.html#Submitting
Patches">Submitting Patches</jump>.
+</p>
+</s2>
+
+</s1>
Propchange: xerces/c/trunk/doc/bug-report.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Modified: xerces/c/trunk/doc/build.xml
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/build.xml?rev=1799488&r1=1799487&r2=1799488&view=diff
==============================================================================
--- xerces/c/trunk/doc/build.xml (original)
+++ xerces/c/trunk/doc/build.xml Wed Jun 21 17:18:13 2017
@@ -90,7 +90,7 @@
</tr>
<tr>
<td><code>-Dnetwork-accessor=winsock</code></td>
- <td>use WinSock (only on Windows and MinGW)</td>
+ <td>use WinSock (only on Windows, Cygwin, MinGW)</td>
</tr>
<tr>
<td><code>-Dnetwork:BOOL=OFF</code></td>
@@ -323,7 +323,7 @@
</tr>
<tr>
<td><code>--enable-netaccessor-winsock</code></td>
- <td>use WinSock (only on Windows and MinGW)</td>
+ <td>use WinSock (only on Windows, Cygwin, MinGW)</td>
</tr>
<tr>
<td><code>--disable-network</code></td>
@@ -356,7 +356,7 @@
</tr>
<tr>
<td><code>--enable-transcoder-windows</code></td>
- <td>use Windows APIs (only on Windows and MinGW)</td>
+ <td>use Windows APIs (only on Windows, Cygwin, MinGW)</td>
</tr>
</table>
@@ -511,7 +511,7 @@
and Solaris, the environment variable name is
<code>LD_LIBRARY_PATH</code>, on AIX it is
<code>LIBPATH</code>, on Mac OS X it is
- <code>DYLD_FALLBACK_LIBRARY_PATH</code>, and on HP-UX
+ <code>DYLD_LIBRARY_PATH</code>, and on HP-UX
it is <code>SHLIB_PATH</code>.
</note>
@@ -526,30 +526,10 @@
<anchor name="Windows"/>
<s3 title="Building on Windows using Microsoft Visual C++">
- <p>&XercesCName; source distribution comes with Microsoft Visual C++
projects and solutions.
- The following describes the steps you need to build with this
compiler.</p>
-
- <p>To build &XercesCName; from the source distribution you will
- need to open the solution containing the project. The solutions
- containing the &XercesCName; project files are in the following
- sub-directories in the <code>&XercesC3SrcInstallDir;</code>
- directory:</p>
-
-<source>
-(For VC7.1) projects\Win32\VC7.1\xerces-all\xerces-all.sln
-(For VC8.0) projects\Win32\VC8\xerces-all\xerces-all.sln
-(For VC9.0) projects\Win32\VC9\xerces-all\xerces-all.sln
-(For VC10.0) projects\Win32\VC10\xerces-all\xerces-all.sln
-</source>
-
- <p>Once you have the solution open, you need to build the
- project named <code>XercesLib</code>. You can select
- Debug/Release, Static/DLL, and, for VC8, VC9, and VC10,
- 32/64 bit builds using the Configuration Manager dialog.
- You can also select whether the &XercesCName; library
- should use ICU for transcoding.</p>
+ <p>Solution files for supported versions can be generated via CMake,
+ as described above.</p>
- <p>When building your own applications you need to make sure
+ <p>When building your own applications you need to make sure
that you are linking your application with the
&XercesC3WindowsLib;.lib (Release) and/or
&XercesC3WindowsLib;D.lib (Debug)
@@ -557,29 +537,11 @@
and also that the associated DLLs are somewhere in the
executable/DLL search path (<code>PATH</code>).</p>
- <note>If you are linking your application to the static
+ <note>If you are linking your application to the static
&XercesCName; library,
then you will need to compile your application with the
XERCES_STATIC_LIBRARY preprocessor macro defined in order
to turn off the DLL import/export mechanism.</note>
-
- <p>If you would also like to build tests and/or samples, inside
- the solution files mentioned above, you'll find several other
- projects which are for the tests and samples. Select all
- the tests/samples that you would like to build and then
- right click on the selection. Choose "Build (selection
- only)" to build all the selected projects in one shot.</p>
- </s3>
-
- <anchor name="BorlandCC"/>
- <s3 title="Building on Windows using Borland C++">
- <p>&XercesCName; source distribution comes with the Borland C++
makefiles. The
- following describes the steps you need to build &XercesCName; with
this compiler.</p>
- <ol>
- <li>Change to the
<code>&XercesC3SrcInstallDir;\projects\Win32\BCC5\Xerces-all</code>
directory</li>
- <li>Run <code>MakeBuildDirs.bat</code></li>
- <li><code>make -f Xerces-all.mak</code> to build the library,
examples, and tests.</li>
- </ol>
</s3>
</s2>
</s1>
Propchange: xerces/c/trunk/doc/build.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: xerces/c/trunk/doc/charter.xml
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/charter.xml?rev=1799488&view=auto
==============================================================================
--- xerces/c/trunk/doc/charter.xml (added)
+++ xerces/c/trunk/doc/charter.xml Wed Jun 21 17:18:13 2017
@@ -0,0 +1,457 @@
+<?xml version="1.0" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
+
+<s1 title="&XercesCFullName;">
+
+<s2 title="Xerces Project Charter">
+<p>
+The following charter applies to all Xerces projects.
+</p>
+</s2>
+
+<s2 title="1 INTRODUCTION" >
+<p>
+1.1 Apache Xerces is a collaborative software development project
+dedicated to providing robust, full-featured, commercial-quality, and
+freely available XML parsers and closely related technologies
+on a wide variety of platforms supporting several languages. 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.
+</p>
+<p>
+1.2 This charter briefly describes the mission, history, organization, and
+processes of the project.
+</p>
+</s2>
+
+<s2 title="2 MISSION" >
+<p>
+2.1 Apache Xerces 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
+parsers and closely related technologies in order to engender such
+improvements.
+</p>
+
+<p>
+2.2 The Apache Xerces parsers support standard APIs (formal, de facto,
+or proposed).
+They are designed to be high performance, reliable, and easy to use.
+To facilitate easy porting of ideas between languages, the API's supported
+should be as similar as possible, given the constraints of the languages
+and existing architectures. Apache Xerces parsers should also be designed
+to work efficiently with other Apache projects that deal
+with XML whenever possible.
+</p>
+
+<p>
+2.3 We believe that the best way to further these goals
+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.
+</p>
+<p>
+2.4 In order to achieve a coherent architecture between Apache Xerces
+parsers
+and other components and applications, standards (formal or
+de facto) will be used as much as possible for both protocols and
+APIs. Where appropriate, experiences and lessons learned will be fed
+back to standards bodies in an effort to assist in the development of
+those standards. We will also encourage the innovation of new
+protocols, APIs, and components in order to seed new concepts not
+yet defined by standards.
+</p>
+
+</s2>
+<s2 title="3 HISTORY" >
+<p>
+3.1 The code base which formed the foundations of both the
+Xerces-Java and Xerces-C++ subprojects of the Apache XML Project
+was originally donated to Apache by IBM in 1999. Xerces-Perl
+came into existence as a subproject of the Apache XML project
+after the Xerces-C++ community had already matured to a
+significant extent. All three were subprojects of the Apache XML
+Project until late 2004. At this time, reflecting the growth in
+the Apache XML project and these communities themselves, Apache
+Xerces became a top-level Project of the Apache Software
+Foundation. Apache Xerces still shares much infrastructure with
+the Apache XML project and the other former subprojects of Apache
+XML that have become projects in their own right.
+</p>
+
+</s2>
+
+<s2 title="4 TERMS" >
+<p>
+4.1 The ASF Board. The management board of the Apache Software
+Foundation.
+</p>
+
+<p>
+4.2 The Project. The Apache Xerces Project; intended
+to refer to the source code, website and community that are Apache Xerces.
+</p>
+
+<p>
+4.3 Subproject. Apache Xerces is composed of a number of subprojects
+which fit into one of two categories:
+</p>
+<p>
+a) An XML parser implementation in some particular programming
+ language. There may be multiple parsers for a given
+ language, if the API's the parsers support are sufficiently
+ dissimilar. At the time of writing, there is one parser for
+ each of Java, C/C++ and Perl.
+</p>
+<p>
+b) A set of components serving some purpose not directly
+ pertinent to XML parsing, but which are used in related
+ applications and are tightly bound, usually through internal
+ API's, to one (or more) of the parser subprojects.
+</p>
+
+<p>
+4.4 Product. Some deliverable (usually a binary or source
+package) that a subproject releases to the public. Subprojects
+may have multiple products.
+</p>
+
+<p>
+4.5 Contributor. Anyone who makes a contribution to the development
+of the Apache Xerces project or a subproject.
+</p>
+<p>
+4.6 Committer. Apache Xerces has a set of committers. Committers
+are contributors who have read/write access to the source code
+repository.
+</p>
+
+
+</s2>
+
+<s2 title="5 THE PROJECT MANAGEMENT COMMITTEE" >
+<p>
+5.1 The Apache Xerces project is managed by a core group of
+committers known as the Project Management Committee [PMC],
+which is composed of volunteers from among the active committers
+(see 8.3 below) from all subprojects. Each subproject must have
+at least one representative on the PMC, to ensure active
+supervision of the subproject.
+</p>
+
+<p>
+5.2 The activities of the PMC are coordinated by the Chairperson,
+who is an officer of the corporation and reports to the Apache
+Board. The Chairperson will, on the request of the Apache Board,
+provide reports to the Board on issues related to the running of
+the Apache Xerces project.
+</p>
+
+<p>
+5.3 The PMC has the following responsibilities:
+</p>
+
+<p>
+a) Accepting new subproject proposals, voting on these
+ proposals and creating the
+ subproject (see SUBPROJECTS below). This is done in collaboration
+ with the Incubator (see http://incubator.apache.org).
+
+</p>
+<p>
+b) Facilitating code or other donations by individuals or companies,
+ in collaboration with the Incubator.
+</p>
+<p>
+c) Resolving license issues and other legal issues in conjunction with
+ the ASF board.
+</p><p>
+d) Ensuring that administrative and infrastructure work is completed.
+</p><p>
+e) Facilitating relationships among subprojects and other Apache projects.
+</p><p>
+f) Facilitating relationships between Apache Xerces and the external
+ world.
+</p><p>
+g) Overseeing Apache Xerces to ensure that the mission defined in
+ this document is being fulfilled.
+</p><p>
+h) Resolving conflicts within the project.
+</p><p>
+i) Reporting to the ASF board (through the Chair) on the progress
+ of the project.
+
+</p><p>
+5.4 In cases where the sub-project is unable to directly provide
+at least one representative on the PMC--implying that there are no
+active committers on that code base--then the subproject should
+be considered dormant, and any relevant Apache policies for dormant
+projects should be implemented. At the least, the subproject's status
+should
+be updated on its website.
+
+</p><p>
+5.5 Every 12 months, or at the request of the Board, the PMC will provide
+a recommendation to the Apache Board for the position of Chairperson
+of the PMC.
+</p><p>
+5.6 This recommendation will be made on the basis of an election held
+within the PMC. The election will be performed using a simple
+majority vote of PMC members.
+</p><p>
+5.7 Upon agreement by the Apache Board, the recommended Chairperson will,
+if they are not already, be appointed an officer of the corporation.
+See http://www.apache.org/foundation/bylaws.html for more information.
+</p><p>
+5.8 In the unlikely event that a member of the PMC becomes disruptive to
+the process, ceases to make codebase contributions for an extended
+period, or ceases to take part in PMC votes for an extended period of
+time, said member may be removed by unanimous vote of remaining PMC
+members.
+</p><p>
+5.9 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 approved by a two-thirds majority of all members
+of the PMC.
+</p>
+</s2>
+
+
+
+<s2 title="6 SUBPROJECTS" >
+<p>
+6.1 When a new subproject proposal is submitted to the PMC, it
+may be accepted by a two-thirds vote of the PMC.
+
+</p><p>
+6.2 A subproject may be removed by unanimous vote of the PMC, subject to
+the
+approval of the ASF board.
+
+</p>
+</s2>
+<s2 title="7 CONTRIBUTORS" >
+<p>
+7.1 Like all Apache projects, the Apache Xerces project is a meritocracy
+--
+the more work you do, the more you are allowed to do. Contributions
+will include participating in mailing lists, reporting bugs, providing
+patches and proposing changes to a product.
+
+</p><p>
+7.2 In order to ensure that all code contained in the Apache
+Xerces project's code repository is free of licensing,
+intellectual property and patent issues, any developer wishing
+to contribute a new feature to Xerces must either sign:
+
+</p><p>
+a) If contributing as an individual, sign the "Individual
+ Contributor License Agreement (CLA)"
+ (http://www.apache.org/licenses/icla.txt) and file a copy with
+ the Secretary of the Corporation; or
+</p><p>
+b) If making the contribution as part of their employment
+ responsibilities, sign the "Corporate CLA (CCLA)",
+ (http://www.apache.org/licenses/cla-corporate.txt) and file a
+ copy with the Secretary of the Corporation.
+
+</p><p>
+7.3 If the contribution in question is a small bugfix, the
+contributor need not sign a CLA, but need only provide the
+following information, attaching it to the communication
+containing the patch:
+
+</p><p>
+a) Name and employer
+</p><p>
+b) Are you the author of the code being contributed?
+</p><p>
+c) Do you have the right to grant the copyright and patent
+ licenses for the contribution that are set forth in the ASF v.2.0
+ license (http://www.apache.org/licenses/LICENSE-2.0)?
+</p><p>
+d) Does your employer have any rights to code that you have
+ written, for example, through your contract for employment? If
+ so, has your employer given you permission to contribute the code
+ on its behalf or waived its rights in the code?
+</p><p>
+e) Are you aware of any third-party licenses or other
+ restrictions (such as related patents or trademarks) that could
+ apply to your contribution? If so, what are they?
+
+</p><p>
+7.4 Contributors who make regular and substantial contributions may become
+committers as described below.
+
+</p>
+</s2>
+
+<s2 title="8 COMMITTERS" >
+<p>
+8.1 Each subproject has a set of committers. Committers are
+contributors who have read/write access to the source code
+repository.
+
+</p><p>
+8.2 Normally, a new committer is added after a contributor has
+been nominated by a committer and approved by at least 50 percent
+of the active committers for that subproject with no opposing
+votes. In the case that a subproject has a very small number of
+active committers, the PMC may choose to require a PMC resolution
+to approve the nomination of a contributor by one of the active
+committers in that subproject. All committers must have a signed
+Contributor License Agreement on file with the Secretary of the
+Corporation. Since, in most cases, contributors will already
+have contributed significant amounts of code, this should usually
+have been done before nomination.
+
+</p><p>
+8.3 Although committers have write access to all Apache Xerces
+subprojects,
+they are only permitted to make changes to the subprojects to which they
+have been elected committers. A committer may be elected to multiple
+subprojects, but, except that no new access need be granted, the
+process is the same as for any other contributor.
+
+</p><p>
+8.4 For the purposes of voting, committers will be classed as "active" or
+"inactive". Only active committers will be included in the totals used to
+determine the success or failure of a particular vote, and
+only active committers are part of the PMC.
+
+</p><p>
+8.5 Committers remain active as long as they are contributing code or
+posting to the subproject mailing lists. If a committer has neither
+contributed code nor posted to the subproject mailing lists in 3
+months, the PMC chair may e-mail the
+committer, the subproject development list, and the PMC mailing list
+notifying the committer that they are going to be moved to inactive
+status. If there is no response in 72 hours, the committer will become
+inactive, and may be removed from the PMC mailing list.
+
+</p><p>
+8.6 An inactive status will not prevent a committer committing new code
+changes or posting to the mailing lists. Either of these activities will
+automatically re-activate the committer for the purposes of
+voting, and necessitate their addition to the PMC mailing list.
+
+</p>
+</s2>
+<s2 title="9 INFRASTRUCTURE" >
+<p>
+9.1 The Apache Xerces project relies on the Apache XML project
+and the Apache Infrastructure project for the following:
+
+</p><p>
+a) Bug Database -- This is a system for tracking bugs and feature
+ requests.
+
+</p><p>
+b) Subproject Source Repositories -- These are several repositories
+ containing both the source code and documentation for the
+ subprojects.
+
+</p><p>
+c) Website -- A xerces.apache.org website will contain information about
+ the Apache Xerces project, including documentation, downloads of
+ releases, and this charter. Each subproject will have its own website
+ with subproject information.
+
+</p><p>
+d) 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.
+
+</p><p>
+e) General Mailing List -- This mailing list is open to the public. It is
+ intended for discussions that cross subprojects.
+
+</p><p>
+f) Subproject Mailing Lists -- Each subproject should have at least one
+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.
+
+</p>
+</s2>
+<s2 title="10 LICENSING" >
+<p>
+10.1 All contributions to the Apache Xerces project adhere to the
+Apache Software Foundation License, v.2.0
+(http://www.apache.org/licenses/LICENSE-2.0)?
+All further contributions must be made under the
+same terms.
+
+</p><p>
+10.2 When a committer is considering integrating a contribution
+from a contributor who has no CLA on file with the Corporation,
+it is the responsibility of the committer, in consultation with
+the PMC, to conduct due diligence on the pedigree of the
+contribution under consideration; see sections 7.2 and 7.3.
+
+</p>
+</s2>
+<s2 title="11 THE DEVELOPMENT PROCESS" >
+<p>
+11.1 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 significant 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.
+
+</p>
+</s2>
+<s2 title="12 SUBPROJECT REQUIREMENTS" >
+<p>
+12.1 Each subproject should have a set of requirements as well as an
+up-to-date release plan and design document on its dedicated web page.
+
+</p><p>
+12.2 It is recommended that each subproject have a smoke-test system
+that works at least as a basic integration test.
+
+</p>
+</s2>
+<s2 title="13 RELATIONSHIP TO OTHER APACHE PROJECTS" >
+
+<p>
+13.1 The Apache Xerces project should work closely with other Apache
+projects, such as XML, Jakarta and the Apache Server, to avoid redundancy
+and achieve a coherent architecture among Apache Xerces and these
+projects.
+
+</p>
+
+</s2>
+
+
+</s1>
Propchange: xerces/c/trunk/doc/charter.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/createdoc.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/domcount.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/domprint.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: xerces/c/trunk/doc/download.xml
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/download.xml?rev=1799488&view=auto
==============================================================================
--- xerces/c/trunk/doc/download.xml (added)
+++ xerces/c/trunk/doc/download.xml Wed Jun 21 17:18:13 2017
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
+
+<s1 title="Download">
+
+ <s2 title="Download">
+ <p>Use the links below to download &XercesCName; from one of
+ our mirrors. You <em>must</em> <link anchor="verify">verify the
+ integrity</link> of the downloaded files using signatures downloaded
+ from our main distribution directory.</p>
+
+ <p>You can download the &XercesCName; distributions from
+ the <jump href="http://www.apache.org/dist/xerces/c/";>master
+ distribution directory</jump> or, preferably, its <jump
+ href="[preferred]/xerces/c/">mirror</jump>. Only current
+ recommended releases are available on the main distribution
+ site and its mirrors.</p>
+
+ <p>Older releases are available from the
+ <jump href="http://archive.apache.org/dist/xerces/c/";>archive
+ download site</jump>, but you should be aware that there is a lot
+ of accumulated "cruft" in the archives, and many confusingly
+ named files. Anything labeled "current" is likely not.</p>
+ </s2>
+
+ <s2 title="Mirror">
+ <p>The currently selected mirror is <em>[preferred]</em>. If you
+ encounter a problem with this mirror, please select another
+ mirror. If all mirrors are failing, there are <em>backup</em>
+ mirrors (at the end of the mirrors list) that should be available.</p>
+
+
+<form action="[location]" method="get" id="SelectMirror">
+Other mirrors: <select name="Preferred">
+[if-any http]
+ [for http]<option value="[http]">[http]</option>[end]
+[end]
+[if-any ftp]
+ [for ftp]<option value="[ftp]">[ftp]</option>[end]
+[end]
+[if-any backup]
+ [for backup]<option value="[backup]">[backup] (backup)</option>[end]
+[end]
+</select>
+<input type="submit" value="Change" />
+</form>
+
+ <p>You may also consult the <jump
href="http://www.apache.org/mirrors/";>complete
+ list of mirrors</jump>.</p>
+ </s2>
+
+ <s2 title="Latest 3-Series Release">
+
+ <p>The &XercesCName; &XercesCLatest; release is available in source code
+ distributions only. If binaries are produced at a future point, this
+ page will be updated.</p>
+
+ <s3 title="Source Distributions">
+ <p>
+ <jump
href="[preferred]/xerces/c/3/sources/xerces-c-&XercesCLatest;.zip">xerces-c-&XercesCLatest;.zip</jump>
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.zip.asc";>PGP</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.zip.md5";>MD5</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.zip.sha1";>SHA1</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.zip.sha256";>SHA2</jump>]<br/>
+
+ <jump
href="[preferred]/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.gz">xerces-c-&XercesCLatest;.tar.gz</jump>
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.gz.asc";>PGP</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.gz.md5";>MD5</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.gz.sha1";>SHA1</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.gz.sha256";>SHA2</jump>]<br/>
+
+ <jump
href="[preferred]/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.bz2">xerces-c-&XercesCLatest;.tar.bz2</jump>
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.bz2.asc";>PGP</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.bz2.md5";>MD5</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.bz2.sha1";>SHA1</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.bz2.sha256";>SHA2</jump>]<br/>
+
+ <jump
href="[preferred]/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.xz">xerces-c-&XercesCLatest;.tar.xz</jump>
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.xz.asc";>PGP</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.xz.md5";>MD5</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.xz.sha1";>SHA1</jump>]
+ [<jump
href="http://www.apache.org/dist/xerces/c/3/sources/xerces-c-&XercesCLatest;.tar.xz.sha256";>SHA2</jump>]
+
+ </p>
+ </s3>
+ </s2>
+
+ <anchor name="verify"/>
+ <s2 title="Verify the integrity of the files">
+
+ <p>It is essential that you verify the integrity of the downloaded
+ files using the PGP or MD5/SHA files. Please read <jump
+ href="http://httpd.apache.org/dev/verification.html";>Verifying
+ HTTP Server Releases</jump> for more information on why you
+ should verify our releases.</p>
+
+ <p>The PGP signatures can be verified using PGP or GPG. First
+ download the <jump
href="http://www.apache.org/dist/xerces/c/KEYS";>&XercesCName; KEYS</jump>
+ as well as the <code>.asc</code> signature file for the particular
+ distribution. Make sure you get these files from the <jump
+ href="http://www.apache.org/dist/xerces/c/";>main distribution
+ directory</jump>, rather than from a mirror. Then verify the
+ signatures using:</p>
+
+<source>
+% pgpk -a KEYS
+% pgpv <distribution-name>.asc
+</source>
+<p><em>or</em></p>
+<source>
+% pgp -ka KEYS
+% pgp <distribution-name>.asc
+</source>
+<p><em>or</em></p>
+<source>
+% gpg --import KEYS
+% gpg --verify <distribution-name>.asc
+</source>
+
+ <p>Alternatively, you can verify the digests on the files. A
+ command line program called <code>md5</code> or <code>md5sum</code>
+ is included in most UNXI distributions. It is also available as
+ part of <jump
href="http://www.gnu.org/software/textutils/textutils.html";>GNU
+ Textutils</jump>. Windows users can get binary md5 programs from <jump
+ href="http://www.fourmilab.ch/md5/";>here</jump>, <jump
+ href="http://www.pc-tools.net/win32/freeware/console/";>here</jump>, or
+ <jump href="http://www.slavasoft.com/fsum/";>here</jump>.</p>
+
+ </s2>
+
+</s1>
Propchange: xerces/c/trunk/doc/download.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/enumval.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/faq-build.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/faq-contributing.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/faq-distrib.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/faq-other.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/faq-parse.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: xerces/c/trunk/doc/feedback.xml
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/feedback.xml?rev=1799488&view=auto
==============================================================================
--- xerces/c/trunk/doc/feedback.xml (added)
+++ xerces/c/trunk/doc/feedback.xml Wed Jun 21 17:18:13 2017
@@ -0,0 +1,192 @@
+<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
+
+<s1 title="Feedback Procedures">
+ <s2 title="Questions or Comments">
+
+ <p>Please browse through this bundled documentation completely. Most of
+ the common questions have been answered in the FAQs. Browsing this
+ documentation may be the quickest way to get an answer. Of course, if
+ all else fails, as mentioned in the link above, you can post a question
+ to one of the <jump href="mailing-lists.html">&XercesCName; mailing
+ lists</jump>.</p> <p>See <jump href="bug-report.html">Bug
Reporting</jump>
+ if you would like to report a defect (which is greatly appreciated).</p>
+
+ </s2>
+
+ <s2 title="Acknowledgements">
+
+ <p>Ever since this source code base was initially created, many people
+ have helped to port the code to different platforms, and provided
+ patches for both new features and bug fixes.
+ </p>
+
+ <p>Listed below are some names (in alphabetical order) of people to
whom
+ we would like to give special thanks. </p>
+
+ <ul>
+ <li>Nadav Aharoni</li>
+ <li>Curt Arnold</li>
+ <li>Edward Avis</li>
+ <li>Anupam Bagchi</li>
+ <li>Torbjörn Bäckström</li>
+ <li>Abe Backus</li>
+ <li>Frank Balluffi</li>
+ <li>Matthew Baker</li>
+ <li>Devin Barnhart</li>
+ <li>James Berry</li>
+ <li>David Bertoni</li>
+ <li>John Bellardo</li>
+ <li>Arundhati Bhowmick</li>
+ <li>Joanne Bogart</li>
+ <li>Michael Boos</li>
+ <li>Edward Bortner</li>
+ <li>Sean Bright</li>
+ <li>Phil Brown</li>
+ <li>Robert Buck</li>
+ <li>Scott Cantor</li>
+ <li>David Cargill</li>
+ <li>Chris Cates</li>
+ <li>Gilbert Chan</li>
+ <li>Sumit Chawla</li>
+ <li>Nick Chiang</li>
+ <li>Chih Hsiang Chou</li>
+ <li>Radovan Chytracek</li>
+ <li>Hiram Clawson</li>
+ <li>John Clayton</li>
+ <li>Todd Collins</li>
+ <li>Nathan Codding</li>
+ <li>Michael Crawford</li>
+ <li>Murray Cumming</li>
+ <li>Zeid Derhally</li>
+ <li>James Devries</li>
+ <li>Ailian Ding</li>
+ <li>Steve Dulin</li>
+ <li>David Earlam</li>
+ <li>Helmut Eiken</li>
+ <li>Mark Everline</li>
+ <li>Andrew Fang</li>
+ <li>Simon Fell</li>
+ <li>Paul Ferguson</li>
+ <li>Greg Franks</li>
+ <li>Pierpaolo Fumagalli</li>
+ <li>Syam Gadde</li>
+ <li>Guido Gagliardi</li>
+ <li>Gary Gale</li>
+ <li>Michael Glavassevich</li>
+ <li>Natalie Gorden</li>
+ <li>Max Gotlib</li>
+ <li>Petr Gotthard</li>
+ <li>Neil Graham</li>
+ <li>Matthew Hall</li>
+ <li>Jay Hansen</li>
+ <li>Susan Hardenbrook</li>
+ <li>Jeff Harrell</li>
+ <li>Andrew Hefford</li>
+ <li>Adam Heinz</li>
+ <li>Andy Heninger</li>
+ <li>John Hibbert</li>
+ <li>William L. Hopper</li>
+ <li>Michael Huedepohl</li>
+ <li>Anders Hybertz</li>
+ <li>Rahul Jain</li>
+ <li>Tom Jordahl</li>
+ <li>Christopher Just</li>
+ <li>Martin Kalen</li>
+ <li>Joe Kesselman</li>
+ <li>John Kim</li>
+ <li>Artur Klauser</li>
+ <li>Bob Kline</li>
+ <li>Richard Ko</li>
+ <li>Boris Kolpackov</li>
+ <li>Paul Kramer</li>
+ <li>Volker Krause</li>
+ <li>Berin Lautenbach</li>
+ <li>Arnaud LeHors</li>
+ <li>Andy Levine</li>
+ <li>Jeff Lewis</li>
+ <li>James Littlejohn</li>
+ <li>Ray Logel</li>
+ <li>Pedro Lopes</li>
+ <li>Matt Lovett</li>
+ <li>Sean MacRoibeaird</li>
+ <li>Alberto Massari</li>
+ <li>Don Mastrovito</li>
+ <li>David McCreedy</li>
+ <li>Charles McLouth</li>
+ <li>Shin'ya Morino</li>
+ <li>Urs Muff</li>
+ <li>Jordan Naftolin</li>
+ <li>Tinny Ng</li>
+ <li>David Nickerson</li>
+ <li>Anton Nikolaevsky</li>
+ <li>Khaled Noaman</li>
+ <li>Michael Ottati</li>
+ <li>Anthony O'Dowd</li>
+ <li>Mike Pawlowski</li>
+ <li>Kevin Philips</li>
+ <li>Mike Pogue</li>
+ <li>Joe Polastre</li>
+ <li>John Ponzo</li>
+ <li>Vitaly Prapirny</li>
+ <li>Shengkai Qu</li>
+ <li>Gareth Reakes</li>
+ <li>Jim Reitz</li>
+ <li>Caroline Rioux</li>
+ <li>Dean Roddey</li>
+ <li>John Roper</li>
+ <li>Dan Rosen</li>
+ <li>Steven Rosenthal</li>
+ <li>Erik Rydgren</li>
+ <li>Markus Scherer</li>
+ <li>Bill Schindler</li>
+ <li>Erik Schroeder</li>
+ <li>Christian Schuhegger</li>
+ <li>Tobias Schuette</li>
+ <li>John Smirl</li>
+ <li>Andrei Smirnov</li>
+ <li>John Snelson</li>
+ <li>Gereon Steffens</li>
+ <li>Jason Stewart</li>
+ <li>Rick J. Stevens</li>
+ <li>Roman Sulzhyk</li>
+ <li>Linda M. Swan</li>
+ <li>Vasily Tchekalkin</li>
+ <li>Pieter Van-Dyck</li>
+ <li>Curtis Walker</li>
+ <li>John Warrier</li>
+ <li>Tom Watson</li>
+ <li>Mark Weaver</li>
+ <li>Roger Webster</li>
+ <li>Robert Weir</li>
+ <li>Axel Weiss</li>
+ <li>Carolyn Weiss</li>
+ <li>Christian Will</li>
+ <li>Kari Whitcomb</li>
+ <li>Dietrich Wolf</li>
+ <li>Kirk Wylie</li>
+ <li>Peter A. Volchek</li>
+ <li>Grace Yan</li>
+ <li>Hiramatsu Yoshifumi</li>
+ <li>PeiYong Zhang</li>
+ <li>Henry Zongaro</li>
+ </ul>
+ </s2>
+</s1>
Propchange: xerces/c/trunk/doc/feedback.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Propchange: xerces/c/trunk/doc/html/
------------------------------------------------------------------------------
--- svn:ignore (added)
+++ svn:ignore Wed Jun 21 17:18:13 2017
@@ -0,0 +1,3 @@
+*.html
+graphics
+resources
Modified: xerces/c/trunk/doc/html/ApacheDOMC++Binding.html
URL:
http://svn.apache.org/viewvc/xerces/c/trunk/doc/html/ApacheDOMC%2B%2BBinding.html?rev=1799488&r1=1799487&r2=1799488&view=diff
==============================================================================
--- xerces/c/trunk/doc/html/ApacheDOMC++Binding.html (original)
+++ xerces/c/trunk/doc/html/ApacheDOMC++Binding.html Wed Jun 21 17:18:13 2017
@@ -6868,7 +6868,7 @@ DOMXPathResult
<tr ALIGN=LEFT VALIGN=TOP>
<td ALIGN=CENTER><i><font color="#0086B2">
<font size=-1>
-Copyright © 1999-2014 The Apache Software Foundation. All Rights Reserved.
+Copyright © 1999-2017 The Apache Software Foundation. All Rights Reserved.
</font>
</font>
</i>
@@ -6882,4 +6882,4 @@ Copyright © 1999-2014 The Apache So
</body>
</html>
-
\ No newline at end of file
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
