Applied Technologies Group

14 May 2007 13th UN/CEFACT Plenary 1

Applied Technologies Group

Applied Technologies Group

• Chair• Mark Crawford

• Vice Chairs• Gait Boxman• Jostein Frømyr

http://www.uncefactforum.org/ATG/ATG_Home.htm


ATG Goal – Consistent Syntax TransformationATG Goal – Consistent Syntax Transformation

Type OCQ OCT PQ PT RT Oc.

<<ABIE>>

Purchase Order Details

<<BBIE>> Purchase

OrderIdentification Identifier [1..1]

<<BBIE>> Purchase

OrderCreation Date Time [0..1]

<<BBIE>> Purchase

OrderConfirmation Indicator [0..1]

<<ASBIE>> Purchase

OrderBill To Party [1..1]

<<ASBIE>> Purchase

OrderDeliver To Party [1..1]

<<ASBIE>> Purchase

OrderCosmetic Supply Item [1..n]


<<ABIE>>

Party Details

<<BBIE>> Party Identification Identifier [1..1]

<<BBIE>> Party Organization Name [0..1]


<<ABIE>>

Item DetailsCosmetic_ Supplies_

<<BBIE>>Cosmetic_

Supply_Item Identification Identifier [1..1]

<<BBIE>>Cosmetic_

Supply_Item Inventory Identifier [0..1]

<<BBIE>>Cosmetic_

Supply_Item Product Name [1..1]

<<BBIE>>Cosmetic_

Supply_Item Price Amount [0..1]

<<BBIE>>Cosmetic_

Supply_Item Ordered Quantity [1..1]


<<ABIE>>

Address DetailsPhysical_

<<BBIE>> Physical_ Address Street Name [1..1]

<<BBIE>> Physical_ Address HouseNumber_

Text[0..1]

<<BBIE>> Physical_ Address City Name [1..1]

<<BBIE>> Physical_ Address Postal Code Identifier [1..1]

<<BBIE>> Physical_ Address Zip Code Identifier [1..1]

<<ASBIE>> Party Physical Address [1..1]

<<BBIE>> Physical_ Address Country Code [1..1]

*

*

Ret

*

*

*

Rol

Context

*

*

*

*

*

*

Co

*

*

*

*

*

Cos

Ind

*

*

*

*

*

Rol

Context

*

*

*

*

*

Co

*

Cos

*

*

*

Ind

*

*

*

*

*

*

Rol

Context

*

*

*

DE

US

*

Co

*

*

*

*

*

*

Ind

*

*

*

Rol

Context

*

*

*

Cy

*

*

*

Ind

XML Schema UML Class Diagram Data Base Relations

CCTS Based Model

in specific context

Consistency in multi-syntax design and use XML NDR for Schema Development

EDI Transformation Rules UML2XML through CC Profiles UML2EDIFACT transformation

rules


ATG MandateATG Mandate

• Create and maintain the trade, business and administration document structures based on a specific technology or standard

• Design, assembly and production of syntax specific solutions based on identified business and/or technical requirements from the empowered groups of UN/CEFACT


ATG DeliverablesATG Deliverables

• Technical assessment and maintenance of syntax specific solutions through the application of Data Maintenance Requests

• A series of coherent, consistent and normalised syntax solutions that are aligned with domain reference models for publication in a designated UN/CEFACT information Registry:• UN/EDIFACT messages and their support directories• XML Schemas• UNeDocs


ATG DeliverablesATG Deliverables

• Procedures and Mechanisms for the maintenance and quality of the syntax solutions

• Appropriate technical specifications detailing the design and production rules, guidelines and checklists

• Maintenance of Recommendations/Technical Specifications in coordination with TC154• UNECE Recommendation 1 (UN Layout Key) technical

aspects• ISO 9735 - UN/EDIFACT Syntax


ATG1 EDIFACT SyntaxATG1 EDIFACT Syntax

• Purpose• Development and Maintenance of EDIFACT

syntax solutions to support UN/CEFACT work program

• Officers• Chair: Gait Boxman

• http://www.uncefactforum.org/ATG/ATG1.htm


Ongoing Work ItemOngoing Work Item

EDIFACT Data Maintenance Request (DMR) processing

• New Delhi Forum – EDIFACT Data Maintenance Request (DMR) processing – 83 Data Maintenance Requests (DMRs)

• 59 Approved• 22 Approved with Changes

• Mostly added code values

• 2 Postponed• Dublin Forum – EDIFACT Data Maintenance Request (DMR)

processing – 96 Data Maintenance Requests (DMRs)• 12 Approved• 81 Approved with changes

• Mostly added code values

• 2 Postponed at request of TBG1• 1 Withdrawn


ATG1 ProjectsATG1 Projects

• UML2EDIFACT Project• Defines methodology for transforming UN/CEFACT

Modelling Methodology (UMM) conformant UML models into the EDIFACT syntax

Project Lead Gait Boxman

Editor Open

Approval status Approved by FMG

Current ODP step 6

Anticipate Completion Dependent on requirements of TBG


ATG2 – XML SyntaxATG2 – XML Syntax

• Group Purpose• Development and maintenance of XML syntax

solutions to support UN/CEFACT work program

• Officers• Chair: Jostein Frømyr

• http://www.uncefactforum.org/ATG/ATG1.htm


Ongoing Work Item – Schema Generation

