{"id":43852,"date":"2026-11-21T09:39:21","date_gmt":"2026-11-21T08:39:21","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43852"},"modified":"2026-11-14T14:39:41","modified_gmt":"2026-11-14T13:39:41","slug":"mobility-data-specification-mds-joins-smart-data-models-8-candidate-models-for-shared-mobility-regulation","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/mobility-data-specification-mds-joins-smart-data-models-8-candidate-models-for-shared-mobility-regulation\/","title":{"rendered":"Mobility Data Specification (MDS) Joins Smart Data Models: 8 Candidate Models for Shared Mobility Regulation"},"content":{"rendered":"<p>Smart Data Models\u2019 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> now includes a new candidate standard translated from the <strong>Open Mobility Foundation<\/strong>: <strong><code>mds<\/code><\/strong>, with <strong>8 candidate models<\/strong> from the <strong>Mobility Data Specification (MDS) 2.1.0<\/strong>: vehicles, events, telemetry, trips, stops, incidents, geographies and policies. MDS is published under <strong>CC BY 4.0<\/strong>. Like every candidate, each model comes with a JSON Schema, an NGSI-LD <code>@context<\/code> and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.<\/p>\n<h2 id=\"about-mds\">About the Mobility Data Specification<\/h2>\n<p><a href=\"https:\/\/www.openmobilityfoundation.org\/about-mds\/\">MDS<\/a> is the data standard that cities and public agencies use to manage mobility services operating in the public right of way: shared scooters and bikes, car share and fleets, delivery robots and passenger services such as taxis and robotaxis. Operators share their vehicles, trips, vehicle events and telemetry; agencies publish geographies and policies (fleet caps, speed limits, fees). <a href=\"https:\/\/github.com\/openmobilityfoundation\/mobility-data-specification\/tree\/2.1.0\">Release 2.1.0<\/a> (July 2026) adds incidents and enforcement, links to GTFS and other external data, statistical areas and accelerometer data.<\/p>\n<h2 id=\"the-models\">The models<\/h2>\n<table>\n<thead>\n<tr>\n<th>Model<\/th>\n<th>What it describes<\/th>\n<th>Attributes<\/th>\n<th>Example<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>Vehicle<\/code><\/td>\n<td>A vehicle registered by an operator: type, propulsion, capacities<\/td>\n<td>14<\/td>\n<td>Standing e-scooter<\/td>\n<\/tr>\n<tr>\n<td><code>Event<\/code><\/td>\n<td>A change of vehicle state (available, on trip, non-operational\u2026)<\/td>\n<td>21<\/td>\n<td>Trip end at a corral<\/td>\n<\/tr>\n<tr>\n<td><code>Telemetry<\/code><\/td>\n<td>One GPS\/GNSS point with sensor data<\/td>\n<td>17<\/td>\n<td>Point mid-trip, on a bike lane<\/td>\n<\/tr>\n<tr>\n<td><code>Trip<\/code><\/td>\n<td>A customer or operator trip with start, end, duration, distance and cost<\/td>\n<td>25<\/td>\n<td>8-minute rider trip<\/td>\n<\/tr>\n<tr>\n<td><code>Stop<\/code><\/td>\n<td>A docking station, corral or parking area, with capacity and availability<\/td>\n<td>24<\/td>\n<td>Corral for scooters and bikes<\/td>\n<\/tr>\n<tr>\n<td><code>Incident<\/code><\/td>\n<td>Crash, tip over, near miss, vandalism, violation\u2026 (new in 2.1)<\/td>\n<td>16<\/td>\n<td>Harsh stopping, no injury<\/td>\n<\/tr>\n<tr>\n<td><code>Geography<\/code><\/td>\n<td>A versioned GeoJSON area published by an agency<\/td>\n<td>10<\/td>\n<td>Louisville Metro municipal boundary (real)<\/td>\n<\/tr>\n<tr>\n<td><code>Policy<\/code><\/td>\n<td>Agency rules: caps, speed limits, time and distance limits, fees<\/td>\n<td>12<\/td>\n<td>Fleet cap and 15 mph speed limit<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"examples\">Examples: one story, and privacy first<\/h2>\n<p>MDS trip and telemetry data is sensitive location data, so no real operator feed is used. The examples tell one synthetic story in downtown Louisville, Kentucky: a fictitious operator\u2019s scooter makes a short trip, records a harsh-stopping incident and ends the trip at a corral. The <code>Geography<\/code> example is real: the Louisville Metro municipal boundary that the Open Mobility Foundation publishes in the MDS repository (CC BY 4.0). The example policy refers to that boundary but is invented.<\/p>\n<h2 id=\"translation-notes\">Translation notes<\/h2>\n<ul>\n<li><strong>Taken from the 2.1.0 tables.<\/strong> The OMF OpenAPI description still covers MDS 2.0 only, so the models were generated from the field tables of the 2.1.0 specification, with the OpenAPI used as a cross-check.<\/li>\n<li><strong>MDS names, verbatim.<\/strong> Fields keep their MDS names (<code>device_id<\/code>, <code>vehicle_state<\/code>, <code>event_types<\/code>\u2026). The only rename is the MDS GPS object <code>location<\/code>, which becomes <code>mdsLocation<\/code> because <code>location<\/code> is reserved for GeoJSON in NGSI-LD.<\/li>\n<li><strong>Linked entities.<\/strong> References between models (an event\u2019s vehicle, trips, stop and geographies; telemetry\u2019s incidents; a stop\u2019s geography) are NGSI-LD Relationships.<\/li>\n<li><strong>Ready for geo-queries.<\/strong> Events, telemetry, stops and geographies get an NGSI-LD <code>location<\/code> built from MDS\u2019s own coordinates. It is the only addition to the MDS content. Timestamps stay in MDS format (milliseconds since the Unix epoch).<\/li>\n<li><strong>Upstream notes.<\/strong> A few small inconsistencies in the specification (for example <code>system_start<\/code> vs <code>service_start<\/code> in the event types) are documented in the metadata, ready to report to the OMF.<\/li>\n<\/ul>\n<h2 id=\"try-it-and-tell-us-whats-missing\">Try it, and tell us what\u2019s missing<\/h2>\n<p>These are <strong>Candidates<\/strong>: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open question is overlap with <code>dataModel.Transportation<\/code> (Vehicle, FleetVehicle, BikeHireDockingStation, RoadAccident\u2026), <code>dataModel.UrbanMobility<\/code> and the shared-vehicles candidate <code>edint-vehiculos-compartidos<\/code>. Natural next steps are MDS Reports, Vehicle Status and the agency data Requirements.<\/p>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/mds\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/mds<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Open Mobility Foundation: mds, with 8 candidate models from the Mobility Data Specification (MDS) 2.1.0: vehicles, events, telemetry, trips, stops, incidents, geographies and policies. MDS is published under CC BY 4.0. Like every candidate, each model&#8230; <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/mobility-data-specification-mds-joins-smart-data-models-8-candidate-models-for-shared-mobility-regulation\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[107,42],"tags":[],"class_list":["post-43852","post","type-post","status-publish","format-standard","hentry","category-smart-cities","category-transportation"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":41633,"url":"https:\/\/smartdatamodels.org\/index.php\/state-of-the-candidates-repository-29-standards-385-data-models\/","url_meta":{"origin":43852,"position":0},"title":"State of the Candidates Repository: 29 Standards, 385 Data Models","author":"maestro","date":"08\/09\/2026","format":false,"excerpt":"This is just a summary for the participants of the FIWARE global summit 2026. See you there in Menton. Smart Data Models' Candidates repository has grown a lot over the past few weeks. This post is a single roundup of everything in it today: 29 source standards, translated into 385\u2026","rel":"","context":"In &quot;Governance&quot;","block_context":{"text":"Governance","link":"https:\/\/smartdatamodels.org\/index.php\/category\/governance\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43858,"url":"https:\/\/smartdatamodels.org\/index.php\/camara-apis-join-smart-data-models-7-candidate-models-for-telco-network-data-in-smart-cities\/","url_meta":{"origin":43852,"position":1},"title":"CAMARA APIs Join Smart Data Models: 7 Candidate Models for Telco Network Data in Smart Cities","author":"Agent","date":"17\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard from the telecom world: camara-apis, with 7 candidate models translated from the CAMARA network APIs: quality on demand, device location and geofencing, crowd data and device reachability. The CAMARA specifications are published under Apache-2.0. Like every candidate, each model\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43815,"url":"https:\/\/smartdatamodels.org\/index.php\/catena-x-joins-smart-data-models-8-candidate-models-for-automotive-traceability\/","url_meta":{"origin":43852,"position":2},"title":"Catena-X Joins Smart Data Models: 8 Candidate Models for Automotive Traceability","author":"Agent","date":"14\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":7053,"url":"https:\/\/smartdatamodels.org\/index.php\/presentations-of-the-smart-data-models-session-at-fiware-summit\/","url_meta":{"origin":43852,"position":3},"title":"Presentations of the Smart Data Models session at FIWARE summit","author":"maestro","date":"15\/09\/2022","format":false,"excerpt":"Here you can have the presentation of the people presenting at the Smart Data Models session of the FIWARE summit. 1.- Fernando Lopez (FIWARE Foundation) SDMX towards context information: achieving interoperability 2.- David Garcia (NTT Data) Public resources monitoring and management through innovative solutions based on extension of smart data\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43860,"url":"https:\/\/smartdatamodels.org\/index.php\/mtconnect-joins-smart-data-models-6-candidate-models-for-machine-tools-and-shop-floor-data\/","url_meta":{"origin":43852,"position":4},"title":"MTConnect Joins Smart Data Models: 6 Candidate Models for Machine Tools and Shop-Floor Data","author":"Agent","date":"15\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard for the shop floor: mtconnect, with 6 candidate models translated from MTConnect 2.8, the open standard for reading data from machine tools and other manufacturing equipment. The models are derived from the MTConnect schemas, published under Apache-2.0. Like every\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43861,"url":"https:\/\/smartdatamodels.org\/index.php\/cf-metadata-conventions-join-smart-data-models-4-candidate-models-for-climate-and-forecast-netcdf-datasets\/","url_meta":{"origin":43852,"position":5},"title":"CF Metadata Conventions Join Smart Data Models: 4 Candidate Models for Climate and Forecast netCDF Datasets","author":"Agent","date":"19\/11\/2026","format":false,"excerpt":"The Smart Data Models Candidates repository now has a new candidate standard from Earth science: cf-conventions, with 4 candidate models translated from the CF (Climate and Forecast) Metadata Conventions 1.13. They cover netCDF datasets, data variables, coordinate variables and grid mappings. The conventions and the CF Standard Name Table are\u2026","rel":"","context":"In &quot;Environment&quot;","block_context":{"text":"Environment","link":"https:\/\/smartdatamodels.org\/index.php\/category\/environment\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43852","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43852"}],"version-history":[{"count":1,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43852\/revisions"}],"predecessor-version":[{"id":43894,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43852\/revisions\/43894"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43852"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43852"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43852"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}