ebXML Semantic Content Management

ebXML Semantic Content Management

Mark CrawfordLogistics Management Institute

[email protected]

Mark Crawford, LMI, 11 February 2004 LMI

Agenda

• ebXML Overview• The ebXML Registry Concept• ebXML Core Components• Summary


The ebXML Initiative

• A joint UN/CEFACT and OASIS 18-month effort, concluding in May 2001

• Over 1000 international participants from both XML and Business Communities

• The vision: a global electronic marketplace where enterprises of any size, anywhere, can:– Find each other electronically– Conduct business by exchanging XML messages

• Initial product is a technical framework that enables XML and other payloads to be utilized in a consistent manner for the exchange of all electronic business data

• ebXML work continues in OASIS and UN/CEFACT


The ebXML Concept

ebXML compliantsystem

Business ProfilesBusiness Scenarios

ebXMLRegistry

XML

Request Business Details

1

Build Local SystemImplementation

Register Implementation DetailsRegister COMPANY A Profile

3

2

5Agree on Business Arrangement4

Query about COMPANY A profile

DownloadScenarios and Profiles

DO BUSINESS TRANSACTIO

NS

6

COMPANY A

COMPANY B



ebXMLRegistry

XML


1



3

2





NS

6

COMPANY A

COMPANY B



ebXMLRegistry

XML


1



3

2





NS

6

COMPANY A

COMPANY B

Source: ebXML Architecture TS, V1.04, Feb 2003


The ebXML Construct

Mark Crawford, LMI, 11 February 2004


ebXML Design Time and Runtime Reference Model

88ebXML CCBP Analysis

Transport

Package

BusinessService

Interface

BusinessServices/App’s

Ru

n T

ime

BusinessService

Interface

BusinessServices/App’s

Registry/ Repository

Core/DomainComponents

BusinessDocuments

CP Agreement

Des

ign

Tim

e BusinessProcess

CollaborationProtocolProfile

CollaborationProtocolProfile

Register & Discover

Business Library

Source: ebXML Business Process and Business Information Analysis Overview v1.0


Agenda

• ebXML Overview

• The ebXML Registry The ebXML Registry ConceptConcept

• ebXML Core Components• Summary


ebXML Registry

• Purpose:– Provide a set of services that enable sharing of information

between interested parties– Enable business process integration between parties based on the

ebXML specifications– Manage repository objects

• Latest specifications:– ebXML Registry Information Model, Version 2.5, June

2003– ebXML Registry Services Specification, Version 2.5,

June 2003

• What it does:– Identifies shared objects maintained in a repository– Provides a set of services to manage and share these objects


RIM – Public View

RIM Provides information on: 1.

The types of metadata stored in the Registry 2.

The relationships among the various metadata classes.

Source: ebXML RIM Specification, V 2.5, June 2003


RIM – Detailed Inheritance View

Source: ebXML Registry Information Model Specification, V 2.5, June 2003


Agenda

• ebXML Overview• The ebXML Registry Concept

• ebXML Core ComponentsebXML Core Components• Summary


ebXML Core Components

• A set of the lowest common denominators that capture information about real world (business) concepts

• Core Components are neutral– in the notation for every kind of industry– in the syntax for every kind of business

document standard or implementation


ebXML Core Components

• Reusable pieces (objects) of contents that can be atomic or aggregate– Enables interoperability among different industry domains and

areas– Uses common semantic units at any level consistent across

context– Holds any related information together and avoids fragmented

semantic dispersal– Facilitates multilingual support

• Accompanied by methodologies for context and extensibility– Enables users to define meaningful business and process data– Ensures maximum interoperability


Core Components Are Based On ISO 11179 Data Constructs

Each aspect of 11179 relates to a CC construct


An Example

• This is basic object-oriented “good stuff”

Object class

Property 1: representation 1Property 2: representation 2Property 3: representation 3Property 4: representation 4

Address

Street: textPost code: textTown: textCountry: identifier

ISO 11179 governs data dictionaries:defines the notions of object class, property, and representation term


Core Component Overview

CoreComponent Type (CCT)

ContentComponent

Supplementary Component

Basic CoreComponent

Aggregate CoreComponent

Core ComponentProperty

Data Type

Consists of

Consists of

1

1-n

Specifiesrestrictions on

