Skip to content

Commit d3e0fde

Browse files
authored
Bumped up header sizes
1 parent 3408554 commit d3e0fde

1 file changed

Lines changed: 13 additions & 13 deletions

File tree

README.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
- [Use Cases](#use-cases)
1717
- [Related Projects](#related-projects)
1818

19-
## About
19+
# About
2020

2121
The Mobility Data Specification (**MDS**), a project of the [Open Mobility Foundation](http://www.openmobilityfoundation.org) (OMF), is a set of Application Programming Interfaces (APIs) focused on dockless e-scooters, bicycles, mopeds and carshare. Inspired by projects like [GTFS](https://developers.google.com/transit/gtfs/reference/) and [GBFS](https://github.com/NABSA/gbfs), the goals of MDS are to provide a standardized way for municipalities or other regulatory agencies to ingest, compare and analyze data from mobility service providers, and to give municipalities the ability to express regulation in machine-readable formats.
2222

@@ -28,7 +28,7 @@ The Mobility Data Specification (**MDS**), a project of the [Open Mobility Found
2828

2929
[Top][toc]
3030

31-
## Endpoints
31+
# Endpoints
3232

3333
**MDS** is comprised of six distinct APIs, with multiple endpoints under each API:
3434

@@ -68,7 +68,7 @@ The [`metrics`](/metrics) API endpoints are intended to be implemented by regula
6868

6969
---
7070

71-
### Modularity
71+
## Modularity
7272

7373
MDS is designed to be a modular kit-of-parts. Regulatory agencies can use the components of the API that are appropriate for their needs. An agency may choose to use only `agency`, `provider`, or `policy`. Other APIs like `geography`, `jurisdiction`, and `metrics` can be used in coordination as described with these APIs or sometimes on their own. Or agencies may select specific elements (endpoints) from each API to help them implement their goals. Development of the APIs takes place under the guidance of either the OMF's [City Services](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/MDS-City-Services-Working-Group) or [Provider Services](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/MDS-Provider-Services-Working-Group) Working Groups.
7474

@@ -78,13 +78,13 @@ You can read more in our **[Understanding the different MDS APIs](https://github
7878

7979
![MDS APIs and Endpoints](https://i.imgur.com/L5s927a.png)
8080

81-
### GBFS Requirement
81+
## GBFS Requirement
8282

8383
All MDS compatible Provider feeds [must also expose](/provider/README.md#gbfs) a public [GBFS](https://github.com/NABSA/gbfs) feed. Compatibility with [GBFS 2.0](https://github.com/NABSA/gbfs/blob/v2.0/gbfs.md) or greater is advised due to privacy concerns and support for micromobility. See our [MDS Vehicles Guide](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/MDS-Vehicles) for how MDS Provider `/vehicles` can be used by regulators instead of the public GBFS `/free_bike_status`. Additional information on MDS and GBFS can be found in this [guidance document](https://github.com/openmobilityfoundation/governance/blob/main/technical/GBFS_and_MDS.md).
8484

8585
[Top][toc]
8686

87-
## Get Involved
87+
# Get Involved
8888

8989
To stay up to date on MDS releases, meetings, and events, please **subscribe to the [mds-announce](https://groups.google.com/a/groups.openmobilityfoundation.org/forum/#!forum/mds-announce) mailing list** and read our **[Community Wiki](https://github.com/openmobilityfoundation/mobility-data-specification/wiki)**.
9090

@@ -103,21 +103,21 @@ You can view info about current and past releases, the public OMF calendar, and
103103

104104
For questions about MDS please contact by email at [info@openmobilityfoundation.org](mailto:info@openmobilityfoundation.org) or [on our website](https://www.openmobilityfoundation.org/get-in-touch/). Media inquiries to [media@openmobilityfoundation.org](mailto:media@openmobilityfoundation.org).
105105

106-
### Membership
106+
## Membership
107107

108108
OMF Members (public agencies and commercial companies) have additional participation opportunities with leadership roles on our [Board of Directors](https://www.openmobilityfoundation.org/about/), [Privacy, Security, and Transparency Committee](https://github.com/openmobilityfoundation/privacy-committee), [Technology Council](https://github.com/openmobilityfoundation/governance/wiki/Technology-Council), and [Strategy Committee](https://github.com/openmobilityfoundation/governance/wiki/Strategy-Committee), as well as the steering committees of all [Working Groups](https://github.com/openmobilityfoundation/mobility-data-specification/wiki#omf-meetings).
109109

110110
Read about [how to become an OMF member](https://www.openmobilityfoundation.org/how-to-become-a-member/) and [contact us](https://mailchi.mp/openmobilityfoundation/membership) for more details.
111111

112112
[Top][toc]
113113

114-
## Versions
114+
# Versions
115115

116116
MDS has a **current release** (version 1.1.0), **previous releases** (both recommended and longer recommended for use), and **upcoming releases** in development. For a full list of releases, their status, recommended versions, and timelines, see the [Official MDS Releases](https://github.com/openmobilityfoundation/governance/wiki/Releases) page.
117117

118118
The OMF provides guidance on upgrading for cities, providers, and software companies, and sample permit language for cities. See our [MDS Version Guidance](https://github.com/openmobilityfoundation/governance/blob/main/technical/OMF-MDS-Version-Guidance.md) for best practices on how and when to upgrade MDS as new versions become available. Our complimentary [MDS Policy Language Guidance](https://github.com/openmobilityfoundation/governance/blob/main/technical/OMF-MDS-Policy-Language-Guidance.md) document is for cities writing MDS into their operating policy and includes sample policy language.
119119

120-
### Technical Information
120+
## Technical Information
121121

122122
The latest MDS release is in the [`main`](https://github.com/openmobilityfoundation/mobility-data-specification/tree/main) branch, and development for the next release occurs in the [`dev`](https://github.com/openmobilityfoundation/mobility-data-specification/tree/dev) branch.
123123

@@ -131,23 +131,23 @@ The MDS specification is versioned using Git tags and [semantic versioning](http
131131

132132
[Top][toc]
133133

134-
## Cities Using MDS
134+
# Cities Using MDS
135135

136136
More than 115 cities and public agencies around the world use MDS, and it has been implemented by most major [mobility service providers](#providers-using-mds). See our webpage for a list of known [cities using MDS](https://www.openmobilityfoundation.org/about-mds/mds-users/#cities-using-mds) with links to public mobility websites and policy/permit documents.
137137

138138
Please let us know [via our website](https://www.openmobilityfoundation.org/get-in-touch/) or in the [public discussion area](https://github.com/openmobilityfoundation/mobility-data-specification/discussions) if you are an agency using MDS, especially if you have published your policies or documents publicly, so we can add you to the city resource list.
139139

140140
[Top][toc]
141141

142-
## Providers Using MDS
142+
# Providers Using MDS
143143

144144
Over two dozen mobility service providers (MSPs) around the world use MDS, allowing them to create tools around a single data standard for multiple cities. See our webpage for a [list of known MSPs](https://www.openmobilityfoundation.org/about-mds/mds-users/#mobility-providers-using-mds). For a table list with unique IDs, see the MDS [provider list](/providers.csv).
145145

146146
To add yourself to the provider list, please let us know [via our website](https://www.openmobilityfoundation.org/get-in-touch/) or open an [Issue](https://github.com/openmobilityfoundation/mobility-data-specification/issues) or [Pull Request](https://github.com/openmobilityfoundation/mobility-data-specification/pulls).
147147

148148
[Top][toc]
149149

150-
## Software Companies Using MDS
150+
# Software Companies Using MDS
151151

152152
An open source approach to data specifications benefits cities and companies by creating a space for collaborative development, reducing costs, and nurturing a healthy, competitive ecosystem for mobility services and software tools. The open model promotes a competitive ecosystem for software tools built by dozens of software companies providing their servives to cities, agencies, and providers.
153153

@@ -157,7 +157,7 @@ Please [let us know](https://www.openmobilityfoundation.org/get-in-touch/) if yo
157157

158158
[Top][toc]
159159

160-
## Use Cases
160+
# Use Cases
161161

162162
How cities use MDS depends on a variety of factors: their transportation goals, existing services and infrastructure, and the unique needs of their communities. Cities are using MDS to create policy, enforce rules, manage hundreds of devices, and ensure the safe operation of vehicles in the public right of way. Some examples of how cities are using MDS in practice are:
163163

@@ -174,7 +174,7 @@ Please [let us know](https://www.openmobilityfoundation.org/get-in-touch/) if yo
174174

175175
[Top][toc]
176176

177-
## Related Projects
177+
# Related Projects
178178

179179
Community projects are those efforts by individual contributors or informal groups that take place outside Open Mobility Foundation’s formalized process, complementing MDS. These releated projects often push new ideas forward through experimental or locally-focused development, and are an important part of a thriving open source community. Some of these projects may eventually be contributed to and managed by the Open Mobility Foundation.
180180

0 commit comments

Comments
 (0)