From ab0029bb91f874931292ebc5502b130ad9a8f5ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Thu, 24 Apr 2025 16:19:05 +0200 Subject: [PATCH 1/5] SD-2138: CS 1.0: Release notes for Patch 1.0.1 --- cs/v1/README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/cs/v1/README.md b/cs/v1/README.md index c5c0ffad4..675ec4f75 100644 --- a/cs/v1/README.md +++ b/cs/v1/README.md @@ -2,6 +2,20 @@ The DCSA Commercial Schedules API is specified on [**SwaggerHub**](https://app.swaggerhub.com/apis/dcsaorg/DCSA_CS). +[Release v1.0.1 (25 April 2025)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_CS/1.0.1) +--- +This is a patch release for the DCSA Commercial Schedules API. The primary purpose of this patch is to include the `routingReference` property in the Point-to-point responses in order to be able to reference a route in [Booking](https://github.com/dcsaorg/DCSA-OpenAPI/tree/master/bkg/v2). Here is a list of changes + +- `routingReference` property added to the PointToPoint object. +- `maxTranshipment` query parameter description imporved to explain meaning of a "transhipment" +- `facilitySMDGCode` query parameter description improved +- remove the reference to `ISO 8601` (all dateTime fields must comply with [RFC 3339, section 5.6](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)), affecting the following query parameters: `startDate` and `endDate`, the following properties: `dateTime` (in `PlaceOfReceipt`, `PlaceOfDelivery`, `PlaceOfArrival` and `PlaceOfDeparture`), `eventDateTime` (in Timestamp), `cutOffDateTime` (in CutOffTime), `errorDateTime` (in ErrorResponse) +- typos and punctuation fixed in descriptions +- `operatorCarrierCodeListProvider` and `carrierCodeListProvider` descriptions improved in order to list the enum values +- remove Servers list that was wrongly added (no Virtual Servers are connected to DCSA APIs) + +Link to [commits included in this patch](https://github.com/dcsaorg/DCSA-OpenAPI/commits/master/cs/v1/CS_v1.0.1.yaml?since=2024-01-15&until=2025-04-25) + ### [Release v1.0.0 (24 September 2024)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_CS/1.0.0) --- From 5650b92ae3080b4764f9d8f189680bf289b79f25 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Thu, 24 Apr 2025 16:35:06 +0200 Subject: [PATCH 2/5] Improve release notes --- cs/v1/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/v1/README.md b/cs/v1/README.md index 675ec4f75..99f01cd0d 100644 --- a/cs/v1/README.md +++ b/cs/v1/README.md @@ -12,7 +12,10 @@ This is a patch release for the DCSA Commercial Schedules API. The primary purpo - remove the reference to `ISO 8601` (all dateTime fields must comply with [RFC 3339, section 5.6](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)), affecting the following query parameters: `startDate` and `endDate`, the following properties: `dateTime` (in `PlaceOfReceipt`, `PlaceOfDelivery`, `PlaceOfArrival` and `PlaceOfDeparture`), `eventDateTime` (in Timestamp), `cutOffDateTime` (in CutOffTime), `errorDateTime` (in ErrorResponse) - typos and punctuation fixed in descriptions - `operatorCarrierCodeListProvider` and `carrierCodeListProvider` descriptions improved in order to list the enum values +- `facilitySMDGCode`, `startDate` and `endDate` descriptions have been improved +- Github link to reference data for `cutOffDateTimeCode` has been removed - remove Servers list that was wrongly added (no Virtual Servers are connected to DCSA APIs) +- Contact Us link update to **https://dcsa.org/get-involved/contact-us** Link to [commits included in this patch](https://github.com/dcsaorg/DCSA-OpenAPI/commits/master/cs/v1/CS_v1.0.1.yaml?since=2024-01-15&until=2025-04-25) From babf7893d2fd86e29a35be2741fbf4545b845ad1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Thu, 24 Apr 2025 16:56:15 +0200 Subject: [PATCH 3/5] Fix typo Co-authored-by: palatsangeetha <138600841+palatsangeetha@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 99f01cd0d..11c98f484 100644 --- a/cs/v1/README.md +++ b/cs/v1/README.md @@ -14,7 +14,7 @@ This is a patch release for the DCSA Commercial Schedules API. The primary purpo - `operatorCarrierCodeListProvider` and `carrierCodeListProvider` descriptions improved in order to list the enum values - `facilitySMDGCode`, `startDate` and `endDate` descriptions have been improved - Github link to reference data for `cutOffDateTimeCode` has been removed -- remove Servers list that was wrongly added (no Virtual Servers are connected to DCSA APIs) +- removed Servers list that was wrongly added (no Virtual Servers are connected to DCSA APIs) - Contact Us link update to **https://dcsa.org/get-involved/contact-us** Link to [commits included in this patch](https://github.com/dcsaorg/DCSA-OpenAPI/commits/master/cs/v1/CS_v1.0.1.yaml?since=2024-01-15&until=2025-04-25) From ed2826d7180e11506297b9a67292917e0a9692d5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Fri, 25 Apr 2025 09:32:49 +0200 Subject: [PATCH 4/5] Update tran**ss**hipment --> tran**s**hipment --- cs/v1/CS_v1.0.1.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/v1/CS_v1.0.1.yaml b/cs/v1/CS_v1.0.1.yaml index b0c61265d..41db94875 100644 --- a/cs/v1/CS_v1.0.1.yaml +++ b/cs/v1/CS_v1.0.1.yaml @@ -202,7 +202,7 @@ paths: description: | Specifies the maximum number of transhipments that the proposed routings can have in the response. By default, transhipments are allowed and the responses can have either direct routings or routings with transhipment. The default value of maximum transhipments is defined by the carrier for when the consumer does not provide a value. If the user sets the number of transhipments to 0, only direct routings can be returned in the response. - **Note:** According to the DCSA definition, a “transshipment” specifically refers to transferring containers or cargo from one vessel to another, focusing exclusively on ocean transport. This means that, under the current interpretation, only vessel-to-vessel transfers are counted as transshipments. Moves between road, rail, or barge and a vessel (i.e., inland legs) do not fall under this definition and, therefore, should not be counted as transshipments. + **Note:** According to the DCSA definition, a “transhipment” specifically refers to transferring containers or cargo from one vessel to another, focusing exclusively on ocean transport. This means that, under the current interpretation, only vessel-to-vessel transfers are counted as transhipments. Moves between road, rail, or barge and a vessel (i.e., inland legs) do not fall under this definition and, therefore, should not be counted as transhipments. - schema: type: string enum: From d2a874a7cedbcb7f40b7fe43335089a82e747ac0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Helm=C3=B8=20Larsen?= Date: Fri, 25 Apr 2025 09:48:32 +0200 Subject: [PATCH 5/5] Remove duplicate --- cs/v1/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/cs/v1/README.md b/cs/v1/README.md index 11c98f484..c7df6bed0 100644 --- a/cs/v1/README.md +++ b/cs/v1/README.md @@ -8,7 +8,6 @@ This is a patch release for the DCSA Commercial Schedules API. The primary purpo - `routingReference` property added to the PointToPoint object. - `maxTranshipment` query parameter description imporved to explain meaning of a "transhipment" -- `facilitySMDGCode` query parameter description improved - remove the reference to `ISO 8601` (all dateTime fields must comply with [RFC 3339, section 5.6](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6)), affecting the following query parameters: `startDate` and `endDate`, the following properties: `dateTime` (in `PlaceOfReceipt`, `PlaceOfDelivery`, `PlaceOfArrival` and `PlaceOfDeparture`), `eventDateTime` (in Timestamp), `cutOffDateTime` (in CutOffTime), `errorDateTime` (in ErrorResponse) - typos and punctuation fixed in descriptions - `operatorCarrierCodeListProvider` and `carrierCodeListProvider` descriptions improved in order to list the enum values