Test cases for XMLSig Interoperability

2.2.4.1 Test cases for checking xml:base attribute propagation

This section specifies test cases that check how the tools propagate xml:base attributes through the tree when the result of the filtering is a document subset.

	<?xml version="1.0" encoding="UTF-8"?>
	<ietf:CanXML11XmlBaseDoc1 xmlns:ietf="http://www.ietf.org" xmlns:w3c="http://www.w3.org"  	xml:base="http://xmlbaseexample.org/xmlbase0/">
		<ietf:e1 xml:base="/xmlbase1/">
			<ietf:e11 xml:base="/xmlbase11/">
				<ietf:e111 xml:base="/xmlbase111/"/>
			</ietf:e11>
			<ietf:e12 at="2" >
				<ietf:e121 xml:base="/xmlbase121/"/>
			</ietf:e12>
		</ietf:e1>
		<ietf:e2>
			<ietf:e21 xml:base="/xmlbase21/" />
		</ietf:e2>
		<ietf:e3>
			<ietf:e31 at="3" />
		</ietf:e3>
	</ietf:CanXML11XmlBaseDoc1 >
						

The document's root element ietf:CanXML11XmlBaseDoc1 defines a xml:base attribute. This element contains three children.

The first one ietf:e1 has another xml:base attribute. All the ietf:e1's descendant have a xml:base attribute. Transforms that select subsets of ietf:e1's descendant will test how each level in the tree of elements incorporates its corresponding part to the value of the final xml:base.

The second one ietf:e2 does not have a xml:base attribute, but its child, ietf:e21 's has a xml:base attribute. Transforms that select ietf:e21 will test how it takes the value of xml:base from an ancestor different to its parent.

As for the third element, neither it nor any of its descendant have have a xml:base. Transforms that select ietf:e3 or any of its descendant will test how they inherit the xml:base from the root element without any further processing

Test case canXML11.xmlbase.prop#2-positive
Input details	The document shown above. The ds:Transform contains a XPath expression whose result is a node set that includes element ietf:e1 and its descendant but not ietf:CanXML11XmlBaseDoc1.
Rationale	Check that implementations of [XML-C14N1.1] properly build the xml:base at the first level (ietf:e1).
Document subset expression	(//. | //@* | //namespace::*) [ancestor-or-self::ietf:e1]
Output
Link to test cases

Test case canXML11.xmlbase.prop#3-positive
Input details	The document shown above. The ds:Transform contains a XPath expression whose result is a node set that includes element ietf:e11 and its descendant. Elements ietf:CanXML11XmlBaseDoc1 and ietf:e1 do not appear.
Rationale	Check that implementations of [XML-C14N1.1] properly build the xml:base if one of intermediate the levels (ietf:e1) are absent from the document subset.
Document subset expression	(//. | //@* | //namespace::*) [ancestor-or-self::ietf:e11]
Output
Link to test cases

Test case canXML11.xmlbase.prop#4-positive
Input details	The document shown above. The ds:Transform contains a XPath expression whose result is a node set that includes element ietf:e111 and its descendant. Elements ietf:CanXML11XmlBaseDoc1, ietf:e11 and ietf:e1 do not appear.
Rationale	Check that implementations of [XML-C14N1.1] properly build the xml:base if several intermediate levels (ietf:e1 and ietf:e11) are absent from the document subset.
Document subset expression	(//. | //@* | //namespace::*) [ancestor-or-self::ietf:e111]
Output
Link to test cases

Test case canXML11.xmlbase.prop#5-positive
Input details	The document shown above. The ds:Transform contains a XPath expression whose result is a node set that includes element ietf:e2 and its descendant. Elements ietf:CanXML11XmlBaseDoc1, ietf:e1 and its descendant, and ietf:e3 and its descendant do not appear.
Rationale	Check that implementations of [XML-C14N1.1] properly build the xml:base if one intermediate level (ietf:e2) without any xml:base attribute is absent from the document subset.
Document subset expression	(//. | //@* | //namespace::*) [ancestor-or-self::ietf:e21]
Output
Link to test cases

Test case canXML11.xmlbase.prop#6-positive
Input details	The document shown above. The ds:Transform contains a XPath expression whose result is a node set that includes element ietf:e3 and its descendant. Elements ietf:CanXML11XmlBaseDoc1, ietf:e1 and its descendant, and ietf:e2 and its descendant do not appear.
Rationale	Check that implementations of [XML-C14N1.1] properly build the xml:base in one element that originaly had no xml:base attribute.
Document subset expression	(//. | //@* | //namespace::*) [ancestor-or-self::ietf:e3]
Output
Link to test cases

Test case canXML11.xmlbase.prop#7-positive
Input details	The document shown above. The ds:Transform contains a XPath expression whose result is a node set that includes elements ietf:CanXML11XmlBaseDoc1 and ietf:e3 and its descendant. Elements ietf:e1 and its descendant, and ietf:e2 and its descendant do not appear.
Rationale	Check that implementations of [XML-C14N1.1] do not pass the xml:base to another element when it is not necessary.
Document subset expression	(//. | //@* | //namespace::*) [ancestor-or-self::ietf:CanXML11XmlBaseDoc1 and not(ancestor-or-self::ietf:e1 or ancestor-or-self::ietf:e2)]
Output
Link to test cases

2.2.4.2 Tests for checking XML-C14N1.1 annex A

This section specifies test cases for checking if the applications are aligned with [XML-C14N1.1] Annex A.

Each test case in this section will specify an input string, representing a URI that will have to be processed as per [XML-C14N1.1] Annex A.

Each test case appears in a row of the table shown below. The first column identifies the input URI that has to be processed. The second column shows the corresponding output.

Test case canXML11.xmlbase.annexA#1-positive
Input details	Output details
no/.././/pseudo-netpath/seg/file.ext	pseudo-netpath/seg/file.ext
no/..//.///pseudo-netpath/seg/file.ext	pseudo-netpath/seg/file.ext
yes/no//..//.///pseudo-netpath/seg/file.ext	yes/pseudo-netpath/seg/file.ext
no/../yes	yes
no/../yes/	yes/
no/../yes/no/..	yes/
../../no/../..	../../../
no/../..	../
Editorial note   Here the rest of test cases identified by Konrad	Editorial note   Here the rest of test cases identified by Konrad