BS ISO IEC 15944-10-2013 Information technology Business Operational View IT-enabled coded domains as semantic components in business transactions《信息技术 商业运作视图 作为商业交易中语义成分的启用IT编码的领域.pdf

《BS ISO IEC 15944-10-2013 Information technology Business Operational View IT-enabled coded domains as semantic components in business transactions《信息技术 商业运作视图 作为商业交易中语义成分的启用IT编码的领域.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 15944-10-2013 Information technology Business Operational View IT-enabled coded domains as semantic components in business transactions《信息技术 商业运作视图 作为商业交易中语义成分的启用IT编码的领域.pdf（138页珍藏版）》请在麦多课文档分享上搜索。

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationBS ISO/IEC 15944-10:2013Information technology Business Operational ViewPart 10: IT-enabled coded domainsas semantic components in businesstransactionsBS ISO/IEC 15944-10:2013 BR

2、ITISH STANDARDNational forewordThis British Standard is the UK implementation ofISO/IEC 15944-10:2013.The UK participation in its preparation was entrusted to TechnicalCommittee IST/40, Data management and interchange.A list of organizations represented on this committee can beobtained on request to

3、 its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2013.Published by BSI Standards Limited 2013 ISBN 978 0 580 71538 9 ICS 35.240.60 Compliance with a British Stand

4、ard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 28 February 2013. Amendments issued since publicationDate T e x t a f f e c t e dBS ISO/IEC 15944-10:2013Reference numberISO/IEC 15944-10:2013(E)I

5、SO/IEC 2013INTERNATIONAL STANDARD ISO/IEC15944-10First edition2013-02-15Information technology Business Operational View Part 10: IT-enabled coded domains as semantic components in business transactions Technologies de linformation Vue oprationnelle daffaires Partie 10: Domaines cods activs comme co

6、mposantes smantiques dans les transactions daffaires BS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2013 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic

7、 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 ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41

8、22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2013 All rights reservedBS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) ISO/IEC 2013 All rights reserved iiiContents Page Foreword vi0 Introduction vii0.1 Overview of purpose and nature of

9、 coded domains . vii0.2 Benefits of the use of coded domains . viii0.3 Identification, mapping and IT-enablement of existing standards for widely-used code sets. ix0.4 Link to fundamental components in Business Transaction Model (BTM) . xi0.5 IT-enabled and content predefined Semantic Components . x

10、ii0.6 Coded domains as reusable business objects . xiii0.7 Use of “Person“, “organization“ and “party“ in the context of business transaction and commitment exchange. xiv0.8 Importance and role of terms and definitions xv0.9 Use of “identifier“ as “identifier (in business transaction)“ to prevent am

11、biguity xvi0.10 Organization and description of document xvii1 Scope 11.1 Statement of Scope . 11.2 Exclusions 21.3 Aspects currently not yet addressed 21.3.1 Addressing “Quadrant B, C b) ensure as high a degree of data integrity of the semantics of the data interchanged; c) maximize an IT-enabled a

12、pproach; d) maximize granularity and flexibility Given the fact that in Open-edi there are many differing internal and external constraints as well as the wide variety of applications and sectors, it is important that the recorded information interchanged among the parties concerned be as “granular”

13、 and precise as possible. Here “coded domains” serve as flexible “lego blocks” from which data values can be retrieved and used as unambiguous semantic components. The concept of “coded domain” is unique in the context of an Open-edi approach and has been defined in an ISO/IEC 15944 context. This co

14、ncept and its definition represents an approach, methodology and tool which is needed to support appropriate level of unambiguity of (electronic) data interchange needed to support. The concept of “coded domain” covers several perspectives1; 1) business and information (modelling) perspective, i.e.,

15、 those of users and the BOVs; 2) IT modelling perspectives such as: a) entity-relationship modelling where a coded domain is viewed as an entity type functioning as a “domain”; and, b) object-oriented modelling where a coded domain is viewed as an “object class”. 3) an information science (informati

16、on management, library, records management, etc.) perspective where coded domains are viewed as “schedules”, “authority files”, “tables” (which one at times “attaches” to a concept/term thesauri (or indexing/classification schemes of “instance relationships”; 1For the definition, see entry “D033” an

17、d Clause 5.3.2 in ISO/IEC 15944-7:2007. BS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) viii ISO/IEC 2013 All rights reserved4) an electronic data interchange perspective where coded domains are known as “code sets” i.e., a set of codes representing “xyz”. (pop-ups choices in a data entry module);

