DirectionRef vs. DestinationRef in Part 7

[DohmenClaus]

Hint/Question from Emanuel de Verdalle (email to Claus Dohmen, March 26, 2025):

Regrading SIRI-VM chapter §9 in the EU profile v1.2 document.
The element “DirectionRef” is used in the example of §9.4.1 as part of the MonitoredVehicleJourney structure.
But “DirectionRef”is not part of the table 77 in §9.2.5 describing the MonitoredVehicleJourney structure which includes “DestinationRef”.
In general the example in §9.4.1 does not seem to be aligned with the table 77 in §9.2.5. Is it a misalignement or did I missed something ?
“DirectionRef” is part of Table 42 – AffectedVehicleJourneyStructure in §7 SIRI-SX (without example), Table 56 - EstimatedVehicleJourney in §8 SIRI-ET (+ related examples) and example of §9.4.1 as part of the MonitoredVehicleJourney structure.
“DestinationRef” is only part of the Table 77 – MonitoredVehicleJourneyStructure in §9 SIRI-VM.

[rbnrtp]

MonitoredVehicleJourney has a DirectionRef and using it in VM service makes a lot of sense.
Maybe it was forgotten in the table ?
(I don't have the document at hand to check sorry)

[haeckerbaer]

I suggest to add the missing elements (from the xml example) in table 77 as follows (highlighted in yellow):

Given that LineRef is mandatory and typically coupled with DirectionRef, it makes indeed sense to include the latter. Since it is a "last minute" change I added it as optional (0:1) but I'm also ok with multiplicity 1:1. DestinationRef/Name can be left unchanged. On another note, in some cases the element descriptions don't match with the xml annotations of version 2.1.

I also want to remark that DestinationName and other related elements have xml type "NaturalLanguagePlaceNameStructure" which is more restrictive than the more common NaturalLanguageStringStructure. The former does not allow commas which are standard in stops of (at least) the german speaking regions of Europe. I therefore suggest to also change the data type of the affected elements (concerns also the other services).

[rbnrtp]

Though LineRef and DirectionRef works logically together in a MVJ, from experience, there are systems that have either no use of Direction or a very twisted use of Direction... as such, I personnaly thinks that it is better to keep DirectionRef optional.

[TuThoThai]

Group decision as of 24 Sept 2025: go with the correction suggested by the @haeckerbaer (i.e., add the lines in the table, so it fits the example).

[haeckerbaer]

(also check IDs in VM examples)

[DohmenClaus]

Kursley Alairy from CEN requested detailed information on the corretion that is needed. I send him the attached word file and some explanation.

Table_78_corrected.docx

Btw.: It is now table 78 rather than table 77 as it was in earlier comments. This is due to another issue with table numbering in the published document.

[DohmenClaus]

On March 25th Kursley Alairy from CEN wrote: "The request was not accepted. It might be easier to launch a NWI and implement the correction.”

On May 13 the SIRI group decided not to raise a separate NWI only to cover these corrections. This is to be included in the upcoming EN transformation and Version 3.0.

-> moved to milestone 3.0