Kuala Lumpur

1
UNLK and eUNLK - UNeDocs Paperless Trade
Migration Michael Dill, GEFEG Chair,
UN/CEFACT/TBG2 Digital Paper Work
Group Co-Leader UNeDocs Project HoD Germany for
ISO TC154 Co-Editor CEFACT Core Component
Library EDIFICE representative to UN/CEFACT/TBG17

• What is ebXML?

2
Migration to eDocs

• from UNLayout Key to its successor UNeDocs
• Why?
• Starting position and new requirements
• Data model and eLayout
• Specific forms and paper aspects
• The standard gap

3
UNLK UN/ECE Rec. 1The unsung Global Hero

• First published 1973
• Flexible aligned data presentation which has
  become the de facto standard for the majority of
  international trade documents
• Foundation for International transport
  conventions e.g. Maritime B/L (ICS), Airwaybill
  (IATA), Road CMR (IRU), Rail CIM (UIC) etc.
• Foundation of Customs and other Regulatory
  Procedures e.g SAD, Phyto-Sanitary Certificates,
  Cert of Origins etc.
• Hundreds of document formats based on UNLK across
  trade, transport, finance, customs, insurance,
  inspection etc.
• TDED (ISO 7372), box completion guidelines

4
UN Layout Key
Cross-Sector Transaction Data
Sector Specific Detail e.g. order line items,
goods items ...
Document Function Specific
5
Starting position

• UN Layout Keys and UN Trade Data Element
  Directory
• UNECE pilot project UNeDocs
• EDIFACT Guidelines for e.g. SAD
• UN Set of aligned documents
• SITPROs UK national Implementation of UNLK
• World Customs Data Model V1

6
New environment

• Core Components as a semantic driven and syntax
  independent modelling methodology released
• Core Components became mandatory for CEFACT
  members and modelling approaches mandatory for
  some Governments
• CEFACT and UBL XML Naming rules (drafts)
• Core Component compliant TDED 2005 released
• First drafts of a CEFACT Library
• Technology standards, e.g. W3C XML schema, XSLT,
  FO, xForms, and products using them

7
Experiences

• UML, Core Component and eLayout experiences with
  the UNECE pilot and WCO data models
• Results of the pilot support from Adobe and
  Microsoft
• Contributions to the development of eLayouts,
  Core Components and XML schema for OASIS UBL
• Other document oriented projects, e.g. Bolero

8
UNeDocs Wishlist

• Support for presentation of eForms
• Maintains print format capabilities
• Links to electronic data exchanges
• Updated to reflect current global trade practices
• Core Component aware
• Support for multilingual aspects
• Webservice support
• Integration of the legacy EDI and XML world

9
The Standards Map
CCTS (ISO 15000-5), UMM eUNLK TS
CC Library, UNTDED (ISO 7372)
Contextualised Data Models eUNLK Meta eForms
NDR XSD, EDIFACT instance production rules NDR eUNLK instance production rules
XSD, EDIFACT Migs FO, Stylesheets, Others

CEFACT Registry
10
UNeDocs Data Models

• Just apply the existing standards
• Development of Core Component data models, use of
  the released CEFACT Core Component Library, XSD
  schema auto generation, mapping to EDI
  Guidelines,
• Development of methodologies for context,
  Implementation Guidelines, reuse and
  extensibility, maintenance etc.

11
The Standards Map
CCTS (ISO 15000-5), UMM eUNLK TS
CC Library, UNTDED (ISO 7372)
Contextualised Data Models eUNLK Meta eForms
NDR XSD, EDIFACT instance production rules NDR eUNLK instance production rules
XSD, EDIFACT Migs FO, Stylesheets, Others

CEFACT Registry
12
UN eLayout key

• Paper and form specifics
• Missing syntax independent eLayout standards
• The eLayouts have to meet Conventions,
  Regulations (set up by states) and Traditions
  not vice versa

13
Some form aspects A Form has...
layout data
semantic content
medium
fill-in data
background master data
14
The old fashioned paper form

• knows different sizes and formats (letter, A4)
• knows continuing pages, a backside and splitting
  of data
• layout elements may have a semantic meaning
  (colours)
• has background master data (titles, standing
  clauses, box completion guidelines, watermarks,
  holograms), even multilingual
• likes clear names
• is flat and hides the deeper structuring of data
• is flexible, simple and allows different data in
  a box
• may allow annotations and non-requested data

15
Missing link eLayout Core Components

• Example the change of a name in a data model
  results in the change of an auto generated XML
  schema. How to organize the same mechanism for
  e.g. a stylesheet?
• Other requirements administrative and
  maintenance data
• -gt encourage research, solution provider support
  and set up a standard joint working group with ISO