ISO/TS 15000-5:2005

Electronic Business Extensible Markup Language (ebXML) — Part 5: ebXML Core Components Technical Specification, Version 2.01(ebCCTS)

ISO/TS 15000-5:2005 can be employed wherever business information is being shared or exchanged amongst and between enterprises, governmental agencies, and/or other organisations in an open and worldwide environment. ISO/TS 15000-5:2005 will form the basis for standards development work of business analysts, business users and information technology specialists supplying the content of and implementing applications that will employ the UN/CEFACT Core Component Library (CCL). The Core Component Library will be stored in a UN/CEFACT repository and identified in an ebXML compliant registry. Due to the evolving nature of the UN/CEFACT Core Component Library, ISO/TS 15000-5:2005 includes material that focuses on the business community doing further discovery and analysis work. Some of the contents of ISO/TS 15000-5:2005 are not typical of this type of technical document. However, they are critical for successful adoption and standardization in this area to move forward.

Commerce électronique en langage de balisage extensible (ebXML) — Partie 5: Spécification technique des composants principaux (ebXML), Version 2.01(ebCCTS)

General Information

• Status: Withdrawn
• Publication Date: 15-Sep-2005
• Withdrawal Date: 15-Sep-2005
• ICS: 35.040 - Information coding
• ICS: 35.040.50 - Automatic identification and data capture techniques
• Technical Committee: ISO/TC 154 - Processes, data elements and documents in commerce, industry and administration
• Drafting Committee: ISO/TC 154 - Processes, data elements and documents in commerce, industry and administration
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 14-Apr-2014

Relations

• Revised: ISO 15000-5:2014 - Electronic Business Extensible Markup Language (ebXML) — Part 5: Core Components Specification (CCS)
• Effective Date: 28-Jan-2012
• Amended By: ISO/TS 15000-5:2005/Amd 1:2011 - Electronic Business Extensible Markup Language (ebXML) — Part 5: ebXML Core Components Technical Specification, Version 2.01(ebCCTS) — Amendment 1
• Effective Date: 31-Jul-2021

Standards Content (Sample)

TECHNICAL ISO/TS
SPECIFICATION 15000-5
First edition
2005-09-15

Electronic Business Extensible Markup
Language (ebXML) —
Part 5:
ebXML Core Components Technical
Specification, Version 2.01(ebCCTS)
Commerce électronique en langage de balisage extensible (ebXML) —
Partie 5: Spécification technique des composants principaux (ebXML),
Version 2.01(ebCCTS)




Reference number
ISO/TS 15000-5:2005(E)
©
ISO 2005

---------------------- Page: 1 ----------------------
ISO/TS 15000-5:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's 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
downloading this file, parties accept therein the responsibility of not infringing Adobe's 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 General 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 below.


©  ISO 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2005 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/TS 15000-5:2005(E)
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
 an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
 an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee
casting a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
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.
ISO/TS 15000-5 was prepared jointly by Technical Committee ISO/TC 154, Processes, data elements and
documents in commerce, industry and administration in collaboration with UN/CEFACT.
ISO/TS 15000 consists of the following parts, under the general title Electronic business eXtensible mark-up
language (ebXML):
 Part 1: Collaboration-protocol profile and agreement specification (ebCPP)
 Part 2: Message service specification (ebMS)
 Part 3: Registry information model specification (ebRIM)
 Part 4: Registry services specification (ebRS)
 Part 5: ebXML Core Components Technical Specification, Version 2.01(ebCCTS)

© ISO 2005 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT

United Nations Centre for Trade Facilitation and Electronic Business









Core Components Technical Specification –
Part 8 of the ebXML Framework




15 November 2003
Version 2.01

Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 1 of 113

© ISO 2005 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT

United Nations Centre for Trade Facilitation and Electronic Business


1 Status of This Document
This UN/CEFACT Technical Specification has been developed in accordance with the
UN/CEFACT/TRADE/22 Open Development Process (ODP) for Technical Specifications. It has
been approved by the United Nations Centre for Trade Facilitation and Electronic Business
(UN/CEFACT) Techniques and Methodologies Group (TMG) for promulgation as a UN/CEFACT
Technical Specification in accordance with Step 7 of the ODP.
This document contains information to guide in the interpretation or implementation of ebXML
concepts.
Distribution of this document is unlimited.
The document formatting is based on the Internet Society’s Standard RFC format.
This version: Core Components Technical Specification – Part 8 of the ebXML Framework, Version
2.01 of 15 November 2003
Previous version: UN/CEFACT – Core Components Technical Specification, Version 2.0 of 11
August 2003
This edition is an updated version of Core Components Technical Specification Version 2.0 (first
published 11 August 2003); it merely incorporates a title correction and minor first-edition errata
related to ebXML references as a convenience to readers.

Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 2 of 113

