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

1、BSI Standards PublicationBS ISO 15000-5:2014Electronic Business ExtensibleMarkup Language (ebXML)Part 5: Core Components Specification(CCS)BS ISO 15000-5:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 15000-5:2014.The UK participation in its preparation w

2、as entrusted to TechnicalCommittee ICT/-/4, eBusiness coordination committee.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correcta

3、pplication. The British Standards Institution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 83147 8ICS 35.040Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Commit

4、tee on 30 June 2014.Amendments issued since publicationDate Text affectedBS ISO 15000-5:2014 ISO 2014Electronic Business Extensible Markup Language (ebXML) Part 5: Core Components Specification (CCS)Commerce lectronique en langage de balisage extensible (ebXML) Partie 5: Spcification des composants

5、principaux (CCS)INTERNATIONAL STANDARDISO15000-5First edition2014-04-15Reference numberISO 15000-5:2014(E)BS ISO 15000-5:2014ISO 15000-5:2014(E)ii ISO 2014 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2014All rights reserved. Unless otherwise specified, no part of this publication may be repr

6、oduced or utilized otherwise in any form or by any means, electronic 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 requeste

7、r.ISO copyright officeCase postale 56 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyrightiso.orgWeb www.iso.orgPublished in SwitzerlandBS ISO 15000-5:2014ISO 15000-5:2014(E) ISO 2014 All rights reserved iiiContents PageForeword ivIntroduction vi1 Scope . 12 Normative referen

8、ces 13 Terms and definitions . 14 Core Component Framework . 64.1 General . 64.2 Core Components . 64.3 Data Types 84.4 Business Information Entities . 84.5 Naming Convention 104.6 Library of Core Components 165 Context .165.1 General 165.2 Overview of Context Specification 165.3 Approved Context Ca

9、tegories 176 Conformance 20Annex A (normative) Primitive Type definitions .21Annex B (normative) List of approved Core Component Types (CCT) 22Annex C (normative) List of approved Core Component Type Content and Supplementary Components 24Annex D (normative) List of permissible Representation Terms

10、26Bibliography .27BS ISO 15000-5:2014ISO 15000-5:2014(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees.

11、 Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the Interna

12、tional Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the differ

13、ent types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall

14、not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).Any trade name used in this document is i

15、nformation given for the convenience of users and does not constitute an endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) se

16、e the following URL: Foreword - Supplementary informationThe committee responsible for this document is Technical Committee ISO/TC 154, Processes, data elements and documents in commerce, industry and administration.This first edition of ISO 15000-5 cancels and replaces ISO/TS 15000-5:2005. It also

17、incorporates the Amendment ISO/TS 15000-5:2005/Amd 1:2011.The following revisions have been made: removal of rules that were unclear or that were specific to the English language; clarification of rules that were ambiguous; updating of metamodels to reflect reality; removal of non-normative clauses.

18、ISO 15000 consists of the following parts, under the general title Electronic Business Extensible Markup Language (ebXML): Part 5: Core Components Specification (CCS)The following parts are under preparation: Part 1: Collaboration-protocol profile and agreement specification (ebCPP)1) Part 2: Messag

19、e service specification (ebMS)2) Part 3: Registry information model specification (ebRIM)3)1) Revision of ISO/TS 15000-1:2004.2) Revision of ISO/TS 15000-2:2004.3) Revision of ISO/TS 15000-3:2004.iv ISO 2014 All rights reservedBS ISO 15000-5:2014ISO 15000-5:2014(E) Part 4: Registry services specific

20、ation (ebRS)4)4) Revision of ISO/TS 15000-4:2004. ISO 2014 All rights reserved vBS ISO 15000-5:2014ISO 15000-5:2014(E)Introduction0.1 GeneralThis International Standard describes and specifies a new approach to the well-understood problem of the lack of information interoperability between applicati

21、ons in the e-business arena. Traditionally, standards for the exchange of business data have been focused on static message definitions that have not enabled a sufficient degree of interoperability or flexibility. A more flexible and interoperable way of standardizing Business Semantics is required.

22、 The Core Component solution described in this International Standard presents a methodology for developing a common set of 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

