ISO/IEC 15944-1:2011

Information technology — Business operational view — Part 1: Operational aspects of open-edi for implementation

The Open-edi Reference Model (ISO/IEC 14662:2010, Clause 4) states: "The intention is that the sending, by an Open-edi Party, of information from a scenario, conforming to Open-edi standards, shall allow the acceptance and processing of that information in the context of that scenario by one or more Open-edi Parties by reference to the scenario and without the need for agreement. However, the legal requirements and/or liabilities resulting from the engagement of an organization in any Open-edi transaction may be conditioned by the competent legal environment(s) or the formation of a legal interchange agreement between the participating organizations. Open-edi Parties need to observe rule-based behaviour and possess the ability to make commitments in Open-edi (e.g., business, operational, technical, legal, and/or audit perspectives)." ISO/IEC 15944-1:2011 addresses the fundamental requirements of the commercial and legal frameworks and their environments on business transactions, and also integrates the requirements of the information technology and telecommunications environments. In addition to the existing strategic directions of "portability" and "interoperability", the added strategic direction of ISO/IEC JTC 1 of "cultural adaptability" is supported in ISO/IEC 15944-1:2011. It also supports requirements arising from the public policy/consumer environment, cross-sectorial requirements and the need to address horizontal issues. It integrates these different sets of requirements. ISO/IEC 15944-1:2011 allows constraints [which include legal requirements, commercial and/or international trade and contract terms, public policy (e.g. privacy/data protection, product or service labelling, consumer protection), laws and regulations] to be defined and clearly integrated into Open-edi through the BOV. This means that terms and definitions in ISO/IEC 15944-1:2011 serve as a common bridge between these different sets of business operational requirements, allowing the integration of code sets and rules defining these requirements to be integrated into business processes electronically. ISO/IEC 15944-1:2011 contains a methodology and tool for specifying common business practices as parts of common business transactions in the form of scenarios, scenario attributes, roles, Information Bundles and Semantic Components. It achieves this by 1) developing standard computer processable specifications of common business rules and practices as scenarios and scenario components; and thus 2) maximizing the re-use of these components in business transactions.

Technologies de l'information — Vue opérationnelle d'affaires — Partie 1: Aspects opérationnels de l'Edi ouvert pour application

General Information

• Status: Published
• Publication Date: 20-Jul-2011
• ICS: 35.240.60 - IT applications in transport
• ICS: 35.240.63 - IT applications in trade
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 1 - eBusiness
• Current Stage: 9092 - International Standard to be revised
• Completion Date: 16-Sep-2021

Relations

• Revises: ISO/IEC 15944-1:2002 - Information technology — Business agreement semantic descriptive techniques — Part 1: Operational aspects of Open-edi for implementation
• Effective Date: 26-Sep-2009

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15944-1
Second edition
2011-08-01


Information technology — Business
Operational View —
Part 1:
Operational aspects of Open-edi for
implementation
Technologies de l'information — Vue opérationnelle d'affaires —
Partie 1: Aspects opérationnels de l'Edi ouvert pour application




Reference number
ISO/IEC 15944-1:2011(E)
©
ISO/IEC 2011

