- ISO 15926 Primer
- ISO15926 Standard Structure
- IDS-ADI Coordination Structure
- IDS-ADI Infrastructure
- The AVALON Project
- Core Modelers Projects
- Core Implementers Projects
- Core Compliance Project
- Core Methodology Project
- IDS-ADI Matrix Master (login)
- IDS-ADI Matrix 1,2,3 activity
- IDS-ADI Matrix 4 activity
- IDS-ADI Matrix 8 activity
- IDS-ADI Part3 Harmonization
- IDS-ADI BIDG (aka Handover Guide)
- IDS-ADI Proteus Project
POSC-Caesar FIATECH IDS-ADI Projects
Intelligent Data Sets Accelerating Deployment of ISO15926
Realizing Open Information Interoperability
Template Implementation Modelling
This is a topic discussion page of the IDS-ADI Core Modellers. The focus is modelling for implementation and business use, NOT to revisit or revise conceptual and logical modelling so far.
Those points considered agreed as implementable needs are summarised here. (Rationale leading to these are found in the discussion and comments below.)
A. In order to maintain the maximum potential exploitation beyond the scope of ISO15926, Part2, Part7, Part8 and Part9 will remain as unconstrained as possible, eg as close to generic ontological modelling, first order logic and native W3C standards as practicable.
B. In order to achieve effective, efficient, performant, reliable and manageable implementations in the ISO15926 industrial domain, constraints will be added through reference content ("RDL Items") and content rules. (There remain choices about whether such rules are implemented in content, in functional code, or in verifiable processes. The more they can be implemented in the content itself, the less reliance there will be on code and processes, but ... )
C. These are rules that apply to RDL Items, and their ISO15926 compliant usage, independent of their level of standardization in the iRING federated reference data technology architecture.
- Some of these rules for Part4 content arise explicitly from existing Part5 & Part6.
- Some arise from compliance and industrial usage guidelines (eg drafts for Part11).
- Some arise from direct implementation experience with Part7 and Part8 / Part9 prototypes.
- Ultimately all standardization-level-independent rules, however implemented, should probably be documented in Part5.
All references shall be to an RDL Item record instance "standing for" the relevant item, whether the item is a Part2 entity, a Part7 (or other) Template, a Class, Class-of-Class or a reference individual of any kind.
Templates (RDL Items standing for ..) may be used as roles in other templates.
Any Template roles used to specialize or constrain template use shall be entity type (RDL Item standing for ...) specializations, except ... (To be added ... )