1、INCITS/ISO/IEC 15944-1-20022008 (ISO/IEC 15944-1:2002, IDT) Information technology Businessagreement semantic descriptive techniques Part 1: Operational aspects of Open-edi for implementationINCITS/ISO/IEC 15944-1-20022008(ISO/IEC 15944-1:2002, IDT)INCITS/ISO/IEC 15944-1-20022008 ii ITIC 2008 All ri
2、ghts reserved PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes 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 downloadi
3、ng this file, parties accept therein the responsibility of not infringing Adobes 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 Gene
4、ral 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
5、 below. Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI Approval: 9/17/2008 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2008 by Information Technology Indus
6、try Council (ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resal
7、e. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America
8、INCITS/ISO/IEC 15944-1-20022008 ITIC 2008 - All rights reserved iiiContents Page Forewordv 0 Introduction.vi 0.1 Purpose and overviewvi 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
9、of “Person”, “person”, and “party” in the context of business transactions and commitment exchangexii 0.5 Organization and description of the documentxii 0.6 Registration aspects of Open-edi scenarios, scenario attributes and scenario components.xiii 1 Scope 1 2 Normative references2 3 Terms and def
10、initions .2 4 Symbols and abbreviated terms 12 5 Characteristics of Open-edi12 5.1 Actions based upon following clear, predefined rules13 5.2 Commitment of the parties involved .13 5.3 Communications among parties are automated 13 5.4 Parties control and maintain their states13 5.5 Parties act auton
11、omously.14 5.6 Multiple simultaneous transactions can be supported .14 6 Components of a business transacation 14 6.1 Introduction14 6.2 Rules governing person26 6.3 Rules governing the process component.42 6.4 Rules governing the data component .46 6.5 Business requirements on the FSV (Business dem
12、ands on Open-Edi Support Infrastructure).51 6.6 Primitive classification and identification of Open-edi scenarios54 7 Guidelines for scoping open-edi scenarios64 7.1 Introduction and basic principles 64 7.2 Rules for scoping Open-edi scenarios65 7.3 Template for specifying scope of an Open-edi scena
13、rio.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 interoperability76 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
14、.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 Content99 10 Requirements on Open-e
15、di 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 INCITS/ISO/IEC 15944-1-20022008 iv ITIC 2008 - All rights reservedAnnex A (normative) Con
16、solidated list of terms and definitions with cultural adaptability: ISO English and ISO French language equivalency106 Annex B (normative) Codes representing presence-type attributes: mandatory, conditionals, optionals and not applicable .121 Annex C (informative) Unambiguous identification of entit
17、ies 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
18、: person component .152 Annex F (informative) Business transaction model: process component189 Annex G (informative) Business transaction model: data component207 Annex H (informative) Effect of classification of scenario constructs223 Annex I (informative) Scenario descriptions using the Open-edi s
19、cenario template: “Telecommunications Operations Map“ example228 Annex J (informative) Open-edi and E-commerce: areas of activities and participation 266 INCITS/ISO/IEC 15944-1-20022008 ITIC 2008 - All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the In
20、ternational 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
21、 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 establishe
22、d 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 c
23、ommittee 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.
24、 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 gen
25、eral 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 econom
26、ic ontology Annexes A and B form a normative part of this part of ISO/IEC 15944. Annexes C to J are for information only. INCITS/ISO/IEC 15944-1-20022008 vi ITIC 2008 - All rights reserved0 Introduction 0.1 Purpose and overview ISO/IEC 14462 Open-edi Reference Model1)described the conceptual archite
27、cture 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 e
28、nvironment (for definitions of the terms in Figure 1 use 3.1). Open-edi Reference Model Business Operational ViewBusiness aspectsbusiness transactionsInformation technologyaspects ofBusiness transactionsFunctional Service ViewBUSINESSTRANSACTIViewed asONSBOV RELATEDSTANDARDSFSV RELATEDSTANDARDSofInt
29、er-relatedCovered byComply withCovered byComply withFigure 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
30、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 a
31、nd descriptions than others. 1) ISO/IEC 14662 Information technology - Open-edi Reference Model/Technologies de linformation - Modle de rfrence EDI-ouvert. The English and French versions of this ISO/IEC standard are publicly available. See INCITS/ISO/IEC 15944-1-20022008 ITIC 2008 - All rights rese
32、rved viiTo 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
33、 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 th
34、ere 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
35、 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
36、 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
37、 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
38、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. Appropriat
39、e 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” a
40、s 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 INCITS/ISO
41、/IEC 15944-1-20022008 viii ITIC 2008 - All rights reservedWHAT TO DOHOW TO DO ITABSTRACT CONCRETEOpen- ediReferenceModelISO/IEC14662ISO/IEC 15944-1Concepts ofscenario and itscomponents:Business SemanticDescriptiveTechniquesOeDTsFDTxFDTyUMLISO/IEC 15944-2Registration ofscenarios andtheircomponentsImp
42、lementationFigure 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. T
43、his 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 interconnectio
44、ns, 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 are
45、as 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 spec
46、ifications 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. INCITS/ISO/IEC 15944-1-20
47、022008 ITIC 2008 - All rights reserved ixThe 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 transactions include2): commercial frameworks an
48、d 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 requi
49、rements. This includes meeting localization and multilingualism requirements, i.e., as may be required to meet requirements of a particular jurisdiction or desired for providing a good, service, and/or right in a particular market.3)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 re
