Peter Ring wrote: > While XXE carps on and does not resolve XIncludes using the XPointer scheme, > they are preserved and round-tripped, as far as I can see. That is, while you > can't see and edit the resulting infoset in XXE, you can at least edit the > XPointer expression. > > I customized the DocBook XML V4.2 DTD to allow xi:include at appropriate > places, and also included the EBNF customization. XXE appears to work with > this without further costumization, even display EBNF productions in a very > nice style :). > > My only problem has been that XXE appear to have an internal declaration of > the xi:include element similar to the first http://www.w3.org/2001/XInclude > version, while I use the http://www.w3.org/2001/XInclude that is now a > recommendation (per 20th December 2004). > > If I want to be able to add xi:include elements in XXE, I must put an 'new' > xi:include declaration in the internal subset of the document: > > <!ELEMENT xi:include (xi:fallback?)> > <!ATTLIST xi:include > xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude"; > href CDATA #IMPLIED > parse (xml|text) "xml" > xpointer CDATA #IMPLIED > encoding CDATA #IMPLIED > accept CDATA #IMPLIED > accept-language CDATA #IMPLIED > > > Otherwise, XXE inserts xi:include elements based on the 'old' > http://www.w3.org/2001/XInclude (see > http://www.w3.org/TR/2002/CR-xinclude-20020917/): > > <!ELEMENT xi:include (xi:fallback)> > <!ATTLIST xi:include > xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude"; > href CDATA #REQUIRED > parse (xml|text) "xml" > encoding CDATA #IMPLIED >
This is no longer true. Yes, XMLmind XML Editor used to use fragment identifiers in XInclude hrefs because this was what was mandated in an early version of the XInclude. But, as of V2.7 (August 20, 2004), we have changed our implementation to conform to the recommendation. See http://www.xmlmind.com/xmleditor/changes.html. Excerpts of this file: ~~~~~~~~~~~~~~~~~~~~~~~ The XInclude elements generated by XXE to represent modular document now conform to the latest W3C candidate recommendation (13 April 2004). The main change is that fragment identifiers must not be used in the href attribute of an xi:include element. For example: <xi:include href="VATrates.html#germany_vat"/> must be specified as <xi:include href="VATrates.html" xpointer="germany_vat"/>. Of course, all these technical details are transparent for the user. *However,it is recommended to reopen modular documents created using previous versions of XXE and to save them back to disk using XXE V2.7.* This will ensure that the modular documents created using XXE are interchangeable with other XInclude-aware applications.
