Participate in WWD | Wetware World

Status

WWD 0.1 is a specification with twenty-five normative sections, a JSON Schema set, a reference validator, a conformance suite and example packages that round-trip. It is implementable. It is untested against external work.

There are no adopters and no external implementers. There is no consortium, working group or standards-body relationship. Neutral custody is planned, not in place. The registries are thin.

Six questions

Each changes a specific part of the format. Answer any of them, in any order.

01

Technician hours per batch

Skilled human time per batch, end to end: feeds, media changes, imaging and the analysis afterwards.

02

Batch failure rate, and how you find out

The fraction of batches discarded, the point in the process at which this is discovered, and whether the cause is identifiable. Late detection requires intermediate acceptance criteria.

03

Maturation delay before a construct is usable

Days from seeding to usable state. WWD gives a component a validity window with an explicit time origin: a construct at day 7 and the same construct at day 21 are different articles.

04

What you measure before accepting a batch

The measurement, the instrument, the threshold, and whether it is recorded in a form a second person could reproduce.

05

What mechanical, electrical or fluidic interface you need

How the component physically attaches: loop anchors, pillar spacing, electrode pitch, well geometry, tubing connections, optical access.

06

The thing WWD cannot represent

A property with no slot, a quantity with no unit, or an assay whose calculation cannot be written down.

01 Who you are

Name *

Email * Used to reply to you and for nothing else.

Institution or company

Which of these fits best *

What do you work with

Engineered skeletal or cardiac muscle Neural culture on a substrate or MEA Organoids or spheroids Reconstructed epithelium or barrier model Organ-on-chip or perfused model Biohybrid actuator or robotic element Scaffolds, hydrogels or culture devices Cell banking, expansion or differentiation

02 Your current process

This is the part we care about. Nothing here is required, answer what you can, skip what you cannot, and approximate freely. A rough number you are unsure of is worth more than a blank.

Technician hours per batch End to end, including the analysis afterwards.

Batch failure rate And where in the process you discover it.

Maturation delay before a construct is usable

Batches per month

What do you measure before you accept a batch

What mechanical, electrical or fluidic interface do you need

Where does the current process hurt most

03 On the draft itself

Only if you have read some of it. Skipping this section is completely reasonable.

Something WWD cannot represent In a draft standard this is the most valuable message we can get.

Something in the draft that is wrong

You may follow up with questions about my answers. You may credit me by name in the changelog if something I said changes the specification. Unchecked means anonymous.

Read by a person. Every reply gets an answer, including the ones that tell us we are wrong.

Prefer email

[email protected]

A paragraph in an email is worth more than a completed form. Attach a protocol, a plate map, a figure, or a specification you had to write by hand.

What is most useful

A component the format cannot describe	Send the thing you were trying to express and the point at which it broke.
A quantity with no unit, or an ambiguous unit	Units are mandatory everywhere in WWD. If your quantity has no sensible unit in UO or UDUNITS-2, that is a real gap.
An acceptance criterion whose method cannot be written down	If two laboratories cannot reproduce the calculation from the file alone, name the field.
A biological identity with no CURIE	WWD delegates to CL, NCBI Taxonomy, UBERON, ChEBI, Cellosaurus and SBOL. Report identities covered by none of them.
A real .wwd file	From production work rather than a test case. Round-tripping real designs reveals which fields are wrong.

What will be declined

New vocabularies for things that already have one. If the Cell Ontology has the cell type, WWD uses the Cell Ontology.
Fields that encode a unit in their name. force_mN is not acceptable; force with an explicit unit is.
A number without a method. A force value that does not state how it was measured is not comparable between suppliers.
Anything that makes the simple case harder. A uniform property must stay one quantity string.
Backing types outside the core five. external is an escape hatch, not a sixth backing; new backings need an extension namespace.

Licensing of what you send

Anything you send is used to improve the specification. Specification prose is CC BY 4.0 and schemas and code are Apache-2.0, so if your input becomes part of the draft it is published under those terms. If you send something confidential, say so and it will be used only to inform decisions, never quoted or published.

Change process

1

Issue before pull request

Anything beyond a typo starts as a written problem statement. A change to a normative section without prior discussion is returned as an issue.
2

Fixture required

Every normative change ships with one valid and one invalid example, which become validator tests. Conformance review is the gate.
3

Additive by default

New versions add capability. Redefining an existing field is possible only in a major version with a migration path. A term that meant peak isometric force in 0.1 keeps that meaning; a new concept gets a new term.
4

Public changelog

Each change is published with its reason and the contributor named, unless they requested otherwise.

Participate

Status

Six questions

Technician hours per batch

Batch failure rate, and how you find out

Maturation delay before a construct is usable

What you measure before accepting a batch

What mechanical, electrical or fluidic interface you need

The thing WWD cannot represent

Change process

Issue before pull request

Fixture required

Additive by default

Public changelog

Submit feedback