Release 2.1.0 Checkpoint Plan
The MDS Working Group Steering Committee met for the Plan Checkpoint for the 2.1.0 proposed release, and will present these results at a the next Working Group meeting. This builds on the work we started in the July 2024 WG meeting and before.
The checkpoint lets them review the past release, discuss unresolved features, and set goals for the current release.
For this work, we used our rubric to help guide the evaluation, looking at feature utility, stakeholder adoption, implementation simplicity, direction consensus, and work completed as part of the evaluation criteria.
See the Release Plan for details of these features. The outcomes and actions from these discussions are summarized here:
Clearer support for AV taxis (aka robotaxis) within Passenger Services mode #905
- Utility: 3. Documentation updates moderately important, defining stops more essential
- Adoption: 2. Might be ahead of the market a bit, need to get commitment from cities to use
- Simplicity: 3. State machine is already complex, but might not be a big change
- Consensus: 4. Seems kinda straightforward and not much chance for opposition
- Work: 2. Needs more discussion and find edge cases, proper wording
Improved support for real-time Policy for emergency response #906
- Utility: 4. Useful to add a productive way to check in real time, needed by cities and vendors
- Adoption: 4. Will be adopted, as we have cities and vendors ready
- Simplicity: 3. Not sure of final solutions, but should be pretty simple
- Consensus: 2. Haven't gotten org on board yet around details
- Work: 2. Just good ideas now, but need work to start
Crash information, both historic and real-time, for Passenger Services, Car Share, and Delivery Robots #613
- Utility: 2. Will likely be useful, but not sure until details are fleshed out.
- Adoption: 2. Some vendors should use the final version, like INRIX and Vianova, not sure until details are done.
- Simplicity: 1. Going to be complex to work out the details and scope
- Consensus: 1. Disagreements on real time/historic, use cases, PII or reports/hotspots.
- Work: 1. Ideas and need identified, but no one has started work yet.
Crash information, both historic and real-time, for Passenger Services, Car Share, and Delivery Robots #613
- Utility: 3. Clear asks from cities and companies now
- Adoption: 3. Cities and companies want these updates
- Simplicity: 4. Simple requests and optional fields building on what's there now
- Consensus: 2. Some thought given, needs more consensus building
- Work: 2. Good ideas for what to do, needs finish and polish work and review
Connections to CDS #731
- Utility: 2. Probably going to be useful
- Adoption: 2. Not sure who will adopt it yet, but it's been requested
- Simplicity: 3. Probably straightforward connection between spec IDs
- Consensus: 2. Nothing to rally around yet in detail
- Work: 2. Ideas now but no champion or PR
Possible air taxi mode support (AAM/UAM) #896
- Utility: 2. Likely useful when AAM comes to cities
- Adoption: 2. Eve Air and some others ready to use
- Simplicity: 1. Going to likely be tough to add to spec, especially vertiports
- Consensus: 1. Not sure the scope yet or who is aligned on this
- Work: 1. No work started on what the real PRs or solutions need to be in MDS
