forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-forrest/src/documentation/content/xdocs uri-namespace.xml
Date Tue, 12 Nov 2002 10:53:44 GMT
stevenn     2002/11/12 02:53:44

  Added:       src/documentation/content/xdocs uri-namespace.xml
  something which has been laying around on my harddisk for much too long time
  please expand!
  Revision  Changes    Path
  1.1                  xml-forrest/src/documentation/content/xdocs/uri-namespace.xml
  Index: uri-namespace.xml
  <?xml version="1.0"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
      <title>URI namespace description</title> 
      <subtitle>Background reading for the Forrest sitemap</subtitle> 
      <authors><person name="Steven Noels" email=""/></authors>
      <abstract>This document describes the URI request namespace as being
        declared and supported by Forrest. Its concrete implementation can be found in
        Forrest's Cocoon sitemap.</abstract> 
      <p>Since Forrest uses Cocoon as its documentation generation mechanism, it
        ships with a Cocoon
    stating the so-called URI namespace being declared by Forrest. So this document
    serves as a background reader for people trying to understand the sitemap and
    the internal workings of the Cocoon link crawling. It should answer questions
    like "what kind of resources can I add to my project documentation" and "how
    should I specify my links inside my documents so that they are correctly
    processed by Forrest". This doesn't mean your HTML hypertext writing skills of
    the past will not help you anymore while creating documents to be processed by
    Forrest, but since Cocoon is a less forgiving (read: "best practices
    enforcing") hypertext processing environment than the Web, there is a need for
    an authorative source on URIs in the Forrest space. This document is meant to
    be that source.</p> 
      <title>URI hierarchy</title> 
        <p><strong>Network protocol</strong> Currently, the only network
          that can be used to access Forrest resources is <em>HTTP</em>. Of course,
          can embed hypertext references to other protocols (<code>news:</code>,
          <code>mailto:</code>, ...), but these links are not processed by the
        <p><strong>Host</strong> Forrest publishes its generated documentation
          some server, so part of the URI namespace is the <em>host address</em>,
          <code></code>,<code>intranetsrv2</code> or
        <p><strong>Mountpoint</strong> Similar to so-called Java Web
          Applications, a Forrest website URI is often prepended with a
          <em>mountpoint</em>, indicating the root of the website shouldn't be
found on
          <code>http://somehost/</code>, but on <code>http://somehost/mountpoint/</code>
          instead. Declaring a mountpoint is <em>optional</em> however.</p>

        <p>Both <code>host</code> and <code>mountpoint</code>
are passed into the
          Forrest processing pipeline as Cocoon sitemap parameters and subsequently as
          XSLT parameters too, which means they are accessible to skin designers. They
          should be declared like:</p> 
          <li><strong>host:</strong> <code></code>
          <li><strong>mountpoint:</strong> <code>forrest</code>
            hence no trailing slash!)</em></li> 
        <p>Forrest will add slashes in-between if needed.</p> 
        <note>It is currently undefined how these parameters will be configured
          when running Forrest. This can be done using Ant-filtered copying of the
          sitemap, or using some to-be-created Cocoon CLIInputModule.</note>
        <p>Adding documents to your local documentation fileset means they will
          become available across Forrest too. There exists however a naming convention
          for a number of 'special' documents, which has to be taken into account.
          Furthermore, Forrest adds a number of autogenerated resources.</p>
          <title><code> (empty URI)</code></title>
          <p>This URI is automatically redirected (server-side) to
            <code>index.xml</code>. It serves as the root of your documentation
      <title>Media types</title> 
      <p>Forrest is able to explicitely process the following media types:</p>

          <td>Plain web pages (default rendition format)</td> 
          <td>Acrobat files</td> 
          <td>Portable Network Graphic files (preferred image format)</td> 
          <td>Compuserve GIF graphics</td> 
          <td>JPEG graphics</td> 
          <td>Scalable Vector Graphics</td> 
          <td>plain text documents</td> 
          <td>compressed file archive</td> 
          <td>'tape' archives</td> 
          <td>compressed tar file archives</td> 
          <td>compressed tar file archives</td> 
          <td>Java application archives</td> 
          <td>Java web application archives</td> 
          <td>Java enterprise application archives</td> 

View raw message