[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: DOCBOOK: full recursive docbook
On Mon, Mar 17, 2003 at 03:14:57PM +0100, Frédéric Glorieux wrote: > By advance thanks for your reactivity. > > I need to propose a schema for an organisation > They have probably a few hundred thousands of documents (size of an > article) in various forms, not often XML (a nightmare). Docbook seems to > answer most of their needs. > > Object of this question: > > One law of their systems is the fully recursive linking from an article > to children. > The tree could be very long (It's about architectural heritage) > One example from one of their orgdiv > country/region/department/city/monuments/monument/monument-part/objects/ > object/object-part > Sometimes it's full path, sometimes not, sometimes other paths. > > They would like to keep publishing abilities at each point, to > any depth. Be able to build valid docbook everywhere could be nice. > > Is there an already docbook solution for such a problem? > If not, I got a partial proposition but... You can set up modular docbook files using recursive 'section' elements. You can use XInclude to assemble them as needed. You can use olinks to form links between them. The olink database (an XML file) can also be used as a database of content that can be machine processed to build a container document that assembles the content you want. Any children would also be made into nested container documents. For example: <?xml version="1.0"?> <!DOCTYPE section PUBLIC ...> <section id="startingpoint"> <title>Starting point</title> <para>Stuff for this starting file</para> <xi:include href="firstchild.xml" xmlns:xi="..." /> <xi:include href="secondchild.xml" xmlns:xi="..." /> ... </section> and each of firstchild.xml etc. would also be similarly assembled. With such deep nesting, you will likely run into issues of how to format titles for very deep hierarchies. The current XSL stylesheets only go about 6 levels deep. See the following doc for more on modular docbook: http://www.sagehill.net/xml/docbookxsl/ModularDoc.html http://www.sagehill.net/xml/docbookxsl/Olinking.html Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bobs@sco.com Received: (qmail 25522 invoked by uid 60881); 20 Mar 2003 13:40:52 -0000 Received: from robert@cogent.ca by hermes by uid 0 with qmail-scanner-1.15 (spamassassin: 2.43. Clear:SA:0(-1.7/8.0):. Processed in 0.209897 secs); 20 Mar 2003 13:40:52 -0000 X-Spam-Status: No, hits=-1.7 required=8.0 Received: from unknown (HELO fep02-mail.bloor.is.net.cable.rogers.com) (66.185.86.72) by mail.oasis-open.org with SMTP; 20 Mar 2003 13:40:52 -0000 Received: from bob.cogentrts.com ([65.49.162.248]) by fep02-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20030320134809.YXQZ311274.fep02-mail.bloor.is.net.cable.rogers.com@bob.cogentrts.com> for <docbook@lists.oasis-open.org>; Thu, 20 Mar 2003 08:48:09 -0500 Date: Thu, 20 Mar 2003 08:51:01 -0500 From: Robert McIlvride <robert@cogent.ca> To: docbook@lists.oasis-open.org Subject: Re: [docbook] DocBook Technical Committee Meeting Minutes: 18 Mar 2003 Message-Id: <20030320085101.132c2e18.robert@cogent.ca> In-Reply-To: <3E79B776.2070800@fillmore-labs.com> References: <5.2.0.9.2.20030318210126.0271e830@pop3.Nildram.co.uk> <87of48wxm9.fsf@nwalsh.com> <87u1e2jhuu.fsf@nwalsh.com> <87of48wxm9.fsf@nwalsh.com> <5.2.0.9.2.20030318210126.0271e830@pop3.Nildram.co.uk> <5.2.0.9.2.20030319172452.022ec408@pop3.Nildram.co.uk> <3E79B776.2070800@fillmore-labs.com> Organization: Cogent Real-Time Systems, Inc. X-Mailer: Sylpheed version 0.7.5 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep02-mail.bloor.is.net.cable.rogers.com from [65.49.162.248] using ID <robertmc95@rogers.com> at Thu, 20 Mar 2003 08:48:09 -0500 Yet another 2 cents (Canadian, at that :-) This thread has been quite entertaining and educational. I appreciate the desire to make things easy to learn, but in light of the paradigm shift that must take place when moving from HTML to DocBook, learning a few more (meaningful) tagnames and how to apply them (within their consistent framework) seems inconsequential, as Mr. Kosek has pointed out. I would agree more with the arguments in favor of the simplicity of supporting one table model, of aiming for 100% consistency (for <title> etc.), and of having meaningful tagnames. I notice that most members of the committee are "willing" to include the XHTML table model, but that wording gives me the feeling that not all of them are demanding it. It wouldn't hurt or help me very much if the TC agreed to include the XHTML model, but I don't think it's vitally necessary, nor do I believe it to be particularly consistent with the intent of DocBook. Cheerio! Bob --------------------------------------- Robert McIlvride (robert@cogent.ca) Cogent Real-Time Systems (www.cogent.ca)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]