Skip to content

ConformityCredential Product vs DPP Product

Created by: Fak3

On the ConformityCredential diagram There is a Product class, which has properties testedBatchId and verifiedByCAB which do not belong to the generic Product, but to the particular ConformityAsessment Screenshot_20240613_131738 If there are multiple ConformityAsessment of the same product, the resulting graph will appear confusing, as json object nesting is lost at the graph level:

- type: ConformityAsessment
  subjectProducts:
  - id: product1
    testedBatchId: goodBatch1
- type: ConformityAsessment
  subjectProducts:
  - id: product1
    testedBatchId: badBatch1

will result in RDF graph triples:

product1 testedBatchId goodBatch1;
product1 testedBatchId badBatch1;

The association of product batch to the measured results is lost.

One potential way to correctly model the graph is to introduce ProductAsessment class:

classDiagram
    ConformityAsessment <|-- ProductAsessment
    ProductAsessment <|-- Product
    class ConformityAsessment{
      ProductAsessment subjectProducts
    }
    class ProductAsessment{
      URI testedBatchId
      Product product
    }
    class Product{
      Identifier indentifier
      Text modelName
    }

Another way could be to rename Product to the ProductAsessment, so that the assessment has unique id, distinct form the Product id