Web conference notes, 2020.11.19 (Joint Working Group City Services)

Joint Working Group - Provider Services

#red NOTE NEW TIME TWO HOURS SOONER #red

#red NOTE NEW ZOOM MEETING ID/LINK/PHONE NUMBER #red

Meeting ID: 671 331 832 - https://zoom.us/j/671331832

One tap mobile: +19294362866,,671331832# US

Dial by phone: +1 929 436 2866 (US) (Find your local number)

Attendees

Add your own name, link, and organization during call

Main Topics

Release 1.1.0 extended 2 weeks to finalize multiple conversations including the ones below. The Release Plan has been updated to reflect this.
Jurisdiction followup
Stops in Policy, Stop image
Geography 'Type', retire date, MultiPolygon
Other Items
- The idea of requirement/necessity to rule types in policy
- Discussing self-driving vehicles 1) modifying the state machine and 2) describing non-trip movement.

Next week's meeting is cancelled for the US holidays.

Notes and or transcript of the call with presentation, document, GitHub links and calls to action.

Jurisdiction followup

Recap: Proposed Jurisdiction API is a method to communicate agency boundaries and jurisdictions, especially important in multi-jurisdiction environment. References geographies, mobility_mode (also in development), and provides immutability.
Proposal is to start narrow in scope. Future changes may include making it public and allow agencies with separate MDS deployments to communicate with each other.
There has been good community discussion on this and we will plan to include it in the next release

Stops in Policy, Stop image

This PR consolidates a number of Stops-related PRs:
- Stop Image: Allows for adding URL to an image of the stop
- Adding Stops to policy: Stops can be referenced in policy as a list of UUIDS that are defined in Geographies. This may be confusing since Stops could be defined separately in Agency or Provider, depending on how it’s implemented, and the implementer would need to ensure consistency in the definition of points across various endpoints. There was a more complex proposal to simplify/streamline this and solve for some other scenarios, but a PR would need to be made for the next release and the community would need to digest this. Neil said he could work on it in the future. The group should add comments to help flesh this out. Consensus is to remove from policy rule in PR. Michael will attempt to integrate this into the PR.

Geography 'Type', retire date, MultiPolygon

Geography_type: Added a policy_zone as a reference to Policy. Looks good.
Retire_date: Added as optional field that can be updated. However this could invalidate immutability. Future digital signing of each fields could add a layer of authenticity to the immutability. Also need to further clarify language on what retiring means, e.g., future policies can no longer reference it, old policies referencing it should be updated, and retired geographies should continue to be returned. Consensus is to remove the immutable exception from the PR and make retire date function like all the others.
Stop center point: should be point in stop for simplicity but polygon in geography.
Location as point: Proposal that if point is used then a 20 meter buffer should be assumed. Keep in PR but move to geography spec instead as a general rule.

Other Items

The idea of requirement/necessity to rule types in policy: Briefly discussed and we need further discussion about how will this be used. -
- Leave comments in the PR.
Discussing self-driving vehicles 1) modifying the state machine and 2) describing non-trip movement. Leave comments in the PR. This hasn’t been fully discussed so will be pushed to 1.2.

Release status