Author: desruisseaux
Date: Thu May 26 17:41:25 2016
New Revision: 1745630
URL: http://svn.apache.org/viewvc?rev=1745630&view=rev
Log:
Reduce the use of upper-case in titles for making clearer the user of accronym
of class names.
Modified:
sis/site/trunk/book/en/annexes.html
sis/site/trunk/book/en/coverage.html
sis/site/trunk/book/en/geometry.html
sis/site/trunk/book/en/introduction.html
sis/site/trunk/book/en/utility.html
sis/site/trunk/book/en/xml.html
sis/site/trunk/content/book/en/developer-guide.html
Modified: sis/site/trunk/book/en/annexes.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/book/en/annexes.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/book/en/annexes.html (original)
+++ sis/site/trunk/book/en/annexes.html Thu May 26 17:41:25 2016
@@ -39,7 +39,7 @@
The following sections provide some tip for easing this task.
</p>
- <h3 id="UML-annotation-indep">Mapping Given by <code>@UML</code>
Annotations</h3>
+ <h3 id="UML-annotation-indep">Mapping given by <code>@UML</code>
annotations</h3>
<p>
For each class, method and constant defined by an <abbr>OGC</abbr> or
<abbr>ISO</abbr> standard,
GeoAPI indicates its provenance using annotations defined in the
<code>org.opengis.annotation</code> package.
@@ -79,7 +79,7 @@ System.out.println("The GeoAPI interface
- <h3 id="ServiceLoader">Fetching implementations of GeoAPI Interfaces</h3>
+ <h3 id="ServiceLoader">Fetching implementations of GeoAPI interfaces</h3>
<p>
GeoAPI defines factories (<code>Factory</code>) that can create
implementations of interfaces.
For example, <code>DatumFactory</code> provides methods that can create
instances which implement interfaces of the
@@ -114,7 +114,7 @@ public class MyApplication {
- <h4 id="GeoAPI-simple">Defining Custom Implementations</h4>
+ <h4 id="GeoAPI-simple">Defining custom implementations</h4>
<p>
Implementing GeoAPI oneself in order to meet very specific needs is not
difficult.
A developer might concentrate on a handful of interfaces among the
hundreds available,
@@ -226,7 +226,7 @@ public class MyApplication {
- <h3 id="GeoAPI-validators">Instance Validations</h3>
+ <h3 id="GeoAPI-validators">Instance validations</h3>
<p>
GeoAPI can validate an instance of its interfaces by checking that
certain constraints are observed.
Many constraints can not be expressed in the method signature. Those
constraints
@@ -312,7 +312,7 @@ public class MyTest {
- <h3 id="GeoAPI-tests">Executing Pre-defined Tests</h3>
+ <h3 id="GeoAPI-tests">Executing pre-defined tests</h3>
<p>
JUnit tests are defined in the <code>org.opengis.test</code>
sub-packages.
All test classes bear a name ending in "<code>Test</code>".
Modified: sis/site/trunk/book/en/coverage.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/book/en/coverage.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/book/en/coverage.html (original)
+++ sis/site/trunk/book/en/coverage.html Thu May 26 17:41:25 2016
@@ -22,12 +22,12 @@
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Data Coverages</title>
+ <title>Data coverages</title>
<link rel="stylesheet" type="text/css" href="../book.css"/>
</head>
<body>
<header>
- <h1 id="Coverage">Data Coverages</h1>
+ <h1 id="Coverage">Data coverages</h1>
</header>
<p>
Images, or <i>rasters</i>, are a particular case of a data structure
called a <i>coverage</i>.
@@ -75,7 +75,7 @@
<code>CV_DiscreteCoverage</code> type.
</p>
<aside>
- <h2>SIS's <code>Range</code> Class and its Relationship to the
Standards</h2>
+ <h2>SIS's <code>Range</code> class and its relationship to the
standards</h2>
<p>
The distinction between the ranges of all types of values and the
ranges of numeric values is represented in
<abbr>SIS</abbr> by the <code>Range</code> and <code>NumberRange</code>
Modified: sis/site/trunk/book/en/geometry.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/book/en/geometry.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/book/en/geometry.html (original)
+++ sis/site/trunk/book/en/geometry.html Thu May 26 17:41:25 2016
@@ -36,7 +36,7 @@
- <h2 id="Geometry-root">Base Classes</h2>
+ <h2 id="Geometry-root">Base classes</h2>
<p>
Each geometric object is considered an infinite set of points.
As a set, their most fundamental operations are of the same nature as
the standard operations of Java collections.
@@ -58,7 +58,7 @@
- <h3 id="DirectPosition">Direct Points and Positions</h3>
+ <h3 id="DirectPosition">Direct points and positions</h3>
<p>
<abbr>ISO</abbr> 19107 defines two types of structures to represent a
point:
<code>GM_Point</code> and <code class="OGC">DirectPosition</code>.
@@ -111,7 +111,7 @@
- <h4 id="AntiMeridian">Envelopes that Cross the Antimeridian</h4>
+ <h4 id="AntiMeridian">Envelopes that cross the antimeridian</h4>
<p>
Minimums and maximums are the values most often assigned to <code
class="OGC">lowerCorner</code>
and <code class="OGC">upperCorner</code>.
@@ -159,7 +159,7 @@
<code>org.apache.sis.geometry</code> package perform their calculations
according to this convention.
</p>
<aside>
- <h5>Generalizing to Other Types of Axes</h5>
+ <h5>Generalizing to other types of axes</h5>
<p>
This section specifically relates to longitude, as it is the most
usual example of a cyclic axis.
However, in Apache <abbr>SIS</abbr> envelopes, there is no explicit
mention of longitude, or of its 360° cycle.
@@ -188,7 +188,7 @@
<cite><i>upper</i></cite> values.
</p>
<aside>
- <h5>The Special Case of the Range [+0 â¦Â -0]</h5>
+ <h5>The special case of [+0 â¦Â -0] range</h5>
<p>
Java (or more generally, IEEE Standard 754) defines two values
distinct from zero:
a positive zero and a negative zero. These two values are considered
equal when we compare them with the <code>==</code> operator in Java.
Modified: sis/site/trunk/book/en/introduction.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/book/en/introduction.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/book/en/introduction.html (original)
+++ sis/site/trunk/book/en/introduction.html Thu May 26 17:41:25 2016
@@ -22,12 +22,12 @@
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Standards and Norms</title>
+ <title>Standards and norms</title>
<link rel="stylesheet" type="text/css" href="../book.css"/>
</head>
<body>
<header>
- <h1 id="Standards">Standards and Norms</h1>
+ <h1 id="Standards">Standards and norms</h1>
</header>
<p>
A geospatial information community is a collection of systems or
individuals capable of exchanging their geospatial data
@@ -72,7 +72,7 @@
- <h2 id="ConceptualModels">Sources of Conceptual Models used by Apache
SIS</h2>
+ <h2 id="ConceptualModels">Sources of conceptual models used by Apache
SIS</h2>
<p>
Most standards used by Apache <abbr>SIS</abbr> have been devised by the
<a href="http://www.opengeospatial.org";>Open Geospatial Consortium</a>
(<abbr>OGC</abbr>),
sometimes in collaboration with the <a
href="http://www.iso.org";>International Organization for Standardization</a>
(<abbr>ISO</abbr>).
@@ -103,7 +103,7 @@
<summary>More about standardization process</summary>
<article id="OGC-process">
<header>
- <h1><abbr>OGC</abbr> Standardization Process</h1>
+ <h1><abbr>OGC</abbr> standardization process</h1>
</header>
<p>
The work of the <abbr title="Open Geospatial Consortium">OGC</abbr>
is done by email, teleconferences, and at <a
href="http://www.opengeospatial.org/event?category=ogctcpc";>in-person
meetings</a>.
@@ -119,7 +119,7 @@
while <abbr>SWG</abbr>s require that their participants enter into
an agreement not to hinder the distribution of the standard through
intellectual property claims.
</p>
- <h2 id="OGC-SWG">Standard Working Group (<abbr>SWG</abbr>)
Procedures</h2>
+ <h2 id="OGC-SWG">Standard Working Group (<abbr>SWG</abbr>)
procedures</h2>
<p>
In order to be accepted, a standardization project must be supported
by a minimum number of members belonging to distinct organizations.
These founding members draft a charter defining the objectives of
the <abbr>SWG</abbr>,
@@ -162,7 +162,7 @@
and certain <abbr>OGC</abbr> standards become <abbr>ISO</abbr>
standards.
</p>
- <h2 id="OGC-RFC">Procedure for the Submission of Proposals for
Modification</h2>
+ <h2 id="OGC-RFC">Procedure for the submission of proposals for
modification</h2>
<p>
All users, whether or not they are members of the Open Geospatial
Consortium, may propose modifications to <abbr>OGC</abbr> standards.
A list of current proposals for changes, along with a form for
submitting new proposals, is <a
href="http://www.opengeospatial.org/standards/cr";>available online</a>.
@@ -412,7 +412,7 @@
- <h2 id="GeoAPI">From Conceptual Models to Java Interfaces: GeoAPI</h2>
+ <h2 id="GeoAPI">From conceptual models to Java interfaces: GeoAPI</h2>
<p>
The <a href="http://www.geoapi.org";>GeoAPI</a> project offers a set of
Java interfaces for geospatial applications.
In a series of <code>org.opengis.*</code> packages, GeoAPI defines
structures representing metadata,
@@ -621,7 +621,7 @@
<details>
<summary>More about GeoAPI modules</summary>
<article id="GeoAPI-modules">
- <h1>GeoAPI Modules</h1>
+ <h1>GeoAPI modules</h1>
<p>
The GeoAPI project consists of a standardized part
(<code>geoapi</code>)
and an experimental part (<code>geoapi-pending</code>).
@@ -680,7 +680,7 @@
- <h3 id="UML-annotation">Explicit Mapping Given by <code>@UML</code>
Annotations</h3>
+ <h3 id="UML-annotation">Explicit mapping given by <code>@UML</code>
annotations</h3>
<p>
For each class, method and constant defined by an <abbr>OGC</abbr> or
<abbr>ISO</abbr> standard,
GeoAPI indicates its provenance using annotations defined in the
<code>org.opengis.annotation</code> package.
@@ -728,7 +728,7 @@ System.out.println("Standard name of typ
- <h3 id="MappingToJDK">Implicit Mapping to Standard <abbr>JDK</abbr></h3>
+ <h3 id="MappingToJDK">Implicit mapping to standard <abbr>JDK</abbr></h3>
<p>
Some classes and methods have neither an <code>@UML</code> annotation,
nor an entry in the <code class="GeoAPI">class-index.properties</code> file.
They are either extensions of GeoAPI, or else types defined in other
libraries, such as standard <abbr title="Java Development Kit">JDK</abbr>.
@@ -957,7 +957,7 @@ assert MediumName.<code class="GeoAPI">v
- <h2 id="About">Conventions Used in This Guide</h2>
+ <h2 id="About">Conventions used in this guide</h2>
<p>
Standards sometimes favour the application of certain generic terms to
particular contexts,
which may differ from the context in which other communities use these
terms.
@@ -978,7 +978,7 @@ assert MediumName.<code class="GeoAPI">v
- <h3 id="CodeColors">Code Colors</h3>
+ <h3 id="CodeColors">Code colors</h3>
<p>
The elements defined in a computer language, such as classes and methods
in Java or elements in an <abbr>XML</abbr> document,
appear in monospaced font.
Modified: sis/site/trunk/book/en/utility.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/book/en/utility.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/book/en/utility.html (original)
+++ sis/site/trunk/book/en/utility.html Thu May 26 17:41:25 2016
@@ -22,19 +22,19 @@
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Utility Classes and Methods</title>
+ <title>Utility classes and methods</title>
<link rel="stylesheet" type="text/css" href="../book.css"/>
</head>
<body>
<header>
- <h1 id="Utilities">Utility Classes and Methods</h1>
+ <h1 id="Utilities">Utility classes and methods</h1>
</header>
<p>
This chapter describes aspects of Apache <abbr>SIS</abbr> that apply to
the entire library.
Most of these utilities are not specific to spatial information systems.
</p>
- <h2 id="ComparisonMode">Comparison Modes of Objects</h2>
+ <h2 id="ComparisonMode">Comparison modes of objects</h2>
<p>
There are various opinions on how to implement Java standard's
<code>Object.equals(Object)</code> method.
According to some, it should be possible to compare different
implementations of the same interface or base class.
@@ -119,7 +119,7 @@
The approach used also determines whether it is possible to share the
same instance of an object for all languages.
</p>
- <h3 id="LocalizedString">Distinct Character Sequences for Each Locale</h3>
+ <h3 id="LocalizedString">Distinct character sequences for each locale</h3>
<p>
Some classes are only designed to function according to one locale
convention at a time.
This is of course true for the standard implementations of
<code>java.text.Format</code>,
@@ -186,7 +186,7 @@
- <h3 id="Locale.ROOT"><code>Locale.ROOT</code> Convention</h3>
+ <h3 id="Locale.ROOT"><code>Locale.ROOT</code> convention</h3>
<p>
All <abbr>SIS</abbr> methods receiving or returning the value of a
<code>Locale</code> type accept the <code>Locale.ROOT</code> value.
This value is interpreted as specifying not to localize the text.
@@ -212,7 +212,7 @@
- <h3 id="UnicodePoint">Treatment of Characters</h3>
+ <h3 id="UnicodePoint">Treatment of characters</h3>
<p>
In Java, sequences of characters use UTF-16 encoding.
There is a direct correspondence between the values of the
<code>char</code> type and the great majority of characters,
@@ -259,7 +259,7 @@
- <h4 id="Whitespaces">The Interpretation of Blank Spaces</h4>
+ <h4 id="Whitespaces">Blank spaces interpretation</h4>
<p>
Standard Java provides two methods for determining whether a character
is a blank space:
<code>Character.isWhitespace(â¦)</code> and
<code>Character.isSpaceChar(â¦)</code>.
Modified: sis/site/trunk/book/en/xml.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/book/en/xml.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/book/en/xml.html (original)
+++ sis/site/trunk/book/en/xml.html Thu May 26 17:41:25 2016
@@ -22,12 +22,12 @@
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
- <title>Representing Objects in XML</title>
+ <title>Representing objects in XML</title>
<link rel="stylesheet" type="text/css" href="../book.css"/>
</head>
<body>
<header>
- <h1 id="XML-ISO">Representing Objects in <abbr>XML</abbr></h1>
+ <h1 id="XML-ISO">Representing objects in <abbr>XML</abbr></h1>
</header>
<p>
Objects defined by <abbr>OGC</abbr>/<abbr>ISO</abbr> standards must be
able to communicate with remote machines via the Internet,
@@ -91,7 +91,7 @@
</table>
<aside>
- <h2>Tools for Reading and Writing <abbr>XML</abbr> Documents</h2>
+ <h2>Tools for reading and writing <abbr>XML</abbr> documents</h2>
<p>
Apache <abbr>SIS</abbr> uses different libraries to read and write
different types of objects.
The library used depends on the complexity of the object and on
performance constraints.
@@ -119,7 +119,7 @@
- <h2 id="XML-ISO-19115">Representing Metadata According to <abbr>ISO</abbr>
19115-3</h2>
+ <h2 id="XML-ISO-19115">Representing metadata according to <abbr>ISO</abbr>
19115-3</h2>
<p>
For each metadata class, there is an <abbr>XML</abbr> type with the same
name than in the abstract specification
(for example, <code>gmd:MD_Metadata</code> and
<code>gmd:CI_Citation</code>).
@@ -200,14 +200,14 @@
</p>
<aside>
- <h3>Implementation Strategy in Apache <abbr>SIS</abbr></h3>
+ <h3>Implementation strategy in Apache <abbr>SIS</abbr></h3>
<p>
<code>org.apache.sis.internal.jaxb.*</code> packages (non-public)
define <abbr>JAXB</abbr> adaptors for all types of <abbr>ISO</abbr> objects.
These adaptors are required anyway to allow <abbr>JAXB</abbr> to get
<abbr>SIS</abbr> classes while implementing GeoAPI interfaces.
Conveniently, <abbr>SIS</abbr> made both <abbr>JAXB</abbr> adaptors
and objects wrapping the ârealâ object to be read or written.
This double usage avoids having to double the number of classes
(already quite high) present in the internal packages.
</p>
- <h4>Naming Conventions in <abbr>XSD</abbr> Schemas</h4>
+ <h4>Naming conventions in <abbr>XSD</abbr> schemas</h4>
<p>
For each element of the first group listed above, the <abbr>XSD</abbr>
schemas of the <abbr>OGC</abbr>
define a type whose name ends with â<code
class="OGC">_PropertyType</code>â.
@@ -221,7 +221,7 @@
</aside>
- <h3 id="gco-id">Identification of Already-Defined Instances</h3>
+ <h3 id="gco-id">Identification of already-defined instances</h3>
<p>
The parent element may contain an <code class="OGC">id</code> or <code
class="OGC">uuid</code> attribute.
If one of these attributes is present, the parent attribute may be
completely omitted;
@@ -304,7 +304,7 @@ public class MyClass {
- <h3 id="nilReason">Representing Missing Values</h3>
+ <h3 id="nilReason">Representing missing values</h3>
<p>
When a property is not defined, the corresponding GeoAPI method usually
returns <code>null</code>.
However, things become complicated when the missing property is a value
considered mandatory by <abbr>ISO</abbr> 19115 standard.
Modified: sis/site/trunk/content/book/en/developer-guide.html
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/book/en/developer-guide.html?rev=1745630&r1=1745629&r2=1745630&view=diff
==============================================================================
--- sis/site/trunk/content/book/en/developer-guide.html (original)
+++ sis/site/trunk/content/book/en/developer-guide.html Thu May 26 17:41:25 2016
@@ -26,57 +26,57 @@
<p><b style="font-size: 20pt">Table of content</b></p>
<nav>
<ul class="toc">
-<li><a href="#Standards">Standards and Norms</a><ul>
-<li><a href="#ConceptualModels">Sources of Conceptual Models used by Apache
SIS</a></li>
-<li><a href="#GeoAPI">From Conceptual Models to Java Interfaces: GeoAPI</a><ul>
-<li><a href="#UML-annotation">Explicit Mapping Given by @UML
Annotations</a></li>
-<li><a href="#MappingToJDK">Implicit Mapping to Standard JDK</a></li>
+<li><a href="#Standards">Standards and norms</a><ul>
+<li><a href="#ConceptualModels">Sources of conceptual models used by Apache
SIS</a></li>
+<li><a href="#GeoAPI">From conceptual models to Java interfaces: GeoAPI</a><ul>
+<li><a href="#UML-annotation">Explicit mapping given by @UML
annotations</a></li>
+<li><a href="#MappingToJDK">Implicit mapping to standard JDK</a></li>
<li><a href="#GeoAPI-implementation">Implementations provided by Apache
SIS</a></li></ul></li>
-<li><a href="#About">Conventions Used in This Guide</a><ul>
-<li><a href="#CodeColors">Code Colors</a></li></ul></li></ul></li>
-<li><a href="#Utilities">Utility Classes and Methods</a><ul>
-<li><a href="#ComparisonMode">Comparison Modes of Objects</a></li>
+<li><a href="#About">Conventions used in this guide</a><ul>
+<li><a href="#CodeColors">Code colors</a></li></ul></li></ul></li>
+<li><a href="#Utilities">Utility classes and methods</a><ul>
+<li><a href="#ComparisonMode">Comparison modes of objects</a></li>
<li><a href="#Internationalization">Internationalization</a><ul>
-<li><a href="#LocalizedString">Distinct Character Sequences for Each
Locale</a></li>
+<li><a href="#LocalizedString">Distinct character sequences for each
locale</a></li>
<li><a href="#InternationalString">Single instance for all supported
locales</a></li>
-<li><a href="#Locale.ROOT">Locale.ROOT Convention</a></li>
-<li><a href="#UnicodePoint">Treatment of Characters</a><ul>
-<li><a href="#Whitespaces">The Interpretation of Blank
Spaces</a></li></ul></li></ul></li></ul></li>
+<li><a href="#Locale.ROOT">Locale.ROOT convention</a></li>
+<li><a href="#UnicodePoint">Treatment of characters</a><ul>
+<li><a href="#Whitespaces">Blank spaces
interpretation</a></li></ul></li></ul></li></ul></li>
<li><a href="#Geometry">Geometries</a><ul>
-<li><a href="#Geometry-root">Base Classes</a><ul>
-<li><a href="#DirectPosition">Direct Points and Positions</a></li>
+<li><a href="#Geometry-root">Base classes</a><ul>
+<li><a href="#DirectPosition">Direct points and positions</a></li>
<li><a href="#Envelope">Envelopes</a><ul>
-<li><a href="#AntiMeridian">Envelopes that Cross the
Antimeridian</a></li></ul></li></ul></li></ul></li>
-<li><a href="#Coverage">Data Coverages</a></li>
-<li><a href="#XML-ISO">Representing Objects in XML</a><ul>
-<li><a href="#XML-ISO-19115">Representing Metadata According to ISO
19115-3</a><ul>
-<li><a href="#gco-id">Identification of Already-Defined Instances</a></li>
-<li><a href="#nilReason">Representing Missing
Values</a></li></ul></li></ul></li>
+<li><a href="#AntiMeridian">Envelopes that cross the
antimeridian</a></li></ul></li></ul></li></ul></li>
+<li><a href="#Coverage">Data coverages</a></li>
+<li><a href="#XML-ISO">Representing objects in XML</a><ul>
+<li><a href="#XML-ISO-19115">Representing metadata according to ISO
19115-3</a><ul>
+<li><a href="#gco-id">Identification of already-defined instances</a></li>
+<li><a href="#nilReason">Representing missing
values</a></li></ul></li></ul></li>
<li><a href="#Annexes">Annexes</a><ul>
<li><a href="#ReduceDependency">Reduce direct dependency to Apache SIS</a><ul>
-<li><a href="#UML-annotation-indep">Mapping Given by @UML Annotations</a></li>
-<li><a href="#ServiceLoader">Fetching implementations of GeoAPI
Interfaces</a><ul>
-<li><a href="#GeoAPI-simple">Defining Custom
Implementations</a></li></ul></li></ul></li>
+<li><a href="#UML-annotation-indep">Mapping given by @UML annotations</a></li>
+<li><a href="#ServiceLoader">Fetching implementations of GeoAPI
interfaces</a><ul>
+<li><a href="#GeoAPI-simple">Defining custom
implementations</a></li></ul></li></ul></li>
<li><a href="#Tests">Test suites</a><ul>
-<li><a href="#GeoAPI-validators">Instance Validations</a></li>
-<li><a href="#GeoAPI-tests">Executing Pre-defined
Tests</a></li></ul></li></ul></li>
+<li><a href="#GeoAPI-validators">Instance validations</a></li>
+<li><a href="#GeoAPI-tests">Executing pre-defined
tests</a></li></ul></li></ul></li>
</ul>
</nav>
<main>
<section>
<header>
-<h1 id="Standards"><span class="section-number">1.</span> Standards and
Norms</h1>
+<h1 id="Standards"><span class="section-number">1.</span> Standards and
norms</h1>
<nav><div class="chapter-links"><div class="next-chapter"><a
href="#Utilities">Next chapter</a> â¡</div></div></nav>
</header>
<nav>In this chapter:<ul class="toc">
-<li><a href="#ConceptualModels">Sources of Conceptual Models used by Apache
SIS</a></li>
-<li><a href="#GeoAPI">From Conceptual Models to Java Interfaces: GeoAPI</a><ul>
-<li><a href="#UML-annotation">Explicit Mapping Given by @UML
Annotations</a></li>
-<li><a href="#MappingToJDK">Implicit Mapping to Standard JDK</a></li>
+<li><a href="#ConceptualModels">Sources of conceptual models used by Apache
SIS</a></li>
+<li><a href="#GeoAPI">From conceptual models to Java interfaces: GeoAPI</a><ul>
+<li><a href="#UML-annotation">Explicit mapping given by @UML
annotations</a></li>
+<li><a href="#MappingToJDK">Implicit mapping to standard JDK</a></li>
<li><a href="#GeoAPI-implementation">Implementations provided by Apache
SIS</a></li></ul></li>
-<li><a href="#About">Conventions Used in This Guide</a><ul>
-<li><a href="#CodeColors">Code Colors</a></li></ul></li></ul></nav>
+<li><a href="#About">Conventions used in this guide</a><ul>
+<li><a href="#CodeColors">Code colors</a></li></ul></li></ul></nav>
<p>
A geospatial information community is a collection of systems or individuals
capable of exchanging their geospatial data
through the use of common standards, allowing them to communicate with one
another.
@@ -120,7 +120,7 @@ but which risk to hit them before the en
-<h2 id="ConceptualModels"><span class="section-number">1.1.</span> Sources of
Conceptual Models used by Apache SIS</h2>
+<h2 id="ConceptualModels"><span class="section-number">1.1.</span> Sources of
conceptual models used by Apache SIS</h2>
<p>
Most standards used by Apache <abbr title="Spatial Information
System">SIS</abbr> have been devised by the <a
href="http://www.opengeospatial.org";>Open Geospatial Consortium</a>
(<abbr>OGC</abbr>),
sometimes in collaboration with the <a href="http://www.iso.org";>International
Organization for Standardization</a> (<abbr>ISO</abbr>).
@@ -151,7 +151,7 @@ Such voluntary compliance with these spe
<summary>More about standardization process</summary>
<article id="OGC-process">
<header>
-<h1><abbr>OGC</abbr> Standardization Process</h1>
+<h1><abbr>OGC</abbr> standardization process</h1>
</header>
<p>
The work of the <abbr title="Open Geospatial Consortium">OGC</abbr> is done by
email, teleconferences, and at <a
href="http://www.opengeospatial.org/event?category=ogctcpc";>in-person
meetings</a>.
@@ -167,7 +167,7 @@ A working group is proposed as a <i>Doma
while <abbr>SWG</abbr>s require that their participants enter into an
agreement not to hinder the distribution of the standard through intellectual
property claims.
</p>
-<h2 id="OGC-SWG">Standard Working Group (<abbr>SWG</abbr>) Procedures</h2>
+<h2 id="OGC-SWG">Standard Working Group (<abbr>SWG</abbr>) procedures</h2>
<p>
In order to be accepted, a standardization project must be supported by a
minimum number of members belonging to distinct organizations.
These founding members draft a charter defining the objectives of the
<abbr>SWG</abbr>,
@@ -210,7 +210,7 @@ the <abbr>OGC</abbr> adopts the <abbr>IS
and certain <abbr>OGC</abbr> standards become <abbr>ISO</abbr> standards.
</p>
-<h2 id="OGC-RFC">Procedure for the Submission of Proposals for
Modification</h2>
+<h2 id="OGC-RFC">Procedure for the submission of proposals for
modification</h2>
<p>
All users, whether or not they are members of the Open Geospatial Consortium,
may propose modifications to <abbr title="Open Geospatial
Consortium">OGC</abbr> standards.
A list of current proposals for changes, along with a form for submitting new
proposals, is <a href="http://www.opengeospatial.org/standards/cr";>available
online</a>.
@@ -460,7 +460,7 @@ Finally, GeoAPI packages will be introdu
-<h2 id="GeoAPI"><span class="section-number">1.2.</span> From Conceptual
Models to Java Interfaces: GeoAPI</h2>
+<h2 id="GeoAPI"><span class="section-number">1.2.</span> From conceptual
models to Java interfaces: GeoAPI</h2>
<p>
The <a href="http://www.geoapi.org";>GeoAPI</a> project offers a set of Java
interfaces for geospatial applications.
In a series of <code class="GeoAPI">org.opengis.*</code> packages, GeoAPI
defines structures representing metadata,
@@ -669,7 +669,7 @@ However, we can get an overview of its c
<details>
<summary>More about GeoAPI modules</summary>
<article id="GeoAPI-modules">
-<h1>GeoAPI Modules</h1>
+<h1>GeoAPI modules</h1>
<p>
The GeoAPI project consists of a standardized part (<code
class="GeoAPI">geoapi</code>)
and an experimental part (<code class="GeoAPI">geoapi-pending</code>).
@@ -728,7 +728,7 @@ Apache <abbr>SIS</abbr> uses them to tes
-<h3 id="UML-annotation"><span class="section-number">1.2.1.</span> Explicit
Mapping Given by <code class="GeoAPI">@UML</code> Annotations</h3>
+<h3 id="UML-annotation"><span class="section-number">1.2.1.</span> Explicit
mapping given by <code class="GeoAPI">@UML</code> annotations</h3>
<p>
For each class, method and constant defined by an <abbr title="Open Geospatial
Consortium">OGC</abbr> or <abbr>ISO</abbr> standard,
GeoAPI indicates its provenance using annotations defined in the <code
class="GeoAPI">org.opengis.annotation</code> package.
@@ -776,7 +776,7 @@ provided in a <a href="#UML-annotation-g
-<h3 id="MappingToJDK"><span class="section-number">1.2.2.</span> Implicit
Mapping to Standard <abbr>JDK</abbr></h3>
+<h3 id="MappingToJDK"><span class="section-number">1.2.2.</span> Implicit
mapping to standard <abbr>JDK</abbr></h3>
<p>
Some classes and methods have neither an <code class="GeoAPI">@UML</code>
annotation, nor an entry in the <code
class="GeoAPI">class-index.properties</code> file.
They are either extensions of GeoAPI, or else types defined in other
libraries, such as standard <abbr title="Java Development Kit">JDK</abbr>.
@@ -1005,7 +1005,7 @@ However such instantiations should be do
-<h2 id="About"><span class="section-number">1.3.</span> Conventions Used in
This Guide</h2>
+<h2 id="About"><span class="section-number">1.3.</span> Conventions used in
this guide</h2>
<p>
Standards sometimes favour the application of certain generic terms to
particular contexts,
which may differ from the context in which other communities use these terms.
@@ -1026,7 +1026,7 @@ in order to reduce the risk of confusion
-<h3 id="CodeColors"><span class="section-number">1.3.1.</span> Code Colors</h3>
+<h3 id="CodeColors"><span class="section-number">1.3.1.</span> Code colors</h3>
<p>
The elements defined in a computer language, such as classes and methods in
Java or elements in an <abbr>XML</abbr> document,
appear in monospaced font.
@@ -1057,23 +1057,23 @@ Text in gray boxes are for information p
</section>
<section>
<header>
-<h1 id="Utilities"><span class="section-number">2.</span> Utility Classes and
Methods</h1>
+<h1 id="Utilities"><span class="section-number">2.</span> Utility classes and
methods</h1>
<nav><div class="chapter-links"><div class="previous-chapter">â¬
<a
href="#Standards">Previous chapter</a></div><div class="next-chapter"><a
href="#Geometry">Next chapter</a> â¡</div></div></nav>
</header>
<nav>In this chapter:<ul class="toc">
-<li><a href="#ComparisonMode">Comparison Modes of Objects</a></li>
+<li><a href="#ComparisonMode">Comparison modes of objects</a></li>
<li><a href="#Internationalization">Internationalization</a><ul>
-<li><a href="#LocalizedString">Distinct Character Sequences for Each
Locale</a></li>
+<li><a href="#LocalizedString">Distinct character sequences for each
locale</a></li>
<li><a href="#InternationalString">Single instance for all supported
locales</a></li>
-<li><a href="#Locale.ROOT">Locale.ROOT Convention</a></li>
-<li><a href="#UnicodePoint">Treatment of Characters</a><ul>
-<li><a href="#Whitespaces">The Interpretation of Blank
Spaces</a></li></ul></li></ul></li></ul></nav>
+<li><a href="#Locale.ROOT">Locale.ROOT convention</a></li>
+<li><a href="#UnicodePoint">Treatment of characters</a><ul>
+<li><a href="#Whitespaces">Blank spaces
interpretation</a></li></ul></li></ul></li></ul></nav>
<p>
This chapter describes aspects of Apache <abbr title="Spatial Information
System">SIS</abbr> that apply to the entire library.
Most of these utilities are not specific to spatial information systems.
</p>
-<h2 id="ComparisonMode"><span class="section-number">2.1.</span> Comparison
Modes of Objects</h2>
+<h2 id="ComparisonMode"><span class="section-number">2.1.</span> Comparison
modes of objects</h2>
<p>
There are various opinions on how to implement Java standard's
<code>Objectâ.equals(Object)</code> method.
According to some, it should be possible to compare different implementations
of the same interface or base class.
@@ -1158,7 +1158,7 @@ or at the level of the objects that crea
The approach used also determines whether it is possible to share the same
instance of an object for all languages.
</p>
-<h3 id="LocalizedString"><span class="section-number">2.2.1.</span> Distinct
Character Sequences for Each Locale</h3>
+<h3 id="LocalizedString"><span class="section-number">2.2.1.</span> Distinct
character sequences for each locale</h3>
<p>
Some classes are only designed to function according to one locale convention
at a time.
This is of course true for the standard implementations of
<code>java.text.Format</code>,
@@ -1225,7 +1225,7 @@ so sharing a single instance becomes eve
-<h3 id="Locale.ROOT"><span class="section-number">2.2.3.</span>
<code>Locale.ROOT</code> Convention</h3>
+<h3 id="Locale.ROOT"><span class="section-number">2.2.3.</span>
<code>Locale.ROOT</code> convention</h3>
<p>
All <abbr title="Spatial Information System">SIS</abbr> methods receiving or
returning the value of a <code>Locale</code> type accept the
<code>Locale.ROOT</code> value.
This value is interpreted as specifying not to localize the text.
@@ -1251,7 +1251,7 @@ use of exponential notation and the abse
-<h3 id="UnicodePoint"><span class="section-number">2.2.4.</span> Treatment of
Characters</h3>
+<h3 id="UnicodePoint"><span class="section-number">2.2.4.</span> Treatment of
characters</h3>
<p>
In Java, sequences of characters use UTF-16 encoding.
There is a direct correspondence between the values of the <code>char</code>
type and the great majority of characters,
@@ -1298,7 +1298,7 @@ even if some may be present in the seque
-<h4 id="Whitespaces"><span class="section-number">2.2.4.1.</span> The
Interpretation of Blank Spaces</h4>
+<h4 id="Whitespaces"><span class="section-number">2.2.4.1.</span> Blank spaces
interpretation</h4>
<p>
Standard Java provides two methods for determining whether a character is a
blank space:
<code>Characterâ.isWhitespace(â¦)</code> and
<code>Characterâ.isSpaceChar(â¦)</code>.
@@ -1335,10 +1335,10 @@ or the use of <code>isWhitespace(â¦)
<nav><div class="chapter-links"><div class="previous-chapter">â¬
<a
href="#Utilities">Previous chapter</a></div><div class="next-chapter"><a
href="#Coverage">Next chapter</a> â¡</div></div></nav>
</header>
<nav>In this chapter:<ul class="toc">
-<li><a href="#Geometry-root">Base Classes</a><ul>
-<li><a href="#DirectPosition">Direct Points and Positions</a></li>
+<li><a href="#Geometry-root">Base classes</a><ul>
+<li><a href="#DirectPosition">Direct points and positions</a></li>
<li><a href="#Envelope">Envelopes</a><ul>
-<li><a href="#AntiMeridian">Envelopes that Cross the
Antimeridian</a></li></ul></li></ul></li></ul></nav>
+<li><a href="#AntiMeridian">Envelopes that cross the
antimeridian</a></li></ul></li></ul></li></ul></nav>
<p>
This chapter introduces a few aspects of <abbr title="International
Organization for Standardization">ISO</abbr> 19107 standard (<i>Spatial
schema</i>)
and the Apache <abbr title="Spatial Information System">SIS</abbr> classes
that implement them.
@@ -1346,7 +1346,7 @@ and the Apache <abbr title="Spatial Info
-<h2 id="Geometry-root"><span class="section-number">3.1.</span> Base
Classes</h2>
+<h2 id="Geometry-root"><span class="section-number">3.1.</span> Base
classes</h2>
<p>
Each geometric object is considered an infinite set of points.
As a set, their most fundamental operations are of the same nature as the
standard operations of Java collections.
@@ -1368,7 +1368,7 @@ prefix (as prescribed in GeoAPI conventi
-<h3 id="DirectPosition"><span class="section-number">3.1.1.</span> Direct
Points and Positions</h3>
+<h3 id="DirectPosition"><span class="section-number">3.1.1.</span> Direct
points and positions</h3>
<p>
<abbr title="International Organization for Standardization">ISO</abbr> 19107
defines two types of structures to represent a point:
<code class="OGC">GM_Point</code> and <code class="OGC">DirectPosition</code>.
@@ -1421,7 +1421,7 @@ The expressions <i>lower corner</i> and
-<h4 id="AntiMeridian"><span class="section-number">3.1.2.1.</span> Envelopes
that Cross the Antimeridian</h4>
+<h4 id="AntiMeridian"><span class="section-number">3.1.2.1.</span> Envelopes
that cross the antimeridian</h4>
<p>
Minimums and maximums are the values most often assigned to <code
class="OGC">lowerCorner</code>
and <code class="OGC">upperCorner</code>.
@@ -1468,7 +1468,7 @@ All the <code class="SIS">add(â¦)</c
<code class="SIS">org.apache.sis.geometry</code> package perform their
calculations according to this convention.
</p>
<aside>
-<h5>Generalizing to Other Types of Axes</h5>
+<h5>Generalizing to other types of axes</h5>
<p>
This section specifically relates to longitude, as it is the most usual
example of a cyclic axis.
However, in Apache <abbr title="Spatial Information System">SIS</abbr>
envelopes, there is no explicit mention of longitude, or of its 360° cycle.
@@ -1497,7 +1497,7 @@ coordinates within the desired limits, s
<cite><i>upper</i></cite> values.
</p>
<aside>
-<h5>The Special Case of the Range [+0 â¦Â -0]</h5>
+<h5>The special case of [+0 â¦Â -0] range</h5>
<p>
Java (or more generally, IEEE Standard 754) defines two values distinct from
zero:
a positive zero and a negative zero. These two values are considered equal
when we compare them with the <code>==</code> operator in Java.
@@ -1514,7 +1514,7 @@ then it is guaranteed that the envelope
</section>
<section>
<header>
-<h1 id="Coverage"><span class="section-number">4.</span> Data Coverages</h1>
+<h1 id="Coverage"><span class="section-number">4.</span> Data coverages</h1>
<nav><div class="chapter-links"><div class="previous-chapter">â¬
<a
href="#Geometry">Previous chapter</a></div><div class="next-chapter"><a
href="#XML-ISO">Next chapter</a> â¡</div></div></nav>
</header>
<nav>In this chapter:<ul class="toc"/></nav>
@@ -1564,7 +1564,7 @@ Thus, since interpolations are only poss
<code class="OGC">CV_DiscreteCoverage</code> type.
</p>
<aside>
-<h2>SIS's <code class="SIS">Range</code> Class and its Relationship to the
Standards</h2>
+<h2>SIS's <code class="SIS">Range</code> class and its relationship to the
standards</h2>
<p>
The distinction between the ranges of all types of values and the ranges of
numeric values is represented in
<abbr title="Spatial Information System">SIS</abbr> by the <code
class="SIS">Range</code> and <code class="SIS">NumberRange</code>
@@ -1585,13 +1585,13 @@ as well as other information such as <i>
</section>
<section>
<header>
-<h1 id="XML-ISO"><span class="section-number">5.</span> Representing Objects
in <abbr>XML</abbr></h1>
+<h1 id="XML-ISO"><span class="section-number">5.</span> Representing objects
in <abbr>XML</abbr></h1>
<nav><div class="chapter-links"><div class="previous-chapter">â¬
<a
href="#Coverage">Previous chapter</a></div><div class="next-chapter"><a
href="#Annexes">Next chapter</a> â¡</div></div></nav>
</header>
<nav>In this chapter:<ul class="toc">
-<li><a href="#XML-ISO-19115">Representing Metadata According to ISO
19115-3</a><ul>
-<li><a href="#gco-id">Identification of Already-Defined Instances</a></li>
-<li><a href="#nilReason">Representing Missing
Values</a></li></ul></li></ul></nav>
+<li><a href="#XML-ISO-19115">Representing metadata according to ISO
19115-3</a><ul>
+<li><a href="#gco-id">Identification of already-defined instances</a></li>
+<li><a href="#nilReason">Representing missing
values</a></li></ul></li></ul></nav>
<p>
Objects defined by <abbr title="Open Geospatial Consortium">OGC</abbr>/<abbr
title="International Organization for Standardization">ISO</abbr> standards
must be able to communicate with remote machines via the Internet,
using different software written in different languages.
@@ -1654,7 +1654,7 @@ These prefixes are defined in the <code
</table>
<aside>
-<h2>Tools for Reading and Writing <abbr>XML</abbr> Documents</h2>
+<h2>Tools for reading and writing <abbr>XML</abbr> documents</h2>
<p>
Apache <abbr title="Spatial Information System">SIS</abbr> uses different
libraries to read and write different types of objects.
The library used depends on the complexity of the object and on performance
constraints.
@@ -1682,7 +1682,7 @@ when the <abbr>XML</abbr> elements do no
-<h2 id="XML-ISO-19115"><span class="section-number">5.1.</span> Representing
Metadata According to <abbr title="International Organization for
Standardization">ISO</abbr> 19115-3</h2>
+<h2 id="XML-ISO-19115"><span class="section-number">5.1.</span> Representing
metadata according to <abbr title="International Organization for
Standardization">ISO</abbr> 19115-3</h2>
<p>
For each metadata class, there is an <abbr>XML</abbr> type with the same name
than in the abstract specification
(for example, <code class="OGC">gmd:MD_Metadata</code> and <code
class="OGC">gmd:CI_Citation</code>).
@@ -1763,14 +1763,14 @@ These classes may be ignored, unless the
</p>
<aside>
-<h3>Implementation Strategy in Apache <abbr title="Spatial Information
System">SIS</abbr></h3>
+<h3>Implementation strategy in Apache <abbr title="Spatial Information
System">SIS</abbr></h3>
<p>
<code class="SIS">org.apache.sis.internal.jaxb.*</code> packages (non-public)
define <abbr title="Java Architecture for XML Binding">JAXB</abbr> adaptors for
all types of <abbr title="International Organization for
Standardization">ISO</abbr> objects.
These adaptors are required anyway to allow <abbr>JAXB</abbr> to get
<abbr>SIS</abbr> classes while implementing GeoAPI interfaces.
Conveniently, <abbr>SIS</abbr> made both <abbr>JAXB</abbr> adaptors and
objects wrapping the ârealâ object to be read or written.
This double usage avoids having to double the number of classes (already quite
high) present in the internal packages.
</p>
-<h4>Naming Conventions in <abbr title="XML Schema Definition">XSD</abbr>
Schemas</h4>
+<h4>Naming conventions in <abbr title="XML Schema Definition">XSD</abbr>
schemas</h4>
<p>
For each element of the first group listed above, the <abbr>XSD</abbr> schemas
of the <abbr title="Open Geospatial Consortium">OGC</abbr>
define a type whose name ends with â<code
class="OGC">_PropertyType</code>â.
@@ -1784,7 +1784,7 @@ These attributes do not have dedicated J
</aside>
-<h3 id="gco-id"><span class="section-number">5.1.1.</span> Identification of
Already-Defined Instances</h3>
+<h3 id="gco-id"><span class="section-number">5.1.1.</span> Identification of
already-defined instances</h3>
<p>
The parent element may contain an <code class="OGC">id</code> or <code
class="OGC">uuid</code> attribute.
If one of these attributes is present, the parent attribute may be completely
omitted;
@@ -1867,7 +1867,7 @@ where all types of identifiers (not only
-<h3 id="nilReason"><span class="section-number">5.1.2.</span> Representing
Missing Values</h3>
+<h3 id="nilReason"><span class="section-number">5.1.2.</span> Representing
missing values</h3>
<p>
When a property is not defined, the corresponding GeoAPI method usually
returns <code>null</code>.
However, things become complicated when the missing property is a value
considered mandatory by <abbr title="International Organization for
Standardization">ISO</abbr> 19115 standard.
@@ -1925,12 +1925,12 @@ But when a <code class="OGC">nilReason</
</header>
<nav>In this chapter:<ul class="toc">
<li><a href="#ReduceDependency">Reduce direct dependency to Apache SIS</a><ul>
-<li><a href="#UML-annotation-indep">Mapping Given by @UML Annotations</a></li>
-<li><a href="#ServiceLoader">Fetching implementations of GeoAPI
Interfaces</a><ul>
-<li><a href="#GeoAPI-simple">Defining Custom
Implementations</a></li></ul></li></ul></li>
+<li><a href="#UML-annotation-indep">Mapping given by @UML annotations</a></li>
+<li><a href="#ServiceLoader">Fetching implementations of GeoAPI
interfaces</a><ul>
+<li><a href="#GeoAPI-simple">Defining custom
implementations</a></li></ul></li></ul></li>
<li><a href="#Tests">Test suites</a><ul>
-<li><a href="#GeoAPI-validators">Instance Validations</a></li>
-<li><a href="#GeoAPI-tests">Executing Pre-defined
Tests</a></li></ul></li></ul></nav>
+<li><a href="#GeoAPI-validators">Instance validations</a></li>
+<li><a href="#GeoAPI-tests">Executing pre-defined
tests</a></li></ul></li></ul></nav>
<h2 id="ReduceDependency"><span class="section-number">6.1.</span> Reduce
direct dependency to Apache SIS</h2>
<p>
Previous chapters used Apache SIS static methods for convenience.
@@ -1941,7 +1941,7 @@ However this may require that applicatio
The following sections provide some tip for easing this task.
</p>
-<h3 id="UML-annotation-indep"><span class="section-number">6.1.1.</span>
Mapping Given by <code class="GeoAPI">@UML</code> Annotations</h3>
+<h3 id="UML-annotation-indep"><span class="section-number">6.1.1.</span>
Mapping given by <code class="GeoAPI">@UML</code> annotations</h3>
<p>
For each class, method and constant defined by an <abbr title="Open Geospatial
Consortium">OGC</abbr> or <abbr title="International Organization for
Standardization">ISO</abbr> standard,
GeoAPI indicates its provenance using annotations defined in the <code
class="GeoAPI">org.opengis.annotation</code> package.
@@ -1981,7 +1981,7 @@ The <code class="SIS">org.apache.sis.uti
-<h3 id="ServiceLoader"><span class="section-number">6.1.2.</span> Fetching
implementations of GeoAPI Interfaces</h3>
+<h3 id="ServiceLoader"><span class="section-number">6.1.2.</span> Fetching
implementations of GeoAPI interfaces</h3>
<p>
GeoAPI defines factories (<code class="GeoAPI">Factory</code>) that can create
implementations of interfaces.
For example, <code class="GeoAPI">DatumFactory</code> provides methods that
can create instances which implement interfaces of the
@@ -2016,7 +2016,7 @@ for example when multiple libraries coex
-<h4 id="GeoAPI-simple"><span class="section-number">6.1.2.1.</span> Defining
Custom Implementations</h4>
+<h4 id="GeoAPI-simple"><span class="section-number">6.1.2.1.</span> Defining
custom implementations</h4>
<p>
Implementing GeoAPI oneself in order to meet very specific needs is not
difficult.
A developer might concentrate on a handful of interfaces among the hundreds
available,
@@ -2128,7 +2128,7 @@ since <code class="GeoAPI">geoapi-confor
-<h3 id="GeoAPI-validators"><span class="section-number">6.2.1.</span> Instance
Validations</h3>
+<h3 id="GeoAPI-validators"><span class="section-number">6.2.1.</span> Instance
validations</h3>
<p>
GeoAPI can validate an instance of its interfaces by checking that certain
constraints are observed.
Many constraints can not be expressed in the method signature. Those
constraints
@@ -2214,7 +2214,7 @@ This approach requires the creation of a
-<h3 id="GeoAPI-tests"><span class="section-number">6.2.2.</span> Executing
Pre-defined Tests</h3>
+<h3 id="GeoAPI-tests"><span class="section-number">6.2.2.</span> Executing
pre-defined tests</h3>
<p>
JUnit tests are defined in the <code class="GeoAPI">org.opengis.test</code>
sub-packages.
All test classes bear a name ending in "<code>Test</code>".
