NeTEx-CEN
Adding different types of restrictions between Services especially for DRT
Implementing more restrictions/eligibilty for services.
This is needed to describe many rules that exist for DRT services. Based on the discussion of: https://3.basecamp.com/3256016/buckets/2570434/messages/8778284879 based on https://github.com/NeTEx-CEN/NeTEx/issues/920 redoing #958 for next
redoing https://github.com/NeTEx-CEN/NeTEx/pull/958 not working yet and not adapted examples
TODO:
- fix problem with substitutionGroup
- change examples
- reduce to the max
We can now have the discussion
- if this fixes everything: @duexw @klement-MENTZ
- If this fits in the main structure @nick-knowles @Aurige
I think what you are still missing are the unique constraints in de root xsd. And potential relationships.
@skinkie will check. I made them all BookingArrangements from the id point of view. But I check
I don't think that it can be a 2.0 milestone since it contains several addition from the CEN submitted version (ServiceCompetitiveCondition ...)
@Aurige 2.0.1? Also those are additions, so they don't invalidate anything that is in the 2.0 specification
yes, but additions need documentation .. the idea behind the 2.0 is to stay as close as possible to the document. I'm of course fully Ok to have such PR in post 2.0 (also note that it also triggers a TM change request...)
Input from Felix Gründling for more parameters: https://felixguendling.github.io/transit-qa/
This would also allow for perpiece linear functions in the form of a table from 0 mim taxi: 35 penalty points per taxi minute from 1 min taxi: 12 penalty points per taxi minute
Soa penalty factor forDRTis missing DistanceFromClassical seems problematic, as an existing line may not operate (at this hour).
There may be other dominance rules for DRT vs DRT (first -mile/last-mile DRT vs direct DRt)
Temporal distance needs better definition e.g. mean between departure time and arrival time. Other functions might apply.
He an Moriz are interested in a discusion.