18、and, 5) application and implementation perspective (and physical data model) where coded domains are commonly known as (edi) tables (or reference tables). The term “coded domain” is introduced to differentiate Open-edi, BOV and e-Business requirements from various other concepts and associated terms

19、 such as generic (encodable) value domains, “enumerated domains”, code sets, which appear to be similar in nature similar in nature in ISO standards. See Annex C for more detailed information. In addition, a key purpose of Part 10 is to ensure that at the granular level as much information is made a

20、vailable about a semantic component, at whatever level of granularity as is required to ensure unambiguity in a commitment exchange. Another key purpose of this Part 10 is to maximize the level of “intelligence” at the highest most precise level, i.e., that of the actual data values being interchang

21、ed. Here use of coded domains presents a simple and pragmatic approach. No “expert system”, intelligent interface, use of heuristics, etc., can metamorphose “dumb” fuzzy data into unambiguous data values which are precise enough to be able to serve as EDI IBs or SCs in support of the making of commi

22、tments as actualized in a instantiated business transaction. On the other hand “smart data” within an intelligent structure, i.e., as part of a coded domain, can not only stand on its own but also be much simpler, precise, easier to reference and use. This approach at the data element level focuses

23、on the development of intelligently coded data elements as part of coded domains. This involves rule-based, structured and pre-defined values whose purpose and use has been stated clearly and unambiguously (hereby facilitating an IT-enabled approach).20.2 Benefits of the use of coded domains The ben

24、efits of using the construct, methodology and implementation of “coded domains”, in compliance with this Part 10, presented below include (in no order of importance): 1) Maximizing if not ensuring unambiguity in semantics among parties to a commitment exchange instantiated as a business transaction;

25、 2) Ensuring ability to support Human Interface Equivalencies (HIEs) in support of multilingual and individual accessibility requirements; 3) Maximize a Total Quality Management (TQM) approach for data integrity control and trustworthiness and quality assurance; 4) Maximize exchange ability of data

26、among Persons and their applications through computer-to-computer electronic data interchange (EDI) among the IT-systems of the parties involved; 5) Serve as a methodology and tool which it IT-neutral, i.e., Part 10 conformant “coded domains” are completely independent of application software and IT

27、-platforms used; 6) Minimization of data entry costs and simplification data entry processes; 7) Enables more efficient and effective search, retrieval and use of recorded information (in multiple languages); 8) Significant minimization in costs and duplication of effort due to the inherent shareabl

28、e nature of coded domains; 2See further SC32/WG1 N0520 “Amended 15944-1:2010 Figure 22 Focus of BOV Open-edi Standardization Work ”for use in development of Part 10”. BS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) ISO/IEC 2013 All rights reserved ix9) Increased efficiencies and cost reductions in

29、both the internal operations of organizations and public administrations as well as among them via EDI; 10) Promotes modularity, re-usability of shared solutions supporting both paperless environments; 11) Increased productivity, through reduction of common (non-competitive) costs at organizations a

30、nd public administrations as well as at the jurisdictional domain level; and, 12) Serve as a methodology in support of the development of consensus building with respect to the development of permitted values of a data element in support of the use of a semantic component in (electronic) data interc

31、hange (based on the Pareto principle3). 0.3 Identification, mapping and IT-enablement of existing standards for widely-used code sets A coded domain consists of entries of “entities” which the responsible Source Authority (SA) has decided to include into its “Set of codes representing X” for the spe

32、cified and particular purpose for which this SA has decided to establish and maintain the resulting “set of codes representing X” to be used by its members. However, it is recognized that many “Persons” of whatever nature, i.e., either as an “organization” and/or “public administration”, and at time

33、s, “individuals” as well use a “Set of codes representing X” for a purpose and in a context which is quite different from that of the purpose and use of the Source Authority which created and maintains that “Set of Codes representing X”. Two primary examples here are ISO 3166-1 ISO/IEC 7812 for indi

