Skip to content

DirectionType in JourneyPatternProperties vs GroupOfServicesCommonGroup #842

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.

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

Open
skinkie opened this issue Mar 19, 2025 · 0 comments
Open
Assignees
Labels
bug Technical mistake, inconsistency with the documentation, etc.
Milestone

Comments

@skinkie
Copy link
Contributor

skinkie commented Mar 19, 2025

What is the reason that we are using <xsd:element name="DirectionType" type="DirectionTypeEnumeration" minOccurs="0"> vs <xsd:element ref="DirectionType" minOccurs="0"/> in the latter?

Should we make this consistent?

@skinkie skinkie added the bug Technical mistake, inconsistency with the documentation, etc. label Mar 19, 2025
skinkie added a commit to MMTIS/badger that referenced this issue Mar 19, 2025
One bug is caused by the assumption that direction_type would always be the class "DirectionType" but for specifically ServiceJourneyPattern this is the enumeration "DirectionTypeEnumeration". For this inconsistency is raised a bug. NeTEx-CEN/NeTEx#842

The other problem was with an non-named argument.
@skinkie skinkie added this to the netex_2.0 milestone Apr 3, 2025
skinkie added a commit that referenced this issue Apr 21, 2025
skinkie added a commit that referenced this issue Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Technical mistake, inconsistency with the documentation, etc.
Projects
None yet
Development

No branches or pull requests

3 participants