You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: policy/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Versioning must be implemented as specified in the [Versioning section][versioni
61
61
62
62
## Background
63
63
64
-
The goal of this specification is to enable Agencies to create, revise, and publish machine-readable policies, as sets of rules for individual and collective device behavior exhibited by both _mobility as a service_Providers and riders / users. [Examples](./examples/README.md) of policies include:
64
+
The goal of the Policy API specification is to enable agencies to create, revise, and publish machine-readable policies, as sets of rules for individual and collective device behavior exhibited by both _mobility as a service_providers and riders / users. [Examples](./examples/README.md) of policies include:
65
65
66
66
- City-wide and localized caps (e.g. "Minimum 500 and maximum 3000 scooters within city boundaries")
67
67
- Exclusion zones (e.g. "No scooters are permitted in this district on weekends")
@@ -70,7 +70,7 @@ The goal of this specification is to enable Agencies to create, revise, and publ
70
70
- Idle-time and disabled-time limitations (e.g. "5 days idle while rentable, 12 hours idle while unrentable, per device")
71
71
- Trip fees and subsidies (e.g. "A 25 cent fee applied when a trip ends downtown")
72
72
73
-
The machine-readable format allows Providers to obtain policies and compute compliance where it can be determined entirely by data obtained internally.
73
+
The machine-readable format allows Providers to obtain policies and compute compliance where it can be determined entirely by data obtained internally, and know what data is required from them and provided to them.
74
74
75
75
**See the [Policy Examples](./examples/README.md) for ways these can be implemented.**
76
76
@@ -114,7 +114,7 @@ See the [Responses section][responses] for information on valid MDS response cod
114
114
115
115
### Authorization
116
116
117
-
Authorization is not required. An agency may decide to make this endpoint unauthenticated and public. See [Optional Authentication](/general-information.md#optional-authentication) for details.
117
+
Authorization is not required and agencies are encouraged to make these endpoints unauthenticated and public. See [Optional Authentication](/general-information.md#optional-authentication) for details.
118
118
119
119
### Policies
120
120
@@ -139,7 +139,7 @@ Policies will be returned in order of effective date (see schema below), with pa
139
139
140
140
### Geographies
141
141
142
-
**Deprecated:** see the new [Geography API](/geography#transition-from-policy) to understand the transistion away from this endpoint, and how to support both in a MDS 1.x.0 release.
142
+
**Deprecated:** see the new [Geography API](/geography#transition-from-policy) to understand the transistion away from this endpoint, and how to support both in MDS 1.x.0 releases.
0 commit comments