EBL 3.0: DT-2511: Update UTE description

[HenrikHL]

User description

DT-2511: Update UtilizedTransportEquipment description

---

PR Type

Documentation

---

Description

• Update UtilizedTransportEquipment schema descriptions across multiple files

• Clarify container equipment information and related details

• Standardize description format for consistency

• Remove references to calculated fields (weight, volume)

---

Diagram Walkthrough

flowchart LR
  A["UtilizedTransportEquipment<br/>Schemas"] -- "Update descriptions" --> B["Clarified<br/>Equipment Info"]
  A -- "Remove calculated<br/>field references" --> C["Standardized<br/>Format"]
  B --> D["EBL v3.0.3"]
  B --> E["EBL ISS v3.0.3"]
  B --> F["EBL PINT v3.0.0"]

Loading

File Walkthrough

Relevant files

Documentation

EBL_v3.0.3.yaml Update UTE schema descriptions                                                      ebl/v3/EBL_v3.0.3.yaml Updated UtilizedTransportEquipment description to clarify equipment information and remove weight/volume references Updated UtilizedTransportEquipmentShipper description with consistent format Updated UtilizedTransportEquipmentHBL description to match standardized format +3/-3      EBL_ISS_v3.0.3.yaml Update UTE description in issuance schema                                ebl/v3/issuance/EBL_ISS_v3.0.3.yaml Updated UtilizedTransportEquipment description to clarify equipment information and remove calculated field references +1/-1      EBL_PINT_v3.0.0.yaml Update UTE description in PINT schema                                        pint/v3/EBL_PINT_v3.0.0.yaml Updated UtilizedTransportEquipment description to clarify equipment information and remove weight/volume references +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟢	🎫 #SD-2511 🟢 Update the UtilizedTransportEquipment description in TD to remove mention of total weight and total volume. Replace the current description with: “Specifies the container (equipment) information, possible ActiveReeferSettings, seals, references, and other related details.”
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[Copilot]

Pull request overview

This PR standardizes the description of the UtilizedTransportEquipment schema across multiple EBL API specification files. The key change is removing references to calculated fields (weight and volume) and adopting a more generic description format that mentions "container information" and "related details" instead of enumerating specific fields.

• Removed explicit mentions of weight and volume from schema descriptions
• Standardized description format across different schema variants
• Fixed inconsistent capitalization in field references

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
pint/v3/EBL_PINT_v3.0.0.yaml	Updated UtilizedTransportEquipment description to remove weight/volume references and use standardized format
ebl/v3/issuance/EBL_ISS_v3.0.3.yaml	Updated UtilizedTransportEquipment description to match the standardized format
ebl/v3/EBL_v3.0.3.yaml	Updated three schema variants (UtilizedTransportEquipment, UtilizedTransportEquipmentShipper, UtilizedTransportEquipmentHBL) with consistent descriptions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add missing property to description Add the missing references property to the description of UtilizedTransportEquipmentHBL for consistency. ebl/v3/EBL_v3.0.3.yaml [7260-7264] UtilizedTransportEquipmentHBL: type: object title: Utilized Transport Equipment (House B/L) description: | - Specifies the container (`equipment`) information, `seals` and other related details. + Specifies the container (`equipment`) information, `seals`, `references`, and other related details. [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that references was likely omitted by mistake from the description of UtilizedTransportEquipmentHBL, making it inconsistent with both its previous version and other similar objects updated in this PR.	Low
Update