2 © ISO 2005 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

2 Core Components Technical Specification Administration
The leaders and editors express gratitude to the significant number of participants who
contributed to the successful completion of this document.
We would like to recognise the following for their significant participation to the development
of this Technical Specification.
Project Team Leader: Alan Sitzer  Marsh USA, Inc
Lead Editor: Mark Crawford LMI
Editing Team Mike Adcock  APACS
Mary Kay Blantz AIAG (Past Project Team Lead)
Arofan Gregory AEON Consulting
Alan Stitzer  Marsh, Inc.
Frank Vandamme SWIFT
James Whittle  e Centre

Contributors:
Hartmut Hermes Siemens (Past Project Team Lead)
Bernd Boesler  DIN
Todd Boyle  NetAccount
Kerstien Celis  Seagha c.v.
Jean-Luc Champion Enterprise Integration Partners
Marianne Cockle APACS
Scott Colthurst State Farm
Alain Dechamps CEN/ISSS
Eduardo Gutentag Sun Microsystems
Paula Heilig  Worldspan
Stig Korsgaard Danish Bankers Association
Melanie McCarthy General Motors
Sue Probert  Commerce One
Andreas Schultz DKV
Lisa Seaburg  AEON Consulting
Gunther Stuhec SAP AG
Hisanao Sugamata ECOM-Japan
Herbert Thomas AustriaPro
Fred Van Blommestein Berenschot
Nigel Wooden            ACORD


This technical specification is dedicated to our friend and collegue Mike Adcock without
whose tireless efforts and significant contribution this specification would not be possible.

Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 3 of 113

© ISO 2005 – All rights reserved 3

---------------------- Page: 6 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

3 Table of Contents
1 Status of This Document.2
2 Core Components Technical Specification Administration.3
3 Table of Contents .4
4 Introduction .7
4.1 Scope and Focus.7
4.2 Structure of this Specification.8
4.2.1 Notation.8
4.3 Conformance.9
4.4 Related Documents.9
4.5 Overview.10
4.6 Key Concepts.11
4.6.1 Key Core Component Concepts.11
4.6.2 Key Business Information Entity Concepts .15
4.7 Relationship between UN/CEFACT Modelling Methodology
and Core Components .19
5 Working Process and Methodology .20
5.1 Overview.20
5.1.1 Discovery.20
5.1.2 How to use UN/CEFACT Core Components .21
5.1.2.1 Core Components and Semantic Interoperability .21
5.1.2.2 Overall Discovery and Document Design.22
5.2 Core Components Discovery .25
5.2.1 Core Component Discovery – Preparation Steps.25
5.2.2 Core Component Discovery – Search Registry/Repository.26
5.2.3 Core Component Discovery – Basic and Association Business
Information Entities .28
5.2.4 Data Types, Property, and Identifying Similarities.28
5.3 Preparation for Submission.29
5.3.1 Applying the Naming Convention to a New Item.29
5.3.2 Preparation for Submitting New Items.32
5.3.2.1 New Aggregate Core Components.32
5.3.2.2 New Basic Core Components .34
5.3.2.3 New Aggregate Business Information Entities which re-use
Existing Aggregate Core Components.34
5.4 Harmonization.35
5.5 Technical Assessment and Approval .36
5.6 Context in the Discovery Process.37
5.6.1 Context Categories.37
5.6.2 Guidelines for Analysing Business Information Entities in Context .38
6 Technical Details.41
6.1 Core Components, Data Types and Business Information Entities .41
6.1.1 Core Components.41
6.1.2 Data Types.44
6.1.3 Business Information Entities .44
6.1.4 Naming Convention.46
6.1.4.1 Core Component Naming Rules .47
6.1.4.1.1 Core Component Dictionary Information .47
Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 4 of 113

4 © ISO 2005 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

