[fix] Resolve namespace for prefixed attribute names in range index conditions

[joewiz]

Summary

• Fixes namespace resolution for prefixed attribute names (e.g. wwp:field) in range index <condition> elements
• Updates collection.xconf.xsd to accept prefixed attribute names
• Adds XQSuite tests for prefixed and unprefixed attribute conditions

Closes #5189

What Changed

RangeIndexConfigAttributeCondition.java — The constructor now accepts a Map<String, String> namespaces parameter (the same namespace map already used by <create qname="..."> resolution). When the @attribute value contains a prefix, the prefix is resolved to a namespace URI. The matches() method now uses getAttributeNS() for namespaced attributes instead of getAttribute() with the raw prefixed string.

ComplexRangeIndexConfigElement.java — Passes the namespaces map through to the RangeIndexConfigAttributeCondition constructor.

collection.xconf.xsd — Changed attributeReq type from xs:NCName to xs:string, consistent with how @qname is typed elsewhere in the schema. (xs:QName is unsuitable here because XSD QName validation requires the prefix to be resolvable in the schema instance context.)

prefixed-conditions.xql — 6 new XQSuite tests verifying that both prefixed (wwp:field) and unprefixed (field) attribute conditions correctly index matching elements and that the query optimizer rewrites predicates on both.

Test Plan

• Range index XQSuite tests: 351 pass, 0 failures
• RangeIndexConfigTest unit test passes
• CI: all checks pass (ubuntu/windows/macOS integration, unit tests, license, XQTS, Codacy)

🤖 Generated with Claude Code

[joewiz]

Documentation update notes

Suggested additions to the "Conditional Indexes" section of https://exist-db.org/exist/apps/doc/newrangeindex:

• Namespaced attribute conditions are now supported. The @attribute value in a <condition> element can use a prefixed name (e.g., wwp:field), and the prefix will be resolved against the namespace declarations on the <index> element — the same mechanism already used for @qname on <create> elements.

• Example showing a prefixed attribute condition:

  <index xmlns:tei="http://www.tei-c.org/ns/1.0"
         xmlns:wwp="http://www.wwp.northeastern.edu/ns/textbase">
      <range>
          <create qname="tei:title">
              <condition attribute="wwp:field" value="title"/>
              <field name="wwp-title" type="xs:string"/>
          </create>
      </range>
  </index>

  This indexes only tei:title elements that have @wwp:field="title", where wwp:field is resolved to the http://www.wwp.northeastern.edu/ns/textbase namespace.

• Namespace declaration requirement: The prefix used in @attribute must be declared on the <index> element (or an ancestor in the collection.xconf). This is the same requirement as for prefixed @qname values on <create> elements.

• Prefixed vs. unprefixed: <condition attribute="wwp:field" .../> matches the namespaced attribute @wwp:field, while <condition attribute="field" .../> matches the unprefixed (null namespace) attribute @field — even if both appear on the same element, they are treated as separate attributes and indexed independently.

🤖 Co-authored with Claude Code