ean.ucc xml implementation of eb xml

EAN.UCC

Implementation of

ebXML

Pere Rosell, AECOC - EAN Spain

Melanie Kudela, UCC

May 2002

©2002 Uniform Code Council, Inc. and EAN International

2

• ebXML TRP Implementation Guidelines

• Core and Extended Component Strategy

• The Basic Building Blocks

• ebXML Context Classification

• EAN.UCC ContextProcess Example

• EAN.UCC ContextProduct Example

• The Big Picture

• Our learning

• What ebXML should do

EAN.UCC XML Implementation of ebXML

EAN.UCC Global Standard Management Process

EAN.UCC ebMethodology


3

EAN International member countries

USA and Canada are covered by UCC

Manufacturer numbers are allocated ona direct basis by EAN International and UCC

EAN·UCC: Working together around the world


4

EAN·UCC Global Standard Management Process


5

Customer driven. Transparency/visibility at all stages in the process. One single repository of standards. Presenting a single face to EAN.UCC customers. Designed jointly by EAN and UCC. Central Operations – a “virtual” office on a worldwide

scale.

GSMP Principles


6

Business Impact and Benefits

• An open and visible process, encouraging global participation.

• A significantly reduced standards development cycle. • Standards based on global consensus.• A single methodology to enable consistent standards

development, reusability, and interoperability.• A responsive and robust process that delivers single

solutions with multi-sector global applicability.


7

Global Standards Process OverviewGlobal Standards Process Overview

WE NEED A METHODOLOGY TO MAKE IT RUN!WE NEED A METHODOLOGY TO MAKE IT RUN!


8

EAN.UCC Core Process Suite

UML (UMM) Business DomainExperts

Choreography Business Context

Syntax Instantiations

EAN·UCC ebMethodology ScopeEAN·UCC ebMethodology Scope


9

EAN·UCC ebMethodology ScopeEAN·UCC ebMethodology Scope


10

ebXML TRP Implementation Guidelines


11

Communications Protocol Envelope (HTTP, SMTP, etc.)

SOAP with Attachments MIME envelope

MIME Part

SOAP -ENV: Envelope

SOAP -ENV: Header

eb:MessageHeader

eb:Error

eb:Etc.

other:Etc.

eb:Manifest

eb:Etc.

other:Etc

MIME Part(s)h

SOAP -ENV: Body

Payload

Container(s)

Header Container

Message Package

Message Layer

Transaction

Command

Document Layer

Item

Party

Order

other …

Message Layer

Transaction

Command

Document Layer

Item

Party

Order

other … EAN.UCC Payload(s)



12


What we learned:• We can make it work and it works• ebXML TRP definition is still too open• Nobody has experience on TRP implementation• No software can support the full recommendation• There is a lack of interoperability

What we ask from ebXML:• We need to push for implementation• We need stability to start our implementations• Try to be more precise in the content of the documents• Develop an interoperability set of tests


13

Core Component Strategy

The Basic Building Blocks


14Choreography (BPSS)

Identify Core Components

Buyer Order Reference. Details ABIE Definition:Reference details assigned by a buyer to an orderUses: Reference. Details ACC (999999) Definition:Identification and date of reference of a document

Reference. Identifier (999998) Not usedReference. Date Time (999997) Not usedReference. Identifier (999998) Not usedReference. Date Time (999997)Used

Consignment. Number BBIE Definition: Identification of a consignment Uses: Consignment Identifier BCC (999996)Definition: Identification of a consignment


Reference. Identifier (999998)UsedReference. Date Time (999997)Used


Agree Core Process Model


Reference. Identifier (999998)UsedReference. Date Time (999997)UsedReference. Identifier (999998) Not UsedReference. Date Time (999997)Not Used


Model business processes using UML (UMM)


15

EAN.UCC Extended Types = ebXML Core Component Type

A datatype that hasno business meaning on its own.

ebXML Core Component Type


16

ebXML Core Component

EAN.UCC Components = ebXML Core Components

• A semantically correct and meaningful building block.

• Describes a specific concept.

<xsd:element name="document" type="DocumentType" abstract="true"/>……

<xsd:complexType name="DocumentType" abstract="true"><xsd:attribute name="contentVersion" type="VersionType" use="optional" fixed="1.0"/><xsd:attribute name="documentStructureVersion" type="VersionType" use="optional" fixed="1.0"/><xsd:attribute name="lastUpdateDate" type="xsd:date" use="optional"/><xsd:attributeGroup ref="CreationAttributeGroupType"/><xsd:attribute name="documentStatus" type="DocumentStatusListType" use="required"/>

</xsd:complexType>


17

ebXML Basic Business Information Entity

<xsd:element name="buyer" type="PartyIdentificationType"/>

<xsd:complexType name="PartyIdentificationType">

<xsd:sequence>

<xsd:choice>

<xsd:element name="gln" type="GlobalLocationNumberType"/>

<xsd:element name="alternatePartyIdentification" type="AlternatePartyIdentificationType"/>

</xsd:choice>

<xsd:element name="additionalPartyIdentification" type="AlternatePartyIdentificationType" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:complexType>

BIE CC

<xsd:element name=“seller" type="PartyIdentificationType"/>


18

Core Component Strategy

ebXML Context Classification


19

ebXML Context Classification

ContextRegion ContextProcess

ContextProduct ContextIndustry

ContextLegislative

SystemCapabilitiesContext SupportingRoleContext

New Context Classification


20

Extended Process ModelNew Context Classification

ContextRegion ContextProcess

ContextProduct ContextIndustry

ContextLegislative

SystemCapabilitiesContext SupportingRoleContext


Reference. Identifier (999998)UsedReference. Date Time (999997)UsedReference. Identifier (999998) Not UsedReference. Date Time (999997)Not Used


