MDS Alignment

[schnuerle]

For the initial Scope of Work for CDS v1.0, we intentionally kept is separate from MDS to keep the implementation burden low and the features focused on just curb use cases.

For the next CDS, we may consider more alignment with MDS, especially around Policy, Geography, Jurisdiction, and even Metrics or other areas, to leverage the structure and features there and merge the ecosystems.

To that end, we will keep some naming and architectural concepts align with MDS where possible.

The next release of MDS will be 2.0 (after the upcoming 1.2 version) and one of the focuses there will be revisiting the Policy APIs. So there is a chance to add concepts to it that can support CDS using Policy in a future release.

We can use this issue to track ideas, discussions, and work between CDS and MDS in this regard.

See this MDS issue for more conversation and context:
openmobilityfoundation/mobility-data-specification#731

[jiffyclub]

It would also be interesting to think about the overlap between the various MDS events (in Provider status changes and in Agency events) and curb events. Can we come up with any advice for folks that are publishing both, or want to choose between one and the other? Might be hard before we have more use-cases, but I'll give it some thought.

[schnuerle]

Going to see if we can do this in a non breaking way for CDS 1.1.