From ae1ca642e3d9a39ccaacc4873f4a88f747ccb1a0 Mon Sep 17 00:00:00 2001 From: "henrik.larsen@dcsa.org" Date: Tue, 8 Sep 2026 14:23:28 +0200 Subject: [PATCH 1/3] CS 1.0: SD-3258: Add isCargoOperationalCall to TransportCall --- cs/v1/CS_v1.0.4.yaml | 15 +++++++++++++++ cs/v1/README.md | 8 ++++++++ 2 files changed, 23 insertions(+) diff --git a/cs/v1/CS_v1.0.4.yaml b/cs/v1/CS_v1.0.4.yaml index 4c28d8f3..8cde2321 100644 --- a/cs/v1/CS_v1.0.4.yaml +++ b/cs/v1/CS_v1.0.4.yaml @@ -1051,6 +1051,21 @@ components: $ref: '#/components/schemas/CutOffTime' location: $ref: '#/components/schemas/TransportCallLocation' + isCargoOperationalCall: + type: boolean + default: true + description: | + Indicates whether cargo loading and/or discharge is applicable at the transport call. + - `true`: cargo loading and/or discharge is applicable. + - `false`: cargo loading and discharge are not applicable. + - If omitted, the value **MUST** be interpreted as `true`. + + The property is independent of whether the associated timestamps are Planned (`PLN`), Estimated (`EST`) or Actual (`ACT`). It does not indicate whether cargo was actually loaded or discharged. + + Other activities, such as bunkering, do not change this classification when cargo operations are also applicable. + + Consumers requiring only cargo-operational calls can filter out calls where this property is `false`. + example: false timestamps: type: array minItems: 1 diff --git a/cs/v1/README.md b/cs/v1/README.md index f027d5b1..b3e706ab 100644 --- a/cs/v1/README.md +++ b/cs/v1/README.md @@ -3,6 +3,14 @@ The DCSA Commercial Schedules API is specified on [**SwaggerHub**](https://app.swaggerhub.com/apis/dcsaorg/DCSA_CS). [Release v1.0.4](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_CS/1.0.4) +--- +Identify cargo-operational calls in Vessel Schedules. + +- Added optional `isCargoOperationalCall` to `TransportCall` in Vessel Schedules to indicate whether cargo loading and/or discharge is applicable at the call. + - If omitted, the value **MUST** be interpreted as `true`. + - `false` indicates that neither cargo loading nor discharge is applicable, allowing consumers to filter these calls while retaining access to the complete published vessel rotation. + - The classification is independent of Planned (`PLN`), Estimated (`EST`) or Actual (`ACT`) timestamps and does not indicate whether cargo was actually loaded or discharged. + - Calls combining cargo operations with other activities, such as bunkering, remain cargo-operational. [Release v1.0.3 (12 June 2026)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_CS/1.0.3) --- From ffad0971a4b56dbd1728ee21514d638e51391f79 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Tue, 8 Sep 2026 14:33:57 +0200 Subject: [PATCH 2/3] Fix review comment Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- cs/v1/CS_v1.0.4.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/v1/CS_v1.0.4.yaml b/cs/v1/CS_v1.0.4.yaml index 8cde2321..d5b0af11 100644 --- a/cs/v1/CS_v1.0.4.yaml +++ b/cs/v1/CS_v1.0.4.yaml @@ -1057,7 +1057,7 @@ components: description: | Indicates whether cargo loading and/or discharge is applicable at the transport call. - `true`: cargo loading and/or discharge is applicable. - - `false`: cargo loading and discharge are not applicable. + - `false`: cargo loading and/or discharge are not applicable. - If omitted, the value **MUST** be interpreted as `true`. The property is independent of whether the associated timestamps are Planned (`PLN`), Estimated (`EST`) or Actual (`ACT`). It does not indicate whether cargo was actually loaded or discharged. From a5f539923b50d26db918e24b1b7e280ebb507498 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Tue, 8 Sep 2026 14:34:37 +0200 Subject: [PATCH 3/3] Fix review comment Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- cs/v1/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/v1/README.md b/cs/v1/README.md index b3e706ab..4ac424c5 100644 --- a/cs/v1/README.md +++ b/cs/v1/README.md @@ -8,7 +8,7 @@ Identify cargo-operational calls in Vessel Schedules. - Added optional `isCargoOperationalCall` to `TransportCall` in Vessel Schedules to indicate whether cargo loading and/or discharge is applicable at the call. - If omitted, the value **MUST** be interpreted as `true`. - - `false` indicates that neither cargo loading nor discharge is applicable, allowing consumers to filter these calls while retaining access to the complete published vessel rotation. + - `false` indicates that neither cargo loading nor cargo discharge is applicable, allowing consumers to filter these calls while retaining access to the complete published vessel rotation. - The classification is independent of Planned (`PLN`), Estimated (`EST`) or Actual (`ACT`) timestamps and does not indicate whether cargo was actually loaded or discharged. - Calls combining cargo operations with other activities, such as bunkering, remain cargo-operational.