34、viduals, organizations and public administrations; and ISO/IEC 7501 for individuals.5With respect to the “process” component, ISO/IEC 15944-1 identified a set of five fundamental activities which may take place in any order. The five fundamental activities are: (a) planning; (b) identification; (c)

35、negotiation; (d) actualization; and, (e) post-actualization. 5Annex D “Existing standards for the unambiguous identification of persons in business transactions (organizations and individuals) and some common policy and implementation considerations” in ISO/IEC 15944-1 provides further information o

36、n these identification schemas are constructed. BS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) xii ISO/IEC 2013 All rights reserved On the whole, a coded domain consists of predefined and structured data elements. Clause 6.4.2 in ISO/IEC 15944-1 described the relations between concepts of “recorde

37、d information” and “data”. Data is one type of recorded information that can be processed by computer systems. Data is data-element based or non-data element based, as described by Figure 3 and Figure 4 below, which are adapted from ISO/IEC 15944-1 Clause 6.4.2. Recorded information which is not “da

38、ta” “DATA” “COMPUTER SYSTEM” “RECORDED INFORMATION” Electronic business transactions/Open-edi is “data” + “computer system” based Figure 3 Relation of “recorded information”, “data” and “computer system” in electronic business transactions / Open-edi Figure 4 Relations “data” and “data elements” in

39、electronic business transactions / Open-edi 0.5 IT-enabled and content predefined Semantic Components As specified by ISO/IEC 14662, Open-edi scenarios include components of roles, information bundles, and scenario attributes. The coded domain is related to information bundles, which consist of Sema

40、ntic Components (SC). A Semantic Component is a unit of recorded information unambiguously defined in the context of business goal of the business transaction. Since not specifically required by the ISO/IEC 14662, the Semantic Components for “Person”, “Process” and “Data” can be either structured or

41、 unstructured, and they can also have predefined contents or undefined contents. It is an ISO/IEC JTC1 requirement that a standard shall support IT-enablement and computational integrity when possible6. Therefore it is the purpose of this Part 10 of ISO/IEC 15944 to maximize the IT-enablement, inter

42、operability, computational integrity approach through the use of coded domains whose context provided predefined and structured data values for use as Semantic Component, as shown in Figure 5 below. 6See further the “Recommendations of the ISO/IEC JTC1 Business Team on Electronic Commerce (BT-EC)”.

43、Ref: ISO/IEC JTC1 N5296. Non dataelement-based “DATA” Data element-based Electronic business transactions/Open-edi is primarily data element-based BS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) ISO/IEC 2013 All rights reserved xiiiPredefined Content Undefined Content Unstructured Structured Maximi

44、ze IT-enablement, interoperability, computational integrity through coded domains Semantic Components (SCs) for - “Person”, - “process” - “data”. “A” quadrant “C” quadrant quadrant “D” quadrant “B” Figure 5 Purpose of coded domain as IT-enabled and content predefined semantic components The focus of

45、 Part 10 of ISO/IEC 15944 is to support “Quadrant A” requirements in the development and use of “coded domains”. This means that the rules governing the allowable contents, i.e., values, in a set of recorded information which (1) support and enable a structured approach; and (2) all the permitted va

46、lues for the semantic component are predefined (and if not there is a very systematic and rule-base to deal with “Others” in an IT-enabled manner).” 0.6 Coded domains as reusable business objects In existing business transactions, whether conducted on a for-profit or not-for-profit basis, business i

47、nformation documents as well as implementable (executable) computer programs consist of reusable components unambiguously understood among participating parties. Coded domains can be used in support of any type of scenario component, i.e., “roles”, “Information Bundles (IBs)”, and “semantic componen

48、ts” (SCs). Coded domains can also be used in support of a scenario attribute registered through procedures specified by ISO/IEC 15944-2. Registration of coded domains offers several benefits to the e-Business community, including the following a) supports wider use of registered coded domains both b

49、y providing international recognition to the fact that such coded domains conform to an International Standard and by making them publicly available to potential users. b) provides both immediate recognition to extensions of an International Standard and a source for updates to that International Standard during the regular maintenance cycle. BS ISO/IEC 15944-10:2013ISO/IEC 15944-10:2013(E) xiv ISO/IEC 2013 All rights reservedc) may provide a single mechanism to access information concerning coded domains that are specified