Added TOC top links

Author: schnuerle

policy/README.md

@@ -25,12 +25,16 @@ This specification describes the digital relationship between _mobility as a ser
 
 The following information applies to all `policy` API endpoints.
 
+[Top][toc]
+
 ### Versioning
 
 `policy` APIs must handle requests for specific versions of the specification from clients.
 
 Versioning must be implemented as specified in the [Versioning section][versioning].
 
+[Top][toc]
+
 ## Background
 
 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 of policies include:
@@ -63,6 +67,8 @@ Policies should be re-fetched whenever:
 
 Flat files have an optional `end_date` field that will apply to the file as a whole.
 
+[Top][toc]
+
 ### REST Endpoints
 
 Among other use-cases, configuring a REST API allows an Agency to:
@@ -112,6 +118,8 @@ Method: `GET`
 | ------------ | --------- | --- | ---------------------------------------------- |
 | `id`         | UUID      | Optional    | If provided, returns one geography object with the matching UUID; default is to return all geography objects.               |
 
+[Top][toc]
+
 ### Flat Files
 
 To use flat files, policies shall be represented in two (2) files:
@@ -184,6 +192,8 @@ Response bodies must be a `UTF-8` encoded JSON object and must minimally include
 }
 ```
 
+[Top][toc]
+
 ### Policy
 
 An individual `Policy` object is defined by the following fields:
@@ -201,6 +211,8 @@ An individual `Policy` object is defined by the following fields:
 | `prev_policies`  | UUID[]          | Optional    | Unique IDs of prior policies replaced by this one                                   |
 | `rules`          | Rule[]          | Required   | List of applicable [Rule](#rules) objects |
 
+[Top][toc]
+
 ### Rules
 
 An individual `Rule` object is defined by the following fields:
@@ -225,6 +237,8 @@ An individual `Rule` object is defined by the following fields:
 | `messages`         | `{ String:String }`         | Optional   | Message to rider user, if desired, in various languages, keyed by language tag (see [Messages](#messages)) |
 | `value_url`        | URL                         | Optional   | URL to an API endpoint that can provide dynamic information for the measured value (see [Value URL](#value-url)) |
 
+[Top][toc]
+
 ### Rule Types
 
 | Name    | Description                                                                                                   |
@@ -235,6 +249,8 @@ An individual `Rule` object is defined by the following fields:
 | `rate`  | **[Beta feature](/general-information.md#beta-features):** Yes (as of 1.0.0). Fees or subsidies based on regions and time spent in one or more vehicle-states. Rule `rate_amount` refers to the rate charged according to the [Rate Recurrence](#rate_recurrence). Agencies and Providers must agree on terms of use prior to utilizing the `rate` rule type.     |
 | `user`  | Information for users, e.g. about helmet laws. Generally can't be enforced via events and telemetry.          |
 
+[Top][toc]
+
 ### Rule Units
 
 | Name      | Description         |
@@ -246,6 +262,8 @@ An individual `Rule` object is defined by the following fields:
 | `mph`     | Miles per hour      |
 | `kph`     | Kilometers per hour |
 
+[Top][toc]
+
 ### Geography
 
 | Name             | Type      | Required / Optional | Description                                                                         |
@@ -258,6 +276,8 @@ An individual `Rule` object is defined by the following fields:
 | `publish_date`   | [timestamp][ts] | Required   | Timestamp that the policy was published, i.e. made immutable                                             |
 | `prev_geographies`  | UUID[]    | Optional   | Unique IDs of prior geographies replaced by this one                                   |
 
+[Top][toc]
+
 ### Rate Recurrences
 
 Rate recurrences specify when a rate is applied – either once, or periodically according to a `time_unit` specified using [Rule Units](#rule-units). A `time_unit` refers to a unit of time as measured in local time for the juristiction – a day begins at midnight local time, an hour begins at the top of the hour, etc.
@@ -268,6 +288,8 @@ Rate recurrences specify when a rate is applied – either once, or periodicall
 | `each_time_unit`            |  During each `time_unit`, rate is applied once to vehicles entering or remaining in a matching status. Requires a `time_unit` to be specified using `rule_units`.  |  
 | `per_complete_time_unit`    | Rate is applied once per complete `time_unit` that vehicles remain in a matching status. Requires a `time_unit` to be specified using `rule_units`.  | 
 
+[Top][toc]
+
 ### Messages
 
 Some Policies as established by the Agency may benefit from rider communication. This optional field contains a map of languages to messages, to be shown to the user.
@@ -283,6 +305,8 @@ Example for a decreased speed-limit rule for Venice Beach on weekends:
 },
 ```
 
+[Top][toc]
+
 ### Value URL
 
 An Agency may wish to provide dynamic or global rules, e.g.
@@ -299,6 +323,8 @@ The payload returned from a `GET` request to the `value_url` will have the follo
 | `timestamp` | [timestamp][ts] | Required   | Timestamp the value was recorded    |
 | `policy_id` | UUID      | Required         | Relevant `policy_id` for reference  |
 
+[Top][toc]
+
 ### Order of Operations
 
 Rules, being in a list, are ordered **most specific** to **most general**. E.g. an "earlier" rule (lower list index) would take precedence over a "later" rule (higher list index).