As developer of the open standard interface DATEX II for the traffic event data of the Open Data Hub, I would like to have some adjustments on the traffic event data collection flow

[rcavaliere]

In order to correctly map the data into DATEX II, following aspects need to be adjusted:

• event data should have a version field, so to underline if the event record is related to an update of the original event record
• we need an API call to provide just the currently active event data, in the sense that I would like to see only the events that are valid now (i.e. current dateTime is within start and end time; if no end time is set, dateTime should be only greater than start time)
• the format of fields dateTime is not the same. For example publisherDateTime and transactionTime are formatted differently. Please let's provide them in the same format

[rcavaliere]

@clezag in relation to this development, I also received this contribution from the supplier about how their development contribution should be then hosted in our infrastructure. What do you say, do you see critical things there?

Architettura nodo Datex - Bolzano.pdf - Rev. 1.pdf

[clezag]

For version tag: If there are any changes to an event with the same UUID, increment version number.

The date format of the metadatafield can remain as is, because it's a string taken directly from the data provider and we don't want to add custom code to change the format