23、 business vocabularies.0.2 OverviewThe Core Components Specification (CCS) described in this International Standard provides 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-readab

24、le and machine-processable representations of this information.The Core Components approach described in this International 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 ebX

25、ML framework will help to ensure that two trading partners using different syntaxes e.g. Extensible Markup Language (XML) and 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 th

26、e same Core Components. This enables clean mapping between disparate message definitions across syntaxes, industry and regional 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

27、 past, these variations have led to incompatible data models and a subsequent lack of interoperability. The core components mechanism will allow identification of similarities and differences between these models. Incompatibility becomes incremental rather than wholesale, i.e. the detailed points of

28、 difference are noted, rather than a whole model being dismissed as incompatible.0.3 Key ConceptsThe CCS key concepts are based 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

29、and a normative definition is given, as well as an example, where appropriate.NOTE The term Core Component is used as a generic term that encompasses Basic Core Components, Association Core Components, Aggregate Core Components, and their associated Core Component Types. Equally, the term Business I

30、nformation Entity is used as a generic term encompassing Basic Business Information Entities, Association Business Information Entities, and Aggregate Business Information Entities.0.4 Key Core Component ConceptsThe central concept of this International Standard is the Core Component. The Core Compo

31、nent is a semantic building block, which is used as a basis to construct all electronic business messages.There are four different categories of Core Components: a) Basic Core Component;b) Association Core Component;c) Core Component Type;d) Aggregate Core Component.vi ISO 2014 All rights reservedBS

32、 ISO 15000-5:2014ISO 15000-5:2014(E)These concepts are described below and their definitions are given in Clause 3.PartyName (Text)Role (Code)Description (Text)ContactType (Code)Job Title (Text)Primary (Indicator)Deg976inedAddressStreet Name (Text)Free Form (Text)Postcode (Text)Country (Identig976ie

33、r)PostalFigure 1 Association Core ComponentFigure 1 is an example of an Association Core Component and shows the following: three Aggregate Core Components: “Party. Details”; “Contact. Details” and “Address. Details”; each Aggregate Core Component has a number of Properties (i.e. business characteri

34、stics); the Aggregate Core Component “Party. Details” has five Properties (“Name”, “Role”, “Description”, “Defined. Contact” and “Postal. Address”); the Aggregate Core Component “Contact. Details” has three Properties (“Type”, “Job Title” and “Primary”); the Aggregate Core Component “Address. Detail

35、s” has four Properties (“Street Name”, “Free Form”, “Postcode” and “Country”).Ten of these Properties are Basic Core Components. They each represent a singular business characteristic and its set of allowed values is defined by a Data Type.In the above example: “Name”, “Description”, “Job Title”, “S

36、treet 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 the Data Type Identifier. ISO 2014 All rights reserved viiBS ISO 15000-5:2014ISO 15000-5:2014(E)The other two Properties are Associ

37、ation 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. Contact” and “Party. Postal. Address” are both Association Core Components. The stru

38、ctures 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 Properties that are defined by Data Types.A Data Type represents the full range of values

39、 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 Supplementary Component(s) of that Core Component Type.The diagram in Figure 2 shows

40、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 Entities is the concept of Business Context. Business context is a mechanism for refining

41、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 qualification and refinement needed to support the use of their Core Component in the given Bus

42、iness 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 Business Information Entity. The Business Information Entity is the result of using a Co

43、re Component within a specific Business Context.viii ISO 2014 All rights reservedBS ISO 15000-5:2014ISO 15000-5:2014(E)A specific relationship exists between Core Components and Business Information Entities. Core Components and Business Information Entities are complementary in many respects. Core

44、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 unique Business Semantic definition in

45、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 Business Information Entity. A Basic Bus

46、iness 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 Business Information Entity is used to

47、 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 (Text)Country (Identig976ier)PostalF

48、igure 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 Address. Details”; each Aggregate Core Com

49、ponent has a number of Properties (i.e. business characteristics); ISO 2014 All rights reserved ixBS ISO 15000-5:2014ISO 15000-5:2014(E) the Aggregate Business Information Entity “Trade_ Party. Details” has four Properties (“Name”, “Role”, “Defined. Responsible_ Contact” and “Postal. Structured_ Address”); the 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