UN/CEFACT Core Components

UNITED NATIONS CENTRE FOR TRADE FACILITATION AND ELECTRONIC BUSINESSUnited Nations Economic Commission for Europe

UN/CEFACT

UN/CEFACT Core Components

Duane Nickull, CEFACT Plenary Bureau Vice-Chair, dnickull@adobe.com

UN/CEFACT

United Nations Centre for Trade Facilitation and Electronic Business

“UN/CEFACT supports activities dedicated to improving the ability of business, trade and administrative organizations, from developed, developing and transitional economies, to exchange products and relevant services effectively.”

UN/CEFACT

UN/CEFACT

Mission:• Trade Facilitation and eBusiness. To improve the

ability of business, trade and administrative organizations, from developed, developing and transitional economies, to exchange products and relevant services effectively - and so contribute to the growth of global commerce

Focus• The worldwide facilitation of national AND

international transactions, through the simplification and harmonization of procedures and information flows.

UN/CEFACT

Why do we need it?We Must Integrate the Information Ecosystem

Impact

Developing nations excluded from benefits of global trade.

The gap between the rich and poor continues to grow.

Social impact of trade in equality affects the entire population.

Economic discrimination hurts many, major social issues.

We can change it!

Action

Analyze, understand key elements of global business Develop methods and processes including technologies. Work with other standards development organizations (SDO’s) Ensure we have one “FREE and OPEN” set of standards to use. Encourage technology companies to behave responsibly. Bridge the gap between paper and electronic commerce. Educate and build capacity for fair global trade.

What we must do!

Problem

Cultural differences, trade regulations, sanctions. Technology barriers to trade. Need to balance global trade with global security. Not all nations have basic infrastructures. Models, technologies constantly changing.

Where we are.

UN/CEFACT

UN/CEFACT Structure

STRATEGY

VISION

TACTICAL

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today (scenario)

Also… Technical Slides (optional)

UN/CEFACT

Core Components are building blocks of metadata.

Each Core Component captures and declares details about a

real world business concept (example – “date”)

Designed to be re-used globally.

Design time artefacts. Could aid in building XML schemas,

UNeDocs code lists etc.

May be specialized for use within a certain context (example –

“date” becomes “OrderDate”)

NOTE: “Core Component” is used herein to cover all CC

terms including ACC, BCC, ABIE, BBIE

What are Core Components

UN/CEFACT

Core Component concepts

BIE

UN/CEFACT

Data Elements build Business Messages at Design Time

Name

Address

email

Phone #

Company

Company

Phone #

email

Address

Name

Party

Party ID

Invoice

PO #

Line Item

Cost

CONTEXT

Date

Order.Date

Business InformationEntities (BIE’s)

UN/CEFACT

What items do we use to describe a CC

Base Data

Unique definition

UUID (DCE 128 bit

algorithm format)

Data Dictionary Name

Object Class Term

Property Term

Representation Term

Data Type

Meta Data (from Registry)

Owner

Version

Status

Home Registry URI

Name

Associations

Classifications

Syntax Information

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today (scenario)

Also… Technical Slides (optional)

UN/CEFACT

Too many data standards

All have different data elements!

HR-XML

EHD

xCat

UBL

Rosettanet

OTAIATA

cXML

E-construct

CATXML

SMDG

PIDXGCI

UNeDoc

XAML

Opentrans

GML

xCBL

HL7

Acord

CIDX

xBRL BSML

agXML

VICS

SWIFT

Togaf

Bolero

UN/CEFACT

Problem: Inconsistent use of Data Elements

Nickull, Duane A.

Mr. Nickull

Duane Nickull

D. A. Nickull

Duane A. Nickull

Duane Allan Nickull

Nickull, Duane Allan

Mr. D. Nickull

Monsieur D.A. Nickull

NAME OF PERSON

UN/CEFACT

Solution: Data Dictionary

“Incompatibility becomes incremental rather than wholesale, i.e. the detailed points of difference are noted, rather than a whole model being dismissed as incompatible.”

Data Element: NameType: string

Data Element: DateType: integerMask: DDMMYY

Data Element: AddressType: Aggregate

Data Element: TelephoneType: string

UN/CEFACT

UN/CEFACT Core Components

verticalseGov XML SGMLX12 XML Etc.

1999

2002

2004

2007

Existing Standards

Reconciliation

Of Data Elements

EDIFACT

UN/CEFACT Core Component Library

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today (scenario)

Also… Technical Slides (optional)

UN/CEFACT

Work started in ebXML – joint initiative between UN/CEFACT and OASIS in 1999.

After May 2001, work continued within UN/CEFACT.

UN/CEFACT TMG applied to ISO for ebXML Core Components TS v 2.01 to become fast tracked as ISO 15000 standard.

Who is working on Core Components

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today (scenario)

Also… Technical Slides (optional)

UN/CEFACT

Core Component DiscoveryBusiness Documents

Country.Identifier

Person.Family Name

Core Componentdiscovery process. Core Component

Library

BusinessProcess

are part of

Context

UNeDocs

UN/CEFACT

Steps to identify Core Components

UN/CEFACT

Using Core Components at Design Time

Core Component Library

New BusinessProcess

has

1. Identify Core components to use for each Business Message

Businessmessages

2. Aggregate CC’s for each new Business Message.

3. Use context to guide refinement of CC’s into BIE’s. Express as final metadata for Business Messages.

<xml><xs:schema>

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today (scenario)

Also… Technical Slides (optional)

UN/CEFACT

CCTS Status CCTS v 2.01 done and submitted to ISO for fast

tracking.

UN/CEFACT ATG has CC naming and Design Rules

out for review.

CCTS getting a few reference implementations and

PoC’s (US, Canadian Government, Adobe, others…

see next page)

First 19 Core Components expected to be ratified

by CEFACT in MacLean Virginia September 2004

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today and tomorrow

(scenario)

Also… Technical Slides (optional)

UN/CEFACT

Using Core Components Today

UNeDocs instances use several pieces of information.

These are specialized Core Components, also called Business Information Entities or BIE’s.

It is possible to place UN/CEFACT Core Components into a Registry/Repository and use them for building UNeDocs today and tomorrow.

Pilot Infrastructure would need to be built

UN/CEFACT

UNeDocs use of Core Components?

Core Component Library (Registry)

UN eDocs

Example CC: Country.Identifier is associated with a list of values (UN LoCode)

Update/change Requests

Could be reflected real time in UN eDocs instances

UN/CEFACT

Q & A

Thank you

dnickull@adobe.com

UN/CEFACT

UN/CEFACTSIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES

FOR GLOBAL BUSINESS.

UN/CEFACT

Supplemental Technical Slides

Illustrative - for Q & A

UN/CEFACT

Agenda

What are Core Components What problems do they solve Who is working on Core Components Core Components explained What is the status How can you use them today (scenario)

Also… Technical Slides (optional)

UN/CEFACT

Core Components concepts

UN/CEFACT

Core Component Model

UN/CEFACT

Data Element Methodology (*CCTS)

UN/CEFACT

Context Declaration Mechanism

UN/CEFACT

Core component to BIE

Core Components are without context After context – become Business Information

Entities. Most data elements in existing languages

are ipso facto BIE’s UMM Business Entities are BIE’s