Pharos XMLEDI Project Transformation from EDIFACT to XML

1
Pharos XML/EDI ProjectTransformation from
EDIFACT to XML

• 2000-06-06

2
Objectives

• To demonstrate EDI by using the XML language
• To transform an EDIFACT message type to a XML DTD
  and XML Schema
• Store the XML Schema in the MS BizTalk Repository
• Produce a transformation method guidelines
• Present the experiences to
• UN/CEFACT/EEG2 - Transport
• EWG/D4 - Transport group
• ITIGG - International Transport Implementation
  Guidelines Group
• UN/CEFACT/TMWG - Techniques and Methodologies
  Working Group
• ebXML-Initiative, Oasis and UN/CEFACT/TMWG

3
EDIFACT to XML Transformations
EDIFACTMessage Type
EDIFACTMessage Types
EDIFACTMessage Types
BusinessModels
TransportDomainModel UML
XML/DTD
MessageDesigner
EDIFACTMessage Types
UMLMessage Types
XML Schema
4
(No Transcript)
5

6
Business Model Example
7
Multiple Business Models
8
UML Message Type Example
Booking Order
1..1
1..1
1..1
1..1
1..1
1..1
contain
contain
0..
0..
0..
0..
Driver
Equipment
1..1
1..1
1..1
1..1
contain
contain
0..
0..
0..
0..
0..
0..
Attached Equipment
Consignments
9
From UML to XML
10
Domain Model - Main Classes
11
TRIM Transport Reference Information
Modelhttp//noemie.informatics.sintef.no/trim
12
Tools

• UML Modelling Tools
• Rational Rose 2000
• PowerDesigner 7, imports the Rose 2000 repository
  
• XML Tools
• PowerDesigner generates MMF - Message Model File
• MessageDesigner transforms MMF to XML/DTD
• MessageDesigner transforms MMF to XML Schema
• XMLSpy, editor for XML messages

13
Conclusions

• The method has been successfully tested
• Can be reused on other message types
• Reasonable amount of resources for UML modeling
• The transformation can be partly automated
• The method can be applied on other standards
  (X12, SWIFT, etc)

14
Further Work

• Test the method on other message types
• Adjust the method with recommendations from the
  ebXML project
• Improve the XML generator tool with functions for
  message layout forms
• Develop a transport domain model