Meliza Lab Specifications
The specifications for the Meliza lab's data formats, published at
https://meliza.org/specifications/. Each is a markdown document in specs/,
with a JSON schema for formats that are JSON.
Python package
The schemas are also a Python package, melizalab-specs, so programs that read
or write these formats can validate against them without fetching them from the
website or keeping their own copies:
pip install "melizalab-specs[validate]"
import melizalab_specs
melizalab_specs.schemas() # every schema, keyed by its $id
melizalab_specs.schema("https://meliza.org/spec:2/pprox.json")
melizalab_specs.validate(document) # against the schema named in its $schema
melizalab_specs.validate(trial, "https://meliza.org/spec:2/pprox.json#pproc")
validate raises jsonschema.ValidationError for a document that doesn't
follow its schema, and melizalab_specs.UnknownSchemaError for a schema that
isn't one of these. Reading the schemas needs no dependencies; validating needs
the validate extra (jsonschema).
A new release of the package carries changes to the schemas to the programs that use them. Releases are published to PyPI from version tags.
Validating jsonschema
The JSON schemas in specs/ and the JSON examples in the markdown documents
(fenced code blocks marked json) are validated with pytest. With
uv:
uv run pytest
Each example is validated against the schema named in its $schema key. For
examples that don't have one, set a default with an example_schema key in
the document's YAML front matter:
---
title: pprox specification
example_schema: https://meliza.org/spec:2/pprox.json#pproc
---
(A schema can also be given in the code block's info string, as in
~~~ json {"$schema": "..."}, but kramdown, which compiles these documents
for the website, doesn't accept that.)
uv installs the dependencies listed in pyproject.toml, at the versions
recorded in uv.lock, into a local .venv, along with the package itself.
To update them, run uv lock --upgrade.
Metadata
Release files for melizalab-specs 0.1.2
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 | Actions |
|---|---|---|---|---|
| melizalab_specs-0.1.2.tar.gz | 19.1 kB | With provenance | Details for melizalab_specs-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| melizalab_specs-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for melizalab_specs-0.1.2-py3-none-any.whl |
Total release size: 44.2 kB
Release files / melizalab_specs-0.1.2.tar.gz
| Download URL | melizalab_specs-0.1.2.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88cb3852e38f83793e7903ec23409b509b32b2d985437581d6244e1044dbb2d8
|
|
BLAKE2b-256 checksum How to use checksums |
3270f53fcd6023a437e64c6b36734dc8476e5510a84a0bb9cae81bef5ca05280
|
| 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 22, 2026.
Transparency logRelease files / melizalab_specs-0.1.2-py3-none-any.whl
| Download URL | melizalab_specs-0.1.2-py3-none-any.whl |
|---|---|
| Size | 25.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c3d9eb8c6fa08a98bdedd6c7b9ace6673e798ffab9069245a50ebcfbdc85176
|
|
BLAKE2b-256 checksum How to use checksums |
35325d8aab82e8ccfd5cc18b921c1a61a4d870fa952eedb2772a2bd8feeea18f
|
| 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 22, 2026.
Transparency logSecurity for melizalab-specs 0.1.2
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 melizalab_specs-0.1.2.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 22, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.