Repository navigation
Conversation
Fare data for one DB long-distance route, exported from the DB system on 1 October 2026 and sent by Clemens Gantert (DB) for the EFIP plenary of 5 November 2026. The file is added as received.
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
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.
Clemens sent me this file this morning because he could not upload it to the repository himself, so I am opening the pull request on his behalf for today's EFIP plenary.
It is the fare data for one DB long-distance route (Fernverkehr), exported from the DB system on 1 October 2026: 58 stations, 5 fare zones, 27 single trip fare products with sales offer packages and prices, and 8 user profiles including companion and disability card rules. I added it exactly as received.
The file does not validate against the v2.1-wip-efip schema yet, so the example check in CI will fail. What I found with xmllint:
<DataObjects>instead of<dataObjects>, which stops validation right at the startversionattribute, a number of objects have noid(SalesOfferPackageElement, GenericParameterAssignment, DistributionAssignment, CompanionProfile, EntitlementRequired), several references have noref(ScheduledStopPointRef, TypeOfFareStructureElementRef, PricingServiceRef), the abstractTransportOrganisationRefandUsageParameterRefare used directly, and there are a fewValue/Keyorder errorsI would suggest we discuss at the plenary whether Clemens updates the export or we tidy the file as part of the consolidation of the examples, and merge once it validates.
Clemens, please check that the description is right.