What problem does it solve?
The 1C platform silently accepts some defective XDTO packages — for example, it substitutes unresolved foreign types with xs:anyType without any error — so broken packages only surface as runtime failures. This Skill statically validates a package before it is loaded into the infobase, catching defects the platform never reports.
Core Features & Use Cases
- Model validation: Checks XML well-formedness, targetNamespace, top-level element order (import → property → valueType → objectType), duplicate type names, and type reference resolution including Clark notation and prefix namespaces.
- Semantic checks: Detects silent degradation to xs:anyType, unused imports, invalid facets (minLength/maxLength, totalDigits/fractionDigits, whiteSpace, variety), invalid property form/bounds, fixed-without-default, and inheritance kind mismatches between objectType and valueType.
- Configuration integration: Verifies the metadata object Name/Namespace, registration in Configuration.xml, targetNamespace uniqueness across packages, and that all imported namespaces resolve to packages present in the configuration.
- Use Case: After creating or editing an XDTO package with xdto-compile or xdto-edit, run validation before db-load-xml and db-update to catch errors like a missing <import> or wrong element order that would make the platform reject the package during configuration update.
Quick Start
Ask the agent to validate the XDTO package at the given path, for example: run xdto-validate on XDTOPackages/MyPackage and report any errors.