Table of contents

[Home] [W3C Specs]

1.1 Relationship to XLink

1.2 Relationship to XML External Entities

1.3 Relationship to DTDs

1.4 Relationship to XML Schemas

1.5 Relationship to Grammar-Specific Inclusions

3.1 xi:include Element

3.2 xi:fallback Element

4 Processing Model

4.1 The Include Location

4.1.1 Escaping of href attribute values

4.1.2 Using XInclude with Content Negotiation

4.2 Included Items when parse="xml"

4.2.1 Document Information Items

4.2.2 Multiple Nodes

4.2.3 Range Locations

4.2.4 Point Locations

4.2.5 Element, Comment, and Processing Instruction Information Items

4.2.6 Attribute and Namespace Declaration Information Items

4.2.7 Inclusion Loops

4.3 Included Items when parse="text"

4.4 Fallback Behavior

4.5 Creating the Result Infoset

4.5.1 Unparsed Entities

4.5.2 Notations

4.5.3 references Property Fixup

4.5.4 Namespace Fixup

4.5.5 Base URI Fixup

4.5.6 Language Fixup

4.5.7 Properties Preserved by the Infoset

5.1 Markup Conformance

5.2 Application Conformance

5.3 XML Information Set Conformance

Appendices

C.1 Basic Inclusion Example

C.2 Textual Inclusion Example

C.3 Textual Inclusion of XML Example

C.4 Fragment Inclusion Example

C.5 Range Inclusion Example

C.6 Fallback Example

1 Introduction

Introduction

Many programming languages provide an inclusion mechanism to facilitate modularity. Markup languages also often have need of such a mechanism. This specification introduces a generic mechanism for merging XML documents (as represented by their information sets) for use by applications that need such a facility. The syntax leverages existing XML constructs - elements, attributes, and URI references.

[Next Chapter] [Home]