Re: [generguide-devel] Processing modular documentation - some concerns

[Cameron S. <ca...@sh...>]

On Friday 29 Aug 2003 6:07 pm, Artur Hefczyc wrote:
> Hi,
>
> I just finished my fights with joining parts of modular documentation
> to one XML document with use of
> Java tools (both xalan and saxon) and xinclude.xsl.

Excellent!!

> It works very well and I would like to describe it somewhere
> but I am not sure where.
> Of course it make sense to describe in this document not
> only how to process modular documentation with java+
> xicnlude.xsl but also how to use other tools xslproc, xmltools,
> xincluder and so on...
>
> There are some possibilities:
> 1. basic.xml (But is this basic xml processing?)
> 2. documentation.xml (But this document describes rather concept
>     but technical information.)
> 3. new document (Similar as entitiesuse.xml)
> 4. Or some other place I couldn't find.
> Have you any idea and suggestions?

I suggest it should go into the Documentation section, under "Publishing 
docbook files".  You will already see a section here which would be outdated 
with your new work.
http://generguide.sourceforge.net/developersguide/developersguide.html#publishingdocbook

>
> Another concern is about our definition of xinclude.mod.
> Our current declaration looks as follows:
> <!ENTITY % xinclude
> PUBLIC "-//NONAME//ELEMENTS DocBook XInclude extension//EN"
> "xinclude.mod">
>
> I propose to change it to something like:
> <!ENTITY % xinclude
> PUBLIC "-//GenerGuide//ELEMENTS SDocBook XInclude extension V1.0//EN"
> "http://generguide.sourceforge.net/xinclude/1.0/xinclude.mod">
> The most important change is to make it available by HTTP url rather that
> as a file on local file system.
> 1. xinclude.mod will be officially available on the net
> 2. All tools parsing xml files containing xinclude element can download
>     this definition at any time, so user don't need to take care about it
>     unless he wants to speed processing up and store all DTDs locally.
> 3. Generic Guide will become some kind of owner of this definition what
>     make it easier to contact in a case when someone find bug or has a
> question related to this definition.

Yes, this sounds reasonable.  (I don't understand what these references mean, 
but your suggestions sound like they would work and I trust your judgement 
enough that I'm happy not to find out.)


-- 
Cameron Shorter              http://cameron.shorter.net
Open Source Developer        http://generguide.sourceforge.net
                             http://mapbuilder.sourceforge.net
                             http://geotools.org
Senior Software Engineer     http://www.adi-limited.com