Proposal: Add description field to ConformityClaim for human-readable context

[ashleythedeveloper]

Impacted sections

• https://uncefact.github.io/spec-untp/docs/specification/DigitalProductPassport

Issue Description

Currently, conformity claims within a DPP rely primarily on referencing standard/regulation names for human readability (e.g. "ISO 12405-4:2018 - Test specification for lithium-ion traction battery packs and systems"). While technically accurate, this approach may not provide sufficient context for general audiences to understand what the claim represents.

Current Digital Product Passport Example:

{
...restOfDPP,
"conformityClaim": [
      {
        "type": [
          "Claim",
          "Declaration"
        ],
        "id": "https://certifier.example.com/attestations/2024-001",
        "assessmentDate": "2024-03-15",
        "conformance": true,
        "conformityTopic": "social.safety",
        "conformityEvidence": {
          "type": [
            "SecureLink",
            "Link"
          ],
          "linkURL": "https://idr.untp.showthething.com/gs1/gtin/09359502000034?linkType=gs1:certificationInfo",
          "linkName": "Conformity Evidence"
        },
        "referenceStandard": {
          "type": [
            "Standard"
          ],
          "id": "https://www.iso.org/standard/71407.html",
          "name": "ISO 12405-4:2018 - Test specification for lithium-ion traction battery packs and systems",
          "issuingParty": {
            "type": [
              "Identifier"
            ],
            "id": "https://www.iso.org",
            "name": "International Organization for Standardization"
          },
          "issueDate": "2018-02-15"
        },
        "declaredValue": [
          {
            "type": [
              "Metric"
            ],
            "metricName": "Short Circuit Test Temperature Rise",
            "metricValue": {
              "type": [
                "Measure"
              ],
              "value": 0,
              "unit": "CEL"
            },
            "accuracy": 0.01,
            "score": "A"
          },
          {
            "type": [
              "Metric"
            ],
            "metricName": "Maximum Operating Temperature",
            "metricValue": {
              "type": [
                "Measure"
              ],
              "value": 55,
              "unit": "CEL"
            },
            "accuracy": 0.01,
            "score": "A"
          }
        ]
      }
    ]
}

Rendering

It would be desirable if implementors had a way to provide additional human-friendly context about conformity claims being made beyond just referencing the standard or regulation name that could then be used within the rendering of the credential (human-friendly version).

Proposal:
Add a description field to the ConformityClaim type to allow implementors to express a human-friendly description of what the claim represents.

Example:

{
  "conformityClaim": {
    "type": ["Claim", "Declaration"],
    "id": "https://certifier.example.com/attestations/2024-001",
    "description": "This battery pack meets international safety standards for thermal management and operating temperatures, ensuring safe operation in electric vehicles",
    "conformance": true,
    "referenceStandard": {
      "name": "ISO 12405-4:2018 - Test specification for lithium-ion traction battery packs and systems"
    }
  }
}

[absoludity]

So the description can't be altered once a conformance certificate for the claim has been attached or linked? (ie. otherwise it would be trivial for people to mis-represent what has been checked). Also will be important that the description is part of what is verified for conformance too, I guess?