Publishers

CORRESPONDING PILLAR Publishers drive the Define pillar. They author and publish the reference models that everyone else consumes.

The pitch , for standards developers and SDOs

The world today. A standard ships as a PDF and immediately begins to die. Ambiguities surface years later, in implementers’ inboxes, one interpretation at a time. Every conformance regime built on the text is a bespoke lab exercise. Errata wait for the next revision cycle. Your authority ends at publication , what industry does with the prose after that is folklore you cannot see, measure, or correct.

What changes. In Primmel, the standard is the executable model. Requirements are constraints over a subject’s IS/HAS/DOES; tests are processes that probe those aspects; report forms are the evidence interfaces. Ambiguity stops being a lawsuit risk and becomes a compile error. Every provision carries clause-level provenance back to the source document, and an edition transition is a model diff , computed, reviewed, and published , never a re-keying exercise.

What it looks like in practice. You author a .prl package; the kernel’s linter (C1-C99) grades it; the coverage calculus proves your tests actually cover your requirements before you publish. OIML does this today: 28 packages spanning four Recommendations, the OIML-CS scheme, and the shared CASCO foundations , all lint-clean, all generated artifacts byte-proven against the source of truth.

The proof. The kernel suite runs 1,062 tests; the OIML SMART program runs the full certification chain end to end (57/57 browser e2e). The living example is OIML SMART , a whole standards program already built on the platform.

The tool. Author with Primmel Studio, the canvas, the inspectors, the doc map back to the source document’s statements, and the validation badge that never sleeps. When the badge is green and the coverage is full, the standard is ready to publish.

Your next step. Read the kernel volume for the full language surface, or build a first model in fifteen minutes.

Who they are

Publishers are the originating authors of a Primmel reference model. The defining feature isn’t who they are , it’s what they do: they release a model for others to consume. Common publisher types:

• Standards bodies , BSI, OIML, ISO, IEC and other national or international standards organisations.
• Industry consortia , sector-specific groups publishing reference frameworks for their members.
• Regulators , government or quasi-government bodies publishing compliance frameworks they enforce.
• Large organisations , companies publishing internal frameworks intended for their subsidiaries, suppliers, or business partners to map to.
• Tooling vendors , occasionally, vendors publish reference models as templates that customers can extend.

What they’re trying to accomplish

• Express a standard’s provisions, processes, and data requirements in a typed, machine-readable form.
• Make the standard instantly available , not just as a PDF, but as an executable artefact.
• Provide a stable, versioned namespace (OCS#, ISO13485#, etc.) that downstream implementers can alias in their own models.
• Trace every provision back to the source clause in the original standard document (via .prd extracts and reference declarations).
• Publish the model under terms that allow adopters, readers, and auditors to consume it freely.

Artifacts they consume / produce

Tools they use

• Authoring editors , purpose-built Primmel editors (e.g. the Paneron extension) for structuring models.
• Validation tooling , structural checks on the model before publication: parse errors, broken cross-references, missing declarations.
• .prd extractors , tools that turn a source PDF or document into a clause-level extract aligned with the reference model’s provisions.
• Publication registries , versioned distribution points where adopters can fetch the published .prl.

A worked example

The implementation package includes a fictional Office Coffee Standard. The publisher’s artefacts are ocs-standard.prd (the clause extract) and the OCS#-prefixed declarations inside acme-coffee-programme.prl (which mirror what the published reference would declare). Acme, as the adopter, doesn’t author these , the publisher does. Acme imports them via the OCS# namespace prefix.

See also

• Define pillar , the architectural activity this audience drives.
• Readers , the next audience downstream, who consume what Publishers produce.
• Implementers , the audience that adopts and maps to the published reference.