ISO 15000-5:2014

INTERNATIONAL ISO
STANDARD 15000-5
First edition
2014-04-15
Electronic Business Extensible
Markup Language (ebXML) —
Part 5:
Core Components Specification (CCS)
Commerce électronique en langage de balisage extensible (ebXML) —
Partie 5: Spécification des composants principaux (CCS)
Reference number
©
ISO 2014
© ISO 2014
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 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 ISO’s member body in the country of
the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved

Contents Page
Foreword .iv
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Core Component Framework . 6
4.1 General . 6
4.2 Core Components . 6
4.3 Data Types . 8
4.4 Business Information Entities . 8
4.5 Naming Convention.10
4.6 Library of Core Components .16
5 Context .16
5.1 General .16
5.2 Overview of Context Specification .16
5.3 Approved Context Categories .17
6 Conformance .20
Annex A (normative) Primitive Type definitions .21
Annex B (normative) List of approved Core Component Types (CCT) .22
Annex C (normative) List of approved Core Component Type Content and
Supplementary Components .24
Annex D (normative) List of permissible Representation Terms .26
Bibliography .27
Foreword
ISO (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. 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 International 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
different 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 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 information 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 ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT) see the following URL: Foreword - Supplementary information
The 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 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.
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:
1)
— Part 1: Collaboration-protocol profile and agreement specification (ebCPP)
2)
— Part 2: Message service specification (ebMS)
3)
— Part 3: Registry information model specification (ebRIM)
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 reserved

4)
— Part 4: Registry services specification (ebRS)
4) Revision of ISO/TS 15000-4:2004.
Introduction
0.1 General
This 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 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 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 Overview
The 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-readable 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 ebXML 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 the 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 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 difference are noted, rather than a whole
model being dismissed as incompatible.
0.3 Key Concepts
The 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
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 Information 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 Concepts
The 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 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 reserved

Deined
These concepts are described below and their definitions are given in Clause 3.
Party
Name (Text)
Role (Code)
Description (Text)
Postal
Address
Contact
Street Name (Text)
Type (Code)
Free Form (Text)
Job Title (Text)
Postcode (Text)
Primary (Indicator)
Country (Identiier)
Figure 1 — Association Core Component
Figure 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 characteristics);
— 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. 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 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 the Data Type Identifier.
The 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. 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 Properties 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 Supplementary
...