belgif / thematic

ICEG: Thematic Working Groups
11 stars 5 forks source link

NETeX x SIRI compliancy #137

Open fhalin opened 1 year ago

fhalin commented 1 year ago

We see in the Vehicle Scheduling AP spec that the linking to real-time information is not covered:

image

More broadly, this NETeX spec should be compliant with the future SIRI belgian profile. Therefore, could you ensure us that:

  1. The Linked Data data model used can handle real-time data updates as required by the SIRI model
  2. The proposed standard remains compliant with the Transmodel overarching specs and, therefore, that a SIRI belgian profile will be compatible with this static data standard.
GeertThijs commented 1 year ago

It is correct that the current linked data (LD) models are about NETEX and not about SIRI. We would need to develop an additional LD model for that. That said, SIRI needs NETEX as a basis (as is mentioned in the NETEX standard and the EPIP profile on NETEX). For example, it is impossible to say that there is a delay if you do not know at what time the vehicle is intended to pass, the latter being covered by NETEX. So if the the Belgian profile of SIRI would be a LD data model, then the LD models of NETEX that we developed are a neccessity. A Belgian profile developed in XML would likewise have to take into account the XML version of NETEX. Of course, if this profile already exists we would then start from there for a LD-version, being confident that the existing profile extends NETEX. Do you have pointer to this future Belgian SIRI profile or has the work to develop it has not started yet?

fhalin commented 1 year ago

Hello @GeertThijs , Thanks for your reply. As far as I know, no one is currently taking the lead in defining a Belgian profile for SIRI. My questions are intended to clarify the consequences of adopting the proposed LD-based NETeX profile as Belgian official profile on the upcoming SIRI Belgian profile definition work.