ISO/IEC 15944-16:2023

INTERNATIONAL ISO/IEC
STANDARD 15944-16
First edition
2023-06
Information technology — Business
operational view —
Part 16:
Consolidated set of the rules and
guidelines identified in ISO/IEC 15944
Business Operational View standards
and their IT-enablement
Reference number
ISO/IEC 15944-16:2023(E)
© ISO/IEC 2023

---------------------- Page: 1 ----------------------
ISO/IEC 15944-16:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 15944-16:2023(E)
Contents Page
Foreword .vii
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms .14
5 Overview of rules and guidelines in the ISO/IEC 15944 series .15
5.1 General . 15
5.2 Representation of rules and guidelines in the ISO/IEC 15944 series .15
5.2.1 General .15
5.2.2 Physical representation . 15
5.2.3 Verbal representation . 16
5.3 Principles for the consolidation process of BOV rulebase . 16
5.3.1 Principle 1: Maintain the integrity of the source rule and associated
guideline . 16
5.3.2 Principle 2: Maintain the cross referencing mechanism of the rules . 16
5.3.3 Principle 3: Ensure timeliness of rulebase . 17
5.3.4 Principle 4: Facilitate search and retrieval for use. 17
6 Rules governing the assignment of unique eBusiness rule ID .17
6.1 eBusiness rule ID . 17
6.2 Composite identifier . 18
7 BOV rulebase model .19
7.1 Overview of BOV rulebase model . 19
7.2 Object classes in the BOV rulebase model . 20
7.2.1 Rulebase class .20
7.2.2 Rule class . 21
7.2.3 Guideline class .22
7.2.4 Rule_relation class .23
7.2.5 Relationship_role class . . .23
7.3 Associations in the BOV rulebase model . 23
7.3.1 rulebase_reference association . 23
7.3.2 rulebase_importation association . 24
7.3.3 rulebase_rule_membership association . 24
7.3.4 rulebase_rule_source association . 24
7.3.5 rulebase_relation_inclusion association . 24
7.3.6 rule_guideline association . 25
7.3.7 relation_role_source association . 25
7.3.8 rule_role association .25
8 Maintenance and management of BOV rulebase .25
8.1 General . 25
8.2 Rules for maintenance of BOV rulebase . 25
8.3 Rules governing the management of BOV rulebase . 26
8.3.1 General . 26
8.3.2 Addition of rules . 26
8.3.3 Amendment of rules .26
8.3.4 Deletion of rules . 27
8.4 Quality control of rulebase . 27
Annex A (normative) Consolidated controlled vocabulary definitions and associated
terms, as human interface equivalents (HIEs), with cultural adaptability: English
and French language equivalency in an IT standardization context.28
iii
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 3 ----------------------
ISO/IEC 15944-16:2023(E)
Annex B (normative) Consolidated set of all rules and guidelines identified in ISO/IEC
15944 business operational view standards .31
Annex C (normative) Set of keywords used by rules . 206
Bibliography . 212
iv
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 15944-16:2023(E)
List of Figures
Figure 1 — BOV rulebase model .19
v
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 15944-16:2023(E)
List of Tables
Table 1 — Example of rule and guideline physical representation in BOV standards .16
Table 2 — Example of rules composite identifiers — Structure and representation
equivalent .18
Table 3 — Example of guidelines composite identifiers — Structure and representation
equivalent .18
Table 4 — Attributes of rulebase class .21
Table 5 — Attributes of rule class .22
Table 6 — Attributes of guideline class .22
Table 7 — Attributes of relation class .23
Table 8 — Attributes of relationship_role class .23
Table B.1 — Organization of columns in Table B.2 .31
Table B.2 — eBusiness rules and associated guidelines entries.33
Table C.1 — Representation of keywords . 206
Table C.2 — Keywords used by eBusiness rules and associated guidelines . 206
vi
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 15944-16:2023(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of
any claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC
had not received notice of (a) patent(s) which may be required to implement this document. However,
implementers are cautioned that this may not represent the latest information, which may be obtained
from the patent database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall
not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
A list of all parts in the ISO/IEC 15944 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
vii
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 15944-16:2023(E)
Introduction
0.1  Purpose and overview
All parts of the ISO/IEC 15944 BOV series are based on the first and primary characteristic of Open-edi
that states that all actions are based on following clear and predefined rules (see ISO/IEC 15944-1:2023,
5.1).
This rule-based approach is central to all existing normative parts of ISO/IEC 15944 and is captured
through a series of rules and (associated) guidelines. The main objective of this document is first to
bring all these rules and guidelines together in a single document, and second provide an IT-enabled
BOV rulebase model to facilitate business applications. The BOV rulebase model can also be used to
the construction of other custom rulebases of eBusiness application requirements (e.g. “a rulebase that
provide instructions and requirements for implementing aspects of privacy protection”).
In keeping also with a central approach and philosophy of the ISO/IEC 15944 series, all rules and
associated guidelines will be referenced using eBusiness rule IDs.
The purpose, therefore, of this document is four-fold:
1) to provide a consolidation of all normative rules and associated guidelines;
2) to provide a unique ID number for each rule and associated guideline within the overall
ISO/IEC 15944 context;
3) to use a BOV rulebase model approach to capture and describe all BOV rulebases; and
4) to provide a systematic approach enhancing the IT-enablement.
0.2  IT systems environment neutrality
This document does not assume or endorse any specific system environment, database management
system, database design paradigm, system development methodology, data definition language,
command language, system interface, user interface, syntax, computing platform, or any technology
required for implementation, i.e. it is information technology neutral. At the same time, this document
maximizes an IT-enabled approach to its implementation and maximizes semantic interoperability.
viii
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 15944-16:2023(E)
Information technology — Business operational view —
Part 16:
Consolidated set of the rules and guidelines identified in
ISO/IEC 15944 Business Operational View standards and
their IT-enablement
1 Scope
This document provides a consolidated set of rules and associated guidelines as found and defined in
the existing parts of the ISO/IEC 15944 series.
NOTE Not all parts of the ISO/IEC 15944 series have rules, that is ISO/IEC 15944-6, ISO/IEC 15944-14 and
ISO/IEC 15944-20.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 15944-2, Information technology — Business operational view — Part 2: Registration of scenarios
and their components as business objects
ISO/IEC 15944-7, Information technology — Business operational view — Part 7: eBusiness vocabulary
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
attribute
characteristic of an object or entity (3.21)
[SOURCE: ISO/IEC 15944-5:2008, 3.4]
3.2
business
series of processes, each having a clearly understood purpose, involving more than one Person (3.43),
realized through the exchange of recorded information and directed towards some mutually agreed
upon goal, extending over a period of time
[SOURCE: ISO/IEC 14662:2010, 3.2]
1
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 15944-16:2023(E)
3.3
business operational view
perspective of business transactions (3.6) limited to those aspects regarding the making of business
(3.2) decisions and commitments (3.11) among Persons (3.43), which are needed for the description of a
business transactions
[SOURCE: ISO/IEC 14662:2010, 3.3]
3.4
BOV rulebase
rulebase (3.59) designed for the consolidated set of rules (3.57) and associated guidelines (3.24)
identified in ISO/IEC 15944 BOV (3.3) standards (3.65)
3.5
BOV rulebase model
conceptual specification and description of the organization, and relationship(s) (3.53) within a BOV
rulebase (3.4)
3.6
business transaction
predefined set of activities and/or processes of Persons (3.43) which is initiated by a Person to
accomplish an explicitly shared business (3.2) goal and terminated upon recognition of one of the agreed
conclusions by all the involved Persons although some of the recognition may be implicit
[SOURCE: ISO/IEC 14662:2010, 3.4]
3.7
buyer
Person (3.43) who aims to get possession of a good, service and/or right through providing an acceptable
equivalent value, usually in money, to the Person providing such a good, service and/or right
[SOURCE: ISO/IEC 15944-1:2023, 3.8]
3.8
capability
user implementation condition stated in a guideline (3.24) to a rule (3.57) that conveys the ability,
fitness, quality, necessary to comply with the requirement (3.55) in the rule
Note 1 to entry: Other implementation conditions that are found in guidelines include: permission, possibility
and recommendation.
3.9
code
data (3.15) representation in different forms according to a pre-established set of rules (3.57)
Note 1 to entry: In this document, the "pre-established set of rules" are determined and enacted by a Source
Authority (3.64) and shall be explicitly stated.
[SOURCE: ISO 639-2:1998, 3.1]
3.10
coded domain
domain for which (1) the boundaries are defined and explicitly stated as a rulebase (3.59) of a coded
domain Source Authority; and, (2) each entity (3.21) which qualifies as a member of that domain is
identified through the assignment of a unique ID code (3.27) in accordance with the applicable
Registration Schema of that Source Authority (3.64)
Note 1 to entry: The rules governing the assignment of an ID code to members of a coded domain reside with its
Source Authority and form part of the Coded Domain Registration Schema of the Source Authority.
Note 2 to entry: Source Authorities which are jurisdictional domains are the primary source of coded domains.
2
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 15944-16:2023(E)
Note 3 to entry: A coded domain is a data set for which the contents of the data element values are predetermined
and defined according to the rulebase of its Source Authority and as such have predefined semantics.
Note 4 to entry: Associated with a code in a coded domain can be: a) one and/or more equivalent codes; b)
one and/or more equivalent representations especially those in the form of Human Interface Equivalent (HIE)
(linguistic) expressions.
Note 5 to entry: In a coded domain the rules for assignment and structuring of the ID codes shall be specified.
Note 6 to entry: Where an entity as member of a coded domain is allowed to have, i.e., assigned, more than one ID
code, i.e., as equivalent ID codes (possibly including names), one of these shall be specified as the pivot ID code.
Note 7 to entry: A coded domain in turn can consist of two or more coded domains, i.e., through the application of
the inheritance principle of object classes.
Note 8 to entry: A coded domain may contain ID code which pertain to predefined conditions other than
qualification of membership of entities in the coded domain. Further, the rules governing a coded domain may
provide for user extensions.
EXAMPLE 1 (1) the use of ID Code "0" (or "00", etc.) for “Others, (2) the use of ID Code "9" (or "99", etc.) for “Not
Applicable”; (3) the use of “8” (or “98”) for “Not Known”; and/or, if required, (4) the pre-reservation of a series of
ID codes for use of “user extensions”.
Note 9 to entry: In object methodology, entities which are members of a coded domain are referred to as instances
of a class.
EXAMPLE 2 In UML modelling notation, an ID code is viewed as an instance of an object class.
[SOURCE: ISO/IEC 15944-2:2015, 3.13]
3.11
commitment
making or accepting of a right, obligation, liability or responsibility by a Person (3.43) that is capable of
enforcement in the jurisdictional domain (3.33) in which the commitment is made
[SOURCE: ISO/IEC 14662:2010, 3.5]
3.12
composite identifier
identifier (3.29) (in a business transaction (3.6)) functioning as a single unique identifier consisting of
one or more other identifiers, and/or one or more other data elements (3.16), whose interworkings are
rule-based
Note 1 to entry: Identifiers (in business transactions) are for the most part composite identifiers.
Note 2 to entry: The rules governing the structure and working of a composite identifier should be specified.
Note 3 to entry: Most widely used composite identifiers consist of the combinations of: (a) the ID of the overall
identification/numbering schema, (e.g. ISO/IEC 6532, ISO/IEC 7812, ISO/IEC 7506, UPC/EAN, ITU-T E.164,
etc.), which is often assumed; (b) the ID of the issuing organization (often based on a block numeric numbering
schema); and, (c) the ID of the entities forming part of members of the coded domain of each issuing organization.
[SOURCE: ISO/IEC 15944-2:2015, 3.16]
3.13
concept
unit of knowledge created by a unique combination of characteristics
Note 1 to entry: Concepts are not necessarily bound to particular languages. They are, however, influenced by
the social or cultural background which often leads to different categorizations.
[SOURCE: ISO 1087:2019, 3.2.7]
3
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 15944-16:2023(E)
3.14
controlled vocabulary
vocabulary whose entries, i.e., definition (3.17)/term (3.66) pairs, are controlled by a Source Authority
(3.64) based on a rulebase (3.59) and process for addition/deletion of entries
Note 1 to entry: In a controlled vocabulary, there is a one-to-one relationship of definition and term.
EXAMPLE The contents of "Clause 3 Terms and definitions" in ISO/IEC standards are examples of controlled
vocabularies with the entities being identified and referenced through their ID code, i.e., via their clause numbers.
Note 2 to entry: In a multilingual controlled vocabulary, the definition/term pairs in the languages used are
deemed to be equivalent, with respect to their semantics.
Note 3 to entry: The rulebase governing a controlled vocabulary may include a predefined concept system.
[SOURCE: ISO/IEC 15944-5:2008, 3.34]
3.15
data
reinterpretable representation of information in a formalized manner suitable for communication,
interpretation, or processing
Note 1 to entry: Data can be processed by humans or by automatic means.
[SOURCE: ISO/IEC 2382:2015, 2121272]
3.16
data element
unit of data (3.15) for which the definition (3.17), identification (3.28), representation and permissible
values are specified by means of a set of attributes (3.1)
[SOURCE: ISO/IEC 11179-1:2015, 3.3.8]
3.17
definition
representation of a concept (3.13) by an expression that describes it and differentiates it from related
concepts
[SOURCE: ISO 1087:2019, 3.3.1]
3.18
eBusiness
business transaction (3.6), involving the making of commitments (3.11), in a defined collaboration space,
among Persons (3.43) using their IT Systems, according to Open-edi (3.39) standards (3.65)
Note 1 to entry: eBusiness can be conducted on both a for-profit and not-for-profit basis.
Note 2 to entry: A key distinguishing aspect of eBusiness is that it involves the making of commitment(s) of any
kind among the Persons in support of a mutually agreed upon goal, involving their IT systems, and doing so
through the use of EDI (using a variety of communication networks including the Internet).
Note 3 to entry: eBusiness includes various application areas such as “e-commerce”, “e-administration”,
“e-logistics”, “egovernment”, “e-medicine”, “e-learning”, etc.
Note 4 to entry: The equivalent French language term for “eBusiness” is always presented in its plural form.
[SOURCE: ISO/IEC 15944-7:2007, 3.06]
3.19
eBusiness rule ID
unique alphanumeric character string that unambiguously identifies a rule (3.57) in the consolidated
set of all rules and guidelines (3.24) identified in ISO/IEC 15944 BOV (3.3) standards (3.65)
4
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 12 ----------------------
ISO/IEC 15944-16:2023(E)
3.20
Electronic Data Interchange
EDI
automated exchange of any predefined and structured data (3.15) for business (3.2) purposes among
information systems of two or more Persons (3.43)
Note 1 to entry: This definition includes all categories of electronic business transactions.
[SOURCE: ISO/IEC 14662:2010, 3.8]
3.21
entity
any concrete or abstract thing that exists, did exist, or might exist, including associations among these
things
EXAMPLE person, object, event, idea, process, etc.
Note 1 to entry: An entity exists whether data about it are available or not.
[SOURCE: ISO/IEC 2382:2015, 2121433]
3.22
external constraint
constraint which takes precedence over internal constraints in a business transaction (3.6), i.e., is
external to those agreed upon by the parties to a business transaction
Note 1 to entry: Normally, external constraints are created by law, regulation, orders, treaties, conventions or
similar instruments.
Note 2 to entry: Other source
...