interoperable-mobility/principles

Interoperable mobility principles

Mobility Data Interoperability Principles

Public Transit, and the mobility services which support it, is a critical backbone to our environmental, economic, and societal well-being. Modern, easily-accessible and well-operated public transit depends on a complex system of operations and customer-oriented technology components which work together.

Interoperable transit technology systems enable transit providers to plan service which is responsive to rider needs, improve service quality and efficiency, and adapt to continuing changes. Interoperability also encourages innovation among transportation technology companies while helping them to contain costs.

Released in October 2021 after a collaborative public process, Mobility Data Interoperability Principles create an industry-agreed upon vision, definition and direction for achieving interoperability with clear roles and responsibilities. The Principles were collaboratively developed and refined over Summer and Fall of 2021 by dozens of public and private organizations and researchers through a public review process.

Over 60 public and private signatories have committed to implementing the Principles. Organizations who are interested in publicly committing to the Principles and their faithful implementation can submit the form found at: Mobility Data Interoperability Principles.

Attribution

• California Association of Coordinated Transportation (CALACT)
• California Integrated Travel Project (Cal-ITP)
• Denver Regional Transportation District (RTD)
• ENTUR
• Los Angeles County Metropolitan Transportation Authority
• Massachusetts Bay Transportation Authority (MBTA)
• MetroTransit
• Metropolitan Transportation Commission (MTC)
• Minnesota Department of Transportation
• MobilityData
• North Carolina Department of Transportation
• Oregon Department of Transportation
• Shared Use Mobility Center (SUMC)
• Taskar Center for Accessible Technology
• Tri-Met
• Vermont Agency of Transportation
• VIA Metropolitan Transit San Antonio
• Washington State Department of Transportation (WSDOT) Public Transportation Division

License

This code in this repository is licensed under Apache 2.0.

The content in this repository is licensed under CC BY 2.0

principles's Issues

Add LICENSES file and both apache and cc-by licenses.

Per README, should make sure both the CC-BY and APACHE licenses are in an appropriate file.

Rename "Proposed Open Standard"

Overview

The name "Proposed Open Standard" has caused confusion among the MDIP audience and is a source of concern particularly for prospective vendor signatories. We should change the name to better reflect the specific kinds of proposals that meet the threshold for requiring support.

Detail

The Principles define two types of standard, the open standard and the proposed open standard. Both types of standard must be supported by vendors and others seeking to achieve alignment with MDIP. The definition of Proposed Open Standard is:

Proposed Open Standard
Any specific ontology, schema, or format that:
Meets all the criteria of an open standard,
Has been transitioned to maintenance by an independent organization,
Has at least one stable release as determined by the maintaining independent organization, and
Has not met the standards for adoption as determined by the maintaining independent organization.

This definition was intended by coauthors to exclude many types of proposals. At the basic level we did not want to include standards which had been recently proposed but had little support, momentum or substance.

There are two opposing goals for the definition of Proposed Open Standard --> we want to 1) leverage MDIP to encourage vendors to become early (or earlier) adopters of standards that have demonstrated they are on a path to adoption and 2) not exact unduly onerous requirements on the vendor community such that they are uncomfrotable with aligning with MDIP.

Apart from any changes which might be made to the content of the definition of Proposed Open Standard, we should change the name of the term so as to better reflect those two goals. This will alleviate some audience concerns and also provide insight into what we are hoping to achieve through the inclusion of Proposed Open Standards.

Deploy previews to Netlify

See this issue for more context cal-itp/data-infra#623

We created a Netlify site specifically to generate previews of GitHub Pages site PRs. This site is not connected to any one GitHub repository, so does not get deployed automatically.

I've created the necessary repository secrets in this repository:

🗳️ Elect a Coalition Chair

After governance document is approved, the Coalition needs to elect a Chair

Add new coauthors and cosignatories, May 31

Add new cosignatories SimplifyTransit and RideScheduler, and MnDOT as a new coauthor to the

🗳️ Approve MOU with MobilityData

Draft MOU

Todo

• Circulate draft MOU to MDIP Coalition for discussion and review
• Get consensus on wording from MobilityData
• Conduct vote of MOU with MDIP Coalition
• Document approval on website and store document on drive

🧹 Update github teams and access to be consistent with MDIP Governance

After the approval of the governance #21 , add structure to Github repository that is consistent with it.

Todo:

• Develop Teams for organization consistent with governance
• Post a CODEOWNERS file for teams allowed to make normative changes to governance or principles
• Add branch access rules to prevent posting to main without a PR and approval from a CODEOWNER

🗳️ Approve formalization of MDIP Governance

Draft for review

Todo

• Circulate draft for review to coalition
• Vote by Coalition
• Document vote result on website and in shared folder

Add new Coauthors and Cosignatories to site

Requirements

• Add new coauthors Los Angeles County Metropolitan Transportation Authority, North Carolina Department of Transportation, and Vermont Agency of Transportation to:
  ** README.md
  ** Co-author section (add logos)
  ** Co-signatory section
• Add new cosignatories to Co-signatory section (in alphabetical order)
  ** Snapper
  ** Vix
  ** City of Santa Monica Department of Transportation
  ** DCR Design
  ** Open Mobility Data in the Nordics
  ** Dr. Tierra Bills, University of California, Los Angeles
  ** Fairsfair.org
  ** Swiftly
  ** Foursquare ITP
  ** EnrouteQ