Fix schematron rules silently skipping all checks due to namespace mismatch

[Copilot]

The schematron rules in hdtSMP64.sch never fired because their XPath expressions used unprefixed element names, which match elements in no namespace — but valid FSMP config files must declare xmlns="FSMP-Validator" (required by targetNamespace in the XSD), placing all elements in that namespace.

Changes

• hdtSMP64.sch: Add <sch:ns prefix="f" uri="FSMP-Validator"/> and qualify all XPath expressions with f::

<!-- Before: never matches namespace-qualified elements -->
<sch:rule context="bone[mass = '0']">
    <sch:assert test="not(inertia)" role="error">...</sch:assert>

<!-- After: correctly matches elements in the FSMP-Validator namespace -->
<sch:ns prefix="f" uri="FSMP-Validator"/>
<sch:rule context="f:bone[f:mass = '0']">
    <sch:assert test="not(f:inertia)" role="error">...</sch:assert>

This applies to both f:bone and f:bone-default rules, and all three assert tests (inertia, linearDamping, angularDamping).

Original prompt

Why isn't the inertia tag line 76 raising an error despite the schematron rules?

Created from VS Code.

[DaymareOn]

@copilot Ok, continue

[Copilot]

@copilot Ok, continue

The fix is in commit af333e9.

Root cause: The schematron XPath expressions used unprefixed element names (e.g., bone[mass='0']), which only match elements in no namespace. But FSMP config XML files must declare xmlns="FSMP-Validator" to be valid against the XSD, so all elements live in the FSMP-Validator namespace — meaning the rules never fired.

Fix: Added <sch:ns prefix="f" uri="FSMP-Validator"/> and updated all XPath contexts and assertions to use the f: prefix (e.g., f:bone[f:mass = '0'], not(f:inertia)).

[DaymareOn]

@copilot Ok, it still doesn't raise any error.