Top Banner
2004 Adobe Systems Incorporated. All Rights Reserved. b c UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework Duane Nickull [email protected]
36

2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

Jan 11, 2016

Download

Documents

Britney Roberts
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

2004 Adobe Systems Incorporated. All Rights Reserved.bc

UN/CEFACT Core Components

Semantic Interoperability of Data Elements and the

Context Framework

Duane [email protected]

Page 2: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 2

United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT)

“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.”

Page 3: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 3

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.

Page 4: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 4

Why do we need it?

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.

Page 5: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 5

Agenda

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

Also… Technical Slides (optional)

Page 6: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 6

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

Page 7: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 7

Core Component concepts

BIE

Page 8: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 8

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)

Core Components (CC’s)

Page 9: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 9

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

Page 10: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 10

Agenda

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

Also… Technical Slides (optional)

Page 11: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 11

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

Page 12: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 12

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

Page 13: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 13

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

Page 14: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 14

UN/CEFACT Core Components vision

UBL eGov XML SGMLX12 XML Etc.

1999

2002

2004

2007

Existing Standards

Reconciliation

Of Data Elements

EDIFACT

UN/CEFACT Core Component Library

Page 15: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 15

Agenda

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

Also… Technical Slides (optional)

Page 16: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 16

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

Page 17: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 17

Agenda

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

Also… Technical Slides (optional)

Page 18: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 18

Core Component Discovery

Business Documents

Country.Identifier

Person.Family Name

Core Componentdiscovery process. Core Component

Library

BusinessProcess

are part of

Context

UNeDocs

Page 19: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 19

Steps to identify Core Components

Page 20: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 20

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>

Page 21: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 21

Agenda

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

Also… Technical Slides (optional)

Page 22: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 22

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…)

Page 23: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 23

Agenda

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

tomorrow (scenario)

Also… Technical Slides (optional)

Page 24: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 24

Using Core Components Today

All new transaction instances use several pieces of information. Picked from CC dictionary.

Business Information Entities or BIE’s can be serialized inline using Context Methodology Framework.

Government of Canada has placed 353 Data Elements in ebXML Registry. Data model XML rendition of UN/CEFACT Core

Components Uses them for building transactions

Work entering phase IV

Page 25: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 25

Example: Context Affects “Human Being” depending on “Role”.

CORE COMPONENT

(BEING)

Police Officer knows he is a WITNESS

FRENCHENGLISH

Police Investigator thinksHe is a SUSPECT

NPB calls him a PAROLEE

Corrections call him aINMATE / CRIMINAL

Judge calls him aDEFENDANT

L'officier de police sait qu'il est un TÉMOINL'investigateur de police pense qu'il est un SUSPECT

NPB l'appelle un LIBÉRÉ SUR PAROLE

Les corrections l'appellent un DÉTENU/CRIMINEL

Le juge l'appelle un DÉFENDEUR

Page 26: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 26

Demo Scenario explained

English or French Text DocumentHTMLXML SchemaPDF eForms

CORE COMPONENT

BUSINESSINFORMATION

ENTITY

SYNTAX BIEEXPRESSION

USAGECONTEXT

Context Key:urn:uuid:4a593056-3509-0766-2e7b-4e154030423fGeo-Political Context: English or FrenchLegislative Context: Narcotics LegistationIndustry Context: NAICS 9221Process Context: HC 3515Process Role Context: Police ChiefSupporting Role Context: RCMP Investigator Product Context: N/ASystems Capabilities Context: XML Schema

1. Example: YEAR

Syntax Independent

Syntax Bound

2. Becomes: BEING.BIRTH.YEAR of Suspect

3.Is expressed in an XML schema fragment

Page 27: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 27

Applications to Support Design Time

Registry/Repository

XML DictionaryData Elements

(CC’s and BIE’s)

References

AssemblerUtility

INPUT

OUTPUT

XML Schema Form Template

May be placed into Registry

Transaction (Assembly Doc)

Process Designers

Context of Use

Calls to Registry

Page 28: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 28

Q & A

Thank you

[email protected]

Page 29: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 29

UN/CEFACTSIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES

FOR GLOBAL BUSINESS.

Page 30: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

2004 Adobe Systems Incorporated. All Rights Reserved.bc

Supplemental Technical Slides

Illustrative - for Q & A

Page 31: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 31

Agenda

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

Also… Technical Slides (optional)

Page 32: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 32

Core Components concepts

Page 33: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 33

Core Component Model

Page 34: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 34

Data Element Methodology (*CCTS)

Page 35: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 35

Context Declaration Mechanism

Page 36: 2004 Adobe Systems Incorporated. All Rights Reserved. bcbc UN/CEFACT Core Components Semantic Interoperability of Data Elements and the Context Framework.

bc

2004 Adobe Systems Incorporated. All Rights Reserved. 36

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