libreccm-legacy/ccm-shp-aplaws/doc/app-schemas/app-schemas.htmc

142 lines
3.0 KiB
Plaintext
Executable File

<html>
<head>
<!-- WARNING -->
<title>APLAWS-II: Application Schemas</title>
<style>
.schema {
border: 1px solid black;
margin: 1em;
padding: 1em;
background: rgb(192,230,230);
}
</style>
</head>
<body bgcolor="white" text="black">
<h1>APLAWS-II: Application Schemas</h1>
<p>
<big><strong><em>Final 1 November 2003</em></strong></big>
</p>
<!-- TABLE OF CONTENTS -->
<!-- SECTION Introduction -->
<p>
This document provides the XML Schemas for the principle public facing
applications in APLAWS. The schemas describe the XML that is generated
by UI components prior to being fed into the XSLT transformer. Since the
precise combination of components that can be present in a particular
JSP page can vary from install to install, these schemas don't document
an entire page, but rather, each individual component that can be plugged
into a page.
</p>
<p>
The official specification for XML schemas can be found at the
<a href="http://www.w3.org/XML/Schema">W3C</a> site. For a gentler introduction, the O'Reilly
<a href="http://www.oreilly.com/catalog/xmlschema/">XML Schema book</a> is recommended reading.
</p>
<!-- SECTION Navigation -->
<p>
Category navigation components may be present on any
page in the site, since they provide things such as
the list of top level categories, breadcrumb trail,
etc.
</p>
<pre class="schema">
<!-- INSERT navigation.xsd -->
</pre>
<!-- SECTION Directory -->
<p>
The directory page in APLAWS, commonly found at /content/directory.jsp
contains a summary of top two levels of navigation categories.
</p>
<pre class="schema">
<!-- INSERT directory.xsd -->
</pre>
<!-- SECTION Services -->
<p>
The services page in APLAWS, commonly found at /content/services.jsp,
is little more than a placeholder for designers to hook on to.
</p>
<pre class="schema">
<!-- INSERT services.xsd -->
</pre>
<!-- SECTION Site Map -->
<p>
The sitemap page in APLAWS, commonly found at /content/sitemap.jsp
is little more than a placeholder for designers to hook on to.
</p>
<pre class="schema">
<!-- INSERT sitemap.xsd -->
</pre>
<!-- SECTION Portals -->
<p>
The portals schema describes the generic framework for browsing
workspaces &amp; portals. Each portlet type will have its own schema
to describe what XML it generates.
</p>
<pre class="schema">
<!-- INSERT portal.xsd -->
</pre>
<!-- SECTION Forums -->
<p>
The schema for forums only describes the components that are used to
present information about messages. It does not cover the Bebop forms
and administrative UI components.
</p>
<pre class="schema">
<!-- INSERT forum.xsd -->
</pre>
<!-- SECTION Search -->
<p>
The schema for search describes the XML document used to represent
the result list and the filter metadata which can be used to build
a query form in HTML.
</p>
<pre class="schema">
<!-- INSERT search.xsd -->
</pre>
<!-- SECTION A-Z -->
<p>
The A-Z application is a framework for providing a list of
topics and items paginated by letter.
</p>
<pre class="schema">
<!-- INSERT atoz.xsd -->
</pre>
<!-- FOOTER Daniel Berrange (berrange@redhat.com) -->
</body>
</html>