Information technology — Business operational view — Part 21: Guidance on the application of the Open-edi business transaction ontology in distributed business transaction repositories
Introduction: ISO/IEC 15944-4 defines the Open-edi Business Transaction Ontology (OeBTO) as a formal, rule-based specification and definition of the concepts pertaining to business transactions and scenarios and the relationships that hold among these concepts. Figure 1 overviews the ontology of a business transaction. It is taken from ISO/IEC 15944-4:2015, Figure 21, modified as follows to bring to light certain properties that were not illustrated at the time: — the generalization of “Partner” to “Person” is according to ISO/IEC 15944-4:2015, Figure 18; — the business policy connections between the three types (i.e. Economic Resource Type, Economic Event Type and Economic Role) is according to ISO/IEC 15944-4:2015, Figure 13; and — the connections of party (OeP) and counterparty (OeCP) are shown as distinct persons having negotiated the Economic Contract. Figure 1 — Open-edi Business Transaction Ontology According to ISO/IEC 15944-4, each business entity, depicted as a box in the diagram, is a computable representation of a real- world entity that participates, occurs, or is materialized during a business transaction. These are either static representations for the duration of the business transaction or dynamically changing representations implemented as individual state machines. Different business events effecting the business transaction are inputs influencing different sets of one or more of the state machines and changing their individual states. The particular states that each bus
Scope: This document specifies the business operational view of an implementation of an Open-edi Distributed Business Transaction Repository (OeDBTR), building on the principles and concepts defined in ISO/IEC 15944-4 of a business transaction. The repository stores the history of the transitions in states of the economic claim and/or other business entities that happen over the course of a business transaction, and does so for a collection of business events. These business events, comprised of transactions and their states, can be identified unambiguously so as to provide the ability to inspect or query the information at some point after the record has been made. The distributed nature of the repository offers users ubiquitous and robust access to the recorded history. A history of business transactions of market exchanges can be useful in auditing or other memoing- based activities, looking back at the immutable record of the interactions between parties. This document does not specify the Functional Services View of a particular implementation of an Open-edi Distributed Business Transaction Repository. For best performance, candidate technologies would likely exhibit properties of long-term permanence, robust immutability, decentralized access, distributed resilience, and fine-grained addressability.