Missing property for 'structuredness' of an evidence exchange

[SebastianSK]

In short:
In Germany the structuredness of a digital evidence in the national data exchange is measured in the so called "Reifegrad".
At EU OOTS level currently (TDD 1.1.0) there is only the mimetype of an evidence giving a hint on the data minimisation capacities of data providers.

Building a German knowledge graph on evidences and procedural requirements in the RegCheck project (see [CCCEV-AP.de] (http://cccev-ap.de/) or http://offene-daten.de/Verwaltung for more information ) we suggest to you to also implement this concept of maturity of evidence exchange at EU OOTS level.
The original project requirement is tracked here: (GERMAN) RegCheck2024/RegCheck#8

In detail:

The model was refined in 2024 to distinguish even more the extent of fullfiling the data minimisation principle
See IT-planning council decision:
https://www.it-planungsrat.de/beschluss/beschluss-2024-15.

The model reads as follow:

A - paper based evidence
B - evidences for electronic exchange
C - evidences for structured electronic exchange
D1 - evidences with only the minimum information requested
D2 - response to a specific criteria

This concept of "structuredness" of the evidence is meant to be a metadata on abilities of the provider side. (such as Mime-Type). It helps to understand, to what granularity an evidence exchange can be supported.

Evidences in SDG can then be

A. non digital (A)
2. non structured (B),
3. structured (regardless whether XML, JSON, PDF or other) (C)
4. taylored to the minimum data set of a procedural requirement (D1)
5. or even be a simple type response like "yes", "no", or "1984" (D2)

In the EU OOTS SDG-Implementation the model of "structuredness" currently is rather naivly coupled with the filetype:
It is the mime-Type of an evidence that indirectly tells about "structured" or "not structured" evidence exchange.
https://code.europa.eu/oots/tdd/tdd_chapters/-/blob/master/OOTS-EDM/codelists/OOTS/OOTSMediaTypes-CodeList.gc

<Row>
         <Value ColumnRef="code">
            <SimpleValue>application/pdf</SimpleValue>
         </Value>
         <Value ColumnRef="name-Value">
            <SimpleValue>.pdf</SimpleValue>
         </Value>
         <Value ColumnRef="name-Structure">
            <SimpleValue>unstructured</SimpleValue>
         </Value>
      </Row>

I see the need to distiguish the MimeType from the "structuredness" of an evidence
Please note, that there is also PDF with structured XML embedded in use in Germany (DIGIZ - digitales Schulzeugnis)

Having made good experience with the German Reifegradmodell 2.0 it is therefore suggested:

• to gather whether similar concepts are used in the national implementations of the Member States

• to discuss about adding this concept "structuredness" or "data minimisation readyness" in general at EU-Level

• to discuss in the SDG subgroups or Gateway coordination group it's impact on the report of national implementation plans, the evidence survey, semantic repository, Common Service API (former LCM) and the evidence explorer

• to discuss such a property at CCCEV-AP level in the EvidenceType class at next webmeetings

• to create an authority table structuredness at least in German and in English (idealy in all EU languages) as an publications office authority table, so the property has a good governed vocabulary where to point to.