XInclude Test Suite

Simple test of including another XML document.

There is an output test associated with this input file.

Test recursive inclusion.

There is an output test associated with this input file.

Simple test of including a set of nodes from an XML document.

There is an output test associated with this input file.

including another XML document with IDs

There is an output test associated with this input file.

Simple test of including another text document

There is an output test associated with this input file.

Simple test of a fallback on unavailable URI.

There is an output test associated with this input file.

Unused fallbacks must not generate errors, even if broken.

There is an output test associated with this input file.

Broken fallback must generate errors, if they're needed.

A BOM in UTF16 is not added to the resulting document.

There is an output test associated with this input file.

A BOM in UTF16LE is added to the resulting document.

There is an output test associated with this input file.

'accept' attributes with characters outside the range #x20 through #x7E must be flagged as fatal errors.

Simple test of including another XML document.

There is an output test associated with this input file.

Test recursive inclusion.

There is an output test associated with this input file.

Simple test of including another text document.

There is an output test associated with this input file.

Simple test of including a set of nodes from an XML document.

There is an output test associated with this input file.

Simple test of including a set of nodes from an XML document.

There is an output test associated with this input file.

Simple test of including a set of nodes from an XML document.

There is an output test associated with this input file.

Simple test of including a set of nodes from an XML document.

There is an output test associated with this input file.

Test the inclusion of another XML document.

There is an output test associated with this input file.

Test that the encoding attribute in the Xinclude element has no effect when parse="xml".

There is an output test associated with this input file.

Test that values other than xml or text, in the parse attribute of the XInclude element, result in fatal errors.

Test of fallback element appearing as a child of an xinclude element.

There is an output test associated with this input file.

Test a fallback element not appearing as a direct child of an xinclude element. A fatal error should be generated.

Test a fallback when a resource error occurs.

There is an output test associated with this input file.

Test an empty fallback element. The xinclude element is removed from the results.

There is an output test associated with this input file.

Test of a fallback element missing from the include element. A resource error results in a fatal error.

Test unqualified attributes in the include element. They must be ignored.

There is an output test associated with this input file.

Test content other than the fallback, in the xinclude element. This content must be ignored.

There is an output test associated with this input file.

Test a resource containing non-well-formed XML. The inclusion results in a fatal error.

Test that is a fatal error for an include element to contain more than one fallback elements.

Test a fallback element containing markup when parse="text".

There is an output test associated with this input file.

Test a fallback element containing markup when parse="text".

There is an output test associated with this input file.

It is illegal for an include element to point to itself, when parse="xml".

Test a document type declaration information item child in the resource information set. the DTD should be excluded for inclusion in the source infoset.

There is an output test associated with this input file.

Test intra-document reference within include elements.

There is an output test associated with this input file.

Simple test of including a set of nodes from an XML document.

There is an output test associated with this input file.

Test the inclusion of a set of nodes from an XML document.

There is an output test associated with this input file.

Test an include location identifying a document information item with an xpointer locating the document root. In this case the set of top level include items is the children of acquired infoset's document information item, except for the document type information item.

There is an output test associated with this input file.

Including an XML document with an unparsed entity.

There is an output test associated with this input file.

Testing when the document (top level) element in the source infoset is an include element.

There is an output test associated with this input file.

Testing an include element in the document (top-level) element in the source doc. Test should fail because is including more than one element.

Testing an include element in the document (top-level) element in the source doc. Test should fail because is including only a processing instruction.

Testing an include element in the document (top-level) element in the source doc. Test should fail because is including only a comment.

Test relative URI references in the included infoset.

There is an output test associated with this input file.

Test that the encoding attribute when parse="xml" does not translate the incoming document.

There is an output test associated with this input file.

including another XML document with IDs, using a shorthand pointer.

There is an output test associated with this input file.

including another XML document with IDs, using a shorthand pointer.

There is an output test associated with this input file.

Including another XML document with IDs, using a shorthand pointer.

There is an output test associated with this input file.

Including an XML document using an XPointer element scheme.

There is an output test associated with this input file.

Including an XML document using an XPointer element scheme.

Including an XML document using an XPointer element scheme.

Including another XML document with ids using XPointer element scheme.

There is an output test associated with this input file.

Including an XML document using an XPointer element scheme.

There is an output test associated with this input file.

Including an XML document using an XPointer element scheme.

There is an output test associated with this input file.

Including another XML document using XPointer Framework scheme-base pointer. If the processor does not support the scheme used in a pointer part, it skip that pointer part.

There is an output test associated with this input file.

Including another XML document using XPointer Framework. If the processor does not support the scheme used in a pointer part, it skip that pointer part.

There is an output test associated with this input file.

Testing the content of the xinclude element. The comment should be ignored .

There is an output test associated with this input file.

Testing the content of the xinclude element. The element should be ignored .

There is an output test associated with this input file.

Testing the content of the xinclude element. This test should result in a fatal error.

Testing the content of the xinclude element. The xinclude element may contain a fallback element; other elements from the xinclude namespace result in a fatal error.

Testing the content of the xinclude element. The content must be one fallback. This test should result in a fatal error.

