[duncdrum]

Summary

• Resolve known eXist/EXPath grammars for POST /api/editor/validate, preferring $EXIST_HOME/schema/ (exist#6528) and falling back to synced copies under resources/schema/ (eXide#842).
• Cover namespaced configs (collection.xconf, controller-config, expath-pkg, security-manager) and no-namespace roots (conf.xml, descriptor, mime-types, users, server), plus xsi:schemaLocation / noNamespaceSchemaLocation when they point at a known grammar or an absolute file://db/ URI.
• Validate with validation:jaxv-report + XSD 1.1 (interim until catalog-based jaxp works against native grammars — exist#6686). Response includes grammar (native|bundled|instance|none) and schema for observability.
• Keep resources/schema/catalog.xml for tooling / a future catalog path; document deprecation of the bundled copies.

Closes #842.

Test plan

• xst package install local-files build/eXide-4.0.1.xar --force --config .existdb.json
• Smoke: collection.xconf + mime-types return grammar: "native" on existdb/existdb:latest
• npx cypress run --spec cypress/e2e/xml_validate_spec.cy.js (7/7)
• CI green on existdb/existdb:latest
• Optional: server without $EXIST_HOME/schema/ still validates via bundled XSDs (grammar: "bundled")

[joewiz]

[This response was prompted by Joe, drafted by Claude Code, and reviewed by Joe.]

@duncdrum I went through this against head 19805337. The hardening in the last commit holds up — I confirmed an instance-supplied file: schema location is now ignored rather than opened as a grammar, and the SCHEMA_BY_ROOT_CHILD corroboration does stop a stray <auth> or <server> from being force-matched. One thing I'd fix before this goes in, plus a couple of smaller notes.

Namespaced grammars still match on namespace alone

The corroboration you added covers SCHEMA_BY_ROOT, but SCHEMA_BY_NS maps http://exist.sourceforge.net/NS/exist — eXist-db's general-purpose namespace, not a controller-specific one — straight to controller-config.xsd with no second signal. Anything else in that namespace gets force-validated against it:

document	result
a REST <query> envelope	invalid — "Cannot find the declaration of element 'query'"
a controller <dispatch> fragment	invalid — three further errors about url and pattern

Both are perfectly good documents someone might have open in the editor. The same trick you used for roots would do it — require a corroborating child (controller-config has a documented shape), or drop that namespace from the map and rely on xsi:schemaLocation for controller configs.

Minor

No-grammar documents come back as "status": "valid" with "grammar": "none", and no src/ file changed in this PR, so src/xml-helper.js's compileError() still branches only on status == "invalid". The editor therefore shows the same all-clear whether a document was schema-validated or merely parsed. One line in the status update — "validated against collection.xconf.xsd" versus "well-formed only" — would make the new grammar/schema fields visible to the person who benefits from them.

Verification

Built the branch and ran its spec against existdb/existdb:latest (eXist-db 7.0.0-SNAPSHOT, build 2026-10-17): xml_validate_spec passes 7/7.

I also ticked the open box in your test plan — the bundled fallback. Masking $EXIST_HOME/schema/ so the native lookup misses, a valid collection.xconf and an expath-pkg.xml both come back "grammar": "bundled", and an invalid collection.xconf is still rejected by the XSD 1.1 assertion. So the fallback path works as intended, not just the native one.

[duncdrum]

@joewiz thanks, and done. Ci failures are unrelated see #910

[dizzzz]

could you post some screen post, when possible?

[duncdrum]

@dizzzz its not very exciting, its mainly about the plumbing, using exists schemas instead of its own copies

The UX is somewhat misleading, let me add one more commit

[duncdrum]

@dizzzz here you go