You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-cvs@xml.apache.org by nd...@apache.org on 2006/04/14 15:00:33 UTC
svn commit: r394079 - in /xml/commons/trunk: java/resolver.xml
src/documentation/content/xdocs/components/resolver/resolver-article.xml
src/documentation/content/xdocs/components/resolver/resolver-release-notes.xml
Author: ndw
Date: Fri Apr 14 06:00:32 2006
New Revision: 394079
URL: http://svn.apache.org/viewcvs?rev=394079&view=rev
Log:
Documentation build updates; added IDs to make warnings go away
Modified:
xml/commons/trunk/java/resolver.xml
xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-article.xml
xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-release-notes.xml
Modified: xml/commons/trunk/java/resolver.xml
URL: http://svn.apache.org/viewcvs/xml/commons/trunk/java/resolver.xml?rev=394079&r1=394078&r2=394079&view=diff
==============================================================================
--- xml/commons/trunk/java/resolver.xml (original)
+++ xml/commons/trunk/java/resolver.xml Fri Apr 14 06:00:32 2006
@@ -204,11 +204,14 @@
<!-- Copy the docs that Forrest built.
The top-level build has already executed the forrest site target. -->
+ <!-- Uhm, no. The forrest targets aren't actually working in the top-level
+ build; so let's not stop this target from working, eh?
+ ndw, 2006-04-14
<copy todir="${build.dir}/docs">
<fileset dir="${docs.site.dir}/components/resolver"
includes="resolver-*.html"/>
</copy>
-
+ -->
</target>
<target name="dist"
Modified: xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-article.xml
URL: http://svn.apache.org/viewcvs/xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-article.xml?rev=394079&r1=394078&r2=394079&view=diff
==============================================================================
--- xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-article.xml (original)
+++ xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-article.xml Fri Apr 14 06:00:32 2006
@@ -118,7 +118,8 @@
<copyright><year>2000</year><holder>Arbortext, Inc.</holder></copyright>
</articleinfo>
-<section><title>Finding Resources on the Net</title>
+<section id="s.finding.resources">
+<title>Finding Resources on the Net</title>
<para>It's very common for web resources to be related to other
resources: documents rely on DTDs and schemas, schemas are derived from
@@ -171,7 +172,8 @@
can be used to map public and system identifiers and other URIs to
local files (or just other URIs).</para>
-<section><title>Resolver Classes Version 1.1</title>
+<section id="s.resolver.classes.11">
+<title>Resolver Classes Version 1.1</title>
<para>The <ulink url="http://xml.apache.org/dist/xml/commons/" role="linktable" xreflabel="Resolver
Classes">Resolver classes</ulink> that are described
@@ -188,7 +190,8 @@
xreflabel="Apache XML Commons">Apache XML Commons</ulink> project.
</para>
-<section><title>Changes from Version 1.0</title>
+<section id="s.changes.from.10">
+<title>Changes from Version 1.0</title>
<para>See the
<ulink url="resolver-release-notes.html">release notes</ulink>.</para>
@@ -204,7 +207,7 @@
</section>
</section>
-<section>
+<section id="s.whats.wrong">
<title>What's Wrong with System Identifiers?</title>
<para>The problems associated with system identifiers (and URIs in general)
@@ -261,7 +264,7 @@
them, the situation is a little more irksome, but it can still be
addressed using a URI Resolver.</para>
</section>
-<section>
+<section id="s.naming.resources">
<title>Naming Resources</title>
<para>In some contexts, it's more useful to refer to a resource by
@@ -281,7 +284,7 @@
and the illusion of a stable name.</para>
</footnote>.</para>
-<section>
+<section id="s.public.ids">
<title>Public Identifiers</title>
<para>Public identifiers are part of <ulink url="http://www.w3.org/TR/REC-xml">XML
1.0</ulink>. They can occur in any form of external entity declaration. They
@@ -293,7 +296,7 @@
found, but it does uniquely name the resource. That public identifier, now
and forever refers to the XML version of DocBook V4.1.2.</para>
</section>
-<section>
+<section id="s.urns">
<title>Uniform Resource Names</title>
<para>URNs are a form of URI. Like public identifiers, they give a location-neutral,
globally unique name to an entity. For example, OASIS might choose to identify
@@ -304,7 +307,7 @@
<para>Like a public identifier, a URN can now and forever refer to a specific
entity in a location-independent manner.</para>
-<section><title>The publicid URN Namespace</title>
+<section id="s.publicid"><title>The publicid URN Namespace</title>
<para>Public identifiers don't fit very well into the web architecture
(they are not, for example, always valid URIs). This problem can be
@@ -318,7 +321,7 @@
</section>
</section>
</section>
-<section>
+<section id="s.resolving.names">
<title>Resolving Names</title>
<para>Having extolled the virtues of location-independent names, it must be
said that a name isn't very useful if you can't find the thing it refers to.
@@ -345,12 +348,13 @@
</listitem>
</itemizedlist>
</section>
-<section>
+<section id="s.catalog.files">
<title>Catalog Files</title>
<para>Catalog files are straightforward text files that describe a mapping
from names to addresses. Here's a simple one:</para>
-<example><title>An Example Catalog File</title>
+<example id="ex.catalog">
+<title>An Example Catalog File</title>
<programlisting><![CDATA[<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
<public publicId="-//OASIS//DTD XML DocBook V4.1.2//EN"
@@ -375,7 +379,7 @@
catalog file unless I encounter a public identifier that I reasonably expect
to find there.</para>
</section>
-<section>
+<section id="s.understanding">
<title>Understanding Catalog Files</title>
<para>The OASIS <ulink
@@ -596,12 +600,12 @@
</variablelist>
</section>
-<section><title>XCatalogs</title>
+<section id="xcatalogs"><title>XCatalogs</title>
<para>The Resolver classes also understand the XCatalog format supported
by Apache.</para>
</section>
-<section><title>Resolution Semantics</title>
+<section id="s.res.semantics"><title>Resolution Semantics</title>
<para>Resolution is performed in roughly the following way:
</para>
@@ -725,7 +729,8 @@
<para>My <filename>CatalogManager.properties</filename> file looks like
this:</para>
-<example><title>Example CatalogManager.properties File</title>
+<example id="ex.catalogmanager.properties">
+<title>Example CatalogManager.properties File</title>
<programlisting>#CatalogManager.properties
verbosity=1
@@ -747,7 +752,7 @@
</section>
-<section>
+<section id="s.using.catalogs">
<title>Using Catalogs with Popular Applications</title>
<para>A number of popular applications provide easy access to catalog
@@ -790,7 +795,7 @@
</variablelist>
</section>
-<section>
+<section id="s.adding.catalog.support">
<title>Adding Catalog Support to Your Applications</title>
<para>If you work with Java applications using a parser that supports
@@ -828,14 +833,14 @@
addition to the system catalogs.</para>
</section>
-<section>
+<section id="s.catalogs.in.action">
<title>Catalogs In Action</title>
<para>The Resolver distribution includes a couple of test programs,
<command>resolver</command> and <command>xparse</command>,
that you can use to see how this all works.</para>
-<section>
+<section id="s.using.resolver">
<title>Using <command>resolver</command></title>
<para>The <command>resolver</command> application simply performs a
@@ -868,7 +873,7 @@
</example>
</section>
-<section>
+<section id="s.using.xparse">
<title>Using <command>xparse</command></title>
<para>The
@@ -934,7 +939,7 @@
</section>
</section>
-<section>
+<section id="s.conclusions">
<title>May All Your Names Resolve Successfully!</title>
<para>We hope that these classes become a standard part of your
Modified: xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-release-notes.xml
URL: http://svn.apache.org/viewcvs/xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-release-notes.xml?rev=394079&r1=394078&r2=394079&view=diff
==============================================================================
--- xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-release-notes.xml (original)
+++ xml/commons/trunk/src/documentation/content/xdocs/components/resolver/resolver-release-notes.xml Fri Apr 14 06:00:32 2006
@@ -51,7 +51,7 @@
package since the 1.0 release.
</para>
-<section>
+<section id="s.catalogmanager.not.static">
<title>The <classname>CatalogManager</classname> Is No Longer Static</title>
<para>The most pervasive change is that the <classname>CatalogManager</classname>
@@ -66,7 +66,7 @@
</section>
-<section>
+<section id="s.system.cats.loaded">
<title>System Catalogs Are Always Loaded</title>
<para>In the previous version, the system catalogs were not loaded if
@@ -80,7 +80,7 @@
</section>
-<section>
+<section id="s.tests">
<title>Tests/Examples Available</title>
<para>There are several tests in the <filename>tests/resolver</filename> directory
@@ -88,7 +88,7 @@
</section>
-<section>
+<section id="s.bootstrap">
<title>Bootstrap resolver for loading catalog files</title>
<para>The resolver now includes catalog.{dtd,rng,xsd} and uses a "bootstrap"
resolver when it is loading catalog files. This avoids the Catch-22 of