Skip to content

Extending BookingArrangement and fixing it #920

@ue71603

Description

@ue71603

On Nicks entries I suggest to go with

  • ELIGIBILITY: If we added a new specialisation of BOOKING ARRANGEMENTs (e.g. BOOKING ELIGIBILITY RESTRICTION
  • COMPETITIVE RESTRICTIONS: I would prefer to use i here, as then we don't have to wait for CoRoM, which is not in the current scope of either 1.3 or 2.0. We can revisit it later. We model it as an extension to booking arrangement and we need to allow for booking arrangement on ServiceJourney, Connection and ServiceeJourneyInterchange besides Line.

Metadata

Metadata

Labels

enhancementnon semantic enhacement: technical enhancement, etc.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions