Skip to content
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

suport carrier associations in regional validity #779

Open
CGantert345 opened this issue Dec 9, 2024 · 0 comments · May be fixed by #780
Open

suport carrier associations in regional validity #779

CGantert345 opened this issue Dec 9, 2024 · 0 comments · May be fixed by #780
Assignees
Labels
improvements New feature or request
Milestone

Comments

@CGantert345
Copy link
Contributor

Fares might be valid for a list of carriers. These carriers are currently included as a list of company codes in the carrier constraint object used for example in regional validity.

As these list can be large (> 50 Carriers and PTAs) they should be named on in the conditions. The current solution is to use the first carrier in the list as "key carrier" for the association.

It would be clearer for implementers to explicitly include the carrier group and to provide a name and description for the group.

-> add carrier group master data

  • list of companies
  • name
  • description
  • legacy code to be used for 108.1 conversion

-> add link from carrierConstraint to carrier group indicating the association as valid valid carriers

@CGantert345 CGantert345 added the improvements New feature or request label Dec 9, 2024
@CGantert345 CGantert345 added this to the 3.4.1 milestone Dec 9, 2024
@CGantert345 CGantert345 self-assigned this Dec 9, 2024
@CGantert345 CGantert345 linked a pull request Dec 9, 2024 that will close this issue
@jspetrak jspetrak moved this to To do in OSDM Specification Dec 9, 2024
@CGantert345 CGantert345 moved this from To do to In progress in OSDM Specification Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvements New feature or request
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

1 participant