[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-tc] Transclusions to XInclude mapping
On 16 October 2010 23:12, Jirka Kosek <jirka@kosek.cz> wrote: General comment. A 'nice to have' would be some indication of a good work flow process, such that transclusion/validation etc are performed in a sensible manner for good error reporting. Is transclusion seen as a separate step, or as one part of the xslt processing? isn't it about time that a multi-phase process was considered, for a reduction in complexity if nothing else? > 1.5. UC-5: Repeated transclusion in one “master” document > Do nothing. This of course doesn't solve problem and result of processing is unpredictable. > > Preserve duplicated IDs only on their first occurrence (in document order). Other then first occurrences of ID are deleted. All links will then point to the first location in final composed document. suggest '(in transcluded document order)' Does this issue need resolution prior to acceptance of this proposal? Without a clear idea of how ID's are to be resolved, this could become ... messy? > 3. DocBook Transclusion Proposal > > This section describes syntax, semantics and processing model of DocBook transclusion mechanism. Please be aware that this is early stage draft – everything described below might change or disappear completely. > > Transclusion in document is described by ref element which references content to transclude. There are two basic types of reference – inline and external. Inline references reference content which is defined in some other place using definitions element. External reference references some external content which might or might not be written using DocBook vocabulary. Query on how good error reporting can be for transclusion. The concern arises from any weak error reporting causing a significant rise in support requests on the mailing lists? Hence the issue of a separate transclusion phase, which would identify the error as being a transclusion error, rather than a transformation error? > 3.3. Special ID/IDREF processing > global > > All IDREFs in transcluded content are adjusted to point to the first element in document order which has matching ID. Matching ID doesn't mean string equality between ID and IDREF values – it is sufficient if second part of ID and IDREF after removal of possibly added prefixes is matching. suggest 'first element in transcluded document order' Great piece of work Jirka. Thanks. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]