S1000D Publication Modules and Applicability
A Publication Module organizes Data Module references for a deliverable. Applicability logic filters the content for a product or configuration before the final package is checked and released.
What does a PM do?
A Publication Module provides publication structure and references, commonly through DMRef entries. It is not the same as a Data Module: the PM organizes a deliverable while the DM carries technical information.
How does applicability affect delivery?
Product attributes and project-defined conditions determine which modules, media and references belong in a product-specific publication. The conditions, syntax and evaluation behavior must follow the adopted Issue and project applicability rules.
From source data to delivery
- Approve the required Data Modules and media.
- Build the PM and verify DMRef references.
- Evaluate applicability for the target product or configuration.
- Check missing, duplicate, obsolete and incompatible objects.
- Generate PDF, IETP or offline delivery packages and record acceptance evidence.
| Delivery check | Question |
|---|---|
| Structure | Does the PM follow the expected publication hierarchy? |
| References | Do all DMRef, media and external references resolve to approved versions? |
| Applicability | Does the target configuration show the right modules and suppress the wrong ones? |
| Reading result | Are navigation, search, graphics, warnings and links usable in the target reader? |
See CSDB for source control and validation for quality gates.
Frequently asked questions
Is a PM the same as a Data Module?
No. A PM organizes a publication and references Data Modules; a Data Module carries a technical information unit.
Does applicability filtering prove delivery completeness?
No. References, media, navigation, safety content and target-reader behavior still need delivery acceptance.