Ongoing Work Item – Schema Generation

• Updated Schema for 06B1 Common Reusable (XML Representation of CCL)1 Unqualified Data Type (Basic Data Types)8 Updated Code List Schema (used by data types)

• New Schema for 06B• Business Process Schema

21 Release Candidate schema for eTendering 1 Release Candidate schema for Cross Industry Invoice

• Supporting Schema 1 Qualified Data Type (restricts value domain)15 New Code List Schema (supporting QDTs)


XML Naming and Design Rules, V3


Specification Purpose• Consistent

transformation of Core Components

• Optimized use of XML

Project Purpose• Align with

CCTS 3.0• Drive

Convergence of SDO’s to UN/CEFACT methodology




Project Lead Mark Crawford

Editor Garret Minakawa


Current ODP step 3 (1st Working Draft)

Anticipate Completion

End of 2007 – Dependent on delivery of CCTS 3.0


Data Type LibraryData Type Library

• Data Types define the value domain for Core Components

• Specification Purpose • Create and Maintain

UN/CEFACT Data Types to support CCTS and syntax solutions

• Provide input to CCTS Project

• Develop guidance to facilitate use

• Project Purpose• Update existing catalogue• Develop responsive

maintenance procedures

Data Type (DT)

+ Data Type Term: Data Type Term+ Data Type Qualifier: String [0..*]+ Usage Rule: String [0..*]

DT Supplementary Component

+ Representation Term: Representation Term+ Property Term: String+ Primitive Type: Primitive Type+ Cardinality: Cardinality+ Default Value: String [0..1]+ Usage Rule: String [0..*]

DT Content Component

+ Property Term: String = Content {readOnly}+ Primitive Type: Primitive Type+ Usage Rule: String [0..*]

Component Restriction

+ Facet Type: String+ Facet Value: String+ Facet Language: String [0..1]

Common Information

+ Dictionary Entry Name (DEN): String+ Definition: String+ Business Term: String [0..*]

Localized Information

+ LanguageCode: LanguageCode+ Other Language DEN: String+ Other Language Definition: String+ Other Language Business Term: String [0..*]

Registry Class

+ Unique Identifier: String+ Version Identifier: String

1

1

1

1

0..*

1

1

1

0..*{only zero or onecomponentrestrictions foreach facet type}

10..*{only zero or onecomponent restrictionsfor each facet type}

1

1..*

1

1

1


Data Type LibraryData Type Library

Project Lead Jostein Frømyr

Editor Gunther Stuhec




Initial Catalogue - end of 2007 – Dependent on delivery of CCTS 3.0


Standard Business Document Header, v2


• Specification Purpose:• Improve A2A handling of

business transaction information

• Project Purpose• Update to reflect CCTS 3.0

and NDR for consistency• SBDH Scope

• Provide information about the routing and processing of the Standard Business Document

• XML Format• EDIFACT Format• Other Format

• SBDH Can be used as either

• An integral part of a Standard Business Document (e.g. either XML instance document or EDI interchange), or

• An object separate from the Standard Business Document itself




Project Lead

Editor Margaret Pemberton


Current ODP step 2 (Prepare Requirements Document and review contributions received)


2008


XML Representation of Core Components


• User Requirements• External standards organizations are interested in submitting

candidate core components to UN/CEFACT using XML• Tool vendors are interested in building support for CCTS, but

are looking for XML syntax standards for CCTS constructs• Specification Purpose

• Provide consistent pattern for XML serialization of core component artefacts

• Approach• Develop requisite UN/CEFACT XML schema modules for

defining submitting and storing Core Component Technical Specification (CCTS) constructs in XML

• compliant to the UN/CEFACT Core Components Technical Specification

• Compliant to the UN/CEFACT XML Naming and Design Rules specification




Project Lead Garret Minakawa

Editor Mark Crawford




End of 2007 – Dependent on delivery of CCTS 3.0


Other ActivitiesOther Activities

• XML Schema User Guide Template• Provide guidance for implementation and use

• Schema Generation and Testing Guidelines• Promulgating Internal Processes to a wider

audience

• Tools


ATG Driving Convergence under UN/CEFACT

ATG Driving Convergence under UN/CEFACT

• Had very successful F2F meetings• September 2006 – Waldorf, Germany• January 2007 – Washington, DC

• Representatives from 9 different SDOs/Industry Consortia + a number of US Government agencies• UBL, AIAG, STAR, ACORD, GS1, RosettaNet, OAGi, CIDX,

ANSI ASC X12• US Navy, NIST, US Treasury, US DoD

• Significant progress in achieving common understanding and alignment on XML technical issues such as:• Serialization rules• Customization• Code Lists


Issues & Resource Requirements


• Internal tools to support deliverables• XML Schema Generation Tool• XML Schema Validation Tool• XML Schema NDR Validation Tool

• Integration of Tools with UN/CEFACT Registry• Collaboration Tool to facilitate work• Better and more flexible list serve tool• Need secretariat support for ATG administration

responsibilities• Web Site/Collaboration tool set up and maintenance• Ongoing administrative requirements




• Participation Issues• 20 Active Members• 88 Virtual Members• Strong Engagement From

• Europe and North America• Service Provider participation

• Need Broader Engagement From• Member countries• Key sectors

Applied Technologies Group

Documents

Transcript of Applied Technologies Group