feat: add additional criteriea to TC002 and TC003 (w/ @zeitgeist)

Author: raimundo-henriques

specs/index.bs

@@ -2770,10 +2770,10 @@ system with a valid access token and the syntax specified in [PACT Tech Specs V2
 
 #### Expected Response #### {#test-case-001-response}
 
-The test target host system must respond with 200 OK with a JSON body containing a list
+The test target host system must respond with 200 OK with a JSON body containing a list of
 `ProductFootprints` (as per the [PACT Tech Specs V2.2
-§api-action-list-response](https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-response)),
-those which include `productIds` with [the format specified for ShipmentFootprints](#pcf-mapping-sf)
+§api-action-list-response](https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-response)).
+Those which include `productIds` with [the format specified for ShipmentFootprints](#pcf-mapping-sf)
 must be conformant with the Data Model specified in [[#dt-sf]]. The relevant properties of the
 `ProductFootprint` must also be confomant with the guidance provided in [[#pcf-mapping-sf]].
 
@@ -2787,12 +2787,17 @@ system with a valid access token and the syntax specified in [PACT Tech Specs V2
 
 #### Expected Response #### {#test-case-002-response}
 
-The test target host system must respond with 200 OK with a JSON body containing a list
+The test target host system must respond with 200 OK with a JSON body containing a list of
 `ProductFootprints` (as per the [PACT Tech Specs V2.2
-§api-action-list-response](https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-response)),
-those which include `productIds` with [the format specified for TOCs](#pcf-mapping-toc) must be
-conformant with the Data Model specified in [[#dt-toc]]. The relevant properties of the
-`ProductFootprint` must also be confomant with the guidance provided in [[#pcf-mapping-toc]].
+§api-action-list-response](https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-response)).
+
+This list must include all the `TOCs` referenced in the `ShipmentFootprint`s returned in
+[[#test-case-001]] (identified through the `productIds` field) and may include others.
+
+All the `ProductFootprints` which include `productIds` with [the format specified for
+TOCs](#pcf-mapping-toc) must be conformant with the Data Model specified in [[#dt-toc]]. The
+relevant properties of the `ProductFootprint` must also be confomant with the guidance provided in
+[[#pcf-mapping-toc]].
 
 ### Test Case 003: Get ProductFootprint with HOC ### {#test-case-003}
 
@@ -2804,12 +2809,17 @@ system with a valid access token and the syntax specified in [PACT Tech Specs V2
 
 #### Expected Response #### {#test-case-003-response}
 
-The test target host system must respond with 200 OK with a JSON body containing a list
+The test target host system must respond with 200 OK with a JSON body containing a list of
 `ProductFootprints` (as per the [PACT Tech Specs V2.2
-§api-action-list-response](https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-response)),
-those which include `productIds` with [the format specified for HOCs](#pcf-mapping-hoc) must be
-conformante with the Data Model specified in [[#dt-hoc]]. The relevant properties of the
-`ProductFootprint` must also be confomant with the guidance provided in [[#pcf-mapping-hoc]].
+§api-action-list-response](https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-response)).
+
+This list must include all the `HOCs` referenced in the `ShipmentFootprint`s returned in
+[[#test-case-001]] (identified through the `productIds` field) and may include others.
+
+All the `ProductFootprints` which include `productIds` with [the format specified for
+HOCs](#pcf-mapping-hoc) must be conformante with the Data Model specified in [[#dt-hoc]]. The
+relevant properties of the `ProductFootprint` must also be confomant with the guidance provided in
+[[#pcf-mapping-hoc]].
 
 ### Test Case 004: Get All TransportActivityData ### {#test-case-004}