XSDFormer
XSDFormer deforms XML schema definitions (XSDs) into Protobuf definitions. It also generates Python code to convert parsed XML into the corresponding Protobuf representation.
It supports enough of the XSD specification to convert the ClinVar and BioC schemas; full support for all XSD features is a non-goal.
Why convert from XSD to Protobuf?
While XML and XSDs (or alternatively JSON and JSON schemas) are powerful for defining complex, human-readable data structures, they have some drawbacks, especially in high-performance applications or when dealing with large datasets.
Performance and Size
- Parsing Speed: XML is a text-based format and can be slow to parse. Protobuf is a binary format that is designed for speed and efficiency. Converting XML data to Protobuf can result in significantly faster parsing times.
- Storage Space: XML is verbose, with opening and closing tags that add to the file size. Protobuf's binary format is much more compact, leading to smaller file sizes. This is a major advantage for storing large datasets or for transmitting data over a network. Effectively compressing XML requires a schema-specific dictionary, or compressing multiple records together so that the dictionary of tag/key names can be reused. However this limits the possibility for random access enabled by compressing records individually.
Developer Experience
- Generated Code: Protobuf compilers generate code in many languages, providing a simple and consistent way to work with the data.
- Type Safety: The Protobuf schema provides strong typing, which can help to prevent bugs. Parsing the wire format requires the protobuf definition, meaning that the data is tied to its typed representation. Conversely XML representations are only optionally validated by a schema, and so by default type information is lost during parsing (everything is treated as text).
By converting XSDs to Protobuf definitions, xsd-former allows
developers to take advantage of the benefits of Protobuf while still
working with data that is originally defined in an XML schema.
Output formats
From a single XSD (or DTD) source, XSDFormer can emit:
- Protobuf (
.proto) —--proto-out. - Python XML→protobuf converters —
--py-out/--py-module. - JSON Schema —
--json-schema-out(from the XSD, or directly from a.protovia theprotosubcommand).
Metadata
Release files for xsd-former 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| xsd_former-2.0.0.tar.gz | 210.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xsd_former-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 253.7 kB
Release files / xsd_former-2.0.0.tar.gz
| Download URL | xsd_former-2.0.0.tar.gz |
|---|---|
| Size | 210.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d21458028f5395e6652bf098089aedd6636758ad421dbbbfa29ad8e453908c8e
|
|
BLAKE2b-256 checksum How to use checksums |
a8c476fcbfa047ce8e847bf772015ebe03053039279d81cce6bd3c490d9708fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / xsd_former-2.0.0-py3-none-any.whl
| Download URL | xsd_former-2.0.0-py3-none-any.whl |
|---|---|
| Size | 43.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e44f7993ce9745ae171e538a6115e3ee75c58c6841275dd965b9211a59a1f39c
|
|
BLAKE2b-256 checksum How to use checksums |
2ec47f046c9190484b53a6971ce7b3498ce83bfd7e0f3aae6cd3952c744dcd02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for xsd-former 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xsd_former-2.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.