EBL 3.0: SD-2934: Update What's New for PINT v3.0.0

[HenrikHL]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Add What's New documentation for PINT v3.0.0 Beta 2026TBD

📝 Documentation

Walkthroughs

Description

• Add release notes for PINT v3.0.0 Beta 2026TBD
• Document Transport Document schema updates and improvements
• List new platform onboardings and endpoint examples
• Detail deprecated fields and extended field support

Diagram

flowchart LR
  A["PINT v3.0.0 Beta 2026TBD"] --> B["Transport Document Changes"]
  A --> C["Platform & Code Updates"]
  A --> D["Endpoint Improvements"]
  B --> E["Extended HS/Commodity Codes"]
  B --> F["Nested innerPackagings"]
  B --> G["Address & Facility Fields"]
  C --> H["3 New Platforms Added"]
  C --> I["Deprecated Fields Marked"]

Loading

File Changes

1. pint/v3/README.md 📝 Documentation +23/-0

Document PINT v3.0.0 Beta 2026TBD release notes

• Added comprehensive release notes for PINT v3.0.0 Beta 2026TBD snapshot
• Documented Transport Document schema changes including extended HS codes, extended national
 commodity codes, and nested innerPackagings support
• Listed three new platform onboardings: DocuTrade (DOCU), AEOTrade (AEOT), and SGTraDex (SGTD)
• Detailed deprecations of HSCodes, nationalCommodityCodes, and chargeName with their extended
 replacements
• Documented new fields including addressLines, facilityName, role in VesselVoyage, and eblPlatform
 in party objects

pint/v3/README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0) 📐 Spec deviations (0)

1. Placeholder release identifier 🐞 Bug ⚙ Maintainability

Description

The new v3.0.0 Beta entry uses placeholder values ("2026TBD" / "TBD 2026") in the anchor and
SwaggerHub URL; once the real snapshot identifier is known, renaming will break stable deep-links to
this changelog section. This repo’s OpenAPI specs already deep-link into README anchors for
changelog navigation, so an unstable anchor is likely to cause broken references later.

Code

pint/v3/README.md[R12-14]

+<a name="v300B2026TBD"></a>[Release v3.0.0 Beta 2026TBD (TBD 2026)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_EBL_PINT/3.0.0-Beta-2026TBD)
+---
+Snapshot as of TBD 2026 for EBL Platform Interoperability 3.0.0 Beta. Purpose of the snapshot is to align with eBL v3.0.3. Appart from changes to Transport Document, examples on endpoints have been improved and 3 new platforms have been added.

Evidence

The README introduces a placeholder anchor/link for the release entry. Separately, PINT OpenAPI YAML
files link directly to README anchors (URL fragments) for changelog navigation; changing the anchor
later would invalidate those links.

pint/v3/README.md[12-14]
pint/v3/EBL_PINT_v3.0.0-Beta-2.yaml[41-45]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`pint/v3/README.md` adds a new release entry whose anchor (`v300B2026TBD`) and linked SwaggerHub version (`3.0.0-Beta-2026TBD`) contain placeholders. Once the actual snapshot identifier/date is known, changing the anchor will break any existing deep-links to this section.

## Issue Context
Other files in this repo (OpenAPI YAML descriptions) already link to README anchors as changelog references (e.g., `.../pint/v3#v300B2`). To avoid future broken links, anchors should be stable once published.

## Fix Focus Areas
- pint/v3/README.md[12-14]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Typos in release notes 🐞 Bug ⚙ Maintainability

Description

The newly added release notes contain multiple spelling errors (e.g., "Appart", "gramatical",
"giong"), reducing clarity and professionalism of the published changelog. These should be corrected
before merging/publishing.

Code

pint/v3/README.md[R14-30]

+Snapshot as of TBD 2026 for EBL Platform Interoperability 3.0.0 Beta. Purpose of the snapshot is to align with eBL v3.0.3. Appart from changes to Transport Document, examples on endpoints have been improved and 3 new platforms have been added.
+- examples on endpoints have been added
+- `errorCode` description updated
+- removed `TODO` comments
+- `eblPlatform` and `codeListProvider` lists updated with platforms that have been onboarded to the DCSA eBL APIs
+  - `DOCU` (DocuTrade)
+  - `AEOT` (AEOTrade)
+  - `SGTD` (SGTraDex)
+- **Transport Document** changes:
+  - corrected many descriptions for typos and gramatical errors (`numberOfOriginalsWithCharges`, `numberOfOriginalsWithoutCharges`, Reference and ReferenceConsignmentItem `type`, `OuterPackaging`, `packageCode`, `numberOfPackages`, OuterPackaging `description`, `innerPackagings`, `NetExplosiveContent`, NetExplosiveContent `description`, `InnerPackaging`, `UtilizedTransportEquipment`, `VesselVoyage`, `street`, `streetNumber`, `floor`, `postCode`, `city` and `stateRegion`)
+  - `HSCodes` marked as deprecated everywhere, `extendedHSCodes` to be used instead
+  - `extendedHSCodes` added in order to support 12 character codes
+  - `nationalCommodityCodes` marked as deprecated everywhere, `extendedNationalCommodityCodes` to be used instead
+  - `extendedNationalCommodityCodes` added in order to support 16 character codes
+  - `innerPackagings` can now have a nested `innerPackagings` to allow multiple innerPackaging-layers
+  - `role` added to `VesselVoyage` in order to specify the vessel as being: `FIRST_SEA_GOING` (First sea giong vessel) or `MOTHER` (Mother vessel)
+  - an unstructured address object called `addressLines` added to: `PlaceOfReceipt`, `PlaceOfDelivery` and `OnwardInlandRouting`. Also added to the following party objects: `Shipper`, `OnBehalfOfShipper`, `Consignee`, `OnBehalfOfConsignee`, `Endorsee`, `CarriersAgentAtDestination`, `NotifyParty`, general `Party` and `IssuingParty`

Evidence

The new release-note paragraph and bullets include the misspellings directly in the added text.

pint/v3/README.md[14-30]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Fix spelling errors in the new v3.0.0 Beta release note section to improve readability.

## Issue Context
Examples present in the added text include:
- "Appart" -> "Apart"
- "gramatical" -> "grammatical"
- "giong" -> "going"

## Fix Focus Areas
- pint/v3/README.md[14-30]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more