6.1.4.1.2 Core Component General Rules.48
6.1.4.1.3 Core Component Rules for Definitions.48
6.1.4.1.4 Core Component Rules for Dictionary Entry Names.49
6.1.4.1.5 Rules for Core Component Business Terms .51
6.1.4.2 Rules for Business Information Entities.51
6.1.4.2.1 Business Information Entity Dictionary Information.51
6.1.4.2.2 Business Information Entity General Rules .52
6.1.4.2.3 Business Information Entity Rules for Definitions .52
6.1.4.2.4 Rules for Business Information Entity Dictionary Entry Names.53
6.1.4.2.5 Rules for Business Information Entity Business Terms.54
6.1.4.3 Rules for Data Types.54
6.1.4.3.1 Data Type Dictionary Information.54
6.1.4.3.2 Data Type General Rules .55
6.1.4.3.3 Data Type Rules for Definitions .55
6.1.4.3.4 Rules for Data Type Dictionary Entry Names .55
6.1.4.3.5 List of Permissible Representation Terms .56
6.1.5 Catalogue of Core Components .57
6.1.6 Catalogue of Business Information Entities.58
6.2 Context.58
6.2.1 Overview of Context Specification .58
6.2.1.1 Context Categories.59
6.2.1.2 Constraint Language.59
6.2.1.3 Syntax Binding.60
6.2.2 Approved Context Categories .60
6.2.2.1 Business Process Context.61
6.2.2.2 Product Classification Context.62
6.2.2.3 Industry Classification Context.62
6.2.2.4 Geopolitical Context.63
6.2.2.5 Official Constraints Context.64
6.2.2.6 Business Process Role Context .65
6.2.2.7 Supporting Role Context.65
6.2.2.8 System Capabilities Context.65
6.2.3 Context Values.66
6.2.4 Core Components Context Constraints Language .66
6.2.4.1 Assembly Construct.73
6.2.4.2 ContextRules Construct.73
6.2.4.3 Output Constraints.74
6.2.4.4 Ordering and Application.74
7 Technical Details - Core Component Registry/Repository Storage.75
7.1 Storing Core Components.75
7.1.1 Stored Core Components .76
7.1.2 Stored Aggregate Core Components.77
7.1.3 Stored Core Component Properties.77
7.1.4 Stored Basic Core Component Properties.78
7.1.5 Stored Association Core Component Properties.78
7.1.6 Stored Basic Core Components.78
7.1.7 Stored Association Core Components.78
7.1.8 Stored Core Component Types .78
7.1.9 Stored Supplementary Components.79
7.1.10 Stored Content Components.80
Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 5 of 113

© ISO 2005 – All rights reserved 5

---------------------- Page: 8 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

7.2 Storing Data Types.80
7.2.1 Stored Data Types .80
7.2.2 Stored Content Component Restrictions.81
7.2.3 Stored Supplementary Component Restrictions .83
7.3 Stored Context.84
7.3.1 Stored Business Contexts.84
7.3.2 Stored Classification Schemes .84
7.3.3 Stored Context Values.85
7.4 Stored Business Information Entities.85
7.4.1 Stored Aggregate Business Information Entities .86
7.4.2 Stored Aggregate Business Information Entities .87
7.4.3 Stored Business Information Entity Properties .88
7.4.4 Stored Basic Business Information Entity Properties .88
7.4.5 Stored Association Core Component Properties.89
7.4.6 Stored Basic Business Information Entities .89
7.4.7 Stored Association Business Information Entities.89
7.5 Core Component Storage Metadata .89
7.5.1 General Metadata Storage Rules .91
7.5.2 Management Information.91
7.5.2.1 Administrative Information.91
7.5.2.2 Status Information.92
7.5.2.3 Change History.92
7.5.2.4 Replacement Information.92
7.5.3 Content Information.93
7.5.3.1 Descriptive Information.93
7.5.3.2 Representation Information.93
7.5.3.3 Association Information.94
8 Approved Core Component Type, Content, and Supplementary
Components; and Permissible Representation Terms.95
8.1 Approved Core Component Types.95
8.2 Approved Core Component Type Content and Supplementary
Components.97
8.3 Permissible Representation Terms.100
9 Definition of Terms.103
10 References.109
11 Disclaimer.111
12 Contact Information.112
Copyright Statement .113

Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 6 of 113

6 © ISO 2005 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