Describesvalues of

Provides businesscharacteristic

Without businesssemantics

With knownbusiness semantics

Aggregated in

CoreComponent Type (CCT)

Basic Core Component

Aggregate Core Component

CoreComponent

Property

Data Type


Describesvalues of


BasicBusiness Information Entity

Property

Basic Business InformationEntity

Aggregate Business InformationEntity

BusinessInformation

EntityProperty


Describesvalues of


Aggregatedin

Message Assembly

AssemblyComponent

Qualifies the Object Class

of

Isbased

on

Isbased

on

Core Business

Core Component Library

Aggregatedin

Adds extra information

Data TypeFurther restricts

Aggregatedin

Aggregatedin

Instantiating CC’s as BIEs


Technical Details CC and Data Types Metamodel

Core Component

Business Term 0..*

Registry Class

Unique Identifier 1..1Dictionary EntryName 1..1Definition 1..1

CC Property

Property Term 1..1Cardinal ity 1..1

Aggregate Core Component (ACC)

Object Class Term 1..1

1..*1..*

Association Core Component (ASCC)

Association CC Property

1

0..*

1

0..* 1

1

1

1


Content Component

Basic Core Component (BCC)

Core Component Type (CCT)

Primary Representation Term 1..1Secondary Representation Term 0..*

1..*1..*

11

Basic CC Property

11 11

Supplementary Component Restriction

Content Component Restriction

Data Type

Qualifier Term 0..1

0..* 10..*

+basis

11

0..*

1

0..*

0..*0..*

0..*0..*


Technical Details – BIE MetamodelRegistry Class

Unique Identif ier 1..1Dictionary Entry Name 1..1Def inition 1..1

Business Context

Business Inf ormation Entity (BIE)

Business Term 0..*

1..*

0..*

+context 1..*

0..*

Core Component

0..* 10..*

+basis

1

Association BIE Property Association CC Property


1

1

1

1

Association Business Inf ormation Entity (ASBIE)

1

1

1

1

10..*

+basis

10..*

Aggregate Business Inf ormation Entity (ABIE)

Qualif ier Term 0..1Cardinality 1..1

1

0..*

1

0..*



0..*

1

0..*

1

10..*

+basis

10..*

CC Property

Property Term 1..1Cardinality 1..1

1..*1..*

BIE Property

Qualif ier Term 0..1

1..*1..*

10..*

+basis

10..*

Basic Business Inf ormation Entity (BBIE)

Basic BIE Property

1

1

1

1


10..*

+basis

10..*

Basic CC Property

1

1

1

1

Data Ty pe


0..*

1

0..*

1

0..*

1

0..*

1


The StorageMetamodel –Core Components

Core Component

Business Term 0..*

Registry Class

Unique Identi fier 1..1Version 1..1Dictionary EntryName 1..1Definition 1..1Usage Rule 0..*

CC Property

Property Term 1..1Cardinali ty 1..1



1..*1..*


Association CC Property

1

0..*

1

0..* 1

1

1

1


Name 1..1Definition 1..1Primitive type 1..1Possible Value 0..*

Content Component

Name 1..1Definition 1..1Primitive type 1..1


Core Component Type (CCT)

Primary Representation Term 1..1Secondary Representation Term 0..*

1..*1..*11

Basic CC Property

11 11

Supplementary Component Restriction

Supplementary Component Name 1..1Restriction Value 1..*

Content Component Restriction

Restriction Type 1..1Restriction Value 1..1Expression Type 0..1

Data Type

Qual ifier Term 0..1

0..* 10..*

+basis

11

0..*

1

0..*

0..*0..*0..*0..*


Registry Class

Unique Identif ier 1..1Version 1..1Dictionary Entry Name 1..1Def inition 1..1Usage Rule 0..*

Business Context

Business Inf ormation Entity (BIE)

Constraint Language 0..*Business Term 0..*Example 0..*

1..*

0..*

+context1..*

0..*

Core Component

0..*

1

0..*

+basis

1

Data Ty pe


Basic Business Inf ormation Entity (BBIE)Basic BIE Property

1

0..*

1

0..*11 11

BIE Property

Qualif ier Term 0..1Cardinality 1..1

Aggregate Business Inf ormation Entity (ABIE)


1..*1..*

Association Business Inf ormation Entity (ASBIE)

