Hi, The solution we currently use to avoid that XInclude/parse="text" sections are replaced by the actual content is to have a convention on where to store all files included with XInclude/parse="text", e.g. in a folder 'src' relative to current DocBook document.
The person editing the DocBook document must then: 1) don't have the 'src' folder locally 2) temporarily rename the 'src' folder locally This way, opening the DocBook document will give errors regarding XInclude/parse="text", but this allows to modify the DocBook document without the risk of replacing the XInclude/parse="text" sections with the actual content. I know it's not ideal, but at least this allows to keep the DocBook document modular. Question : isn't there a way in XXE to force XInclude/parse="text" sections not being resolved, even when the file it points to exists? This way, the person editing the DocBook document wouldn't need to perform 1) or 2). Regards, Davy Toch IT-Consultant Steria Benelux SA/NV Hussein Shafie wrote: > Davy Toch wrote: > >>> What you suggest certainly makes sense. The problem is that currently, >>> for XXE, <xi:include> elements (like managed references to external >>> entities and namespace prefixes) only exist at document load time and at >>> document save time. >>> >> But XXE only seems to have a problem with XIncludes that have >> parse="text" as attribute. Normal XIncludes that select XML fragments >> from other >> DocBook documents are not replaced by the actual XML fragments when >> modifying and saving the document. >> >> > > A text fragment included from an external document is almost always > merged into an *existing* Text node. Moreover a Text node is a > lightweight object carrying very few information. > > In a nutshell, the implementation of XXE does not allow to treat text > fragments on par with elements. > > >
