Merge pull request #502 from openmobilityfoundation/release-0.4.1-pat…

…ch-1

Release 0.4.1 patch 1 - beta, vehicles, doc clarification (for master)

ReleaseGuidelines.md

@@ -272,6 +272,8 @@ The following steps describe how to make an approved [Release Candidate][prepare
 
 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:
 
     ```diff

general-information.md

@@ -53,4 +53,6 @@ Despite this, MDS users are highly encouraged to use beta features. New features
 
 Users of beta features are strongly encouraged to share their experiences, learnings, and challenges with the broader MDS community via GitHub issues or pull requests. This will inform the refinements that transform beta features into fully proven, stable parts of the specification.
 
+Working Groups and their Steering Committees are expected to review beta designated features with each release cycle and determine whether the feature has reached the level of stability and maturity needed to remove the beta designation. In a case where a beta feature fails to reach substantial adoption after an extended time, Working Group Steering Committees should discuss whether or not the feature should remain in the specification.
+
 [Top](#table-of-contents)

provider/README.md

@@ -398,7 +398,7 @@ Should either side of the requested time range be greater than 2 weeks before th
 
 ### Vehicles
 
-The `/vehicles` endpoint returns the current status of vehicles on the PROW. Only vehicles that are currently in available, unavailable, or reserved states should be returned in this payload. Data in this endpoint should reconcile with data from the `/status_changes` enpdoint. The data returned by this endpoint should be as close to realtime as possible, but in no case should it be more than 5 minutes out-of-date.
+The `/vehicles` endpoint returns the current status of vehicles on the PROW. Only vehicles that are currently in available, unavailable, or reserved states should be returned in this payload. Data in this endpoint should reconcile with data from the `/status_changes` enpdoint. The data returned by this endpoint should be as close to realtime as possible, but in no case should it be more than 5 minutes out-of-date. As with other MDS APIs, `/vehicles` is intended for use by regulators, not by the general public. It does not replace the role of a [GBFS](https://github.com/NABSA/gbfs) feed in enabling consumer-facing applications.
 
 In addition to the standard [Provider payload wrapper](#response-format), responses from this endpoint should contain the last update timestamp and amount of time until the next update: