EBL 3.0: SD-2543: Update issuanceManifestSignedContent description

[HenrikHL]

User description

SD-2543: Update the description for issuanceManifestSignedContent to make it more clear

---

PR Type

Documentation

---

Description

• Clarifies issuanceManifestSignedContent description for better understanding

• Expands scope to include carrier agents as signers

• Reformats description text for improved readability

---

Diagram Walkthrough

flowchart LR
  A["issuanceManifestSignedContent<br/>description"] -- "expanded to include<br/>carrier agents" --> B["Clarified signer<br/>scope"]
  A -- "reformatted for<br/>readability" --> C["Single paragraph<br/>format"]

Loading

File Walkthrough

	Relevant files
Documentation	EBL_ISS_v3.0.2.yaml Expand and clarify issuanceManifestSignedContent description ebl/v3/issuance/EBL_ISS_v3.0.2.yaml Updated issuanceManifestSignedContent description to clarify that payload can be signed by carrier or authorized agents Reformatted multi-line description into single paragraph for better readability Maintained all technical references to RFC 7515 and IssuanceManifest schema +1/-4

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Input validation weakness Description: The regex pattern for JWS (^[A-Za-z0-9_-]+.[A-Za-z0-9_-]+.[A-Za-z0-9_-]+$) excludes base64url padding-less characters only and disallows periods in header/payload/signature beyond the two separators, but does not enforce base64url character set for all cases (acceptable) while also potentially allowing empty segments; verify that empty segments cannot occur and that this lenient pattern is intended. EBL_ISS_v3.0.2.yaml [315-315] Referred Code JWS content with compact serialization according to [RFC 7515](https://datatracker.ietf.org/doc/html/rfc7515#section-7.1). JWS-signed payload is defined in schema [IssuanceManifest](#/IssuanceManifest). This attribute is used to provide integrity of various parts of the payload that enable parties to validate whether a payload matches what the carrier issued originally. Accordingly, the payload is signed by the carrier or a party (typically an agent) acting on behalf of the carrier. # TODO: Update example
Ticket Compliance
🟢	🎫 #SD-2543 🟢 Update the definition/description of issuanceManifestSignedContent to explicitly state it is JWS content with compact serialization per RFC 7515 section 7.1. Reference that the JWS-signed payload is defined in the `IssuanceManifest` schema. Explain that the attribute provides integrity for parts of the payload so parties can validate it matches what the carrier originally issued. Clarify that the payload may be signed by the carrier or a party (typically an agent) acting on behalf of the carrier.
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.

Compliance status legend

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

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Improve readability of long description To improve readability, use a YAML folded block scalar (>) for the long description and wrap the text across multiple lines. ebl/v3/issuance/EBL_ISS_v3.0.2.yaml [314-315] -description: | - JWS content with compact serialization according to [RFC 7515](https://datatracker.ietf.org/doc/html/rfc7515#section-7.1). JWS-signed payload is defined in schema [IssuanceManifest](#/IssuanceManifest). This attribute is used to provide integrity of various parts of the payload that enable parties to validate whether a payload matches what the carrier issued originally. Accordingly, the payload is signed by the carrier or a party (typically an agent) acting on behalf of the carrier. +description: > + JWS content with compact serialization according to [RFC 7515](https://datatracker.ietf.org/doc/html/rfc7515#section-7.1). + JWS-signed payload is defined in schema [IssuanceManifest](#/IssuanceManifest). + This attribute is used to provide integrity of various parts of the payload that enable parties to + validate whether a payload matches what the carrier issued originally. + Accordingly, the payload is signed by the carrier or a party (typically an agent) acting on behalf of the carrier. Apply / Chat Suggestion importance[1-10]: 4 __ Why: The suggestion correctly identifies a readability issue with a very long line and proposes a valid improvement using a YAML folded block scalar (>) to enhance maintainability.	Low
More