0.4.1

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.

LICENSE and DISCLAIMER

Use of OMF Releases are bound by the OMF License and Disclaimer

CHANGES

MDS

• MDS officially transferred from LADOT to OMF:
  • Update license from CC0 to CC-BY
  • Updates to various documentation to support code transfer from LADOT to OMF
  • Switch CODEOWNERS to use OMF teams
  • Add documentation around currently Supported MDS versions
  • Add documentation around Understanding MDS APIs
  • ReleaseGuidelines updates to reflect OMF process and 12 week dev cycle and refinement
• Added "moped" vehicle type

Provider

• Mention ambiguity for event_type reserved
• Clarify no pagination on /trips and /status_changes
• Make required/optional endpoints more explicit
• Adding a /vehicles endpoint
• JSON Schema fixes/updates

Agency

• Add decommissioned event type reason
• Add versioning

Policy

• Update documentation to use correct field name
• Add missing rule_id
• Add versioning

Patch 1

• A minor patch was made on May 18 to include 2 of the above approved items missed during deployment. Please grab the latest version of the code using master or dev.

0.4.1 Release Candidate 1

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:
  • Update license from CC0 to CC-BY
  • Updates to various documentation to support code transfer from LADOT to OMF
  • Switch CODEOWNERS to use OMF teams
  • Add documentation around currently Supported MDS versions
  • Add documentation around Understanding MDS APIs
  • ReleaseGuidelines updates to reflect OMF process and 12 week dev cycle
• Added "moped" vehicle type

Provider

• Mention ambiguity for event_type reserved
• Clarify no pagination on /trips and /status_changes
• Make required/optional endpoints more explicit
• Adding a /vehicles endpoint
• JSON Schema fixes/updates

Agency

• Add decommissioned event type reason
• Add versioning

Policy

• Update documentation to use correct field name
• Add missing rule_id
• Add versioning

0.4.0

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.

CHANGES
Provider

• Improved Handling of Cost Data
• Allow static file storage backed API Endpoints
• Cleanup Provider README
• Legacy Version Header Cleanup
• Internationalization of Currency data
• Specify Types for Query Params
• Clarify the definition of Municipal Boundary
• Update Status Change JSON Schema to include Associated Trip properly

Agency

• Add Accuracy Field for GPS Telemetry Data
• String Limit to 255 Characters
• Remove SLA from /telemetry
• Update State Machine Diagram

Misc

• New Policy API Endpoint
• Improved README for Schema Directory
• Add Car Vehicle Type
• Unify Error Responses between Provider / Agency
• Imrovements to Release Process

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.

CHANGES

Provider

• Add an optional recorded field to provider
• Ordering Definitions
• 406 response - version negiotation

Agency

• JSON Schema for Agency

Misc

• Schema Folder Cleanup
• Global GNSS Support

0.3.1

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.

CHANGES

Provider

• MDS Schema version fix.
• New release process. Thanks @jfh for documenting, all for participating
• Additional documentation around what is considered Breaking / Non-Breaking. Thanks @rf-
• OPTIONS for version negotiation. Thanks @billdirks
• Add Agency Drop off / pick up. Thanks @margodawes
• Explicitly allow associated_trip for any event type

Agency

• Change from UUIDv4 to just UUID. Thanks @Karcass
• Change Error Messages for State Machine validation.
• Update Pagination Rules
• Add Unregistered event.
• Add Event Diagram. Thanks @whereissean
• Removing 412 Responses
• Add deregister and decomissioned events. Thanks @dirkdk
• Remove 5 second Telemetry requirement
• Improve failure and error handling around Telemetry Data

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.

CHANGES

• 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.

0.2.1

Released 2018-12-03

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.

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.

Thanks to all contributors.

0.2.1-dev

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.

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.

Thanks to all contributors.

0.1.1

This release backports two features from 0.2.0:

• Clarifying Location Types as GeoJSON #94

• Adding electric-assist as a propulsion type #48

This makes MDS 0.1.x series more usable for Mobility Providers.

0.2.0

This release includes a number of enhancements and clarifications to the provider spec:

• Introduce JSON Schema for Trips and Status Changes #53

• Clarify query params for API endpoints #64

• Clarify API authentication method #81

• Clarify location formatting #94

• Clarify timestamp formatting #93

• Clarify the associated_trips field in Status Changes #96