Skip to main content

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.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for melizalab-specs 0.1.1
File Size Uploaded Provenance Actions
melizalab_specs-0.1.1.tar.gz 18.5 kB With provenance Details for melizalab_specs-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for melizalab-specs 0.1.1
File Interpreter ABI Platform Actions
melizalab_specs-0.1.1-py3-none-any.whl Python 3 none any Details for melizalab_specs-0.1.1-py3-none-any.whl

Total release size: 42.8 kB

Release files / melizalab_specs-0.1.1.tar.gz

Download URL melizalab_specs-0.1.1.tar.gz
Size 18.5 kB
Tags Source
SHA-256 checksum
How to use checksums
bb928fff8238fa2fffebf41492e4d304fbda4e9b7a5dffbf498315b5393ad71d
BLAKE2b-256 checksum
How to use checksums
1ed03b9c176507a02262e69ed241c0ca2f3e01c7c648d766e07fac349bf0c0e1
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 log

Release files / melizalab_specs-0.1.1-py3-none-any.whl

Download URL melizalab_specs-0.1.1-py3-none-any.whl
Size 24.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
19ae208a289a05660ca5e41541af096fc46baafdbbd31485a7644f722e830663
BLAKE2b-256 checksum
How to use checksums
c0de0b1e06d85f88c4760b9df774fc82023e9f44e8c9ad9be3aae465a20cc5ce
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 log

Security for melizalab-specs 0.1.1

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.

Select from 2 files

Attestation for melizalab_specs-0.1.1.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 log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page