The following table defines the implementation responsibilities, agreed to by the Mobility Data Interoperability Principles’ co-signers, which are required to comply with the intent of the Mobility Data Interoperability Principles. Note that several of these responsibilities will be dependent upon the implementation resources discussed in the following section.
>> mobility technology components shall ¶
- Explicitly state that transit agencies or other mobility service providers own mobility data produced by their respective mobility technology components.
- Utilize current or proposed open standards (along with associated best practices) to receive, process, store and export mobility data.
- Where neither open standards nor proposed open standards are yet available, data schemas and APIs to receive, process, store and export mobility data shall be compatible with open standards and/or proposed open standards, free from cost and restrictions to use, and posted to a public website in human- and the appropriate language-neutral, machine-readable format.
- Allow transit agencies and other mobility service providers to, free from cost and without restrictions, download, distribute and publish data owned by that agency or service provider in a well-documented format.
- Provide transit agencies and other mobility service providers and any other parties at their discretion, free from cost and without restrictions, real-time, read-only or read/write fully-capable programmatic access to mobility data owned by that agency or service provider, including geospatial data (e.g. GIS files).
- Protect individual privacy and anonymity.
>> Transportation technology companies, mobility service providers, and transportation system managers shall ¶
- Collaboratively develop and adopt open standards where gaps currently exist.
>> Transportation technology companies shall ¶
- Ensure the products they provide to transit providers are consistent with the Principles.
>> Mobility providers and transportation system managers shall ¶
- Require compliance with the Principles in procurement of any transit technology components.
Implementation Resources ¶
We developed initial versions of the following implementation resources coinciding with the release of the Public Draft.
|With Public Draft|
|Stand-alone website||For the purposes of the draft, we will use the following web property: [https://interoperable-mobility.github.io/principles/]
- White paper content as a website
-Signatories and co-authors
-Process for becoming a signatory and co-author
|TRB Paper||Submitted for review, but not accepted.|
|Promotional blurb||For use on existing websites, social media posts, etc.|
|White paper||White paper as a stand-alone document.|
The following resources will be available alongside version 1.0 (or soon after its release) in order to support Principle implementation.
|With Version 1.0|
|Graphic identity||To solidify the principles as a unique and cohesive group which extends between the confines of any single organization.|
|Press release||In order to notify the community beyond our own, self-reinforcing networks.|
|Technical one-pager||Posted on the stand-alone website.|
|Policy one-pager||Policy summary points to show high up decision-makers.|
|Policy-oriented single slide||Policy summary points for inclusion in update presentations to high up decision-makers.|
|Overview Presentation||More detailed overview of Principles and process.|
|Model Procurement Language||Menu of actionable language to include based on various situations.|
|Grants and funding language||For funding organizations to address similar issues with procurement language.|
|Implementation stories||Examples of how the Principles can and should be implemented and used.|
|Market Sounding||Similar to a request for information, a market sounding would discuss and assess the state of products on the market.|
|Mobility Dataverse||A directory of open standards.|
|Interoperability Status report||Where are we as a professional community with respect to meeting the intent of the Principles?|