`id` function is not compliant to the spec

[sadiqkhoja]

As per the spec, id function selects elements by their unique ID and attribute for unique ID is declared using DTD.

Q. If no DTD is defined then is id attribute implicitly considered as unique ID of the element node?

Following test fails, because we are not handling DTD at this moment, right?

it.only('adhoc tests', () => {
	const testDocument = xml`<?xml version="1.0" encoding="UTF-8"?>
			<!DOCTYPE root [
					<!ELEMENT root (foo+)>
					<!ELEMENT foo (bar)>
					<!ELEMENT bar (#PCDATA)>
					<!ATTLIST foo name ID #REQUIRED>
			]>
			<root>
					<foo name="first">
							<bar>Some content</bar>
					</foo>
					<foo name="second">
							<bar>Another content</bar>
					</foo>
			</root>
`;
	const evaluator = new Evaluator({rootNode: testDocument});

	const actual = evaluator.evaluate(`count(id('first second'))`);

	expect(actual.numberValue).toBe(2);
})

This issue probably just needs documentation.

[eyelidlessness]

I've inferred that "the spec" above refers to XPath 1.0 (id, 5.2.1 Unique IDs).

Pertinent spec language

The id function selects elements by their unique ID (see [5.2.1 Unique IDs]). [...]

[...]

5.2.1 Unique IDs

An element node may have a unique identifier (ID). This is the value of the attribute that is declared in the DTD as type ID. No two elements in a document may have the same unique ID. If an XML processor reports two elements in a document as having the same unique ID (which is possible only if the document is invalid) then the second element in document order must be treated as not having a unique ID.

NOTE: If a document does not have a DTD, then no element in the document will have a unique ID.

A few notes:

• I can confirm that we're out of [XPath 1.0] spec as reported

• We're also out of [XPath 1.0] spec according to the last NOTE in the quoted language, by treating the id attribute as a unique identifier even in the absence of a DTD

• This function is not included in the ODK XForms Specification (and according to my reading, this is explicit); but since we provide the functionality, I do consider it a bug

• Both aspects of out-of-XPath-1.0-spec behavior are consistent with the native evaluators of each major browser (I checked in Chrome, Firefox, Safari); I would like to find a compliant implementation before we decide to address this

Q. If no DTD is defined then is id attribute implicitly considered as unique ID of the element node?

This is the current behavior, and as mentioned it is consistent with all of the major browsers. I believe the behavior is expected for HTML documents, and any non-HTML consideration is just unaddressed (I'd expect it never will be).

we are not handling DTD at this moment, right?

Correct.

I was curious if there is any precedent for DTD support or interest in it. Not that it's an exhaustive search, but this issue is the first to mention DTD across all of the getodk org.