Issues to fix before 1.0 DCC

[onthebreeze]

Impacted sections

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

Issue Description

• Need to support text as well as numeric value in declaration / assessment Metric class.

[PatStLouis]

We would like to see codes added to the assessorLevelCode, assessmentLevelCode and attestationTypeCode to reflect regulator issued attestation. The current codes are aimed at third party issuance and doesn't quite fit our use case.

My suggestions are as follows:

assessorLevelCode

code: Regulator
name: Regulator Assessment
description: conformity assessment by a regulator

assessmentLevelCode

code: Regulated
name: Government regulation
description: conformity assessment delivered in relation to a regulation from a national or regional government

attestationTypeCode

code: permitting
name: permitting
description: An authorization document issued by a regulatory body.

[onthebreeze]

from brett:

Definition DPCC-01 “Assurance level” is incorrect, as it contradicts both the displayed Logical Model and the Implementation Guidance from the same Github page.
Definition number is wrong since there is already a DCC-01 (named ‘Authorised’, which relates to the issuing party).
‘Assurance level’ is the wrong term, since the definition provided exclusively relates to the ‘endorsement’ entity (which is cross-referenced as ‘authorisation’ in the Implementation Guidance), as well as being potentially confused with the unrelated term ‘assessment_level which describes ‘how assured is the assessment process’.
It is indicated to be a MUST, which seems incorrect, as an endorsement (or authorisation, however named) should be optional