---------------------- Page: 1 ----------------------
ISO/IEC 15944-1:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2011
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 [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 15944-1:2011(E)
Contents Page
Foreword.xii
0 Introduction.xiii
0.1 Purpose and overview.xiii
0.2 Requirements on the business operational view aspects of Open-edi .xv
0.3 Business operational view (BOV), Open-edi and e-commerce, e-business, etc. .xvii
0.4 Use of “Person”, “person”, and “party” in the context of business transactions and
commitment exchange.xviii
0.5 Organization and description of the document.xix
0.6 Registration aspects of Open-edi scenarios, scenario attributes and scenario components.xix
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 on 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 transaction .14
6.1 Introduction.14
6.1.1 Overview.14
6.1.2 Standard based on rules and guidelines .15
6.1.3 Business transaction: commitment exchange added to information exchange .16
6.1.4 Business transaction: unambiguous identification of entities.20
6.1.5 Business transaction model: key components.23
6.1.6 Business transaction model: classes of constraints .23
6.2 Rules governing the Person component .26
6.2.1 Introduction.26
6.2.2 Person, personae, identification and Person signature.26
6.2.3 Person - identity and authentication .31
6.2.4 Person and roles: buyer and seller.34
6.2.5 Person and delegation to “agent” and/or “third party".35
6.2.6 Person and external constraints: the "regulator" .36
6.2.7 Person and external constraints: individual, organization, and public administration .36
6.2.8 Person and external constraints: consumer and vendor.40
6.3 Rules governing the process component.41
6.3.1 Introduction.41
6.3.2 Planning.42
6.3.3 Identification .43
6.3.4 Negotiation .43
6.3.5 Actualization .44
6.3.6 Post-actualization .44
6.4 Rules governing the data component .45
6.4.1 Recorded information .45
6.4.2 Predefined and structured data elements.47
© ISO/IEC 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 15944-1:2011(E)
6.5 Business requirements on the FSV (Business demands on Open-Edi Support Infrastructure).50
6.5.1 Introduction .50
6.5.2 Internal constraints (self-imposed).51
6.5.3 External constraints .52
6.5.4 BOV requirements on the FSV for security methods and techniques .53
6.5.5 Liability of repositories .53
6.6 Primitive classification and identification of Open-edi scenarios.54
6.6.1 Introduction .54
6.6.2 Classification of Open-edi scenarios.54
6.6.2.1 Requirements for classification of Open-edi scenarios.54
6.6.2.2 Market type on business boundary.55
6.6.2.3 Settlement type in business process.55
6.6.2.4 Roles in business transactions: primitive or complex.55
6.6.3 Trade models based on three classification factors.56
6.6.3.1 Trade models by market type: defined and undefined.56
6.6.3.2 Trade models by settlement type: immediate and separate.57
6.6.3.3 Trade models by participation type: bilateral and mediated .58
6.6.4 Classification and scenario types of Open-edi scenarios.58
6.6.4.1 Classification on Open-edi scenarios.58
6.6.4.2 Scenario types.59
6.6.4.2.1 Basic primitive trade scenario: (a) .59
6.6.4.2.2 Basic complex trade scenario: (b).60
6.6.4.2.3 Defined primitive trade scenario: (i).60
6.6.4.2.4 Defined complex trade scenario: (j) .60
6.6.4.2.5 Primitive agreement scenario: (c) .61
6.6.4.2.6 Defined primitive agreement scenario: (k) .61
6.6.4.2.7 Complex agreement scenario: (g) .61
6.6.4.2.8 Defined complex agreement scenario: (m).62
6.6.4.2.9 Separate delivery scenario: (d).62
6.6.4.2.10 Separate payment scenario: (e).62
6.6.4.2.11 Authentication scenario: (f) .62
6.6.4.2.12 Defined authentication scenario: (l).63
6.6.4.3 Remarks on scenario classification.63
6.6.4.3.1 Continuous transaction:.63
6.6.4.3.2 Services transaction:.63
6.6.4.3.3 Auction transaction: .63
6.6.4.3.4 Bidding transaction: .63
6.6.4.3.5 Credit payment transaction: .63
6.6.4.3.6 Regulatory constraints:.63
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.67
7.3.1 Introduction to template.67
7.3.2 Template .68
8 Rules for specification of Open-edi scenarios and their components .71
8.1 Introduction and basic principles .71
8.2 OES demands on interoperability.74
8.3 Rules for specification of Open-edi scenarios and scenario attributes .75
8.3.1 Open-edi scenario rules.75
8.3.2 Open-edi scenario (OeS) attributes and associated rules.75
8.3.2.1 Scenario attribute: OeS identifier .76
8.3.2.2 Scenario attribute: OeS name(s) .76
8.3.2.3 Scenario attribute: OeS purpose .77
8.3.2.4 Scenario attribute: OeS set of roles.77
8.3.2.5 Scenario attribute: OeS set of Information Bundles .77
8.3.2.6 Scenario attribute: OeS set of requirements on Open-edi Parties .77
8.3.2.7 Scenario attribute: OeS set of external constraints on business requirements, i.e., laws
and regulations.78
iv © ISO/IEC 2011 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 15944-1:2011(E)
8.3.2.8 Scenario attribute: OeS inheritance identifier(s) and cross-references.78
8.3.2.9 Scenario attribute: OeS security service requirements.78
8.3.2.10 Scenario attribute: OeS communication - quality of service requirements.79
8.3.2.11 Scenario attribute: OeS role requirements and constraints.79
8.3.2.12 Scenario attribute: OeS dependency among roles in a scenario .79
8.3.2.13 Scenario attribute: OeS dependency among Information Bundles in a scenario.79
8.3.2.14 Scenario attribute: OeS dependency among Semantic Components of different
Information Bundles .79
8.3.2.15 Scenario attribute: OeS demands on Open-edi Parties.79
8.3.2.16 Scenario attribute: OeS demands on Open-edi infrastructure .80
8.4 Rules for specification of Open-edi roles and role attributes.80
8.4.1 Rules governing roles.80
8.4.2 Role attributes and associated rules.81
8.4.2.1 Role attribute: role identifier (ID).82
8.4.2.2 Role attribute: role name(s) .82
8.4.2.3 Role attribute: role purpose.82
8.4.2.4 Role attribute: role business goal(s).83
8.4.2.5 Role attribute: role business rules and constraints.83
8.4.2.6 Role attribute: role inheritance identifiers and cross-references .83
8.4.2.7 Role attribute: role external constraints on business requirements.84
8.4.2.8 Role attribute: role security service requirements.84
8.4.2.9 Role attribute: role communications and quality of service requirements .85
8.4.2.10 Role attribute: Role demands on Open-edi Support Infrastructure (OeSI).85
8.4.3 Role demands on Open-edi Parties .85
8.4.4 Interoperability demands among roles .86
8.4.5 Role states.86
8.4.6 Role transitions.86
8.4.7 Role events.87
8.4.8 Role actions .88
8.4.9 Role internal function.88
8.4.10 Role demand on Open-edi Support Infrastructure (OeSI).88
8.5 Rules for specification of Open-edi Information Bundles (IBs) and IB attributes .89
8.5.1 Rules governing Information Bundles (IBs) .89
8.5.2 Information Bundle (IB) attributes and associated rules .90
8.5.2.1 Information Bundle attribute: IB identifier.90
8.5.2.2 Information Bundle attribute: IB name(s).90
8.5.2.3 Information Bundle attribute: IB purpose.91
8.5.2.4 Information Bundle attribute: business rules controlling content of IBs .91
8.5.2.5 Information Bundle attribute: IB external constraints on business requirements governing
content or concept(s) of an IB .91
8.5.2.6 Information Bundle attribute: IB contents.91
8.5.2.7 Information Bundle attribute: IB security service requirements.91
8.5.2.8 Information Bundle attribute: IB recorded information retention – business rules and
constraints.92
8.5.2.9 Information Bundle attribute: IB recorded information retention - external constraints on
business requirements.92
8.5.2.10 Information Bundle attribute: IB time validity characteristics .92
8.5.3 IB information for interoperability .93
8.5.4 IB demands on Open-edi Support Infrastructure (OeSI) .93
8.5.5 Rules for the specification of Semantic Components and Semantic Component attributes.93
8.5.5.1 Rules governing Semantic Components.93
8.5.5.2 Rules governing Semantic Component attributes .95
8.5.5.2.1 Semantic Component attribute: SC identifier .95
8.5.5.2.2 Semantic Component attribute: SC name(s).95
8.5.5.2.3 Semantic Component attribute: SC definition .95
8.5.5.2.4 Semantic Component attribute: SC security service requirements .96
8.6 Business requirements on FSV (business demands on Open-edi Support Infrastructure).96
9 Primitive Open-edi scenario template .97
9.1 Purpose.97
© ISO/IEC 2011 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 15944-1:2011(E)
9.2 Template structure and content.97
9.2.1 IT-interface needs perspective.98
9.2.2 Human interface needs perspective .98
9.2.3 Consolidated template of attributes of Open-edi scenarios, roles and Information Bundles.98
10 Requirements on Open-edi description techniques .101
10.1 General requirements on Open-edi description techniques.101
10.2 Requirements on OeDTs for roles .102
10.3 Requirements on OeDTs for Information Bundles.103
11 References.104
Annex A (normative) Consolidated list of terms and definitions with cultural adaptability: ISO English
and ISO French language equivalency.105
A.1 Introduction .105
A.2 ISO English and ISO French .105
A.3 Cultural adaptability and quality control.105
A.4 Organization of Annex A - Consolidated List in Matrix Form .106
A.5 Consolidated List of ISO/IEC 15944-1 Terms and Definitions.107
Annex B (normative) Codes representing presence-type attributes: mandatory, conditionals,
optionals, and not applicable .130
Annex C (informative) Unambiguous identification of entities in (electronic) business transactions.133
C.1 Introduction .133
C.2 Key issues .133
C.3 Basic assumptions: Entities, objects and Persons .133
C.4 “Unambiguous” .135
C.5 “Identification”.136
C.6 Identification versus designation (or “identifiers” versus “names”).140
Annex D (informative) Existing standards for the unambiguous identification of Persons in business
transactions (organizations and individuals) and some common policy and implementation
considerations .143
D.1 Introduction .143
D.1.1 Note on compliance with privacy/data protection, consumer protection, etc. .144
D.1.2 Standards referenced in this Annex .144
D.2 Purpose.145
D.3 Approach and overview .146
D.4 Existing standards for the unambiguous identification of Persons .146
D.4.1 Introduction .146
D.4.2 Key exis
...