ISO/IEC 15944-1:2002
(Main)Information technology — Business agreement semantic descriptive techniques — Part 1: Operational aspects of Open-edi for implementation
Information technology — Business agreement semantic descriptive techniques — Part 1: Operational aspects of Open-edi for implementation
Technologies de l'information — Techniques descriptives sémantiques des accords d'affaires — Partie 1: Aspects opérationnels de l'Edi ouvert pour application
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 15944-1
First edition
2002-08-15
Information technology — Business
agreement semantic descriptive
techniques —
Part 1:
Operational aspects of Open-edi for
implementation
Technologies de l'information — Techniques descriptives sémantiques des
accords d'affaires —
Partie 1: Aspects opérationnels de l'Edi ouvert pour application
Reference number
ISO/IEC 15944-1:2002(E)
©
ISO/IEC 2002
---------------------- Page: 1 ----------------------
ISO/IEC 15944-1:2002(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2002
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO/IEC 2002 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 15944-1:2002(E)
Contents Page
Foreword . v
0 Introduction . vi
0.1 Purpose and overview . vi
0.2 Requirements on the business operational view aspects of Open-edi. viii
0.3 Business operational view (BOV), Open-edi and E-commerce, E-business, etc. . xi
0.4 Use of “Person”, “person”, and “party” in the context of business transactions and
commitment exchange . xii
0.5 Organization and description of the document . xii
0.6 Registration aspects of Open-edi scenarios, scenario attributes and scenario components. xiii
1 Scope. 1
2 Normative references. 2
3 Terms and definitions. 2
4 Symbols and abbreviated terms. 12
5 Characteristics of Open-edi . 12
5.1 Actions based upon following clear, predefined rules . 13
5.2 Commitment of the parties involved. 13
5.3 Communications among parties are automated.13
5.4 Parties control and maintain their states. 13
5.5 Parties act autonomously. 14
5.6 Multiple simultaneous transactions can be supported. 14
6 Components of a business transacation. 14
6.1 Introduction . 14
6.2 Rules governing person . 26
6.3 Rules governing the process component . 42
6.4 Rules governing the data component. 46
6.5 Business requirements on the FSV (Business demands on Open-Edi Support Infrastructure) . 51
6.6 Primitive classification and identification of Open-edi scenarios . 54
7 Guidelines for scoping open-edi scenarios . 64
7.1 Introduction and basic principles. 64
7.2 Rules for scoping Open-edi scenarios . 65
7.3 Template for specifying scope of an Open-edi scenario . 68
8 Rules for specification of Open-edi scenarios and their components. 73
8.1 Introduction and basic principles. 73
8.2 OES demands on interoperability . 76
8.3 Rules for specification of Open-edi scenarios and scenario attributes. 76
8.4 Rules for specification of Open-edi roles and role attributes . 81
8.5 Rules for specification of Open-edi Information Bundles (IBs) and IB attributes . 90
8.6 Business requirements on FSV (business demands on Open-edi Support Infrastructure) . 97
9 Primitive Open-edi scenario template. 98
9.1 Purpose . 98
9.2 Template Structure and Content . 99
10 Requirements on Open-edi description techniques. 102
10.1 General requirements on Open-edi description techniques . 102
10.2 Requirements on OeDTs for roles. 103
10.3 Requirements on OeDTs for Information Bundles . 104
11 References . 104
© ISO/IEC 2002 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 15944-1:2002(E)
Annex A (normative) Consolidated list of terms and definitions with cultural adaptability: ISO English
and ISO French language equivalency . 106
Annex B (normative) Codes representing presence-type attributes: mandatory, conditionals, optionals
and not applicable. 121
Annex C (informative) Unambiguous identification of entities in (electronic) business transactions . 124
Annex D (informative) Existing standards for the unambiguous identification of persons in business
transactions (organizations and individuals) and some common policy and implementation
considerations. 132
Annex E (informative) Business transaction model: person component . 152
Annex F (informative) Business transaction model: process component . 189
Annex G (informative) Business transaction model: data component . 207
Annex H (informative) Effect of classification of scenario constructs. 223
Annex I (informative) Scenario descriptions using the Open-edi scenario template:
"Telecommunications Operations Map" example . 228
Annex J (informative) Open-edi and E-commerce: areas of activities and participation. 266
iv © ISO/IEC 2002 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 15944-1:2002(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. In the field of information technology, ISO and IEC have
established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
The main task of the joint technical committee is to prepare International Standards. Draft International Standards
adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this part of ISO/IEC 15944 may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 15944-1 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
ISO/IEC 15944 consists of the following parts, under the general title Information technology — Business
agreement semantic descriptive techniques:
— Part 1: Operational aspects of Open-edi for implementation
— Part 2: Registration of scenarios and their components
— Part 3: Open-edi description techniques
— Part 4: Business transaction scenarios — Accounting and economic ontology
Annexes A and B form a normative part of this part of ISO/IEC 15944. Annexes C to J are for information only.
© ISO/IEC 2002 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 15944-1:2002(E)
0 Introduction
0.1 Purpose and overview
1)
ISO/IEC 14462 Open-edi Reference Model described the conceptual architecture necessary for carrying out
Open-edi. That architecture described the need to have two separate and related views of the business activities.
The first is the Business Operational View (BOV). The second is the Functional Service View (FSV). Figure 1 from
ISO/IEC 14662 illustrates the Open-edi environment (for definitions of the terms in Figure 1 use 3.1).
B
Open-edi Reference Model
U
S
Business Operational View
I
Comply with
N
BOV RELATED
Business aspects
E Covered by
STANDARDS
of
S
business transactions
S
Viewed as
T
Inter-related
R
A
Functional Service View
N
S
Information technology
Comply with
A
FSV RELATED
aspects of
C
Covered by
STANDARDS
Business transactions
T
I
O
N
S
Figure 1 — Open-edi environment
In the BOV, the requirements that the business puts on the exchange of information are described using a
modelling technique. ISO/IEC 14462 recognized that there was no single modelling technique identified whilst the
IS was in preparation that would satisfy all of the conditions which could be identified that the FSV would need as
input. It was also recognized that business users would need a selection of modelling tools since some tools
appear to be better suited to particular types of business specifications and descriptions than others.
1) ISO/IEC 14662 Information technology - Open-edi Reference Model/Technologies de l'information - Modèle de référence
EDI-ouvert. The English and French versions of this ISO/IEC standard are publicly available. {See }
vi © ISO/IEC 2002 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 15944-1:2002(E)
To provide for a situation where business users may select from a range of modelling systems, selection criteria
identifying the characteristics which any suitable modelling system must be able to support have to be defined.
These criteria can be used in two ways. One is to be able to select a suitable modelling system. Another is to
identify shortcomings in a modelling system currently in use so that the users can provide the extra information
themselves if they prefer to use that modelling system.
The BOV is used to capture the business processes from the business perspective, but there are other things that
the BOV would not capture because they are part of the operation of the Open-edi architecture itself. One example
is that a process must be able to relate to specific Information Bundles. This relationship has to be precise
because any supporting computer application has to be able to respond to the information structure that it receives
as a result of a message from another Open-edi user. Another example is the need to provide for the ability to
trigger an action because an event has not occurred (a message has been sent but no response has taken place).
Therefore it is necessary to identify those characteristics which are not expected to be captured in the BOV but are
required by computer systems developers in their work on the FSV.
The FSV is used to express the technical methods by which the parts of the business processes used in Open-edi
are developed. The FSV has to address the definition, development and lifecycle management of Information
Bundles consisting of Semantic Components, together with any rules which are essential to their management and
operation.
The FSV is a specification of the way in which the exchange of information is managed. It does not specify the
syntax used to encode or represent information that is being exchanged. The selection of a suitable syntax is left
to the EDI implementers, just as the selection of the data interchange service on which messages are sent and
received is left to networking specialists. Appropriate specialists must ensure that these syntaxes and services are
able to satisfy overarching communications requirements such as security services if these are not to be supported
through the FSV.
In summary, this standard is the first of a multi-part standard that focuses on aspects of “What to do” as opposed to
“How to do it,” as shown in Figure 2. Existing standards/tools will be used to the extent possible for the “How to.”
The second part of this standard focuses on identification, registration, referencing and re-use of scenarios, their
attributes and components. {See further 0.6}
© ISO/IEC 2002 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/IEC 15944-1:2002(E)
WHAT TO DO
ISO/IEC 15944-2
ISO/IEC 15944-1
Registration of
scenarios and
Concepts of
OeDTs
their
scenario and its
components: components
FDTx
Business Semantic
Descriptive
Open- edi
FDTy
Techniques
Reference
UML
Model
ABSTRACT CONCRETE
ISO/IEC
14662
Implementation
HOW TO DO IT
Figure 2 — Aspects of ISO/IEC 15944
0.2 Requirements on the business operational view aspects of Open-edi
The evolution of information and communications technologies has created a need and opportunity for different
user groups to engage in business relationships using these technologies. This requires automated methods to
carry out EDI among organizations.
Standards required for Open-edi cover a large spectrum of areas and include commercial aspects, support for
national and international laws and regulations, information technology perspectives, telecommunications and
interconnections, security service, etc. To these are added public policy requirements of a generic and horizontal
nature such as consumer protection, privacy, etc. Annex A in the ISO/IEC 14662 describes how the Open-edi
Reference Model serves as the basis for coordination of work of different standardization areas and types of
standardization for Open-edi.
In addition, the widespread adoption and use of Internet and World Wide Web (WWW)-based technologies by
organizations as well as individuals has added urgency to the need to identify and specify the key components of a
business transaction. For such specifications to be carried out as electronic business transactions supported by
automated methods of the functional support services (FSV) requires a standards-based approach for business
semantic descriptive techniques in support of the Business Operational View of Open-edi.
viii © ISO/IEC 2002 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 15944-1:2002(E)
The sources of requirements on the Business Operational View (BOV) aspects which need to be integrated and/or
taken into account in the development of business descriptive techniques for Open-edi based business
2)
transactions include :
commercial frameworks and associated requirements;
legal frameworks and associated requirements;
public policy requirements particularly those of a generic nature such as consumer protection, privacy, etc.;
sectorial and cross-sectorial requirements;
requirements arising from the need to support cultural adaptability requirements. This includes meeting
localization and multilingualism requirements, i.e., as may be required to meet requirements of a particular
3)
jurisdiction or desired for providing a good, service, and/or right in a particular market. Here distinguishing
between information technology (IT) interfaces and their multiple human interface equivalents is the
recommended approach. (For an example, see Annex B below.)
Figure 3 provides an integrated view of the business operational requirements.
2) This list of sources of requirements is a summary of Annexes A and B of ISO/IEC 14662:1997 Open-edi Reference Model;
(titles in English and French):
Annex A (Informative) Standardization areas and types of standardization activities [ISO/IEC 14662 (E) pages 25-
29]./Annexe A (Informative) Domaines de normalisation et types d'activités de normalisation pour l'EDI-ouvert
[ISO/IEC 14662 (F) pages 26-30];
Annex B (Informative) Requirements for Open-edi standards [ISO/IEC 14662 (E) pages 30-33]/Annexe B (Informative)
Exigences portant sur les normes d'EDI-ouvert. [ISO/IEC 14662 (F) pages 31-35].
3) See further the Chapter 6 "Horizontal Aspects" (pages 22-28) of the "Report of the ISO/IEC JTC1 Business Team on
Electronic Commerce" (ISO/IEC JTC1 N5296).
© ISO/IEC 2002 – All rights reserved ix
---------------------- Page: 9 ----------------------
ISO/IEC 15944-1:2002(E)
Sources of Requirements on the Business Operational View (BOV)
aspects of Open-edi which need to be integrated and/or taken into account in
Business Transactions
Legal
Commercial
(Open-edi based)
Framework &
Framework &
Requirements
Requirements
• Characteristics of Open-edi
- Rule-Based
- Commitment Exchange
- Unambiguous Identification
- Business Transaction Model:
Key Components
Person
Information
Process
Technology
Data
Public Policy Requirements &
• Business Transaction Model:
Req’mts Standards
Classes of Constraints
(Privacy,
• Specification, Identification &
Consumer,
Classification of Open-edi
etc.)
scenarios (and components)
• FSV Business Demands on Telecom-
Open-edi Support Infrastructure munications
Req’mts &
• Open-edi Scenario Templates
Standards
(For use in various applications areas
such as: e-commerce, e-
Sectorial (&
administration, e-business, e-
Cross-Sectorial)
logistics, e-government, e-learning, e-
Req’mts
medicine etc.)
ISO & Other
Standards
Environments
Cultural Adaptability
Localization &
Multilingualism
(IT vs Human Interface)
Functional Services View (FSV)
Figure 3 — Integrated View — Business Operational Requirements
x © ISO/IEC 2002 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 15944-1:2002(E)
0.3 Business operational view (BOV), Open-edi and E-commerce, E-business, etc.
The purpose of this part of the introduction is to provide users with an understanding of the relationship between
concepts/terms in this standard and concepts/terms such as “electronic commerce”, “electronic administration”,
“electronic business”, etc.
Concepts/terms such as “edi”, and now e-commerce, (and its compatriots such as e-administration,
e-business, e-government, e-logistics, e-travel, e-tailing, etc.), have a high profile among users and suppliers alike
including those working in standardization. These concepts/terms have many different meanings in various
4)
contexts and perspectives. In addition, marketing people and those seeking to raise investment funds do and will
continue to use “e-“ words in a variety of ways.
The underlying principles and characteristics of e-commerce and e-administration, e-business etc., include:
being business transaction-based (of both a financial and non-financial nature);
using information technology (computers and telecommunications);
5)
interchanging electronic data involving establishment of commitments among Persons .
From a commercial, legal and standardization perspective, one can view electronic commerce as:
electronic commerce
a category of business transactions, involving two or more Persons, enacted through electronic data interchange,
based on a monetary and for profit basis. (Persons can be individuals, organizations, and/or public administrations)
Consequently, interpretations and use of the concepts/terms, “e-commerce”, “e-business”, “e-administration”, etc.,
which do not require:
1) a clearly understood purpose, mutually agreed upon goal(s), explicitness and unambiguity;
2) pre-definable set(s) of activities and/or processes, pre-definable and structured data;
3) commitments among persons being established through electronic data interchange;
4) computational integrity and related characteristics; and,
6)
5) the above being specifiable through Formal Description Techniques (FDTs) and executable through
information technology systems for use in real world actualizations;
are not considered a priority for this standard and are likely to be outside its scope.
These five requirements are essential for achieving interoperability from a BOV perspective (just as existing
computer and telecommunication standards have as a key objective interoperability from an IT perspective).
4) The ISO/IEC JTC1 Business Team on Electronic Commerce (BT-EC) in its Report to JTC1 stated (p.9)
"BT-EC recognizes that Electronic Commerce (EC) can be defined in many different ways. But rather than attempting to
provide a satisfactory definition, the Team has chosen to take a more heuristic approach to EC and to do so from a global
perspective, i.e., world-wide, cross-sectorial, multilingual, various categories of participants (including consumers)".
ISO/IEC JTC1 N5296 "Report to JTC1: Work on Electronic Commerce Standardization to be initiated". 4 May 1998, 74 p.
5) In this standard the term “party(ies)” is used in its generic context independent of roles or categories of “Person”. It assumes
that a party has the properties of a “Person”.
6) The Formal Description Technique (FDT) used in support of this standard is "Unified Modelling Language (UML). UML is
being progressed as new international standard ISO/IEC 19501 by ISO/IEC JTC1/SC7 titled "Information technology — Unified
Modeling Language (UML) — Part 1: Specification [Technologies de l'information — Langage de modélisation unifié (UML) —
Partie 1: Spécification].
© ISO/IEC 2002 – All rights reserved xi
---------------------- Page: 11 ----------------------
ISO/IEC 15944-1:2002(E)
0.4 Use of “Person”, “person”, and “party” in the context of business transactions and
commitment exchange
When the ISO/IEC 14662 Open-edi Reference Model standard was being developed, the “Internet” and “WWW”
were an embryonic stage and their impact on private and public sector organizations was not fully understood. The
Business Operational View (BOV) was therefore initially defined as:
“a perspective of business transactions limited to those aspects regarding the making of business decisions
and commitments among organizations which are needed for the description of a business transaction”.
The existing and widely-used ISO/IEC 6523 standard definition of “organization” was used in ISO/IEC 14662. The
fact that today Open-edi through the Internet and WWW also involves “individuals” has now been taken into
account in this standard. Further, ISO/IEC 14662 did not define “commitment”, nor the discrete properties and
behaviors an entity must have to be capable of making a “commitment” as well as bridging legal and IT
perspectives in the dematerialized world of the Internet.
During the development of ISO/IEC 15944-1 the term “commitment” was defined. At the same time it was
recognized that in order to be able to make a commitment, the term Open-edi Party was not specific enough to
satisfy scenario specifications when the legal aspects of commitment were considered. In many instances
commitments were noted as being actually made between and among machines (automata or computer programs)
acting under the direction of those legally capable of making commitment, rather than the individuals in their own
capacities. It was also recognized that in some jurisdictions commitment could be made by ‘artificial’ persons such
as corporate bodies. Finally, it was recognized that there are occasions where agents act, either under the
instruction of a principal or as a result of requirement(s) laid down by a jurisdiction, or where an individual is
prevented by a relevant jurisdiction from being able to make commitment.
To address these extended requirements an additional term: Person, was defined. The construct of Person has
been defined in such a way that it is capable of having the potential legal and regulatory constraints applied to it.
The reader should understand that:
the use of the Person with a capital “P” represents Person as a defined term in this standard, i.e., as the entity
within an Open-edi Party that carries the legal responsibility for making commitment(s);
“individual”, “organization” and “public administration” are defined terms representing the three common sub-
types of “Person”;
the words “person(s)” and/or “party(ies)” are used in their generic contexts independent of roles of “Person” as
defined sub-types in this standard. A “party to a business transaction” has the properties and behaviors of a
“Person”. {See further below Clause 6, and in particular 6.1.3 and 6.2}.
0.5 Organization and description of the document
This document describes the key concepts required for developing the BOV of a business transaction and
scenario. It considers how a scenario may be decomposed into functions and how the different classes of
constraints to be applied shall
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.