BS ISO/IEC 15944-1:2011

Foreword
0 Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviated terms
5 Characteristics of Open-edi
6 Components of a business transaction
7 Guidelines for scoping Open-edi scenarios
8 Rules for specification of Open-edi scenarios and
   their components
9 Primitive Open-edi scenario template
10 Requirements on Open-edi description techniques
11 References
Annex A (normative) - Consolidated list of terms and
        definitions with cultural adaptability: ISO
        English and ISO French language equivalency
Annex B (normative) - Codes representing presence-type
attributes: mandatory, conditionals, optionals,
        and not applicable
Annex C (informative) - Unambiguous identification of
        entities in (electronic) business transactions
Annex D (informative) - Existing standards for the
        unambiguous identification of Persons in
        business transactions (organizations and
        individuals) and some common policy and
        implementation considerations
Annex E (informative) - Business transaction model:
        Person component
Annex F (informative) - Business transaction model: Process
        component
Annex G (informative) - Business transaction model: data
        component
Annex H (informative) - Effect of classification of scenario
        constructs
Annex I (informative) - Scenario descriptions using the
        Open-edi scenario template: "Telecommunications
        Operations Map" example
Annex J (informative) - Open-edi and e-commerce: Areas of
        activities and participation
Bibliography

Specifies 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.

The Open-edi Reference Model (ISO/IEC14662:2010, Clause4) 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).\'

This part of ISO/IEC15944 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 JTC1 of \'cultural adaptability\' is supported in this part of ISO/IEC15944. 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. See Figure3.

This part of ISO/IEC15944 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 this part of ISO/IEC15944 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.

This part of ISO/IEC15944 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.