Merge remote-tracking branch 'upstream/dev' into dev

Author: quicklywilliam

.github/ISSUE_TEMPLATE/release-candidate-review.md

@@ -1,3 +1,10 @@
+---
+name: Default
+about: Suggest changes to MDS
+title: <Insert Title>
+
+---
+
 # MDS Pull Request
 
 Thank you for your contribution!

.github/pull_request_template.md .github/PULL_REQUEST_TEMPLATE/default.md.github/pull_request_template.md renamed to .github/PULL_REQUEST_TEMPLATE/default.md

@@ -0,0 +1,18 @@
+---
+name: Release Candidate
+about: Initiate discussion to obtain OMF approval for new release
+title: Release Candidate [X.Y.Z]
+labels: admin
+assignees: jfh01
+
+---
+
+### Summary
+
+The Release Candidate for MDS `X.Y.Z` has been submitted: <https://github.com/openmobilityfoundation/mobility-data-specification/releases/tag/X.Y.Z-rc>
+
+Please use this pull request to track Technology Council and OMF Board feedback and/or requested changes.
+
+### Action Item
+
+This pull request will be merged by an OMF maintainer after OMF Board Approval following the [Release Guidelines](https://github.com/openmobilityfoundation/mobility-data-specification/blob/master/ReleaseGuidelines.md#making-a-release).

.github/PULL_REQUEST_TEMPLATE/release-candidate.md

@@ -0,0 +1,18 @@
+---
+name: Release Final
+about: Finalize and publish an OMF approved release
+title: Release [X.Y.Z]
+labels: admin
+assignees: jfh01
+
+---
+
+### Summary
+
+The Release Candidate for MDS `X.Y.Z` has been approved: <https://github.com/openmobilityfoundation/mobility-data-specification/releases/tag/X.Y.Z-rc>
+
+This pull request will make the release official in `master`.
+
+### Action Item
+
+Merge this pull request following the [Release Guidelines](https://github.com/openmobilityfoundation/mobility-data-specification/blob/master/ReleaseGuidelines.md#making-a-release).

.github/PULL_REQUEST_TEMPLATE/release-final.md

@@ -97,7 +97,7 @@ Contributors submit proposals for inclusion in the release cycle in the form of
 
 Contributors will provide feedback on proposals. Where possible, discussion will happen via GitHub. Weekly calls will support dialog around more complex or controversial issues. By the end of week 9, all active proposals must be in the form of a pull request. Proposals can be withdrawn or split apart for inclusion in future releases.
 
-##### Weeks 10-11: Decision making
+#### Weeks 10-11: Decision making
 
 These weeks will start with an web conference work session for all contributors to review and discuss current proposals. Goal is to achieve consensus where possible, or to clearly articulate areas of disagreement where not. Minor changes may be accepted at this stage if they bring contributors to consensus.
 
@@ -228,7 +228,7 @@ The following steps outline the process to prepare a Release Candidate of MDS. T
     This is a pre-release: Check
     ```
 
-1. [Open an Issue][mds-issue-new] to start the Release Candidate review process, using the `Release Candidate review` template. Fill in the appropriate Release Candidate version/URL.
+1. [Open a Pull Request][mds-pr-rc] from the release branch to `dev`. This ensures any changes to the Release Candidate during the review process make their way back into `dev`. This pull request is where review comments and feedback will be collected.
 
 1. Post an announcement to the [MDS-announce Mailing List][mds-announce], copying the [release notes](ReleaseNotes.md) created earlier and linking to the [GitHub release][mds-releases] and Release Candidate review Issue:
 
@@ -270,7 +270,9 @@ Repeat as-needed for subsequent Release Candidates.
 
 The following steps describe how to make an approved [Release Candidate][prepare-rc] an official release of MDS:
 
-1. Ensure OMF review has been completed and the Issue created during the Release Candidate process has been closed.
+1. Ensure OMF review has been completed and approval granted.
+
+1. Ensure the [Milestone][mds-milestones] for this release is at `100%`.
 
 1. In the release branch created earlier, update the ReleaseNotes.md with the new date of the release:
 
@@ -283,9 +285,9 @@ The following steps describe how to make an approved [Release Candidate][prepare
     etc...
     ```
 
-1. [Open a Pull Request][mds-pr-new] from the release branch to `dev`. This ensures any changes to the Release Candidate during the review process make their way back into `dev`. Merge this PR.
+1. Merge the Pull Request created during the Release Candidate process to `dev`.
 
-1. [Open a Pull Request][mds-pr-new] from the release branch to `master`. Merge this PR to make the release official.
+1. [Open a Pull Request][mds-pr-final] from the release branch to `master`. Merge this PR to make the release official.
 
 1. Create a tag in `master` for the new version. For example for `0.5.0`:
 
@@ -372,6 +374,8 @@ In rare cases, a hotfix for a prior release may be required out-of-phase with th
 [mds-milestones]: https://github.com/openmobilityfoundation/mobility-data-specification/milestones
 [mds-pr]: https://github.com/openmobilityfoundation/mobility-data-specification/pulls
 [mds-pr-new]: https://github.com/openmobilityfoundation/mobility-data-specification/compare
+[mds-pr-rc]: https://github.com/openmobilityfoundation/mobility-data-specification/compare?template=release-candidate.md
+[mds-pr-final]: https://github.com/openmobilityfoundation/mobility-data-specification/compare?template=release-final.md
 [mds-releases]: https://github.com/openmobilityfoundation/mobility-data-specification/releases
 [mds-releases-new]: https://github.com/openmobilityfoundation/mobility-data-specification/releases/new
 [mds-schema-common]: https://github.com/openmobilityfoundation/mobility-data-specification/blob/master/schema/templates/common.json

ReleaseGuidelines.md

@@ -1,11 +1,53 @@
-## 0.4.0 
+## 0.4.1
+
+> Released 2020-05-15
+
+0.4.1 is the first release of the Mobility Data Specification under the guidance and stewardship of the Open Mobility Foundation.
+As such, this release includes a number of administrative and documentation changes, including to the licensing and release process.
+This release also brings a number of language clarifications from 0.4.0 and new features across the various APIs, including the much anticipated /vehicles endpoint in Provider.
+
+### CHANGES
+
+*_MDS_*
+
+* [MDS officially transferred from LADOT to OMF](https://github.com/openmobilityfoundation/mobility-data-specification/issues/386):
+  * [Update license from CC0 to CC-BY](https://github.com/openmobilityfoundation/mobility-data-specification/pull/390)
+  * [Updates to various documentation to support code transfer from LADOT to OMF](https://github.com/openmobilityfoundation/mobility-data-specification/pull/391)
+  * [Switch CODEOWNERS to use OMF teams](https://github.com/openmobilityfoundation/mobility-data-specification/pull/404)
+  * [Add documentation around currently Supported MDS versions](https://github.com/openmobilityfoundation/mobility-data-specification/pull/449)
+  * [Add documentation around Understanding MDS APIs](https://github.com/openmobilityfoundation/mobility-data-specification/pull/452)
+  * [ReleaseGuidelines updates to reflect OMF process and 12 week dev cycle](https://github.com/openmobilityfoundation/mobility-data-specification/pull/453)
+* [Added "moped" vehicle type](https://github.com/openmobilityfoundation/mobility-data-specification/pull/416)
+
+*_Provider_*
+
+* [Mention ambiguity for event_type reserved](https://github.com/openmobilityfoundation/mobility-data-specification/pull/439)
+* [Clarify no pagination on /trips and /status_changes](https://github.com/openmobilityfoundation/mobility-data-specification/pull/424)
+* [Make required/optional endpoints more explicit](https://github.com/openmobilityfoundation/mobility-data-specification/pull/456)
+* [Adding a /vehicles endpoint](https://github.com/openmobilityfoundation/mobility-data-specification/pull/376)
+* [JSON Schema fixes/updates](https://github.com/openmobilityfoundation/mobility-data-specification/pull/458)
+
+*_Agency_*
+
+* [Add decommissioned event type reason](https://github.com/openmobilityfoundation/mobility-data-specification/pull/408)
+* [Add versioning](https://github.com/openmobilityfoundation/mobility-data-specification/pull/444)
+
+*_Policy_*
+
+* [Update documentation to use correct field name](https://github.com/openmobilityfoundation/mobility-data-specification/pull/412)
+* [Add missing rule_id](https://github.com/openmobilityfoundation/mobility-data-specification/pull/409)
+* [Add versioning](https://github.com/openmobilityfoundation/mobility-data-specification/pull/444)
+
+## 0.4.0
 
 > Release 2019-10-31
 
-The 0.4.0 release represents a major step forward in the Mobility Data Specification. The `provider` endpoints have been refactored to allow static file backed API servers which should improve uptime, reliability and the ability to backfill what is now growing to years of data. There is a new `policy` API endpoint, designed to be implemented by Agencies, that allows for clearer communication of geofencing, vehicle caps and more. A full list of changes is below. Many thanks to all the contributors who helped on this release. 
+The 0.4.0 release represents a major step forward in the Mobility Data Specification. The `provider` endpoints have been refactored to allow static file backed API servers which should improve uptime, reliability and the ability to backfill what is now growing to years of data. There is a new `policy` API endpoint, designed to be implemented by Agencies, that allows for clearer communication of geofencing, vehicle caps and more. A full list of changes is below. Many thanks to all the contributors who helped on this release.
+
+### CHANGES
 
-**CHANGES**
 *_Provider_*
+
 * [Improved Handling of Cost Data](https://github.com/openmobilityfoundation/mobility-data-specification/pull/388)
 * [Allow static file storage backed API Endpoints](https://github.com/openmobilityfoundation/mobility-data-specification/pull/357)
 * [Cleanup Provider README](https://github.com/openmobilityfoundation/mobility-data-specification/pull/395)
@@ -16,99 +58,107 @@ The 0.4.0 release represents a major step forward in the Mobility Data Specifica
 * [Update Status Change JSON Schema to include Associated Trip properly](https://github.com/openmobilityfoundation/mobility-data-specification/pull/353)
 
 *_Agency_*
+
 * [Add Accuracy Field for GPS Telemetry Data](https://github.com/openmobilityfoundation/mobility-data-specification/pull/360)
 * [String Limit to 255 Characters](https://github.com/openmobilityfoundation/mobility-data-specification/pull/361)
 * [Remove SLA from /telemetry](https://github.com/openmobilityfoundation/mobility-data-specification/pull/371)
 * [Update State Machine Diagram](https://github.com/openmobilityfoundation/mobility-data-specification/pull/363)
 
-*_Misc_* 
+*_Misc_*
+
 * [New Policy API Endpoint](https://github.com/openmobilityfoundation/mobility-data-specification/pull/382)
 * [Improved README for Schema Directory](https://github.com/openmobilityfoundation/mobility-data-specification/pull/398)
 * [Add Car Vehicle Type](https://github.com/openmobilityfoundation/mobility-data-specification/pull/219)
 * [Unify Error Responses between Provider / Agency](https://github.com/openmobilityfoundation/mobility-data-specification/pull/368)
 * [Improvements to Release Process](https://github.com/openmobilityfoundation/mobility-data-specification/pull/372)
 
-## 0.3.2 
+## 0.3.2
 
 > Released 2019-06-13
 
-This release is a series of non breaking and minor changes for provider, along with JSON Schema for agency. 
+This release is a series of non breaking and minor changes for provider, along with JSON Schema for agency.
 
-**CHANGES** 
+### CHANGES
 
 *_Provider_*
+
 * [Add an optional recorded field to provider](https://github.com/openmobilityfoundation/mobility-data-specification/issues/307)
 * [Ordering Definitions](https://github.com/openmobilityfoundation/mobility-data-specification/pull/301)
 * [406 response - version negiotation](https://github.com/openmobilityfoundation/mobility-data-specification/pull/327)
 
 *_Agency_*
-[JSON Schema for Agency](https://github.com/openmobilityfoundation/mobility-data-specification/issues/169)
+
+* [JSON Schema for Agency](https://github.com/openmobilityfoundation/mobility-data-specification/issues/169)
 
 *_Misc_*
-[Schema Folder Cleanup](https://github.com/openmobilityfoundation/mobility-data-specification/pull/328)
-[Global GNSS Support](https://github.com/openmobilityfoundation/mobility-data-specification/pull/316)
+
+* [Schema Folder Cleanup](https://github.com/openmobilityfoundation/mobility-data-specification/pull/328)
+* [Global GNSS Support](https://github.com/openmobilityfoundation/mobility-data-specification/pull/316)
+
 ## 0.3.1
 
 > Released 2019-04-30
 
-This release represents a series of non-breaking changes and clarifications for provider, along with a number of agency bugfixes / changes. 
+This release represents a series of non-breaking changes and clarifications for provider, along with a number of agency bugfixes / changes.
 
-**CHANGES**
+### CHANGES
 
 *_Provider_*
+
 * MDS Schema version fix.
-* [New release process](https://github.com/openmobilityfoundation/mobility-data-specification/pull/264). Thanks @jfh for documenting, all for participating 
+* [New release process](https://github.com/openmobilityfoundation/mobility-data-specification/pull/264). Thanks @jfh for documenting, all for participating
 * [Additional documentation around what is considered Breaking / Non-Breaking](https://github.com/openmobilityfoundation/mobility-data-specification/pull/295). Thanks @rf-
 * [OPTIONS for version negotiation](https://github.com/openmobilityfoundation/mobility-data-specification/pull/293). Thanks @billdirks
-* [Add Agency Drop off / pick up](https://github.com/openmobilityfoundation/mobility-data-specification/pull/291). Thanks @margodawes 
+* [Add Agency Drop off / pick up](https://github.com/openmobilityfoundation/mobility-data-specification/pull/291). Thanks @margodawes
 * [Explicitly allow associated_trip for any event type](https://github.com/openmobilityfoundation/mobility-data-specification/pull/297)
 
 *_Agency_*
+
 * Change from UUIDv4 to just UUID. Thanks @karcass
-* Change Error Messages for State Machine validation. 
-* Update Pagination Rules 
-* Add Unregistered event. 
+* Change Error Messages for State Machine validation.
+* Update Pagination Rules
+* Add Unregistered event.
 * [Add Event Diagram](https://github.com/openmobilityfoundation/mobility-data-specification/pull/258). Thanks @whereissean
 * [Removing 412 Responses](https://github.com/openmobilityfoundation/mobility-data-specification/pull/258)
-* Add deregister and decomissioned events. Thanks @dirkdk 
+* Add deregister and decomissioned events. Thanks @dirkdk
 * [Remove 5 second Telemetry requirement](https://github.com/openmobilityfoundation/mobility-data-specification/pull/261)
 * [Improve failure and error handling around Telemetry Data](https://github.com/openmobilityfoundation/mobility-data-specification/pull/290)
 
-## 0.3.0 
+## 0.3.0
 
 > Released 2019-02-15
 
-This release is the first minor version release of MDS with breaking changes for deployed provider API instances. 
+This release is the first minor version release of MDS with breaking changes for deployed provider API instances.
 
-**CHANGES** 
+### CHANGES
 
-* Improved Time Based Filtering Query Parameters. #139. Thanks @babldev 
-* Changes in Service Area for Agency API. 
+* Improved Time Based Filtering Query Parameters. #139. Thanks @babldev
+* Changes in Service Area for Agency API.
 * Switch timestamps to Integer milliseconds since Epoch rather then seconds. #179
 * Removed unused bbox query parameter. #183
 * Add GBFS discovery URL to `/providers.csv`. #205. Thanks @asadowns
 * Associated Trips -> Associated Trip, no longer an array. #88, #202, #217. Thanks @black-tea, @oderby
-* Version Requirements and documentation. #152, #216, and #114 
-* Agency API refactors to support launch of ladot.io sandbox. #193, #194. Thanks @toddapetersen, @sebdiem, @cttengsfmta. 
-* Clarification on Service Starts, Service Ends and Municipal Boundaries. #211, #226 
-* Documentation on how to implement truncate to save on payload size. 
+* Version Requirements and documentation. #152, #216, and #114
+* Agency API refactors to support launch of ladot.io sandbox. #193, #194. Thanks @toddapetersen, @sebdiem, @cttengsfmta.
+* Clarification on Service Starts, Service Ends and Municipal Boundaries. #211, #226
+* Documentation on how to implement truncate to save on payload size.
 
 ## 0.2.1
 
 > Released 2018-12-03
 
-This release is the first patch release of MDS 0.2. 
+This release is the first patch release of MDS 0.2.
 
-We did not chose to include the `timestamp` change, as discussed in issue #104, because it is breaking. Early versions of this branch included that change. The change will be made in MDS 0.3.0. 
+We did not chose to include the `timestamp` change, as discussed in issue #104, because it is breaking. Early versions of this branch included that change. The change will be made in MDS 0.3.0.
 
-**CHANGES**
+### CHANGES
 
-* Release Guidelines. Ref  #147 #129 
-* Many Validator Fixes/Null Fixes. Ref #166 #165 #128 
-* Many Clarifications / Cleanup to make the spec easier to read. 
-* JSON Schema is now much closer to the written spec, fails on Null if required, doesn't fail if field is not required. 
+* Release Guidelines. Ref  #147 #129
+* Many Validator Fixes/Null Fixes. Ref #166 #165 #128
+* Many Clarifications / Cleanup to make the spec easier to read.
+* JSON Schema is now much closer to the written spec, fails on Null if required, doesn't fail if field is not required.
 
-Thanks to all contributors. 
+Thanks to all contributors.
 
 ## 0.1.1
 

ReleaseNotes.md

@@ -182,7 +182,8 @@
             },
             "event_type_reason": {
               "enum": [
-                "missing"
+                "missing",
+                "decommissioned"
               ]
             }
           }

agency/get_vehicle.json

@@ -248,4 +248,4 @@
     }
   },
   "additionalProperties": false
-}
+}