DIN ISO 15000-5-2014 Electronic Business Extensible Markup Language (ebXML) - Part 5 Core Components Specification (CCS) (ISO 15000-5 2014)《电子商务可扩展标记语言 (ebXML) 第5部分 核心部件规范 (CCS) (I.pdf

《DIN ISO 15000-5-2014 Electronic Business Extensible Markup Language (ebXML) - Part 5 Core Components Specification (CCS) (ISO 15000-5 2014)《电子商务可扩展标记语言 (ebXML) 第5部分 核心部件规范 (CCS) (I.pdf》由会员分享，可在线阅读，更多相关《DIN ISO 15000-5-2014 Electronic Business Extensible Markup Language (ebXML) - Part 5 Core Components Specification (CCS) (ISO 15000-5 2014)《电子商务可扩展标记语言 (ebXML) 第5部分 核心部件规范 (CCS) (I.pdf（37页珍藏版）》请在麦多课文档分享上搜索。

1、October 2014Translation by DIN-Sprachendienst.English price group 17No part of this translation may be reproduced without prior permission ofDIN Deutsches Institut fr Normung e. V., Berlin. Beuth Verlag GmbH, 10772 Berlin, Germany,has the exclusive right of sale for German Standards (DIN-Normen).ICS

2、 35.040; 35.240.60!%;=“2249426www.din.deDDIN ISO 15000-5Electronic Business Extensible Markup Language (ebXML) Part 5: Core Components Specification (CCS) (ISO 15000-5:2014),English translation of DIN ISO 15000-5:2014-10Erweiterbare Auszeichnungssprache fr das elektronische Geschftswesen (ebXML) Tei

3、l 5: Spezifikation der Kernkomponenten (CCS) (ISO 15000-5:2014),Englische bersetzung von DIN ISO 15000-5:2014-10Commerce lectronique en langage de balisage extensible (ebXML) Partie 5: Spcification des composants principaux (CCS) (ISO 15000-5:2014),Traduction anglaise de DIN ISO 15000-5:2014-10Super

4、sedesDIN V 16566-1:2004-02www.beuth.deIn case of doubt, the German-language original shall be considered authoritative.Document comprises 37 pages10.14 A comma is used as the decimal marker. Contents Page National foreword .3 National Annex NA (informative) Bibliography .4 Introduction .5 1 Scope 11

5、 2 Normative references 11 3 Terms and definitions . 11 4 Core Component Framework . 16 4.1 General . 16 4.2 Core Components . 16 4.3 Data Types 18 4.4 Business Information Entities 18 4.5 Naming Convention . 20 4.6 Library of Core Components 26 5 Context . 26 5.1 General . 26 5.2 Overview of Contex

6、t Specification 26 5.3 Approved Context Categories 27 6 Conformance 30 Annex A (normative) Primitive Type definitions 31 Annex B (normative) List of approved Core Component Types (CCT) . 32 Annex C (normative) List of approved Core Component Type Content and Supplementary Components . 34 Annex D (no

7、rmative) List of permissible Representation Terms . 36 Bibliography . 37 2DIN ISO 15000-5:2014-10National foreword This document (ISO 15000-5:2014) has been prepared by Technical Committee ISO/TC 154 “Processes, data elements and documents in commerce, industry and administration”. The responsible G

8、erman body involved in its preparation was the DIN-Normenausschuss Informationstechnik und Anwendungen (DIN Standards Committee Information Technology and selected IT Applications), Working Committee NA 043-03-03 AA Elek-tronisches Geschftswesen. The text of ISO 15000-5 has been adopted without any

9、modification. In translating the text into German particular attention was paid to the use of a correct and consistent technical terminology in German. However, the English abbreviations were taken over for the purposes of compatibility and to facilitate comparison with the original English text. Th

10、e full English term is given for each term in Clause 3 “Terms and definitions”. English text in the figures has been taken over because a translation into German was considered to be unnecessary and the target group of IT specialists normally has sufficient knowledge of English to understand these t

11、exts. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. DIN shall not be held responsible for identifying any or all such patent rights. The DIN Standards corresponding to the International Standards referred to in this document are

12、 as follows: ISO 4217 DIN EN ISO 4217 ISO 8601 DIN ISO 8601 DIN ISO 15000 consists of the following parts, under the general title Electronic Business Extensible Markup Language (ebXML): Part 5: Core Components Specification (CCS) Up to now, further parts of the ISO 15000 series have not been publis

13、hed as German Standards because they are not as important as Part 5, at least in terms of a German translation. In addition, Parts 1 to 4 which were published in 2004 as ISO/TS specifications have since been withdrawn. It is expected that these parts will be revised and republished as ISO Standards.

14、 The complete ISO 15000 series consists of the following parts, under the general title Electronic Business Extensible Markup Language (ebXML): Part 1: Collaboration-protocol profile and agreement specification (ebCPP) under preparation Part 2: Message service specification (ebMS) under preparation

15、Part 3: Registry information model specification (ebRIM) under preparation Part 4: Registry services specification (ebRS) under preparation Part 5: Core Components Specification (CCS) published as ISO 15000-5 3DIN ISO 15000-5:2014-10Amendments This standard differs from DIN V 16566-1:2004-02 as foll

16、ows: a) the national standard number has been modified to include the ISO Standard number; b) editorial and structural modifications have been made in order to publish the document as a full DIN Standard; c) ISO Amendment 1:2011 to ISO/TS 15000-5 has been taken into consideration; d) rules that were

