Transcript The DATEX2 Project

VIKING Domain2
DATEX2 Workshop
in
Stockholm
7 - 8 June 2005
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
1
Agenda
Tuesday 7 June 1000 – 1700
10.00 – 11.30 Welcome and presentation of the DATEX2
project
11.30 – 12.30 Lunch
12.30 – 14.30 Presentation of the data model and data
dictionary (WP 1 and 2)
14.30 – 14.50 Coffee
14.50 – 15.30 Presentation of the data model and data
dictionary (cont.)
15.30 – 16.30 Discussion and conclusions about the data
model and data dictionary
16.30 – 17.00 Presentation of the XML schema (WP 3) and
discussion
19.00
Dinner
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
2
Wednesday 8 June 8.30 – 12.30
08.30 – 09.00 Presentation of the Platform Independent Model (PIM) for
data exchange (WP 4)
09.00 – 09.30 Discussion and conclusions about the PIM for data
exchange
09.30 – 10.00 Presentation of the study for Platform Specific Models
(PSM) for data exchange and “Low cost profile” (WP 4 and 5)
10.00 – 10.20 Coffee
10.20 – 10.50 Discussion and conclusions about PSM for data exchange
and “Low cost profile”
10.50 – 11.20 Presentation of the study for migration (WP 6) and
discussion
11.20 – 12.30 Concluding discussions and harmonising of Viking
viewpoints
12.30
Close of workshop and lunch
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
3
Background
• Standardisation – CEN ENV13106
and ENV13777
• DATEX MoU – organisation –
GAS,SMC,TC – User Fora
• EC – role
• EG-Projects - members
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
4
The DATEX2 Project
•
•
•
•
•
•
•
Tender procedures
Organisation
Work packages
Progress
Status today
TC´s role
Ongoing work
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
5
DATEX2 Project - Organisation
• The European Commission - owner
of the study,The DATEX2 Project
finances and signs the contract.
• The DATEX Technical Committee
(TC) - supports the Commission in
the programme definition and the
technical aspects of the study.
• The contractor - a consortium of
experts led by Faber Maunsell.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
6
2003
2004
EC initiative for a DATEX project
Technical specification
Preannouncment for a DATEX project
Invitation to tender
Start of the project
FM consortium – 6 wp
TC monitoring
2005
End of the DATEX2 project
TC continues the work
2006
2007
Interoperability between a RP and a LCP
Migration
Demonstrator – ITS Barcelona 2006
Testing and validation
Released documents
DATEX2 implementations
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
7
DATEX2 Project
•
•
•
•
•
•
WP1: Data Model
WP2: Data dictionary
WP3: XML schema
WP4: Exchange model and PSM study
WP5: Low cost profile
WP6: Migration
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
8
WP1: Data Model
• Content Platform Independent Model
(PIM)
• Described in UML
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
9
WP2: Data dictionary
• Revision of the current DATEX Data
Dictionary (ENV 13106)
• Requirements from EC - DATEX TC
and CEN TC278 WG8
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
10
WP3: XML schema
• Derived from the data model
• Generated by software
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
11
WP4: Exchange model and PSM study
• Exchange Platform Independent
Model (PIM)
• Exchange Platform Specific Model
(PSM) study
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
12
WP5: Low cost profile
• Simple and low cost
• Minimum implementation and link
establishment complexity
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
13
WP6: Migration
• Migration path from old Datex
• Backwards compatibility issues
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
14
DATEX Technical Committee
Strategical road map for DATEX2
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
15
DATEX Objectives
Facilitate the widespread exchange
of travel information in EU through
the use of common standards and
best practice for both public-sector
and commercial interests and
ensure there are mechanisms in
place to make them happen.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
16
The way to the market
1. Finalize the DATEX2 project
2. Produce usable DATEX2 documents
(DATEX 2.0 specifications)
– PIM Data Model incl. Data Dictionary
– PIM Data Exchange
– XML-schema
– PSM Data Exchange using HTTP, XML
and Web Services
– ”Low cost profile” (subset of ”Regular
profile”)
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
17
The way to the market
Cont.
3. Implementation of demonstrators
4. Evaluation of demonstrators
5. Produce DATEX 2.1 specifications
for the market
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
18
The way to the market
Cont.
6. Organize and implement DATEX
support
7. Start the standardisation process in
CEN
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
19
The way to the market
Comments:
• ”Low cost profile” is a true subset of
”Regular profile”
• Migration is a matter of normal
upgrading or implementation of a
new system and is handled by the
users of DATEX
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
20
Strategical road map for DATEX2
End
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
21
Relationship with Other Initiatives
– ISO TC204 WG9.1
• Should be considered in modelling activity
– CENTRICO OTAP
• The initial phase of OTAP should be a simple form
of the interface defined in this standard.
• The Platform Independent Models used in OTAP
should be compatible with the models defined in
this standard
– Trident
• Experience in the PT domain is useful
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
22
Structure
• Divide Project into:
– Platform Independent Model (PIM)
• Independent of the implementation technology
• Universal across all implementations
– Platform Specific Model (PSM)
• Specific to the implementation technology
• One model for each technology
• New models added as new technologies become
available
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
23
The DATEX Project
Methodology for Development of
Static UML Information Models
Location Referencing
(on-the-fly referencing ?)
Static UML Information Data Models
(DATEX Data Object Models)
Data Dictionary
Universal models
independent of Technology
(see UML mapping
restrictions)
Input from
ISO
TC204
UML Static Models of Objects
(defining relationships,
attributes but no methods)
(Data Registry ISO 14817 ?)
Platform
Independent
Model
(PIM)
Exchange Mechanism / Protocol
(Interface Definition - technology Independent)
Various levels of sophistication
(simplest being OTAP)
Modelling/Definition of I/F objects
& methods (+ sequence, state,
collaboration diagrams)
INTERFACE
INTERFACE
UML Mapping requirements/restrictions to implementation
technologies
Platform
Specific
Model
(PSM)
JAVA RMI
Implementation
EDIFACT
(FTP - ISDN)
Implementation
XML (HTTP)
Implementation
XML Schema
CORBA
Implementation
IDL
7-8 June 2005
PIM
Testing /
Certification
Strategy
(Independent
of
technology)
SOAP
(XML - HTTP)
Implementation
PSM
Testing /
Certification
Strategy
(Specific to
Technology)
???
EDIFACT
(FTP - HTTP))
Implementation
XML Schema
Viking Domain 2 DATEX2 Workshop in Stockholm
24
Platform Independent Model (PIM)
• Methodology for developing Static Information
Publication Models
• Static UML Information Publication Models
(DATEX Data Objects)
• Location Referencing
• Data Dictionary
• Exchange Mechanism / Protocol (PIM interface)
• PIM Testing/Certification Strategy
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
25
Platform Specific Model (PSM)
• UML Mapping Requirements/Restrictions to
specific technology
• Technology Specific Model (one for each
technology)
• PSM Testing/Certification Strategy (one for
each technology)
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
26
PIM - 1
• Static UML Information Publication Models
(DATEX Data Objects)
– What Data Objects are to be modelled?
• ACC, INC, RMK, LOS, TTM, AVS, CTT, FLO, IVD etc.
• new object types e.g. both fixed and moving images
– All attributes in Data Dictionary or only those known
to be used?
– Multimodality (PT) ?
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
27
PIM - 2
• Location Referencing
– What system? Compare options
• AlertC Location Code
• TPEGLoc
• ....
– Extendable to PT ?
– On-the-fly referencing ?
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
28
PIM - 3
• Data Dictionary
– Static (frozen) or dynamic dictionary?
– Application to Data Registry (ISO 14817)
– Data Directory functions ?
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
29
PIM - 4
• Exchange Mechanism / Protocol
– Various levels of sophistication
– Simplest being initial like OTAP
– Objects with behaviour (methods)
– Sequence, state and collaboration diagrams
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
30
PIM - 5
• PIM Testing/Certification Strategy
– Defined testing/certification strategy for each level of
sophistication of the interface
– Is independent of the implementation technology
– Will be used as basis for PSM testing/certification
strategies
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
31
PSM - 1
• UML Mapping Requirements/Restrictions
– Each technology may impose restrictions on validity
of UML models, e.g.
• UML Profile for CORBA
• XMI
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
32
PSM - 2
• Technology Specific Model
– Each technology will have its own model defined
– Will define how the Interface specified in the PIM is
mapped on to the specific technology, e.g.
• IDL for CORBA
• XML Schema for XML over HTTP
– Each model will define link management appropriate
to the technology
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
33
PSM - 3
• PSM Testing/Certification Strategy
– Specific testing/certification strategy for each
implementation technology
– Defined testing/certification strategy for each level of
sophistication of the interface
– PIM Testing/Certification Strategy will be used as a
basis
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
34
WP 1
•
•
•
•
•
•
•
Type of model
MDA
Deliverables
Constrains report
Tools
Model content
Detail study of the model
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
35
Type of model
• UML model
• Model driven Architecture (MDA)
• It is a content model for exchange of traffic
information
– It’s not a data model that you put in a database
– It’s not a model that you need to have in a TIC
system.
• In the model we describe the information
and how it relates to other information.
• It’s the content/payload
• Independent of technology
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
36
MDA
• Model Driven Architecture
• Defined by OMG (Object
Management Group)
• PIM (Platform Independent Model)
• PSM (Platform Specific Model)
• A PIM can be realized in more then
one PSM.
• DATEX1 technology dependent
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
37
Deliverables
• Constrains report
–
–
–
–
–
–
Notation
Rules and UML constrains
Naming conventions
Extension mechanisms
Tagged values
Data types
• UML model
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
38
Requirements
• Input from
– DATEX1
– TRIDENT
– OTAP
– National extensions
– Etc
• All inclusion option was chosen
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
39
Data types
• Generic data type are defined like Integer,
String etc.
• Support that you can create your own
specific data types. Those have to be
derived from a Generic data type.
• E.g.
– Old Attribute SpeedInMetersPerSecond
– Now
• A data type called MetersPerSecond
• An attribute called Speed with data type
MetersPerSecond
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
40
Tools
• Enterprise Architect,
http://www.sparxsystems.com.au/
• Cheap 200€
• Free viewer
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
41
Model content
• Four high level packages
– General
– Payload (WP1)
– Exchange (WP4)
– Management (?)
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
42
Model content
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
43
General
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
44
Payload
cd Payload
Payload
«abstract»
Publication::
Publication
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
45
Payload Publications
cd Publication
MassDataPublication::
MassDataPublication
ElaboratedDataPublication::
ElaboratedDataPublication
Netw orkView Publication::
Netw orkView Publication
FilterPublication::
FilterPublication
7-8 June 2005
CataloguePublication::
CataloguePublication
TrafficView Publication::
TrafficView Publication
SituationPublication::
SituationPublication
«abstract»
Publication
LocationTablePublication::
LocationTablePublication
MeasurementTablePublication::
MeasurementTablePublication
Viking Domain 2 DATEX2 Workshop in Stockholm
46
Publications
• Show all publications
• Focus on
– SituationPublication
– MassDataPublication
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
47
DATEX2 vs DATEX1
•
•
•
•
•
•
•
•
All is identified with GUID
Not bound to AlertC LocationCode
TPEGLoc support
X and Y support
No Trigrams
A real data model
Hierarchical “attributes”
Split in TrafficElements and
OperatorAction
• Old DOB’s have a separate definition of
what it contains.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
48
Summary
• Large model – union
• Not finished, but a good starting
point
• Refinement of traffic data?
• Core model and national extensions?
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
49
WP 2
• Role
• Tools
• Format
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
50
Role
• Same function as the old Data
Dictionary
• Include all definitions
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
51
Tools
• Definitions are in the PIM UML
model, as tagged values.
• The tag “Definition”
• The dictionary is created with a tool
that extracts all definitions and puts
those in a Word document.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
52
More definitions
• Not all definitions are in the UML
model
– Vehicle classification
– Speed classification
– etc
– Other describing text
• Currently no domain ranges
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
53
Summary
• The final document will be created
when the model is finished.
• Tight connection to the model
• National DD are still needed for
translation
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
54
WP 3
•
•
•
•
•
•
•
Deliverables
The role of the XML Schema
The process
The tool
Demo create a Schema
Demo create a XML document
Summary
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
55
Deliverables
• Word document describing the
process and the rules
• XSD conversion tool
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
56
The role of the XML Schema
• XSD
• The XML Schema will be the base in
all PSM implementations.
• Act as a specification of the protocol
• Validation
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
57
The process
DATEX 2
UML Model
saved as XMI
Enterprise
Architect
DATEX 2
Conversion Tool
DATEX 2
Namespaces
&
Data Type
Transformation
7-8 June 2005
XML Schema
saved as XSD
XML Spy
saved as Config.XML
Viking Domain 2 DATEX2 Workshop in Stockholm
58
The tool
• Developed in C# (MS.Net)
• Open Source
• The tool reads an XMI file and
creates an XSD file.
• XMI (OMG specification, how to store
an UML model in XML)
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
59
Demo
• Create a Schema
• Create a XML document
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
60
Summary
• Very simple to create a XML Schema
from the UML model.
• The tool also helps validating the
UML model.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
61
WP 4
•
•
•
•
Background
Deliverables
Deliverable modes
Define the Exchange package
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
62
Background
• At a PIM level define the exchange
mechanism
• The dynamic features
• Without choosing technology
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
63
Deliverables
• UML model
– Sequence diagrams
– Exchange package
• Word document
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
64
The document
•
•
•
•
System overview
Defines Actors
Use cases
Deliverable modes
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
65
The document
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
66
Use cases
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
67
Exchange
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
68
Sequence diagrams
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
69
Summary
• Sometimes handles internal things
• A lot of optional things
• A more clear definition of the
interface is needed.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
70
WP4 PSM study
• Background
• Deliverables
• Summary
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
71
Background
• The study has, evaluate and
proposed the best suited technology
for the “regular profile”
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
72
Deliverable
• Document
• A workshop
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
73
Document
Possible Candidates
•
Transport Control Protocol / Internet Protocol
–
•
TCP/IP is the basis for all following communication protocols. In addition it
can be used on its own and is known as socket connection. It is a powerful
and flexible platform, but programming TCP/IP as it is can be a complex job.
File Transfer Protocol
–
•
FTP is a simple and widely used protocol. Its functionality is limited though.
Hyper Text Transfer Protocol
–
•
HTTP is a simple and standardised protocol. Its functionality is limited and
additionally leads to some server overhead.
Remote Method Invocation
–
•
Java RMI is relatively simple, powerful and flexible. It uses HTTP as
communication medium. It is pure Java so it inherits all advantages and
disadvantages of Java.
Common Object Request Broker Architecture
–
•
CORBA is powerful and flexible. Its complexity is a big disadvantage.
Web Service
–
Web services are software-powered resources or functional components
whose capabilities can be accessed via internet. Standards-based web
services use XML to interact with each other, which allows them to link up
on demand. Web Services use HTTP as communication medium.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
74
Study criteria
• Referring to ISO 9126
• Functionality, performance, usability
etc.
• Out comes a matrix
• The winner was…
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
75
Outcome from workshop
• Workshop in January 2005
• The workshop agreed on technology
• Web Services, HTTP, XML
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
76
Summary
• Web services the best suited
technology for Datex2.
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
77
WP 5
• Background
• Deliverables
• Summary
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
78
Background
• Low cost profile
• OTAP inspired
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
79
Deliverable
• A short document
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
80
Basic idea
•
•
•
•
•
Subset of regular profile
Client requests only
No subscription management
All data sent every time
Cheap and easy to implement
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
81
Summary
•
•
•
•
Ongoing project in Centrico
Looks like OTAP exchange
DATEX2 content
Compatible with Regular profile
SERTI
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
82
Conclusions and Viking statements
• Data model and Data Dictionary
– Union vs core model
– Traffic data and refinement
– Structure
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
83
Refinement chain
Data supplier
Data collection
Content provider
Service provider
Distributor
Road user
Refinement
of data
Refinement
to services
Dissemination
to road user
Presentation
and use
Main objectives:
• Traffic safety
• Availability
• Environment
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
84
Conclusions and Viking statements
• Exchange model
– Degree of refinement
– Level of standardisation
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
85
Conclusions and Viking statements
• Low cost profile
– Subset of regular profile?
– Matter of implementation?
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
86
Conclusions and Viking statements
• Migration
– Matter of implementation?
– Issue for the market and users?
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
87
Viking and DATEX2
• Swedish test implementation 2005
• Viking test sites?
– Denmark
– Finland
– Germany
– Norway
7-8 June 2005
Viking Domain 2 DATEX2 Workshop in Stockholm
88