Test a resource that contains not-well-formed XML. This test should result in a fatal error.

Test a resource that contains not-well-formed XML. This test should result in a fatal error.

Testing the content of the xinclude element. The xinclude element may contain a fallback element; other elements from the xinclude namespace result in a fatal error.

Testing the content of the xinclude element. The xinclude element may contain a fallback element; other elements from the xinclude namespace result in a fatal error.

It is a fatal error to resolve an xpointer scheme on a document that contains unexpanded entity reference information items.

The unexpanded entity reference information items, if present in the source infoset, will appear in the result infoset.

There is an output test associated with this input file.

Test an include location identifying the document information item without an Xpointer, The set of top-level included items should be the children of the acquired inforset's document information item, except for the document type declaration information item.

There is an output test associated with this input file.

Test an include location having an XPointer identifying a comment. The set of top-level included items should consist of the information item corresponding to the comment node in the acquired infoset.

There is an output test associated with this input file.

Test an include location having an XPointer identifying a processing instruction. The set of top-level included items should consist of the information item corresponding to the processing instruction node in the acquired infoset.

There is an output test associated with this input file.

Test that an include location identifying an attribute node will result in a fatal error.

Test that an include location identifying an attribute node will result in a fatal error.

Including a duplicate unparsed entity. Test should ignore duplicate unparsed entity.

There is an output test associated with this input file.

Including an unparsed entity with same name, but different sysid. Test should fail.

Simple whole-file inclusion.

There is an output test associated with this input file.

Verify that xi:include elements in the target have been processed in the acquired infoset, ie before the xpointer is applied.

There is an output test associated with this input file.

Check xml:lang fixup

There is an output test associated with this input file.

xml:base attribute is used to resolve relative URLs in href attributes

There is an output test associated with this input file.

Use XPointer to include an include element in another document, and make sure that's fully resolved too

There is an output test associated with this input file.

xml:base attribute on the xi:include element is used to resolve relative URL in href

There is an output test associated with this input file.

xml:base attribute from an unincluded element still applies to its included descendants

There is an output test associated with this input file.

An include element includes its following sibling element, which has a child include element including the sibling element after that one.

There is an output test associated with this input file.

Include a document that uses XPointers to reference various parts of itself

There is an output test associated with this input file.

xml:lang attribute from including document does not override xml:lang attribute in included document

There is an output test associated with this input file.

xml:lang attribute is added to retain the included element's language, even though the language was originaly declared on an unincluded element

There is an output test associated with this input file.

xml:lang='' is added when the included document does not declare a language and the including element does

There is an output test associated with this input file.

Test that the xml:base attribute is not used to resolve a missing href. According to RFC 2396 empty string URI always refers to the current document irrespective of base URI.

There is an output test associated with this input file.

There's no difference between href="" and no href attribute.

There is an output test associated with this input file.

Make sure base URIs are preserved when including from the same document.

There is an output test associated with this input file.