17、 unclear or were specific to the English language have been removed; e) ambiguous rules have been clarified; f) metamodels have been updated to reflect reality; g) non-normative clauses have been removed. Previous editions DIN V 16566-1: 2004-02 National Annex NA (informative) Bibliography DIN EN IS

18、O 4217, Codes for the representation of currencies and funds DIN ISO 8601, Data elements and interchange formats Information interchange Representation of dates and times 4DIN ISO 15000-5:2014-10Electronic Business Extensible Markup Language (ebXML) Part 5: Core Components Specification (CCS) Introd

19、uction0.1 GeneralThis International Standard describes and specifies a new approach to the well-understood problem of the lack of information interoperability between applications in the e-business arena. Traditionally, standards for the exchange of business data have been focused on static message

20、definitions that have not enabled a sufficient degree of interoperability or flexibility. A more flexible and interoperable way of standardizing Business Semantics is required. The Core Component solution described in this International Standard presents a methodology for developing a common set of

21、semantic building blocks that represent the general types of business data in use today and provides for the creation of new business vocabularies and restructuring of existing business vocabularies.0.2 OverviewThe Core Components Specification (CCS) described in this International Standard provides

22、 a way to identify, document and maximize the re-use of business information to support and enhance interoperability across Business Processes. CCS focuses both on human-readable and machine-processable representations of this information.The Core Components approach described in this International

23、Standard is more flexible than current standards in this area because the semantic standardization is done in a syntax-neutral fashion. Using Core Components as part of the ebXML framework will help to ensure that two trading partners using different syntaxes e.g. Extensible Markup Language (XML) an

24、d United Nations/EDI for Administration, Commerce, and Transport (UN/EDIFACT) are using Business Semantics in the same way on condition that both syntaxes have been based on the same Core Components. This enables clean mapping between disparate message definitions across syntaxes, industry and regio

25、nal boundaries.Business Process and Core Component solutions capture a wealth of information about the business reasons for variation in message semantics and structure. In the past, these variations have led to incompatible data models and a subsequent lack of interoperability. The core components

26、mechanism will allow identification of similarities and differences between these models. Incompatibility becomes incremental rather than wholesale, i.e. the detailed points of difference are noted, rather than a whole model being dismissed as incompatible.0.3 Key ConceptsThe CCS key concepts are ba

27、sed two levels of abstraction: Core Components and Business Information Entities. These focus areas are discussed in Clauses 4 and 5: in each case, the concepts are introduced and a normative definition is given, as well as an example, where appropriate.NOTE The term Core Component is used as a gene

28、ric term that encompasses Basic Core Components, Association Core Components, Aggregate Core Components, and their associated Core Component Types. Equally, the term Business Information Entity is used as a generic term encompassing Basic Business Information Entities, Association Business Informati

29、on Entities, and Aggregate Business Information Entities.0.4 Key Core Component ConceptsThe central concept of this International Standard is the Core Component. The Core Component is a semantic building block, which is used as a basis to construct all electronic business messages.There are four dif

30、ferent categories of Core Components: a) Basic Core Component;b) Association Core Component;c) Core Component Type;d) Aggregate Core Component.5DIN ISO 15000-5:2014-10These concepts are described below and their definitions are given in Clause 3.PartyName (Text)Role (Code)Description (Text)ContactTy

31、pe (Code)Job Title (Text)Primary (Indicator)Deg976inedAddressStreet Name (Text)Free Form (Text)Postcode (Text)Country (Identig976ier)PostalFigure 1 Association Core ComponentFigure 1 is an example of an Association Core Component and shows the following: three Aggregate Core Components: “Party. Deta