Identify New and Extended Components


21

Extensions explained

Managed by Business Context

Extension = Re-usable Component + Unique Requirements

AddressBillToAddress

ShipToAddress

AddressUK

Reusability

<role context=“Buyer”/”Seller”>

Extension

<GeographicContext=UK>

Used as

Used as


22

{Core} Core Components

{Extended} Core Components

{Context}

XSD schema {core}

XSD schema {ext}

XSD SchemaUML ebXML

Bringing the Parts Together


23

EAN.UCC ebXML ContextProcess Example

EAN.UCC Core Component used in a specific process context.

<xsd:complexType name="AbstractCommandType" abstract="true"/>…

<xsd:element name=“order" type=“OrderType“ substitutionGroup="document"/><xsd:element name="forecast" type="ForecastType" substitutionGroup="document"/><xsd:element name=“despatchAdvice" type=" DespatchAdvice Type" substitutionGroup="document"/>…

<xsd:complexType name="DocumentCommandType">

<xsd:complexContent>

<xsd:extension base="AbstractCommandType">

<xsd:sequence>

<xsd:element name="documentCommandOperand" type="DocumentCommandOperandType"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<xsd:complexType name="DocumentCommandOperandType">

<xsd:sequence>

<xsd:element ref="document" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:complexType>


24

Aggregate Business Information Entity


25

Basic and Aggregate Business Information Entity

/eanucc:order/buyer/gln*/eanucc:order/seller/gln*

/eanucc:despatchAdvice/buyer/gln*/eanucc:despatchAdvice /seller/gln*

/eanucc:forecast/buyer/gln*/eanucc:forecast /seller/gln*

* Global Location Number

Aggregate BIE CC


26

EAN.UCC ebXML ContextProduct Example

Describes those aspects of a business situation related to the goods or services being exchanged in the businessprocess.

<eanucc:order documentStatus="ORIGINAL" creationDate="2001-09-15T12:00:00"><buyer>

<gln>0012345000058</gln></buyer> …<lineItem number="1">

<netPrice><amount currencyISOcode="USD">3.00</amount>

</netPrice><requestedQuantity>1</requestedQuantity><itemIdentification>

<gtin>61414100539000</gtin><additionalItemIdentification xsi:type="fmcg:AlternateItemIdentificationType" type="COUPON_FAMILY_CODE" value="11001111"/>

</itemIdentification></lineItem>

</eanucc:order>

<eanucc:order documentStatus="ORIGINAL" creationDate="2001-09-15T12:00:00"><buyer>

<gln>0012345000058</gln></buyer> …<lineItem number="1">

<netPrice><amount currencyISOcode="USD">3.00</amount>

</netPrice><requestedQuantity>1</requestedQuantity><itemIdentification>

<gtin>61414100539000</gtin><additionalItemIdentification xsi:type=“music:AlternateItemIdentificationType" type=“MUSIC_A" value="11001111"/>

</itemIdentification></lineItem>

</eanucc:order>


27

EAN.UCC ebXML ContextProduct Example

/eanucc:order/lineItem/itemIdentification

/additionalItemIdentification

/@xsi:type="fmcg:AlternateItemIdentificationType“

/@type=“COUPON_FAMILY_CODE"

/@value ="11001111"

Where: /@xsi:type=

Fast Moving Consumer

Goods

<xsd:complexType name="AlternateItemIdentificationType">

<xsd:complexContent>

<xsd:extension base="eanucc:AlternateItemIdentificationType">

<xsd:attribute name="type" type="AlternateItemIdentificationListType" use="required"/>

<xsd:attribute name="value" type="eanucc:String1to35Type" use="required"/>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<xsd:simpleType name="AlternateItemIdentificationListType">

<xsd:restriction base="eanucc:String1to80Type">

<xsd:enumeration value="COUPON_FAMILY_CODE"/>

<xsd:enumeration value="LOTTERY_GAME_NUMBER"/>

<xsd:enumeration value="LOTTERY_PACK_BOOK_NUMBER"/>

<xsd:enumeration value="NBCA_PRODUCT_CODE"/>

<xsd:enumeration value="SUPPLIER_NUMBER"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType name="AlternateItemIdentificationListType">

<xsd:restriction base="eanucc:String1to80Type">

<xsd:enumeration value=“APPAREL_A"/>

<xsd:enumeration value="APPAREL _B"/>

<xsd:enumeration value="APPAREL _C"/>

<xsd:enumeration value="APPAREL _D"/>

<xsd:enumeration value="APPAREL _E"/>

</xsd:restriction>

</xsd:simpleType>

/eanucc:order/lineItem/itemIdentification

/additionalItemIdentification

/@xsi:type=“apparel:AlternateItemIdentificationType"

/@type=“APPAREL_A"

/@value="11001111"

Where: /@xsi:type=

APPAREL


28

The Big Picture

XSD schema {core}

XSD schema {ext}

XSD SchemaUML ebXML

Con

text

EAN.UCC GDD

Components

Components

Syntax objects

Syntax objectsCho

reog

raph

y

Business Users


29

ebXML Implementation Guidelines

What we learned:• ebXML CC definition is still too open• ebXML CC Specifications are at a conceptual level • ebXML CC models are difficult to implement• To fully realize ebXML, we need to implement BPSS and CPPA

What we ask from ebXML:• ebXML needs to specify mapping for CC to W3C XSD • ebXML should provide Technical User Guidelines• ebXML should support knowledge transfer through Birds of a Feather Meetings and developer conferences


30

Thank you for your attention

¿Are there any questions?

ean.ucc xml implementation of eb xml

Technology

used reference

date of reference

reference details

document reference

ebxml trp definition

used consignment

optional xsd

ebxml core components