On 31/10/2007, Dave Pawson <davep@d...> wrote:
> Jonathan Robie wrote:
> > Harbarth, Juliane wrote:
> >> So my plan is as follows:
> >> 1. Assemble a first preliminary book as one XML file and check that the
> >> stylesheet nicely renders it.
> >> 2. Hack it into pieces (forming a tree if possible) and connect them
> >> using XInclude. 3. Try to make Saxon render it as in step 1.
> >> 4. Try to enhance the corresponding schema in order to allow validation
> >> of those fragments allowed, i.e. <chapter> and <section> elements. I
> >> don't exactly know what that means, it might well be, the schema is
> >> already fit for that.
> >> 5. Check that validation works with both the whole thing and the pieces.
> >> 6. Set up a SVN repository and load the hopefully tree-like 'book'.
> >> 7. Open the repository for the co-authors to-be and publish the schema,
> >> so that they have a chance of validating their bits.
> >> 8. On a routine base run the assemble-and-transform task and publish the
> >> result.
> >>
> >
> > Looks like a good plan to me.
>
> The 'assemble' is still a bit mysterious?
> How are you going to pull the files from svn into an ant or
> XSLT build process?

Ant can check out from SVN (if thats what you mean)... in my last
place we used to have a task that checked out the latest XSLT, CSS,
images etc before running the nightly batch transforms.


-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/