Return-Path: <crossley@indexgeo.com.au>
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 70930 invoked from network); 7 Apr 2002 09:19:49 -0000
Received: from ptolemy.goulburn.net.au (203.28.11.5)
  by daedalus.apache.org with SMTP; 7 Apr 2002 09:19:49 -0000
Received: (qmail 19784 invoked from network); 7 Apr 2002 09:20:01 -0000
Received: from max-02-021.goulburn.net.au (HELO igacer) (203.28.11.217)
  by ptolemy.goulburn.net.au with SMTP; 7 Apr 2002 09:20:01 -0000
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Crossley <crossley@indexgeo.com.au>
Reply-To: crossley@indexgeo.com.au
To: forrest-dev@xml.apache.org
Subject: Re: Run, Forrest, run!
Date: Sun, 7 Apr 2002 19:19:14 +1000
X-Mailer: KMail [version 1.2]
References: <FDCEAB9D7DE70246A419ECF68553D10456B7D8@POSTMAN.flagship.ru>
 <001701c1dd75$fe5a56d0$670004c0@PC103>
In-Reply-To: <001701c1dd75$fe5a56d0$670004c0@PC103>
MIME-Version: 1.0
Message-Id: <02040719191400.05171@igacer>
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Nicola Ken Barozzi wrote:
> KPiroumian wrote:
> > > From: Steven Noels
> > > Apart from my proposition of having some less book-oriented
> > > sitemap-describing thing dispersed throughout the directory structure,
> > > please re-read my ideas in
> > > http://marc.theaimsgroup.com/?l=forrest-dev&m=101605443113305&w=2 and
> > > http://marc.theaimsgroup.com/?t=101637949200001&r=1&w=2
> > > concerning this ordering issue.
> 
> I just reread the thread, and I thought we agreed that defining the
> book by hand was ok.
> What we just need now is a way of aggregating all the books
> resursively in a single site index.

There is an existing sample in Cocoon that does this, aggregating
all the book.xml files into a ToC. You explicitly define the order of
each book.xml in the documentation sitemap (match=doclist).
There could easily be a better way, but that works OK. This
would get us by for now and support existing practise.
--David Crossley

> > Yes, I remember that discussion. But recent Nicola's updates
> > shows that we are back to the start point again, I mean same old
> > book.xml format. If you remember, I've created a document
> > oriented index file (in book/chapter/section format) to be used
> > with project documentation, but that idea also died.
> 
> Book.xml is what we have now and what other projects are using.
> 
> We have to support them for the transition, and making something equivalent
> to book.xml just with different names is going just to make it harder for us
> and the users with no gain.
> 
> Let's enhance what we have instead like we did with the document (and see my
> previous mail for the faq.)
> 
> > What about a dynamic book.xml? Say, a book.xml that contains also some
> > transformer tags for document sorting/filtering etc.? Book.xml format is
> > rather limiting without an intermediate transformation to add also book
> > sections/chapters to the navigation menu.
> > Example:
> >
> > <book-list>
> > <book src="doc1.xml">
> > <title><xdir:insert select="doc1.xml#/@title"</title>
> > <!-- Some tag to insert chapters and sections here -->
> > </book>
> > <book src="http://www... .doc2.xml">
> > <title>Some external book</title>
> > </book>
> > </book-list>
> 
> FS
> 
> This can be done automatically.
> 
> Content has to be defined in one place only, and the titles and sections are
> defined in the documents.
> I'm against putting this in the book, where it doesn't belong IMO as a
> concern.
> 
> --
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------