CDS Alignment

[schnuerle]

Is your feature request related to a problem? Please describe.

For the initial Scope of Work for CDS v1.0 beta (Curb Data Specification), 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 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 also need to look at how CDS could be connected to Modes in MDS, especially around passenger services, TNC, curb use, device maintenance/recharging, etc.

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

Is this a breaking change

• I'm not sure

Impacted Spec

For which spec is this feature being requested?

• policy
• Modes across MDS

Additional context

See similar issue in CDS:
openmobilityfoundation/curb-data-specification#17

[schnuerle]

Some discussions about automatically adding overlapping MDS locations in curb zones as CDS events data. Useful for demand side of curb. Already has on board GPS. MDS status changes could be a curb event. Events could happen right now, already collecting this data. Rebalancing is part of MDS which could be in curb zones.

Core question: how to convert an MDS status change or state into CDS Event? CDS minimum Curb zones - a geographic rectangle, a curb zone ID, and date/time.