If a vehicle is matched with a rule, then it _will not_ be considered in the sub  The internal mechanics of ordering are up to the Policy editing and hosting software. +[Top][toc]++### Requirement++The agency Policy Requirement file ennumerates all of the parts of MDS that an agency requires from providers, including APIs, endpoints, and optional fields, as well as information for providers about the APIs the agency is hosting. The requirements are specific to the needs and use cases of each agency, and ensures there is clarity on what data is being asked for in operating policy documents from providers, reducing the burden on both. This also allows additional public transparency and accountability around data requirements from agencies, and encourages privacy by allowing agencies to ask for only the data they need.++This endpoint it not authenicated (ie. public), and allows the discovery of other public APIs like Geography, Policy, and Jurisdiction. The agency can host this as a file or API on their servers, on a third party server, or the OMF can host on behalf of an agency in the [agency requirements repo](#). See this [hosting guidance document](#) for more information.  This requirements file can be [referenced directly](https://github.com/openmobilityfoundation/governance/blob/main/technical/OMF-MDS-Policy-Language-Guidance.md) in an agency's operating permit/policy document when discussing program data requirements.++See [Policy Requierment Examples](/policy/examples/requirements.md) for how this can be implemented.++An agency's [Requirements](#requirements) endpoint contains a number of distinct parts, namely [metadata](#requirement-metadata) and [MDS version](#requirement-mds-version) (with sub sections on applicable providers and relevant [MDS APIs](#requirement-mds-apis)). ++```jsonc+{+  "metadata": {+    // metadata fields per the "Requirement Metadata" section+  },+  "mds_versions" [ +    {+      "version" : "[MDS VERSION NUMBER]",+      "provider_ids": [+        // provider id array+      ],+      "mds_apis": [+        {+          "api_name" : "[MDS API]": {+            // MDS endpoints, urls, optional fields+          }+        },+        // other MDS APIs per the "Requirement MDS APIs" section+      ]+    }, +    // other MDS versions per the "Requriement MDS Version" section+  }+}+```+[Top][toc]++#### Requirement Metadata++Contains metadata applicable to the agency and at the top of its [Requirement](#requirement) data feed in the `metadata` section. ++| Name                         | Type            | Required / Optional | Description              |+| ---------------------------- | --------------- | -------- | ----------------------------------- |+| `mds_release`                | text            | Required | Release of MDS that the requirements data feed aligns to, based on official MDS releases. E.g. "1.2.0" |+| `version`                    | integer         | Required | Version of this file. Increment 1 with each modification. E.g. "3" |+| `last_updated`               | [timestamp][ts] | Required | When this file `version` was last updated. E.g. "1611958740" |+| `max_update_frequency`       | integer         | Required | The expected maximum frequency with which this file could be updated. E.g. "P1D" |+| `omf_review`                 | Enum            | Required | yes/no. Was this file reviewed by OMF Staff for accuracy? E.g. "yes" |+| `omf_review_date`            | [timestamp][ts] | Optional | If `omf_review`, add timestamp. E.g. "1611958749" |+| `agency_uuid`                | UUID            | Required | UUID of the agency this file applies to. Must come from [agencies.csv](/agencies.csv) file. E.g. "737a9c62-c0cb-4c93-be43-271d21b784b5" |+| `agency_name`                | text            | Required | Name of the agency this file applies to. E.g. "Louisville Metro" |+| `agency_time_zone`           | text            | Required | Timezone used for dates and times across all MDS endpoints. E.g. "America/New_York" |+| `agency_currency`            | text            | Required | Currency used for all monetary values across all MDS endpoints. E.g. "USD" |+| `agency_policy_website_url`  | URL             | Required | URL of the agency's transportation policy page. E.g. "https://www.cityname.gov/transporation/shared-devices.htm" |+| `agency_policy_document_url` | URL             | Optional | URL of the agency's operating permit rules that mention data requirements. E.g. "https://www.cityname.gov/mds_data_policy.pdf" |+| `gbfs_required`              | Enum            | Required | yes/no. Is public GBFS required explicitly by providers? E.g. "yes" |+| `url`                        | URL             | Required | URL of this file. E.g.  "https://mds.cityname.gov/requirements/1.2.0" |++[Top][toc]++#### Requirement MDS Version++Contains a list of providers and APIs/endpoints/fields that a version of MDS applies to in its [Requirement](#requirement) data feed. Unique combinations for MDS versions and specific providers can be defined. For example an agency can devine MDS version 1.2.0 for Provider #1 in a pilot with beta endpoints and optional fields, version 1.2.0 for other providers without beta features, and version 1.1.0 for Provider #2 with docked bikeshare. ++```jsonc+// ...  +  "mds_versions": [+    {+      "version" : "[MDS VERSION NUMBER]",+      "provider_ids": [+        "[PROVIDER UUID]",+        "[PROVIDER UUID]"+      ],+      "mds_apis" [+        {+          // ...+        },+        // other MDS APIs+      ]+    }+  ]+// ...+```++| Name                         | Type           | Required / Optional | Description              | +| ---------------------------- | -------------- | -------- | ----------------------------------- | +| `version`                    | text           | Required | Version number of an official MDS release | +| `provider_ids`               | UUID[]         | Required | Array of providers that apply to this part of the requirements | ++[Top][toc]++#### Requirement MDS APIs++For each combination of MDS version and provider list, you can specify the MDS APIs, endpoints, and optional fields that are required per your agency's policy. This is an array within the [Requirement MDS Version](#requirement-mds-version) `mds_apis` section in the [Requirement](#requirement) data feed.