stefano 2002/07/01 12:58:09
Modified: src/documentation/xdocs/userdocs/concepts sitemap.xml
Log:
this document was created out of the sitemap draft we used to share
around the mail list for development. I don't think we need that wording anymore.
Revision Changes Path
1.9 +9 -47
xml-cocoon2/src/documentation/xdocs/userdocs/concepts/sitemap.xml
Index: sitemap.xml
===================================================================
RCS file:
/home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/concepts/sitemap.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- sitemap.xml 1 Jul 2002 08:55:24 -0000 1.8
+++ sitemap.xml 1 Jul 2002 19:58:09 -0000 1.9
@@ -17,34 +17,17 @@
<s1 title="The Sitemap">
<s2 title="Introduction">
<p>
- This document is used as a working draft for
- Apache Cocoon architects to understand the issues associated with
- sitemaps and XML publishing in general. It must be considered as a working
- draft and may be updated at any time.
+ This document describes the Cocoon sitemap concept in full details, why
+ it's there, what it does, how it works and how you can use it.
</p>
- <p>
+ <note>
See the <link href="../index.html">User documentation</link>
for details about configuration of each sitemap component.
See the <link href="sitemap-examples.html">Example sitemap snippets</link>.
Explore each <code>sitemap.xmap</code> in the distribution, to see
how the various situations are handled.
- </p>
-
- <p>
- This document is based on ideas and design patterns inspired by Stefano
- Mazzocchi ([EMAIL PROTECTED]) and Pierpaolo Fumagalli ([EMAIL PROTECTED])
- but grew as a collaborative effort to provide a solid foundation of
- design patterns and usability guidelines to create a solid foundation
- of sitemap programmability and usability to the Cocoon Publishing
- Framework.
- </p>
-
- <p>
- This is one of the few examples where open source is transformed into
- "open development" leading both the implementation and the pure research
- around software development and usability.
- </p>
+ </note>
</s2>
<s2 title="Goals">
@@ -99,9 +82,7 @@
The Sitemap has the following general structure:
</p>
- <source>
-<![CDATA[
- <?xml version="1.0"?>
+ <source><![CDATA[<?xml version="1.0"?>
<map:sitemap
xmlns:map="http://apache.org/cocoon/sitemap/1.0";>
@@ -110,18 +91,12 @@
<map:resources/>
<map:action-sets/>
<map:pipelines/>
- </map:sitemap>
-]]>
- </source>
+ </map:sitemap>]]></source>
</s2>
<s2 title="The <map:sitemap>">
- <source>
-<![CDATA[
- <map:sitemap
- xmlns:map="http://apache.org/cocoon/sitemap/1.0";>
-]]>
- </source>
+ <source><![CDATA[<map:sitemap
+ xmlns:map="http://apache.org/cocoon/sitemap/1.0";>]]></source>
<p>
The default namespaces are used mainly for versioning, instead of using
@@ -407,20 +382,7 @@
<s2 title="The <map:resources>">
<p>
The <code><map:resource></code> element is used as a placeholder for
pipelines
- that are used several times inside the document. This element
- is redundant and its functionality is not directly related
- to the sitemap, but could be cloned by the use of internal
- XInclude, for example
- </p>
-
- <p>
- <code><xinclude:include href="#xpointer(resource[@name='Access
refused'])"/></code>
- </p>
-
- <p>
- but given the usability constraints and very specific operation
- it is much easier to include such an element instead of forcing
- the use of xinclude/xpointer.
+ that are used several times inside the document.
</p>
<source>
<![CDATA[
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
