This is an old revision of the document!
16.5 Logical Information Requirements
-
The Logical Architecture / PIM SHALL define Logical Data Structure Definition and Logical Data Structure Instance.
-
The Logical Architecture / PIM SHALL define logical information categories, including Logical Message, Logical Event, Logical Command, Logical Acknowledgement, Logical Assertion, Logical Record, and Logical Information Lineage.
-
A Logical Data Structure Definition SHALL describe the structure, meaning, and constraints of an information class at the platform-independent logical level.
-
A Logical Data Structure Instance SHALL represent a populated occurrence of a Logical Data Structure Definition.
-
A Logical Message SHALL represent a Logical Data Structure Instance exchanged through a Logical Communication Endpoint.
-
A Logical Event SHALL represent a Logical Data Structure Instance reporting an occurrence, observation, state change, decision, or result.
-
A Logical Command SHALL represent a Logical Data Structure Instance expressing an intended action.
-
A Logical Acknowledgement SHALL represent a Logical Data Structure Instance reporting receipt, acceptance, rejection, completion, failure, or outcome.
-
A Logical Assertion SHALL represent a Logical Data Structure Instance stating a conclusion, derived fact, validation result, interpretation result, analytical result, policy decision, or other claim.
-
A Logical Record SHALL represent a Logical Data Structure Instance preserved for continuity, review, audit, provenance, replay, reconstruction, or Evidence.
-
Logical Information Lineage SHALL identify relationship history among Logical Data Structure Instances across exchange, transformation, validation, interpretation, assertion, persistence, replay, release, and Evidence.
-
The Logical Architecture / PIM SHALL distinguish logical information structures from serialisation formats, schema languages, database structures, ontology languages, programming-language type systems, wire formats, generated code, and implementation payloads.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.