4 Introduction
This Core Components Technical Specification 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 standardising
Business Semantics is required. The UN/CEFACT (United Nations Centre for Trade
Facilitation and Electronic Business) Core Component solution described in this specification
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.
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in Internet Engineering Task Force (IETF)
Request For Comments (RFC) 2119.1
4.1 Scope and Focus
This Core Components Technical Specification can be employed wherever business
information is being shared or exchanged amongst and between enterprises, governmental
agencies, and/or other organisations in an open and worldwide environment. The Core
Components User Community consists of business people, business document modellers and
business data modellers, Business Process modellers, and application developers of different
organisations that require interoperability of business information. This interoperability
covers both interactive and batch exchanges of business data between applications through
the use of Internet and Web based information exchanges as well as traditional Electronic
Data Interchange (EDI) systems.
This specification will form the basis for standards development work of business analysts,
business users and information technology specialists supplying the content of and
implementing applications that will employ the UN/CEFACT Core Component Library
(CCL). The Core Component Library will be stored in a UN/CEFACT repository and
identified in an ebXML compliant registry.
Due to the evolving nature of the UN/CEFACT Core Component Library, the specification
includes material that focuses on the business community doing further discovery and
analysis work. Some of the contents of this specification are not typical of this type of
technical document. However, they are critical for successful adoption and standardization in
this area to move forward.

1
Key words for use in RFCs to Indicate Requirement Levels - Internet Engineering
Task Force, Request For Comments 2119, March 1997,
http://www.ietf.org/rfc/rfc2119.txt?number=2119
Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 7 of 113

© ISO 2005 – All rights reserved 7

---------------------- Page: 10 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

4.2 Structure of this Specification
Due to the diversity of the intended audience, this document has been divided into five main
Sections.
• Section 5: Working Process and Methodology for Business UsersDiscovery,
Harmonization, Assessment and How to Use [informative]
• Section 6: Technical DetailsCore Components and Context [normative]
• Section 7: Technical DetailsStorage and Metadata [normative]
• Section 8: Technical Details Permissible Representation Terms and Approved
Core Component Type, Content, and Supplementary Components [normative]
• Section 9: Definition of Terms [normative]
Sections 5, 6, 7 and 8 are complementary, but may also be used independently of each other.
Section 5 is informative. A business audience may choose to read through the working
process and methodology section (Section 5) and only reference the Technical Details
(Sections 6, 7 and 8) as needed. Sections 6, 7 and 8 are normative. A technical audience may
choose to focus on the technical details (Sections 6, 7, and 8), referring to the methodology
(Section 5) and example (published as a supplemental document) sections as appropriate,
using the current permissible Representation Terms and approved Core Component Type,
Content, and Supplementary Components (Section 8) and the glossary (Section 9).
In addition, the UN/CEFACT Forum will prepare supplemental documents that may be used
in conjunction with this Core Components Technical Specification. These supplemental
documents will include:
• Message Assembly – expands on the Assembly principles and Constraints
Language contained in the Core Components Technical Specification and
provides specific methodology for assembling higher level Business Information
Entities for electronic messages.
• Core Components Primer – details how the contents of Sections 5, 6, and 7 would
be used in practice to create a library of Core Components and Business
Information Entities.
• Catalogue of Core Components – represents the work of various organizations
working in a joint endeavour to develop and publish semantically correct and
meaningful information exchange parcels.
4.2.1 Notation
[Definition] – A formal definition of a term. Definitions are normative.
[Example] – A representation of a definition or a rule. Examples are informative.
Core Components Technical Specification V2.01
Part 8 of the ebXML Framework Page 8 of 113

8 © ISO 2005 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/TS 15000-5:2005(E)
UN/CEFACT Technical Specification 2003-11-15

[Note] – Explanatory information. Notes are informative.
[Rn] – Identification of a rule that requires conformance to ensure discovered Core
Components are properly discovered, named and stored. The value R is a prefix to categorise
the type of rule where R=A for Conformance rule, R=B for Business Information Entity rule,
R=C for Core Component rule, R=D for Data Type rule, or R=S for Storage rule; and n (1.n)
indicates the sequential number of the rule]. Rules are normative. In order to ensure
continuity across versions of the specification, rule numbers that are deleted will not be re-
issued, and any new rules will be assigned the next higher number - regardless of location in
the text.
Italics – All words appearing in italics, when not titles or used for emphasis, are special terms
defined in Section 9.
Courier – All words appearing in bolded courier font are values or objects.
4.3 Conformance
Applications will be considered to be in full conformance with this technical specification if
they comply with the content of normative sections, rules and definitions.
[A1] Conformance shall be determined through adherence to the content of normative
sections, rules and definitions.
4.4 Related Documents
The following documents provided significant levels of influence in the development of this
document:
 ebXML Technical Architecture Specification v1.04
 ebXML Business Process Specification Schema v
...