fixup: fix headers, add structure to occurance details

Signed-off-by: Todd Baert <[email protected]>

Author: toddbaert

specification.json

@@ -1095,6 +1095,20 @@
             "content": "If the client's `track` function is called and the associated provider does not implement tracking, the client's `track` function MUST no-op.",
             "RFC 2119 keyword": "MUST",
             "children": []
+        },
+        {
+            "id": "Requirement 6.2.1",
+            "machine_id": "requirement_6_2_1",
+            "content": "The `occurrence details` structure MUST define an optional numeric `value`, associating a scalar quality with an `occurrence`.",
+            "RFC 2119 keyword": "MUST",
+            "children": []
+        },
+        {
+            "id": "Requirement 6.2.2",
+            "machine_id": "requirement_6_2_2",
+            "content": "The `occurrence details` MUST support the inclusion of custom fields, having keys of type `string`, and values of type `boolean | string | number | structure`.",
+            "RFC 2119 keyword": "MUST",
+            "children": []
         }
     ]
 }

specification/sections/06-tracking.md

@@ -80,18 +80,22 @@ See: [context levels and merging](./03-evaluation-context.md#32-context-levels-a
 
 > If the client's `track` function is called and the associated provider does not implement tracking, the client's `track` function **MUST** no-op.
 
-## 6.2. Occurrence Details
+### 6.2. Occurrence Details
 
 The `occurrence details` structure defines optional data pertinent to a particular `occurrence`.
 
-### Requirement 6.2.1
+#### Requirement 6.2.1
 
 > The `occurrence details` structure **MUST** define an optional numeric `value`, associating a scalar quality with an `occurrence`.
 
 `Value` is a well-defined field which some providers may map to equivalent numeric values in their API.
 
 See [provider tracking support](./02-providers.md#27-tracking-support).
 
-### Requirement 6.2.2
+#### Requirement 6.2.2
 
-> The `occurrence details` **MUST** support the inclusion of custom fields, having keys of type `string`, and values of type `boolean | string | number`.
+> The `occurrence details` **MUST** support the inclusion of custom fields, having keys of type `string`, and values of type `boolean | string | number | structure`.
+
+The `occurrence details` supports the addition of arbitrary fields, including nested objects, similar to the `evaluation context` and object-typed flag values.
+
+See [structure](../types.md#structure), [evaluation context](.//03-evaluation-context.md).