Merge pull request #530 from schnuerle/ms-state-diagram

New State Machine Diagram
openmobilityfoundation · Jun 26, 2020 · 8a9cedf · 8a9cedf
2 parents d501f2a + 07bfc14
commit 8a9cedf
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 4 deletions.
diff --git a/MDS-state-machine-diagram.svg b/MDS-state-machine-diagram.svg
diff --git a/agency/images/MDS_agency_event_state.png b/agency/images/MDS_agency_event_state.png
diff --git a/general-information.md b/general-information.md
@@ -180,11 +180,9 @@ Note that to handle out-of-order events, the validity of the prior-state shall n
 | `available`, `reserved`, `on_trip`, `non_operational`, `elsewhere` | `unknown`     | `missing`            | The vehicle is not at its last reported GPS location, or that location is wildly in error |
 | `available`, `reserved`, `on_trip`, `non_operational`, `elsewhere` | `unknown`     | `comms_lost`       | The vehicle is unable to transmit its GPS location or other status information |
 
-NOTES:
+The *State Machine Diagram* shows how the `vehicle_state` and `event_type` relate to each other and how vehicles can transition between states. See [Google Slides](https://docs.google.com/presentation/d/1Ar2-ju8YlddSsTATvQw4YjsSa5108XtidtnJNk-UAfA/edit) for the source file.
+![MDS State Machine Diagram](/MDS-state-machine-diagram.svg)
 
-Should we try to handle "unlicensed movements"?
-
-What's the best way to return from `unknown`?
 
 [Top][toc]