Syntactically incorrect IRI is a fatal error (Eitehr I'm missing something or the spec needs to state this prinicple more clearly.)

Syntactically incorrect IRI with an unrecognized scheme is a fatal error

Syntactically correct IRI with an unrecognized scheme is a resource error

There is an output test associated with this input file.

accept attribute contains carriage-return/linefeed pair

accept attribute contains Latin-1 character (non-breaking space)

Unprefixed, unrecognized attributes on an include element are ignored

There is an output test associated with this input file.

Fallback elements can be empty

There is an output test associated with this input file.

Included documents can themselves use fallbacks

There is an output test associated with this input file.

An included document can use a fallback that points into the included document

There is an output test associated with this input file.

An included document can use a fallback that includes another document as text

There is an output test associated with this input file.

A fallback element in an included document contains an include element with a parse attribute with an illegal value.

A fallback element in an included document contains an include element with neither an xpointer nor an href attribute.

A fallback element in an included document contains an include element whose href attribute has a fragment ID.

The XPointer does not select anything in the acquired infoset, but does select something in the source infoset.

A fallback in an included document contains some text and a comment, but no elements.

There is an output test associated with this input file.

Include element points to another include element, which has a missing resource and therefore activates a fallback.

There is an output test associated with this input file.

An include element can include another include element that then uses a fallback.

There is an output test associated with this input file.

An include element can include another include element that then fails to find a resource, which is a fatal error if there's no fallback.

An include element can include another include element that then fails to find a resource, but it has a fallback, which itself has an include child, which then throws a fatal error.

Basic test from XInclude spec

There is an output test associated with this input file.

An include element points to a document that includes it, using an xpointer to select part of that document.

An include element points to another include element in the same document.

There is an output test associated with this input file.

Include elements can be siblings

There is an output test associated with this input file.

Namespaces (and lack thereof) must be preserved in included documents

There is an output test associated with this input file.

Detect an inclusion loop when an include element refers to itself

Detect an inclusion loop when an include element refers to its ancestor element in the same document

Processing a document that contains no include elements produces the same document.

There is an output test associated with this input file.

Basic inclusion

There is an output test associated with this input file.

The root element of a document can be an include element.

There is an output test associated with this input file.

The root element of a document can be an include element. In this test the included document has a prolog and an epilog and the root element is replaced

There is an output test associated with this input file.

testIncludeElementsCannotHaveIncludeChildren

Include elements cannot have children from the xinclude namespace except for fallback.

Fallback can only be a child of xinclude element

A fallback element cannot have a fallback child element.

"The appearance of more than one xi:fallback element, an xi:include element, or any other element from the XInclude namespace is a fatal error." In this test the fallback is activated.

"The appearance of more than one xi:fallback element, an xi:include element, or any other element from the XInclude namespace is a fatal error." In this test the fallback is not activated.

A document cannot include itself

Document A includes document B which includes document A

Include element is missing an href and xpointer attribute

parse attribute must have value xml or text

Missing resource is fatal when there's no fallback

Missing resource is non-fatal when there's a fallback

There is an output test associated with this input file.

Fallback elements can themselves contain include elements

There is an output test associated with this input file.

encoding="UTF-16"

There is an output test associated with this input file.

A shorthand XPointer

There is an output test associated with this input file.

XPointer that selects nothing is a resource error, and fatal because there's no fallback.

XPointers of the forms described in [XPointer Framework] and [XPointer element() scheme] must be supported.

There is an output test associated with this input file.

Unrecognized colonized XPointer schemes are skipped, and the following scheme is used.

There is an output test associated with this input file.

Even if the first XPointer part locates a resource, a syntax error in the second XPointer part is still a fatal error.

Even if the first XPointer part locates a resource, a syntax error in the second XPointer part is still a fatal error.

You can include another element from the same document without an href attribute.

There is an output test associated with this input file.

Test with 3 element schemes in the XPointer. The first and second one point to nothing. The third one selects something. XPointer parts are evaluated from left to right until one finds something.

There is an output test associated with this input file.

Test with 2 element schemes in the XPointer. The first one uses an ID that doesn't exist and points to nothing. The second one selects something.

There is an output test associated with this input file.

Make sure XPointer syntax errors are treated as a resource error, not a fatal error; and thus fallbacks are applied

There is an output test associated with this input file.

Make sure XPointer syntax errors are treated as a resource error, not a fatal error; and thus fallbacks are applied

There is an output test associated with this input file.

Test with 3 element schemes in the XPointer, separated by white space. The first one points to nothing. The third one selects something.

There is an output test associated with this input file.

An XPointer that doesn't point to anything is a resource error; and fatal because there's no fallback

Syntax error in an XPointer is a resource error; and fatal because there's no fallback

Syntax error in an XPointer is a resource error; and fatal because there's no fallback

Unrecognized XPointer scheme activates fallback

There is an output test associated with this input file.

XPointer uses an element scheme where the first part is an ID

There is an output test associated with this input file.

Can autodetect UTF16 big endian files with a with a byte order mark when parse="text"

There is an output test associated with this input file.

Can autodetect UTF16 little endian files with a with a byte order mark when parse="text"

There is an output test associated with this input file.

Can autodetect UTF-8 files with a with a byte order mark when parse="text"

There is an output test associated with this input file.

Can autodetect UCS2 big endian files with a without a byte order mark when parse="text"

There is an output test associated with this input file.

Can autodetect UCS2 little endian files with a without a byte order mark when parse="text"

There is an output test associated with this input file.

Can autodetect EBCDIC files with a without a byte order mark when parse="text"

There is an output test associated with this input file.

Syntax error in an XPointer is a resource error; and fatal becaue there's no fallback

Syntax error in an XPointer is a resource error; and fatal becaue there's no fallback

Circular references via xpointer are fatal

href attribute with fragment ID is a fatal error even when there's an xpointer attribute

href attribute with fragment ID is a fatal error

Line breaks must be preserved verbatim when including a document with parse="text"

There is an output test associated with this input file.

A fragment identifier is semantically bad; but still meets the syntax of fragment IDs from RFC 2396.

accept-language="fr" This test connects to IBiblio to load the included data. This is necessary because file URLs don't support content negotiation

There is an output test associated with this input file.

accept-language="en" This test connects to IBiblio to load the included data. This is necessary because file URLs don't support content negotiation

There is an output test associated with this input file.

accept="text/plain" This test connects to IBiblio to load the included data. This is necessary because file URLs don't support content negotiation

There is an output test associated with this input file.

accept="text/html" This test connects to IBiblio to load the included data. This is necessary because file URLs don't support content negotiation

There is an output test associated with this input file.

Unrecognized scheme in XPointer is a fatal error if there's no fallback

Unrecognized scheme in XPointer is a resource error so fallbacks apply

There is an output test associated with this input file.

Basic inclusions as XML and text

There is an output test associated with this input file.

Included document has an include element with neither href nor xpointer attribute

XPointers are resolved against the acquired infoset, not thge source infoset

There is an output test associated with this input file.

Test that a non-child sequence in an xpointer is treated as a resource error.

There is an output test associated with this input file.

Since the xpointer attribute is not a URI reference, %-escaping must not appear in the XPointer, nor is there any need for a processor to apply or reverse such escaping.