You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Ruff formatted and ruff lint fixes
- Remove namespace on test_xtce_no_namespace.xml and make namespace handling on definitions.py clearer
- Fix XML structure for XTCE test files
- Fix CTIM XTCE for validity
- Update changelog
- Tighten up warnings for no namespace for XtcePacketDefinition
- Add tests for XSD schema validity
- Add tests for different inputs to validation function
- Add test for different inputs to definition from_xtce
- Add structural validation and tests
- Add validate_xtce to top level module
- Add simple CLI to validation tool
Copy file name to clipboardExpand all lines: docs/source/users.md
+50Lines changed: 50 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,6 +376,56 @@ This equation can be implemented in XTCE by referencing the packet length field
376
376
</xtce:BinaryParameterType>
377
377
```
378
378
379
+
## XTCE Document Validation
380
+
381
+
Space Packet Parser provides comprehensive validation capabilities for XTCE documents to help ensure they are correct and will work properly for parsing packets. The validation system operates in two modes:
382
+
383
+
-**Schema Validation**: Validates the XML document against the in-document referenced XTCE XSD schema
384
+
-**Structural Validation**: Validates XTCE-specific structure and reference integrity
385
+
386
+
Schema validation requires correct namespacing declarations at the top of your XTCE document.
0 commit comments