|Editing XML Documents / Large Documents|
XInclude is a standard for assembling XML instances into another XML document through inclusion. It enables larger documents to be dynamically created from smaller XML documents without having to physically duplicate the content of the smaller files in the main file. XInclude is targeted as the replacement for External Entities. The advantage of using XInclude is that, unlike the entities method, each of the assembled documents is permitted to contain a Document Type Declaration (DOCTYPE Decl.). This means that each file is a valid XML instance and can be independently validated. It also means that the main document to which smaller instances are included can be validated without having to remove or comment the DOCTYPE Decl. as is the case with External Entities. This makes XInclude a more convenient and effective method for managing XML instances that need to be stand-alone documents and part of a much larger project.
The main application for XInclude is in the document-oriented content frameworks such as manuals and Web pages. Employing XInclude enables authors and content managers to manage content in a modular fashion that is akin to Object Oriented methods used in languages such as Java, C++ or C#.
The advantages of modular documentation include: reusable content units, smaller file units that are easier to be edited, better version control and distributed authoring.
Create a chapter file and an article file in the samples folder of the Oxygen XML Developer install folder.
Chapter file (introduction.xml) looks like this:
<?xml version="1.0"?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> <chapter> <title>Getting started</title> <section> <title>Section title</title> <para>Para text</para> </section> </chapter>
Main article file looks like this:
<?xml version="1.0"?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.docbook.org/xml/4.3/docbookx.dtd" [ <!ENTITY % xinclude SYSTEM "../frameworks/docbook/dtd/xinclude.mod"> %xinclude; ]> <article> <title>Install guide</title> <para>This is the install guide.</para> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.dita"> <xi:fallback> <para> <emphasis>FIXME: MISSING XINCLUDE CONTENT</emphasis> </para> </xi:fallback> </xi:include> </article>
In this example the following is of note:
the DOCTYPE Decl. defines an entity that references a file containing the information to add the xi namespace to certain elements defined by the DocBook DTD;
the href attribute of the xi:include element specifies that the introduction.xml file will replace the xi:include element when the document is parsed;
if the introduction.xml file cannot be found, the parser will use the value of the xi:fallback element - a FIXME message.
If you want to include only a fragment of a file in the master file, the fragment must be contained in a tag having an xml:id attribute and you must use an XPointer expression pointing to the xml:id value. For example if the master file is:
<?xml version="1.0" encoding="UTF-8"?> <?xml-model href="test.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?> <test> <xi:include href="a.xml" xpointer="a1" xmlns:xi="http://www.w3.org/2001/XInclude"/> </test>
and the a.xml file is:
<?xml version="1.0" encoding="UTF-8"?> <test> <a xml:id="a1">test</a> </test>
after resolving the XPointer reference the document is:
<?xml version="1.0" encoding="UTF-8"?> <?xml-model href="test.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?> <test> <a xml:id="a1" xml:base="a.xml">test</a> </test>
The XInclude support in Oxygen XML Developer is turned on by default. You can toggle it by going to the entry Enable XInclude processing in the menu . When enabled, Oxygen XML Developer will be able to validate and transform documents comprised of parts added using XInclude.