32、ils”; “Contact. Details” and “Address. Details”; each Aggregate Core Component has a number of Properties (i.e. business characteristics); the Aggregate Core Component “Party. Details” has five Properties (“Name”, “Role”, “Description”, “Defined. Contact” and “Postal. Address”); the Aggregate Core C

33、omponent “Contact. Details” has three Properties (“Type”, “Job Title” and “Primary”); the Aggregate Core Component “Address. Details” has four Properties (“Street Name”, “Free Form”, “Postcode” and “Country”).Ten of these Properties are Basic Core Components. They each represent a singular business

34、characteristic and its set of allowed values is defined by a Data Type.In the above example: “Name”, “Description”, “Job Title”, “Street Name”, “Free Form” and “Postcode” are of the Data Type Text; “Role” and “Type” are of the Data Type Code; “Primary” is of the Data Type Indicator; “Country” is of

35、the Data Type Identifier.6DIN ISO 15000-5:2014-10The other two Properties are Association Core Components. They each represent a set of complex business characteristics and in each case their structure is defined by another associated Aggregate Core Component. In the above example, “Party. Defined.

36、Contact” and “Party. Postal. Address” are both Association Core Components. The structures of these associated Aggregate Core Components are defined by the Aggregate Core Components “Contact. Details” and “Address. Details”, respectively.Core Components (and Business Information Entities) have Prope

37、rties that are defined by Data Types.A Data Type represents the full range of values to be used for the representation of a particular Core Component Property. A Data Type is based on one of the Core Component Types, but can include restrictions of the set of values of the Content Component and/or S

38、upplementary Component(s) of that Core Component Type.The diagram in Figure 2 shows the relationships between the various Core Component elements.Figure 2 Core Component Overview0.5 Key Business Information Entity ConceptsThe key differentiator between Core Components and Business Information Entiti

39、es is the concept of Business Context. Business context is a mechanism for refining the semantic meaning of components according to the specific requirements of their context of use. Once Business Contexts are identified, Core Components can be designed to take into account any necessary qualificati

40、on and refinement needed to support the use of their Core Component in the given Business Context. The Business Process definition provides a high level description of the use of a message and its contents.When a Core Component is used in a real business circumstance it serves as the basis of a Busi

41、ness Information Entity. The Business Information Entity is the result of using a Core Component within a specific Business Context.7DIN ISO 15000-5:2014-10A specific relationship exists between Core Components and Business Information Entities. Core Components and Business Information Entities are

42、complementary in many respects. Core Components are intended to be the linchpin for creating interoperable Business Process models and business documents using a Controlled Vocabulary.An Aggregate Business Information Entity is a piece of business data or a group of pieces of business data with a un

43、ique Business Semantic definition in a specific Business Context.There are three different categories of Business Information Entities:a) Basic Business Information Entity;b) Association Business Information Entity;c) Aggregate Business Information Entity.The most primitive of these is the Basic Bus

44、iness Information Entity. A Basic Business Information Entity is a Basic Core Component used in a specific Business Context.Whenever a Property of an Aggregate Business Information Entity is of a complex nature, and has the structure of another Aggregate Business Information Entity, an Association B

45、usiness Information Entity is used to represent that Property. An Association Business Information Entity is based on an Association Core Component, but exists in a Business Context.Trade_ PartyName (Text)Role (Code)Responsible_ ContactType (Code)Job Title (Text)Deg976inedStructured_ AddressPostcode

46、 (Text)Country (Identig976ier)PostalFigure 3 Association Business Information EntityFigure 3 is an example of Association Business Information Entity and shows the following: three Aggregate Business Information Entities: “Trade_ Party. Details”, “Responsible_ Contact. Details” and “Structured Addre

47、ss. Details”; each Aggregate Core Component has a number of Properties (i.e. business characteristics);8DIN ISO 15000-5:2014-10 the Aggregate Business Information Entity “Trade_ Party. Details” has four Properties (“Name”, “Role”, “Defined. Responsible_ Contact” and “Postal. Structured_ Address”); t

48、he Aggregate Business Information Entity “Responsible_ Contact. Details” has two Properties (“Type” and “Job Title”); the Aggregate Business Information Entity “Structured_ Address. Details” has two Properties (“Postcode” and “Country”).Six of these Properties are Basic Business Information Entities

49、: they each represent a singular business characteristic and in each case their set of allowed values is defined by their Data Type: “Name”, “Job Title” and “Postcode” are of the Data Type Text; “Role” and “Type” are of the Data Type Code; “Country” is of the Data Type Identifier.Two of the Properties are Association Business Information Entities: they each represent a set of complex business characteristics and in each case their struc