Proposing a new PMD class "Standard"

[KhashiYaar]

Summary

Introduce a dedicated class for Standards — directive information entities (e.g., DIN, EN, ISO, ASTM documents) issued or maintained by a standardization body.
This addition enables clear distinction between recipes we execute and standards we comply with, allowing explicit modeling of relationships such as: “This recipe complies with EN 515 Temper Designation.”

---

Motivation

Materials-science and engineering datasets routinely reference formal and internal standards, yet PMD currently lacks a first-class category to represent these normative artifacts.

Adding Standard class enables:

• Representation of normative artifacts (DIN/EN/ISO/ASTM etc.) as first-class directive entities defining standardized plan specifications, test methods, naming systems, measurement methods, or data formats.
• Interoperability across mid-level, application, and domain ontologies by linking recipes, identifiers, and datasets to their Governing Standards and issuing or maintaining organizations.
• Richer queries & reasoning, such as retrieving all standards a process complies with; checking the governance or rights associated with a standard; or distinguishing official public standards from internal/corporate specifications.

Standard - intended Definition
A directive information entity issued or maintained by a standardization body that prescribes requirements, constraints, or controlled vocabularies for processes, measurements, material designations, or data structures. It may specify executable plan specifications and/or define designation or data-format rules that artifacts, procedures, or datasets must conform to.

---

Candidate for Reuse / Adaptation

Standard T4FS:0000381 — from [Terms4FAIRSkills ontology](https://www.ebi.ac.uk/ols4/ontologies/t4fs/classes/http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FT4FS_0000381)

Definition:
Standard T4FS:0000381 Defnition
“Set of agreed-upon and documented guidelines, specifications, accepted practices, technical requirements, or terminologies prepared by a standards-developing organization or group, and published in accordance with established procedures. These can be mandatory or voluntary and are distinct from Acts, regulations, and codes, although standards can be referenced in those legal instruments.”

Placement:
entity (bfo)
  continuant (bfo)
    generically dependent continuant (bfo)
        information content entity (iao)
         data stewardship technical concept (T4FS)
          standard (T4FS)

---

Example subclass pattern

Standard
├── co:DesignationStandard
├── co:MeasurementStandard
├── co:TestMethodStandard
├── co:TerminologyStandard
└── etc. etc.

Object Properties (for consideration)

• denotes ?
• is_denoted_by ?
• complies_with ?
• issued_by ?
• other?!

---

Cautions !

• check the class hierarchies, if/how the upperclass of "Standard" in T4FS ("data stewardship technical concept" obo/T4FS_0000372 ), can be complementary to the PMDco class "directive information entity" (obo/IAO_0000033)
• Import vs. Adaptation: check whether it is appropriate to formally import the T4FS class (Standard) or Adapt the definition & create a PMD-specific co:PMD_Standard class. Consider implications for superclass alignment, inherited axioms, and interoperability with PMD’s existing directive information entity structure.
• check for possible disjointness rules...

[webhart]

I strongly support the idea of having a concept for "standard" ICEs although I am not sure we should integrate it in the core module. During our discussion of the "digital material identifier" DMI we came accross several artifacts that materials could "comply_with", e.g.: standards issued by a recognised standardization body, datasheets issued by a material manufacturer, company internal guidelines or even scientific publications describing properties of a material where the material is designated using common sense concepts. A possible solution may be to integrate those directive ICEs to the logistics module.

In any case we should have a pattern to weakly link continuants to directive ICEs. (For occurents we have the planned process that is linked to a plan.)