Naive XML Bindings for python¶
xsData is a complete XML data binding library for python allowing developers to access and use XML documents as simple objects rather than using DOM.
It ships with a code generator for XML Schema definitions and WSDL 1.1 with SOAP 1.1 bindings. It produces simple dataclasses with type hints that don’t depend on the library itself in order to reduce the learning curve for users that have to write the binding models manually.
The included parser is highly optimized and adaptable with 4 available handlers based on native python and lxml. The parser configuration offers the ability to skip unknown properties and to process xinclude statements.
The parser and serializer are constantly tested against the W3C XML Schema 1.1 test suite and passes more than 99% of the valid instance cases.
Check the documentation demos or our W3C XML Schema 1.1 test runner and the samples repo for more ✨✨✨
Features¶
Generate data models for XML Schema 1.0 and 1.1 definitions.
Generate data models for WSDL 1.1 and SOAP 1.1 bindings.
Support qualified elements/attributes, enumerations and inner classes.
Preserve embedded documentation and references.
Data biding for XML and JSON documents.
Pluggable code writer that supports python dataclasses and PlantUML class diagrams.
Changelog: 20.9 (2020-09-03)¶
Added field metadata key tokens for xs:list or xs:NMTOKENS derived elements.
Added datatype factory to register custom converters.
Added XmlHandler interface to decouple parsing from lxml.
Added lxml based content handlers: LxmlEventHandler, LxmlSaxHandler
Added native python xml content handlers: XmlEventHandler, XmlSaxHandler
Added support for python >= 3.6 #241
Added codegen for soap 1.1 fault messages.
Fixed converting to enum members derived from xs:NMTOKENS.
Fixed package level import naming conflicts. #228
Fixed xml serializing to allow empty strings in attribute values. #230
Fixed xml serializing for mixed content with non generics. #238
Why naive?
The W3C XML Schema offers so much flexibility and abstraction layers and grammatical rules to support practically any xml document definition.
Integration teams and clients don’t care about any of that, take out abstraction and flexibility and you are left with lean named data structures with typed attributes and a namespace for humans to read!