Association BIE Property

1

0..*

1

0..*1

1

1

1

The StorageMetamodel –Business Information Entities


Business Process Context Value

Geopolitical Context Value

Product Context Value

Industry Context Value

Official Constraints Context Value

Business Process Role Context Value

Supporting Role Context Value

Business Context

1..*1..*

1..*

1..*

1..*

1..*

1..*

1..*

System Capabilities Context Value1..*

1..*

1..*

1..*

1..*

1..*

1..*

1..*

Context Value

Value 1..1Meaning 1..1

0..*

0..*

0..*

0..*

Classification Scheme

Context Category 1..1Name 1..1Description 1..1Primitive type 1..1Hierarchy 1..1Owner 1..1

0..1

1..*

0..1

1..*

Registry Class

Unique Identifier 1..1Version 1..1Dictionary EntryName 1..1Definition 1..1Usage Rule 0..*

The Storage Metamodel - Context Definition


Association Information

Association Type 1..1Association Name 1..1Association Description 1..1Association Multiplicity 1..1Start Date 1..1End Date 0..1Comment 0..*

Replacement Information

Replacement Description 1..1Replacement Date 1..1

Status Information

Status 1..1Start Date 1..1Reason 0..1Reference 0..*Comment 0..*

Administrative Information

Registrar 1..1Registration Authority 1..1Submitting Organisation 1..1

Change History

Change Type 1..1Change Date 1..1Change Description 1..1Request By 1..1Request Date 1..1Comment 0..*Reference 0..*

Representation Information

Representation Syntax 1..1Representation 1..1Constraint 0..*

Descriptive Information

Comments 0..*Reference Document 0..*Acronym 0..*Keyword 0..*

Registry Class

Unique Identifier 1..1Version 1..1Dictionary EntryName 1..1Definition 1..1Usage Rule 0..*

0..*0..*

Associated To

0..*

0..10..1

Replaced by0..1

0..1

0..1

Has As Previous Version

0..1

1..*1..*

11

1..*1..*

0..*0..*

0..10..1

Core Component

Business Information Entity (BIE)

Business Context

Data Type

The StorageMetamodel –CCTS Metadata



Where 11179/Core Components Methodology is Being Used

• Basis for Emerging Business Standards– United Nations CEFACT XML, EDI, OO– ANSI ASC X12 XML– OAG OO– OASIS UBL

• Basis for various Federal XML Efforts– NARA Transfer Schema

• With XSLT to METS Schema– SBA Schema Initiatives– FEA Schema– T-REX Schema– Various EPA Schema– Federal & Agency XML Naming and Design Rules– Federal Schema Best Practices– DON XML

• Basis for Data Reference Model piece of FEA• Basis for ebXML Registries• Basis for EPA EDR & DON XML Registry Requirements


Agenda

• ebXML Overview• The ebXML Registry Concept• ebXML Core Components

• SummarySummary


Summary

• ebXML provides a flexible framework for eBusiness information storage, management, and exchange

• ebXML semantic content metadata consists of that required by the RIM and CCTS

• The ebXML registry is at the heart of the architecture

• The ebXML registry provides the mechanism for capturing and managing the content


Summary

• ISO 11179 provides a mechanism for expressing data and metadata consistently across communities

• The ebXML Core Components methodology provides the mechanism for ensuring the semantic content is consistent across users

• ebXML semantic content management provides VCS based approach to consistent registration and metadata standardization for all types of artifacts – to include data and document centric

• A number of key federal and VCS initiatives are basing their work on ebXML/ISO 11179


A Final Thought

Voluntary Consensus Standards are Hard

But in the long run the mission suffers because data is not interoperable and mission resources are diverted to data transformations

Its easy to justify not using them for mission requirements

Especially those that cross functional boundaries


For More Information

• For ebXML: http://www.ebxml.org• For ebXML Registry: http://www.oasis-open.org

• For ebXML Core Components:– <chair: [email protected]>– <editor: [email protected]>

• For ISO 11179 & Metadata Registries– Bruce Bargmeyer - [email protected]

• For other referenced standards work: [email protected]

• For referenced Federal Initiatives using 11179/ebXML: – [email protected]– [email protected]– [email protected]– [email protected]

• For OASIS UBL TC– http://www.oasis-open.org