This release is a pre-release and may not be stable for production use.
BIOMERO Schema
🚀 This package is part of
BIOMERO 2.0 — For complete deployment and FAIR infrastructure setup, start with the NL-BIOMERO Documentation 📖
Shared, versioned Pydantic contracts for the BIOMERO ecosystem.
Documentation · Python API · Pixel identity reference
The package keeps two contract areas separate:
biomero_schema.modelsis BIOMERO's normalized representation of a workflow descriptor.biomero_schema.zarr,biomero_schema.imports, andbiomero_schema.shallowerdefine internal cross-service contracts for managed Zarr sources, pixel identity, shallow collections, importer lifecycle operations, and remote shallowing reports and receipts.
Workflow descriptors
Workflow providers normally describe their tools using an external workflow
format. The adapters in biomero_schema.adapters detect and convert supported
formats into the validated WorkflowSchema from this package:
BIAFLOWS descriptor.json ─┐
├─> biomero adapters ─> WorkflowSchema ─> BIOMERO services
BILAYERS config.yaml ─────┘
Currently supported inputs are:
| Provider format | BIOMERO support |
|---|---|
BILAYERS config.yaml |
Converts the container, command, citations, inputs, parameters, and declared outputs. This is the preferred route for Zarr-to-Zarr and Plate-aware workflows. |
| BIAFLOWS/Cytomine descriptor | Converts the supported legacy cytomine-0.1 subset. It remains useful for established TIFF-oriented BIAFLOWS workflows. |
Native biomero-0.1 descriptor |
Validates directly. This is primarily BIOMERO's normalized service representation, although integrations may produce it explicitly. |
CWL and OpenAPI descriptors are not yet supported. The adapters were moved
here from biomero.schema_parsers
so descriptors can be converted without the BIOMERO runtime:
from biomero_schema.adapters import parse_descriptor
workflow = parse_descriptor(yaml.safe_load(open("config.yaml")))
The adapter determines which fields from an external format are currently converted.
See Workflow descriptors for the conversion boundary and supported mappings.
Installation
Python 3.11 or newer is required.
pip install biomero-schema
For development:
git clone https://github.com/NL-BioImaging/biomero-schema.git
cd biomero-schema
pip install -e .
The repository also supports Pixi:
pixi run test
Native descriptor validation
The CLI validates the normalized BIOMERO descriptor. BILAYERS (.yaml) and
BIAFLOWS descriptors are detected and converted before validation, and
parse --json writes the converted descriptor.
biomero-schema validate config.yaml
biomero-schema parse config.yaml --json > descriptor.json
biomero-schema validate descriptor.json
biomero-schema parse descriptor.json
biomero-schema parse descriptor.json --pretty
biomero-schema schema
A maintained native example is available at
tests/example_workflow.json.
Cross-service contracts
Consumers should import the shared models rather than duplicating JSON fields:
from biomero_schema.zarr import CanonicalZarrSource
source = CanonicalZarrSource.from_dict(payload)
wire_payload = source.to_dict()
json_schema = CanonicalZarrSource.model_json_schema()
The camelCase output from to_dict() is the stable wire representation. Every
contract family carries its own integer schema, independently of the workflow
descriptor version.
The shallow-Zarr manifest is an experimental, versioned BIOMERO storage contract, not RFC-8 metadata. Its portable image/label graph is separate from BIOMERO storage and provenance bindings so that a future standards adapter can reuse the graph without redefining the operational data.
See Remote shallower contracts for the report formats, trusted receipt hand-off, and compatibility requirements. These models do not enable shallow storage or remote execution; feature configuration belongs to the consuming services.
Documentation development
python -m pip install -e .
python -m pip install -r docs/requirements.txt
mkdocs serve
Use mkdocs build --strict to reproduce the documentation CI build. See
docs/contributing.md for publishing details.
Metadata
Release files for biomero-schema 0.3.0b4
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 |
|---|---|---|---|---|
| biomero_schema-0.3.0b4.tar.gz | 88.4 kB | Without provenance | Details for biomero_schema-0.3.0b4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| biomero_schema-0.3.0b4-py3-none-any.whl | Python 3 | none | any | Details for biomero_schema-0.3.0b4-py3-none-any.whl |
Total release size: 122.1 kB
Release files / biomero_schema-0.3.0b4.tar.gz
| Download URL | biomero_schema-0.3.0b4.tar.gz |
|---|---|
| Size | 88.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fca1db4e5d426b634da0d44ea9441a9042cf0aa163824e6f60f007cbbb6459fe
|
|
BLAKE2b-256 checksum How to use checksums |
b948c33f9220a30d1e3613c25d8bd92a5f6ece2f409696b076f152e73f879185
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / biomero_schema-0.3.0b4-py3-none-any.whl
| Download URL | biomero_schema-0.3.0b4-py3-none-any.whl |
|---|---|
| Size | 33.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
172a14521d0e3031473528663c2f2d6097bee0e664a36bc9eb794fc515c8b51d
|
|
BLAKE2b-256 checksum How to use checksums |
1c77466501f4fdd76b5c19acba982ad03bff116b6c69ec3e83d76b6ee10dc983
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for biomero-schema 0.3.0b4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.