Upload
others
View
13
Download
0
Embed Size (px)
Citation preview
DATEX II User Forum – Dublin – 13&14 September 2016
DATEX II PROFILING AND TESTING IN THE CONTEXT OF THE EC DELEGATED REGULATION REQUIREMENTS David König,
AustriaTech
13th September,
DATEX II User Forum Dublin
DATEX II User Forum – Dublin – 13&14 September 2016
TABLE OF CONTENT
Background / Motivation
The Need – DATEX II use in the corridors (CROCODILE approach)
Testing and Validating DATEX II profiles in the context of the delegated regulations
Testframework / Status
Open Questions
DATEX II User Forum – Dublin – 13&14 September 2016
BACKGROUND – DELEGATED REGULATIONS
General Requirements – Delegated Regulations (Priority Actions a-f)
DATEX II User Forum – Dublin – 13&14 September 2016
DATEX II IN THE CORRIDOR (PROFILING)
Project CROCODILE • Project partners: Austria, Cyprus, Czechia, Germany, Greece,
Italy, Poland, Romania, Slovenia
Cooperation towards the fulfilment of the ITS Directive: • Data Exchange based on needs of the ITS Directive • Using DATEX II • Focus on Priority Action c (safety critical information) and e
(truck parking information) fulfilling minimum set of data • Resulting in real deployments within the CROCODILE
corridor
DATEX II User Forum – Dublin – 13&14 September 2016
DATEX II IN THE CROCODILE CORRIDOR
Status DATEX II in the corridors:
• Currently the CROCODILE Member States are on a different level of DATEX II usage
• No single Member State has a final solution for cross-border data exchange up to now.
Therefore CROCODILE agreed on a common way forward to achieve data exchange based on DATEX II
DATEX II User Forum – Dublin – 13&14 September 2016
APPROACH TO DATEX II BASED CROCODILE DATA EXCHANGE • Based on the results of the data availability
survey decision on DATEXII considering SRTI and truck parking data exchange
• There will be NO new DATEXII profile generated development of a middleware specification for defining common minimum set of data elements!
• Status-survey on implemented/planned/considered/not planned SRTI related attributes/enum types addressing all CROCODILE DATEX II WG members
DATEX II User Forum – Dublin – 13&14 September 2016
CROCODILE SPECIFICATION APPROACH TOWARDS SRTI MINIMUM PROFILE
DATEX II User Forum – Dublin – 13&14 September 2016
CROCODILE MIDDLEWARE SPECIFICATION
• Crocodile based Middleware specification for exchanging DATEXII based SRTI-messages (Priority Action c – Safety related traffic information)
DATEX II User Forum – Dublin – 13&14 September 2016
DATEX II – REFERENCE AND VALIDATION (TESTCENTER)
DATEX II Testcenter – the Common Facilitator • Online, web-based service for testing individual DATEX II profiles against predefined validation
rules (focus on Priority actions b,c and e) • Common Work done within the DATEX II project, within Activity 1 – User support • Wherever available: graphical user interfaces: e.g. mapping of D2 content, • Profiles are able to be tested on a voluntarily and anonymously basis by DATEX II users (e.g. road
operators) • Data Handling - Process of Verification + Validation: 1. User-Registration 2. D2 XML File Upload and XML Parsing 3. Validation report generation + Download of the report
DATEX II User Forum – Dublin – 13&14 September 2016
DATEX II – TESTCENTER FRAMEWORK Validation Process (Flow diagram) 1. User registration 2. DII profile Upload by the User (e.g. Member
state) 3. Format verfication (preparsing XML) 4. Provision of validation rules (based on
minimum required DII elements describing Priority actions b, c, e
5. Main profile validation/XML parsing procedure, generation of Log-Files
6. Generation of the Final, Downloadable Validation Report
7. End of the Validation process
DII Profile Validation Process
DII Testcenter Environment
Validation Rules
Member State Profile / Partner
(.XML)
User Registration / XML - File Upload
Profile Validation / XML Parser
Valid?
Match?
User registration and Format Verification
Check if Uploaded File is in a machine-
readable Format (Preparsing)
Yes
No
DII reference schema definition (.XSD)
Minimum required D2 data spec. on Priority actions b, c, e
Validation Report
Log-Files
Yes
No
DATEX II User Forum – Dublin – 13&14 September 2016
DATEX II TESTCENTER - STATUS
Status • Provided in the first step to DATEX II project partners/ associated partners (e.g. road operators)
for testing and commitment purposes
• Currently developing first test/validation-routines
• Starting with Priority action c validation (based on the common Profiling guidance and documentation inputs for SRTI, elaborated by the DATEX II community, CROCODILE project group and the TISA group)
Future • Integrating further priority actions as references to be tested against (b-RTTI, and e-Truck
Parking)
• Elaborating Minimum set of data fulfilling profiling requirements of Priority Action b
• Additionally GIS profiling, covering for static data exchange !?(Delegated Regulation 2015/962, RTTI)
• For ITP the basis for data exchange is formed by the EC profile for static data (minimum requirements resulting from Delegated Regulation 885/2013)
DATEX II User Forum – Dublin – 13&14 September 2016
THANK YOU FOR YOUR ATTENTION!
David König,
AustriaTech,
DUF Dublin, 13th-14th September
Open Questions!?