Publishers

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

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