Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ServiceJourneyInterchange points to ServiceJourney via VehicleJourneyRefStructure #699

Open
skinkie opened this issue Mar 29, 2024 · 1 comment
Open

ServiceJourneyInterchange points to ServiceJourney via VehicleJourneyRefStructure #699

skinkie opened this issue Mar 29, 2024 · 1 comment
Assignees
@Aurige
Labels
enhancement non semantic enhacement: technical enhancement, etc. to be discussed
Milestone
netex_2.0

Comments

@skinkie
Copy link
Contributor

skinkie commented Mar 29, 2024

I think it would again be in hour best interest that VehicleJourneyRefStructure and the consequence that it is basically unknown from which type the Journey originates from is avoided. I understand that from_something and to_something in its short hand form cannot specify a type, but I would then rather see that we have <To> and <From> which receive an abstract substitution group that expilictly use a ServiceJourneyRef, etc.
@skinkie skinkie added enhancement non semantic enhacement: technical enhancement, etc. to be discussed labels Mar 29, 2024
@ue71603 ue71603 added this to the netex_2.0 milestone Apr 17, 2024
@ue71603
Copy link
Contributor

ue71603 commented Apr 17, 2024

@Aurige what to do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Aurige Aurige

Labels
enhancement non semantic enhacement: technical enhancement, etc. to be discussed
Projects
None yet
Milestone
netex_2.0
Development

No branches or pull requests
4 participants
@skinkie @nick-knowles @Aurige @ue71603