Skip to content

Conversation

@jiffyclub
Copy link
Contributor

Explain pull request

When developing CDS we came up with a more expansive definition of rates 1 to better capture real life scenarios. This commit brings that same definition to MDS, but keeps the MDS field rate_applies_when for specifying when the rate applies to an event.

As in CDS, a policy rule may now contain an array of rates specifying monetary charges or subsidies for events that match that rule. This removes the need to create multiple rules on a policy to capture different parts of the rate calculation, it can all be contained in the rate array.

Is this a breaking change

  • Yes, breaking

Impacted Spec

  • policy

Additional context

Closes #785.

When developing CDS we came up with a more expansive definition of
rates [1] to better capture real life scenarios. This commit brings
that same definition to MDS, but keeps the MDS field rate_applies_when
for specifying when the rate applies to an event.

As in CDS, a policy rule may now contain an array of rates specifying
monetary charges or subsidies for events that match that rule.
This removes the need to create multiple rules on a policy to capture
different parts of the rate calculation, it can all be contained in the
rate array.

[1]: https://github.com/openmobilityfoundation/curb-data-specification/tree/1.0.0/curbs#rate
@jiffyclub jiffyclub requested a review from a team as a code owner August 30, 2024 21:06
@schnuerle
Copy link
Member

schnuerle commented Jul 3, 2025

I like this proposal and think it's needed. But will have to wait for a 3.0 release since it's breaking. At the moment we are focused on 2.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants