Conversation
…re DatedServiceJourneyRefs is in use
erlendnils1
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two changes allowing us to move to 2.0.16 version for Entur/NeTEx without creating tmp solutions that will not work with 2.0.
Allowing SpecialServiceRef/DatedVehicleJourneyRef/NormalDatedVehicleJourneyRef
This lifted directly from CEN 2.0.
netex_fareContract_logentries_version.xsd is local change to Entur NeTEx and does not exist in CEN NeTEx. We will have to sort out how to handle this and other changes before moving to 3.0.0, but for now adding a DatedVehicleJourneyRef as a substitution for the removed DatedServiceJourney previously allowed as a substitute for ServiceJourney will make the migration a lot easier for us.