Skip to content

Commit a343752

Browse files
authored
Updated unique policy definition
Signed-off-by: Michael Schnuerle <1285077+schnuerle@users.noreply.github.com>
1 parent 18ce1ac commit a343752

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

policy/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Policies shall be published by regulatory bodies or their authorized delegates a
114114

115115
Policies typically refer to one or more associated geographies. Geographic information is obtained from the MDS [Geography](/geography) API. Each policy and geography shall have a unique ID (UUID).
116116

117-
Policies must be unique. A Policy may not have the exact same [Policy](#policy) object field values with a different `policy_id`. For example if the `mode_id`, `provider_ids`, `start_date`, `end_date`, and `rules` fields have the same values, that is the same Policy and must not be duplicated as two different policies in the Policy payload.
117+
Policies must be unique. A Policy may not have the exact same [Policy](#policy) object field values with a different `policy_id`. For example if the required or optional fields have the same values (either exactly identical or functionally identical), it is considered the same Policy and must not be duplicated as two different policies in the Policy payload.
118118

119119
Geographical data shall be represented as GeoJSON `Feature` objects. No part of the geographical data should be outside the [municipality boundary][muni-boundary].
120120

0 commit comments

Comments
 (0)