ServiceJourney has JourneyPatternRef, shouldn't this be ServiceJourneyPatternRef?

[skinkie]

The ServiceJourney allows the user to set the JourneyPatternRef. This allows the end user to use ServiceJourneyPatternRef, ServicePatternRef, DeadRunJourneyPatternRef and JourneyPatternRef.

Shouldn't we limit this to ServiceJourneyPatternRef?

This would break some things, especially if we change the element name too. And would certainly break the Nordic profile. But I honestly can't see why this type would be so wide.

[Aurige]

To be checked against Transmodel and propose an EPIP update if applicable (@Ulf9 @Aurige )

[vpaturet]

This will indeed break the Nordic Profile and require rework for all producers/consumers. I think we should refrain from performing such breaking changes, unless there is a compelling reason to do so.

[duexw]

This change would break the German Profile (VDV 462) as well. It would not be appreciated, as it would require much reworking of existing interfaces.

[Aurige]

No agreement for 2.0 but may be something to dive in for 3.0 ... with care for "old" systems.
Shall we deprecate the ServiceJourneyPattern ? no agreement either ...