+
+
+
## Description
The digital product passport application provides a consumer user interface to request a battery passport from a battery manufacturer using the standardized components and technologies in a Catena-X network. The passport will be displayed in a human-readable from any browser. The data exchange standards given by Catena-X are used to provide the battery passport to different personas (roles) in the network.
diff --git a/docs/media/dpp-tx-logo.png b/docs/media/dpp-tx-logo.png
new file mode 100644
index 000000000..abbd7960f
Binary files /dev/null and b/docs/media/dpp-tx-logo.png differ
diff --git a/dpp-backend/digitalproductpass/.gitignore b/dpp-backend/digitalproductpass/.gitignore
index c44a0bd71..0deb76d1f 100644
--- a/dpp-backend/digitalproductpass/.gitignore
+++ b/dpp-backend/digitalproductpass/.gitignore
@@ -44,6 +44,8 @@ target/
*.iml
*.ipr
+bin/
+
### NetBeans ###
/nbproject/private/
/nbbuild/
diff --git a/dpp-verification/README.md b/dpp-verification/README.md
new file mode 100644
index 000000000..ffacc57bb
--- /dev/null
+++ b/dpp-verification/README.md
@@ -0,0 +1,933 @@
+
+
+
+
+
+
+
+
+
Catena-X Data Verification Framework
+
Digital Product Pass Verification Add-on
+
+
+
+> [!CAUTION]
+> This documentation is still in progress... Not all the content is yet available. It is being migrated and published here whenever it is ready. It will be finished and added to main in the R24.05
+
+# Metadata
+
+| | Date | Authors & Reviewers |
+| -------------------- | ----------------- | ----------------------------------------------------- |
+| **Created** | December 29, 2023 | [Mathias Brunkow Moser](https://github.com/matbmoser) |
+| **Lastest Revision** | May 13, 2024 | [Mathias Brunkow Moser](https://github.com/matbmoser) |
+
+## Authors
+
+
+| Name | Company | GitHub | Role |
+| --------------------- | ------- | ------------------------------------------ | --------------------------------------- |
+| Mathias Brunkow Moser | CGI | [@matbmoser](https://github.com/matbmoser) | Digital Product Pass Software Architect |
+| | | | |
+| | | | |
+
+## Tags
+
+> [!NOTE]
+> #Cybersecurity #DataVerification #DataCertification #Catena-X #DigitalProductPassVerification #DPP #SignedDocuments #DataCredentials # Framework
+> #DigitalProductPass #VerifiableCredentials #Wallets #DecentralIdenties #SSI #ProductDataExchangeTrust #Verification #Innovation #Ed25519 #JWS #Web3.0
+
+
+
+# Abstract
+
+When talking about increasing trust in data ecosystems there are multiple possible ways to be followed. Contractual and Policy solutions can be taken into consideration to ensure data sovereignty based on analog framework agreement contracts. Blockchain solutions can be implemented to assure that transactions and ownership is mathematically proofed, creating a assertive level of trust in the complete chain. Artificial Intelligence can be used as a neutral party for doing moderation and certification of data of partners and member of the network. However if you want to maintain your data and identify under your control assuring data sovereignty and keeping it decentral the best option to choose are Decentral Identities from the W3C.
+
+Decentralized Identities are already used in the Catena-X Network to digitally identify parties and authorizations across all data exchanges done through an EDC from a peer to peer perspective. This technology is implemented in the current SSI concept used in the network and has been proofed to work and also to be successful when bringing trust to all the data exchanges done which take place in the network.
+
+The data exchanged during the peer to peer connections between EDCs can have different formats, shapes and content. It varies from use case to use case and its up to the owner of the data to choose which data will be provided to who and which one not. However once this data is exchanged there is no assertive way to determine if the data provided is really true or false. Framework agreements cover the legal part of the transaction and participation in the use cases however do not cover the specific product information assertion and confirmation of veracity.
+
+Product Information Certification is the way to go when it comes to creating trust over complete or partial data provided in peer to peer connections between two partners in a network. Once the consumer is allowed to visualize the data he can verify if it was certified by its data issuer or by an external auditor party. This is relevant when we start to talk about bringing the Catena-X Automotive Network to a productive environment, specially where human lives are at stake and mistakes can cause huge monetary and image losses.
+
+This Digital Product Pass Verification and Certification concept aims to create an assertive second layer of trust over the actual peer to peer data exchanges of Product Information. Basing itself in the SSI technology already in place in Catena-X, this concept sets the first steps for data verification statements creation starting with the CX Generic Digital Product Pass Aspect Model. Giving the data providers the possibility of creating self signed documents confirming the information placed into the aspect models and gives data auditors the possibility to certify one or more specific attributes from Aspect Model documents that are relevant to the data provider business cases. It allows the data consumer to base its processes and decisions based on actual production data which has been assertive verified by external auditors, giving safety that not just the data issuer by also a third party has certified that specific data is true or compliant to standards.
+
+The technology concept consists of creating Signed Documents (Verification Statements) using the Verifiable Credentials 2.0 Technology. Which is in resume a JSON-LD structure standardized by the W3C Consortium for Web 3.0 for data trust and identity assurance. Using JSON Web Signatures (JWS) and a wallet component which is connected to Catena-X and identified by the unique company Business Partner Number (BPN), the data issuer and auditor can sign using their Ed25519 private key and the data consumer can access their public key by resolving the DID contained in the signature proof at the certified document credential. The certified data will be stored in the Data Provider infrastructure sub-model server, in order to assure the data sovereignty. Data consumer can access this data if they are allowed by the data provider simply by looking for the Digital Twin from the specific asset type or instance depending on the specific use case. This data will be retrieved using the EDC connector proxy which is protected by Policies and require data consumers to sign "odrl" contracts to maintain data sovereignty.
+
+In this way decentralize data exchange trust is assertive assured. Making possible and easing the transition from the Catena-X network product data exchange from Pre-Production to Production environments. Enabling better decision taking, saving possible human lives, boosting the circular economy use case, creating justification as form of digital proof for possible framework contracts trust breaks or frauds, assuring product quality and increasing employee safety when hazard materials/products are handled.
+
+This concept has been proved to be of high interest from the Certification and Verification roles in the Catena-X Community, generating value for multiple use cases and bringing the Catena-X Network Data Exchange Trust Level to a totally new level. Enabling the different network parties to exchange data with electronic proof of an external party certification revision, reducing the risk of failure and error. Allowing data consumers to comfortably invest and deposit their trust in bring their data into a Catena-X Network Production Data Ecosystem Environment.
+
+## Table of Contents
+
+- [Metadata](#metadata)
+ - [Authors](#authors)
+ - [Tags](#tags)
+- [Abstract](#abstract)
+ - [Table of Contents](#table-of-contents)
+- [Introduction](#introduction)
+ - [Value Proposition Motivators](#value-proposition-motivators)
+ - [Objectives](#objectives)
+ - [Use Cases](#use-cases)
+- [Previous Investigation](#previous-investigation)
+- [Processes Terminology](#processes-terminology)
+ - [**Roles/Actors**](#rolesactors)
+ - [Abstract Interaction (Business Interaction)](#abstract-interaction-business-interaction)
+ - [Document Exchange Details](#document-exchange-details)
+- [Asumptions](#asumptions)
+- [Verification Statements](#verification-statements)
+ - [Abstract Types](#abstract-types)
+ - [Verification Statements Documents/Credentials](#verification-statements-documentscredentials)
+- [Creating Trust and Risk Mitigation Assets](#creating-trust-and-risk-mitigation-assets)
+ - [Verifiable Credential Documents](#verifiable-credential-documents)
+ - [What is a Verifiable Credential?](#what-is-a-verifiable-credential)
+ - [Credential Schema](#credential-schema)
+- [Certification Processes](#certification-processes)
+ - [Attribute Certification Process](#attribute-certification-process)
+ - [Self-Testify Certification Process](#self-testify-certification-process)
+ - [Total Certification Process](#total-certification-process)
+- [Certification and Verification Methods](#certification-and-verification-methods)
+ - [Certified Snapshot Credential](#certified-snapshot-credential)
+ - [Certified Data Credential](#certified-data-credential)
+ - [Complete Data Certification Verification](#complete-data-certification-verification)
+- [Verification Processes](#verification-processes)
+ - [Flow Diagrams](#flow-diagrams)
+ - [CDC Technical Verification Flow](#cdc-technical-verification-flow)
+ - [CSC Technical Verification Flow](#csc-technical-verification-flow)
+- [Technical Specification](#technical-specification)
+ - [Certification Aspects Schemas](#certification-aspects-schemas)
+ - [Certified Data Credential Schema](#certified-data-credential-schema)
+ - [Certified Snapshot Credential Schema](#certified-snapshot-credential-schema)
+ - [Attribute Certification Registry](#attribute-certification-registry)
+- [Technical Integration Design](#technical-integration-design)
+ - [Interfaces](#interfaces)
+ - [Certification Sequence Diagrams](#certification-sequence-diagrams)
+ - [CSC Certification Sequence Diagram](#csc-certification-sequence-diagram)
+ - [CDC + CSC Certification Sequence Diagram](#cdc--csc-certification-sequence-diagram)
+ - [Verification Sequence Diagrams](#verification-sequence-diagrams)
+ - [CSC Verification Sequence Diagram](#csc-verification-sequence-diagram)
+ - [CDC + CSC Verification Sequence Diagram](#cdc--csc-verification-sequence-diagram)
+- [References](#references)
+- [Special Thanks](#special-thanks)
+- [Glossary](#glossary)
+ - [NOTICE](#notice)
+ - [AUTHORS](#authors-1)
+
+
+# Introduction
+
+This Documentation contains the first concept of Data Verification in Catena-X. This verification aims to create a second layer of trust over the EDC data exchanges between consumers and data providers. Allowing auditors to verify specific attributes or complete aspect models for data providers and allowing consumers to retrieve and verify the "validity" of the verification done.
+
+## Value Proposition Motivators
+
+When talking about certification and verification of data there are a series of motivators that create value for data exchanges done in a production environment.
+
+| | Motivator | Description |
+| --- | --------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| 1 | Trustworthiness | Important for **Accurate Decision Taking** and **Money Loss Avoidance** |
+| 2 | Quality Assurance | Proof the quality of the products and be able to **audit product quality standards** |
+| 3 | Regulatory Compliance | For regulatory reasons in some specific products a **rigorous verification process is mandatory to protect consumers.** |
+
+## Objectives
+
+When defining for the first time the way of doing certification and verification of data aspect models and digital product passports in Catena-X some objectives must be set.
+
+In case of the use case we are aiming our objectives are the following:
+
+1. **Create Value and Draft a Verification Process**
+ - Get external verifiers to check the data and generate verifiable credentials or certificates.
+ - Define a process for the business verification of data
+ - Investigate on the existing market solutions
+ - Talk with Catena-X Partners for defining a solid Verification Process draft
+
+2. **Implement the Verification Concept in Catena-X**
+ - Design a technical concept for verifying passports in Catena-X
+ - **“Be able to verify the data without changing the existent architecture”.**
+ - Investigate on existent verification solutions in Catena-X
+ - Research and talk with other Catena-X Components/Use Cases about how to integrate the verification in the network.
+ - Implement a Technical PoC in the Digital Product Pass application
+
+3. **Define how to create Verification Statements in Catena-X**
+ - Set the first steps for other use cases like PCF Verification which need a Verification Statement to be defined.
+ - Create a technical solution that can be scaled to other aspect models rather than the Digital Product Pass Use Case
+ - Talk with different use cases/components in Catena-X to find a common way of using the network to Certify and Verify data.
+ - Following the CX Standards and ideas like Data Sovereignty, Decentralization and Self Sovereign Identities (SSI)
+
+Once this objectives are achieved we will be able to scale the solution and implemented in real life so the benefits of the technology and process defined here can contribute to the automotive industry and increase trust in data exchanges using Catena-X.
+
+## Use Cases
+
+When talking about the certification and verification of data we can find several use cases. Here we have some examples:
+
+| Name | Description |
+| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Assuring Product Quality** | The final serialized product data manufactured may have flaws/imperfections that can be detected with external type level verified aspects. |
+| **Digital Proof of Trust Breaks** | If contractual clauses are broken, having external verified proofs of the actual data provided at a specific time **can be used as legal assets.** This increases the trust of exchanging real production data in Catena-X |
+| **Employee Safety Assurance** | When handling/maintaining a product which contains **critical raw materials**, confirming that the materials present on the product can prevent accidents and fatal human loses. |
+| **Production Inefficiency Detection** | When assets are not performing as they were “design” for, external verified attributes **can certify inefficiency** of the product performance in use. Leading to future changes in manufacturing and design. |
+| **Human Life Handling Products** | Products which handle human lives like Cars, Airplanes and Trains have a strict regulation when it comes to Data Quality requiring the **critical specification data to be “certified/verified** **”** before production for safety reasons |
+| **Easing Decision Taking** | When companies need to take important decisions, having external verified attributes/aspect can make a huge difference in which way to go or which product to choose. |
+| **Secure Data Against Fraud** | The data providers by verifying and signing digitately their data when issued, are **transparently being protected against fraud or false accusations**, because they can demonstrate the data was verified by an external auditors or their internal quality management. |
+
+# Previous Investigation
+
+> [!WARNING]
+> Previous investigation is still not available here!
+
+
+# Processes Terminology
+
+The naming from the different processes is important when it comes to differentiating the role from each actor.
+
+The process terminology from **Data Consumer** to **Data Provider** is called **Data Verification Process** and can optionally be also done between the data auditor and the data consumer.
+
+The other terminology from **Data Provider** to **Data Auditor** is called **Data Certification Process.**
+
+
+
+| **Process Terminology** | **Actors** | **Description** | **Artifacts** |
+| :---------------------- | :----------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-----------------------------------------------------: |
+| **Data Verification** | Data Consumer, Data Provider, Data Auditor | The data verification process englobes the complete journey from retrieving data as a data consumer from a data provider. It includes the search for verification statements and attribute level verification in digital twins.At the end of the journey attribute specific verification may or not be found. Other types of verification like self attestations may be or not retrieved. Depends in the available verification information.In the data verification process is included the verification of the signatures included in the data created and certified in the Data Certification Process. | **Verification Result** *with the status/flaws* |
+| **Data Certification** | Data Provider, Data Auditor | The data certification process includes all the processes related to triggering the verification until providing the data for certifying specific attributes.The data provider triggers the certification for a external or internal data auditor, which generates and optionally stores a verification statements | **Certified Data Aspects** *as Verification Statements* |
+
+## **Roles/Actors**
+Three main roles are defined and have certain responsibilities or can conduct actions in the processes. Each role can have more than one W3C role and generate different artifacts as specified in the following table:
+
+| **Role/Actors** | **Company Types** | **W3C Roles** | **Responsibilities/Actions** | **Use Cases** | **Artifacts** |
+| :-------------- | ------------------------------------------------------------ | ---------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Data Provider | OEMs, Tier-1 | Issuer, Holder | - Creating and Issuing Data- Refence/Provision of data in a Digital Twin Registry - Store and link complete data submodels in a infrastructure - **[OPTIONAL]:** Self-sign data when issuing aspects - **[OPTIONAL]:** Provide and Store certified credentials from external parties - Store link to external parties certified credential aspects in Digital Twin Registry - Requests and pays external parties (data auditors) to audit their data | As a data provider I want to be able to hand over my data to consumers and auditors. I want also to be able to manage my data and verified assets. In some cases I want to be able to self-testify my own issued data. | **Digital Twin + Submodels with EDC Endpoints for CDC and CSC** Certified Data Credential (CDC) or Plain **Digital Product Pass** **[OPTIONAL]:** Storage of Certified Snapshot Credentials (CSC) in **Verification Statements Aspect** |
+| Data Auditor | Auditors, Certification Agencies, Consulting Companies, OEMs | Issuer, **Optional: Holder** | - Selects from the data provider data some attributes following selective disclosure.- Certifies Attributes against "methods". And indicate in the generated credential which methods were used for certifying For example: - Standards - Rulebooks - Regulations - Manuals - Technical Specifications - etc...- Creates and issues a **Certified Verification Statement**- **[OPTIONAL]:** Provide and Store certified credentials | As a data auditor I want to be able to retrieve and visualize the data I need to audit. I also want to be able to "select" then "certify" specific attributes I was payed to audit by a Data Provider. | Certified Snapshot Credentials (CSC) in **Verification Statements Aspect** **[OPTIONAL]:** Storage of Verification Aspect and provision through EDC |
+| Data Consumer | Recyclers, Dismantlers, OEMs, Tier-1 | Verifier | - Initializes the data retrieval process (Requesting the Data Provider).- Searches for the Verification Data after the data retrieval process. (Looking in the Data Provider Digital Twin)- Verifies signatures against a wallet if the data and attribute credentials received are correct.- Verifies data semantics and data plausibility against the data model semantics/restrictions.- Presents the verification result | As a data consumer I want to be able to know if the data I received is verified and which attributes are certified by an external auditor. I also want to be able to verify that the data certified is authentic and has been issued and signed by a Data Auditor or a Data Provider | **Verification Result Presentation** |
+
+### Abstract Interaction (Business Interaction)
+
+In the following diagram we can observe how the data provider, the data auditor and the data consumer interact:# Certification Processes
+
+
+
+The **Data Provider** is always the one that has control from its own data, following the data sovereignty concept. He offers its own data to the **data consumers** and **data auditors**.
+The **Data Consumer** `verifies` the data incoming from the **data provider** and certified by the **data auditor**.
+The **Data Auditor** retrieves data from the **data provider** and `certifies` the data against standards, then sends the `verification statement or certificate` to the **data provider**.
+
+### Document Exchange Details
+
+The different roles will exchange different document which will contain, information and proof of the data which is being exchanged.
+
+
+
+**Data Providers** will be providing data for the *Data Consumers* and the *Data Auditors*.
+This data may vary depending on the data exchanged and certified by the *Data Auditors*. The auditors
+
+# Asumptions
+
+When we talk about verification and certification processes, serveral questions and concerns can be raised in regards of making it productive and implementable.
+When a concept is developed not all the processes and problems can be addressed, therefore this concept has some conditions that should be considered.
+Therefore we have decided to list the initial asumptions that are required for this verification process to be successful:
+
+| Asumption | Description |
+| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Digital Product Pass Process Creation is established** | The digital product pass process is a complex process that is implemented in each *Data Provider* and is tailored to the systems and application avaialable in each company. This concepts starts its journey from the assumption that the digital product pass data is already available in the **Data Provider** infrastructure as a **Serialized Aspect Model Payload** |
+| **Data Exchange is Standardized** | As we know in Catena-X the data exchange between partners in this case need to be standardized, there fore the digital product pass data and all the related statements will be standardized and available for all members of the network to be able to parse and handle the fields and certifications. |
+| **Data Certification Process is defined by Data Auditor** | The complexity of the certification process is high and can vary from auditor company to company. Therefore in this concept there was decided to resume the certification of attributes to the most unitary and simple **Technical Solution**, allowing each company to adopt and implement the process according to its needs and requirements. |
+| **Only minimum exchanged data is specified** | Only the minimum exchanged data is specified when transfering data from one company to another. When a certification process is triggered there are many other attributes, data and elements to be specified. Only the neccessary attributes to retrieve the data are specified in this concept to keep things simple and indicate the MVP attributes needed to make it possible. |
+| **All legal requirements are fullfilled** | In this company we asume that the company has all the neccessary legal requirements and agreements to exchange data with its partners in the Catena-X network, policies and permissions are not going to be specified, all the EDC configurations are the ones specified by the Catena-X network. For more information [see this specification](https://github.com/catenax-eV/cx-odrl-profile). |
+| **The digital product pass standards are followed** | The digital twin registry and data service must be implemented as indicated in the latest CX standard for digital product passports and other products. |
+| **The certification and verification are not limited to digital product passports** | This concept sets the initial path to verify any aspect model payload in Catena-X that uses JSON as its serialized representation. The concept is tailored to digital product passports since the **EcoDesign** regulations are playing a important role in the future of Data Ecosystems like *Catena-X*. |
+| **The wallets used in the concept allow to sign any type of credential** | In order for the concept to work the wallets need to be able to sign any credential document using the private key, and also enable the "DID" endpoint to retrieve the public keys through the internet (DID WEB). |
+| **Each company MUST have an decentral wallet** | In order to sign the credentials by your own as company you need to have a valid that fits to the decentralized wallets concept that is going to be standardized in Catena-X. |
+| **All data exchanges are done through the Eclipse DataSpace Connector** | Every company **MUST** have a EDC in order to provide data to othere parties and consume data from other partners. Data sovereighty is followed and shall use the guidelines provided by the Catena-X network. |
+
+# Verification Statements
+
+For our technical implementation from the Certification/Verification of aspect models and attributes we can abstract two type of verification statements:
+
+## Abstract Types
+
+| Type | Description |
+| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Complete Data Verification Statement | Self Signed Document containing the complete data from a aspect model payload. |
+| Partial Data Verification Statement | Attribute level certified document containing one or more attributes from the **Complete Data Verification Statement** or from a **Plain JSON Aspect Model payload**. |
+
+
+## Verification Statements Documents/Credentials
+
+The different verificaiton statement types were mapped to certain technical verification statement documents which encapsulate the certification and verification of attributes in the framework. Using the **Verifiable Credential** technology from the W3C we are able to idenfity to different documents to have signature from different issuers:
+
+> [!TIP]
+>
+> For more information about what is a verifiable credential [go to this chapter](#what-is-a-verifiable-credential).
+
+
+| Document/Credential Name | Short Name | Issuer | Verification Statement Type | Content | Description |
+| --------------------------------- | ---------- | ------------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Certified Data Credential** | **CDC** | Data Provider | Complete Data Verification Statement | 1. Complete Aspect Model Payload Data 2. Signature from Data Issuer 3. Version Control | Credential that contains the complete passport and is signed by the issuer of the data. It allows to track changes during the updates from the passport in the supply chain. It can be "self-testified" by the data provider when creating/issuing the passport data. |
+| **Certified Snapshot Credential** | **CSC** | Data Auditor | Partial Data Verification Statement | 1. Selected attributes from the Aspect Model Payload Data 2. Hashed "proofs" per attribute and data auditor signature 3. Methods used to "certify" each attribute 4. Reference to Audited Complete Verification Statement Content | Credential that follows "selective disclosure" by hashing the verified fields allowing the verification in milliseconds by just comparing hashes. It contains the "partial" digital product pass. It is signed by the Auditor of the data attributes at the end of the certification, indicating the attributes which are included there were certified against specific "methods". |
+
+# Creating Trust and Risk Mitigation Assets
+
+> Why to place trust in companies which certify data?
+
+The companies auditing the data must be authorized and given the trust
+from another member party to issue data related credentials. Only
+
+We know we humans make mistakes. When third party companies already known
+in the business of providing trust and certifications for specific assets. This assets would be audited or its original data would be audited, and then will be compared to the different **Regulations**, **Standards** and **Rulebooks** that define if the data content is:
+
+- Certify data plausibility (that the values make sense)
+- Certify that the attribute values in the data that follow the standards.
+- Certify Structure and semantics that follow the standards
+- Certify that the actual physical asset has the content which is placed in the Digital Product Pass serialized or type payload.
+- Certify that issuance of data to prevent fraud
+
+## Verifiable Credential Documents
+
+The idea behind the verifiable credentials is to provide signed proof
+for a content. This credential is a JSON-LD structure, which contains
+the "data" that was certified and the proof is able to be verified by
+resolving the "DID Method" contained in the bottom of the credential.
+
+But what is a verifiable credential?
+
+### What is a Verifiable Credential?
+
+According to the W3C
+()
+a verifiable credential is:
+
+- Information related to identifying
+ the [subject](https://www.w3.org/TR/vc-data-model-2.0/#dfn-subjects) of
+ the [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) (for
+ example, a photo, name, or identification number)
+
+- Information related to the issuing authority (for example, a city
+ government, national agency, or certification body)
+
+- Information related to the type
+ of [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) this
+ is (for example, a Dutch passport, an American driving license, or a
+ health insurance card)
+
+- Information related to specific attributes or properties being
+ asserted by the issuing authority about
+ the [subject](https://www.w3.org/TR/vc-data-model-2.0/#dfn-subjects) (for
+ example, nationality, the classes of vehicle entitled to drive, or
+ date of birth)
+
+- Evidence related to how
+ the [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) was
+ derived
+
+- Information related to constraints on the credential (for example,
+ validity period, or terms of use).
+
+A [verifiable
+credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-verifiable-credential) can
+represent all of the same information that a
+physical [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) represents.
+The addition of technologies, such as digital signatures,
+makes [verifiable
+credentials](https://www.w3.org/TR/vc-data-model-2.0/#dfn-verifiable-credential) more
+tamper-evident and more trustworthy than their physical counterparts.
+
+In this concept **Verifiable Credentials** are not representing the identities from the Product but are some sort of **Documents** which contain the actual information from a product and are **signed** by issuer of the data or in case of partial data certified, signed by a data auditor.
+
+### Credential Schema
+
+The signed document credential has the following resumed schema:
+
+
+
+Depending in each verification types different configuration will be provided in the location of the payload aspect or specific attributes. The detailed configuration is defined in the [Technical Integration Design](#technical-integration-design) chapter.
+
+| Section | Description |
+| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Metadata** | The metadata contains the context information and credential schema details. Also contains the identification of the credential and which documents it contained. |
+| **Aspect Model Data / Credential Data** | In this section is defined all the neccessary data of each credential type. The specific attributes with methods and proof from data auditor or the original data issued and sigend by the data provider. |
+| **Proof and Verification Methods** | This section contain the digital signature from the Data Provider or Data Auditor. It also contains all the methods for a Data Verifier/Data Consumer to access the verification requirements to check if the credential is still valid and not revoked. |
+
+# Certification Processes
+
+For easing the understanding from the certification process and the interaction between the Data Provider and the Data Auditor, some diagrams are provided where the different interactions and artifacts generated are mapped.
+
+> [!NOTE]
+>
+> The Certification Processes of data are valid equally for `Type` level digital twins (Aspect Model in Type Level) or `Instance` digital twins (Aspect Model in Serialized Level). The difference relies on the configuration of the digital twin, and in which level the certification wants to be done.
+> Is important to know that the certification **MUST** be at the same level always. If we talk about a Digital Twin in Type Level, then the Digital Product Pass or any aspect model will contain Type level data, as well as the verified attributes.
+
+## Attribute Certification Process
+
+The attribute certification is based on a plain JSON Aspect Model Payload that contains the information from a digital product pass. It starts with the `data provider` that creates the `digital product passport` with the available information from and storing it in the `data service`.
+Once that is done the data will be linked in a `digital twin`, so in this way by receiving the digital twin and searching for the passport submodel it can be found. After that it will be stored in the `digital twin registry`. Now if any attribute level certification is required to be done by an auditor, a `request` will be triggered from the data provider side, so a `EDC Push Notification` will be sent to the `data auditor` with the EDC Provider URL, the Digital Twin Id and the DPP Aspect Submodel Id (unique identification)
+
+> [!TIP]
+>
+> A possible optimization to be done is to send directly the digital product pass data and the path to the attributes to be verified. However, for maintaining data sovereignty and the data not being transmitted without a contact exchange, the best way would be to send the IDs and then the `data auditor` will retrieve the data using the EDC.
+
+Once the EDC Push Notification is received by the `data auditor` the Digital Twin and the Digital Product Pass (JSON aspect model payload to be audited) will be retrieved using the `EDC Connector` and through the `EDC Data Plane proxy`. When the passport aspect is available the data auditor can certify the `specific attributes requested` from the product against the different catena-x standards and regulations. The `data auditor` will create a new document (a certified snapshot credential) which contains the proof of compliance of the specific attributes audited in the passport using selective disclosure, there the data is not copied it is hashed so it can be signed and stored in the wallet from the `data auditor` for tracking reasons.
+
+The `CSC Document` (the certificate) will then be sent to the `data provider` using the EDC Push Notification functionality. When the data arrives in the data provider it will be then added to the `Attribute Certification Registry (ACR)` which contains all the attribute certifications for an specific aspect model payload submodel. It contains a list of credentials provided by one or more auditors for this aspect. It will be linked in the digital twin where the aspect is and if additional certification is required it will be triggered and the process repeats again.
+
+
+
+## Self-Testify Certification Process
+
+The self-testify certification process consist in the data provided singing its own data which is being provided. Basically giving proof that he was the one that aggregated and created this data.
+
+
+
+## Total Certification Process
+
+The total certification process is the same as the attribute verification process however the complete process is not starting with a plain json file. In this case the data provider can `self testify` its own data. The rest of the process is same and will result in the verification from the specific attributes from the aspect.
+
+
+
+# Certification and Verification Methods
+
+## Certified Snapshot Credential
+
+By using `hashes` and indicating which attributes were verified we are able to use `Selective Disclosure` to indicate which values were present in the original data audited. In this way the data gets not duplicated and the verification using the data retrieved from the data provider is still possible.
+
+
+
+## Certified Data Credential
+
+In this case just the data provider would sign its own digital product pass credential and generating the corresponding Certified Data Credential with the proof of the content issued in a specific datetime.
+
+
+
+## Complete Data Certification Verification
+
+The complete verification comparation would be happen when both Certified Data Credential (CDC) and one or more the Certified Snapshot Credentials (CSC) are available. The different partial credential (CSCs) you be compared against the CDC credential hashes. This allows the application to know which attributes were certified by the data-auditor and with each value.
+
+
+
+
+# Verification Processes
+
+## Flow Diagrams
+
+In order for the Certified Data Credential and Certified Snapshot Credential to be retrieve, the consumer application **MUST** be able to access the digital twin in the data auditor registry.
+
+### CDC Technical Verification Flow
+
+By simply accessing the digital twin the data will be available as a submodel, the same way as a normal digital product pass serialized payload is available:
+
+
+
+### CSC Technical Verification Flow
+
+For the partial credential the data will be available in a "Verification" aspect called `Attribute Certification Registry` (ACR) which contains the different attribute verification for a particular submodel in a digital twin.
+
+
+
+# Technical Specification
+
+## Certification Aspects Schemas
+
+
+> [!CAUTION]
+> The information added here its still not productive, what its proposed is simply a MOCK, and its not ready to be implemented in a system yet, the actual schema and details **MUST** be defined in the future of this documentation
+
+### Certified Data Credential Schema
+
+The CDC schema contains the complete passport and some additional information, as well as as the signature of the data provider.
+
+Here we have an example with the [Digital Product Passport v2.0.0](https://raw.githubusercontent.com/eclipse-tractusx/sldt-semantic-models/main/io.catenax.generic.digital_product_passport/2.0.0) Aspect Model.
+
+
+🚀 Expand Certified Data Credential (CDC) Aspect Schema
+
+```json
+{
+ "id": "https://dpp-system-url.com/api/public/cx:mfg024:prt-30001",
+ "@context": [
+ "https://www.w3.org/2018/credentials/v1",
+ "http://json-schema.org/draft-04/schema",
+ "https://raw.githubusercontent.com/eclipse-tractusx/sldt-semantic-models/main/io.catenax.generic.digital_product_passport/2.0.0/gen/DigitalProductPassport-schema.json",
+ "https://w3c.github.io/vc-jws-2020/contexts/v1/"
+ ],
+ "type": ["VerifiableCredential", "CDC", "DPP"],
+ "issuer": "did:web:wallet-url.test.com:BPNL00000007RVTB",
+ "credentialSubject": {
+ "id": "did:web:dpp-test-system.com:BPNL000000000000:api:public:urn%3Auuid%3A6da1f07c-999b-4602-b4d3-8eb649e5d10f",
+ "parent": {
+ "@id": "did:web:dpp-test-system.com:BPNL000000000000:api:public:urn%3Auuid%3A1c5b6a7c-90d4-3481-0538-f134ff53076d",
+ "checksum": "64b1a523da600e8fc0018cf57b8f7756b83bb6e9b11c81b1c7444272fab239902321b1b6ae6624d6846fd010616ae98c118f12491f922badd64e58b782c6a115"
+ },
+ "checksum": "ac35e22f24fc4257e2759f7e7105f14568e5e86573fea4b05515697f254111c1f3490d28653b400cb9ddc9690760ef1390f5cac7a3d55966490dab994c1f5cd1",
+ "data": {
+ "typology" : {
+ "shortName" : "8HP60",
+ "class" : {
+ "definition" : "Manual transmission (motor vehicle)",
+ "code" : "44-09-02-02"
+ },
+ "longName" : "Product Description long text"
+ },
+ "metadata" : {
+ "predecessor" : "null",
+ "issueDate" : "2000-01-01",
+ "version" : "1.0.0",
+ "economicOperator" : {
+ "legitimization" : "DE123456789",
+ "identification" : "BPNL1234567890ZZ"
+ },
+ "status" : "draft",
+ "expirationDate" : "2000-01-01"
+ },
+ "characteristics" : {
+ "physicalDimension" : {
+ "grossWeight" : {
+ "value" : 20.5,
+ "unit" : "unit:kilogram"
+ },
+ "weightOrVolume" : {
+ "left" : {
+ "value" : 20.5,
+ "unit" : "unit:cubicMetre"
+ }
+ },
+ "diameter" : {
+ "value" : 20.5,
+ "unit" : "unit:millimetre"
+ },
+ "grossVolume" : {
+ "value" : 20.5,
+ "unit" : "unit:cubicMetre"
+ },
+ "width" : {
+ "value" : 20.5,
+ "unit" : "unit:millimetre"
+ },
+ "length" : {
+ "value" : 20.5,
+ "unit" : "unit:millimetre"
+ },
+ "height" : {
+ "value" : 20.5,
+ "unit" : "unit:millimetre"
+ }
+ },
+ "lifespan" : [ {
+ "value" : 36,
+ "unit" : "unit:day",
+ "key" : "guaranteed lifetime"
+ } ],
+ "physicalState" : "solid"
+ },
+ "commercial" : {
+ "placedOnMarket" : "2000-01-01"
+ },
+ "identification" : {
+ "localIdentifier" : {
+ "value" : "PRT-30001",
+ "key" : "PartInstanceId"
+ },
+ "additionalCode" : [ {
+ "value" : "8703 24 10 00",
+ "key" : "TARIC"
+ }, {
+ "value" : "MFG024",
+ "key" : "manufacturerPartId"
+ } ],
+ "dataCarrier" : {
+ "carrierType" : "QR",
+ "carrierLayout" : "upper-left side"
+ }
+ },
+ "sources" : [ {
+ "header" : "Sustainability Document Material XY",
+ "category" : "Product Specifications",
+ "type" : "URL",
+ "content" : "www.alink.pdf"
+ } ],
+ "handling" : {
+ "spareParts" : {
+ "left" : {
+ "producer" : [ {
+ "id" : "BPNL1234567890ZZ"
+ } ],
+ "part" : [ {
+ "name" : "Aluminum Housing",
+ "gtin" : "12345678"
+ } ]
+ }
+ },
+ "substanceOfConcern" : {
+ "left" : [ {
+ "name" : {
+ "name" : "phenolphthalein",
+ "type" : "IUPAC"
+ },
+ "location" : "Housing",
+ "unit" : "unit:partPerMillion",
+ "concentration" : {
+ "left" : [ {
+ "max" : 2.6,
+ "min" : 2.1
+ } ]
+ },
+ "exemption" : "shall not apply to product x containing not more than 1,5 ml of liquid",
+ "id" : [ {
+ "type" : "CAS",
+ "id" : "201-004-7"
+ } ]
+ } ]
+ }
+ },
+ "additionalData" : [ {
+ "description" : "This is the machine parameters that are produced when the machine is used",
+ "label" : "Specific Manufacturer Machine Parameters",
+ "type" : {
+ "typeUnit" : null,
+ "dataType" : "object"
+ },
+ "children" : [ {
+ "description" : "The usage of the eletricity in the machine",
+ "label" : "Eletricity Usage",
+ "type" : {
+ "typeUnit" : "unit:volts",
+ "dataType" : "integer"
+ },
+ "data" : "25"
+ }, {
+ "description" : "The name of the machine that produced the product",
+ "label" : "Machine Name",
+ "type" : {
+ "typeUnit" : null,
+ "dataType" : "string"
+ },
+ "data" : "Laser Machine MX-421W"
+ }, {
+ "description" : "The list of products the machine can produce",
+ "label" : "Product Names",
+ "type" : {
+ "typeUnit" : null,
+ "dataType" : "array"
+ },
+ "data" : [ "Tranmissions", "Batteries", "Seats", "Doors" ]
+ } ]
+ }, {
+ "description" : "This are the properties of interest",
+ "label" : "Properties of Interest",
+ "type" : {
+ "typeUnit" : null,
+ "dataType" : "object"
+ },
+ "children" : [ {
+ "description" : "This are the main properties of interest",
+ "label" : "Main Properties",
+ "type" : {
+ "typeUnit" : null,
+ "dataType" : "object"
+ },
+ "children" : [ {
+ "description" : "This is the Normal temperature of production",
+ "label" : "Normal Temperature",
+ "type" : {
+ "typeUnit" : "unit:celcius",
+ "dataType" : "float"
+ },
+ "data" : 62.7
+ }, {
+ "description" : "This is the minimmum temperature of production",
+ "label" : "Minimum Temperature",
+ "type" : {
+ "typeUnit" : "unit:celcius",
+ "dataType" : "float"
+ },
+ "data" : -80.68
+ }, {
+ "description" : "This is the maximum temperature of production",
+ "label" : "Maximum Temperature",
+ "type" : {
+ "typeUnit" : "unit:celcius",
+ "dataType" : "float"
+ },
+ "data" : 800.85
+ } ]
+ } ]
+ } ],
+ "sustainability" : {
+ "PEF" : {
+ "carbon" : [ {
+ "lifecycle" : "main product production",
+ "rulebook" : "https://www.alink.pdf/",
+ "unit" : "kg CO2 eq",
+ "type" : "Climate Change Total",
+ "value" : 12.678
+ } ]
+ },
+ "state" : "first life",
+ "material" : {
+ "left" : [ {
+ "name" : {
+ "name" : "phenolphthalein",
+ "type" : "IUPAC"
+ },
+ "unit" : "unit:partPerMillion",
+ "recycled" : false,
+ "id" : [ {
+ "type" : "CAS",
+ "id" : "201-004-7"
+ } ],
+ "value" : 5,
+ "renewable" : true
+ } ]
+ },
+ "critical" : {
+ "left" : [ "eOMtThyhVNLWUZNRcBaQKxI" ]
+ }
+ },
+ "operation" : {
+ "importer" : {
+ "left" : {
+ "eori" : "GB123456789000",
+ "id" : "BPNL1234567890ZZ"
+ }
+ },
+ "manufacturer" : {
+ "facility" : "BPNS1234567890ZZ",
+ "manufacturingDate" : "2000-01-31",
+ "manufacturer" : "BPNL1234567890ZZ"
+ }
+ }
+ }
+ },
+ "issuanceDate": "2024-02-15T00:00:00.000Z",
+ "proof": {
+ "type": "JsonWebSignature2020",
+ "created": "2024-02-15T12:35:39Z",
+ "verificationMethod": "did:web:wallet-url.test.com:BPNL00000007RVTB#8f858500-7008-4b97-a8bb-605d4c8eca75",
+ "proofPurpose": "assertionMethod",
+ "jws": "eyJhbGciOiJFZERTQSJ9..4snTkqta4UwXIAtKJiIEDhiwmVtAC3kml0j7Wc25vmTbLbPlviXgL9he9X0A0xRTNlnsEwILf0NbPIyeztzJCw"
+ }
+}
+```
+
+
+
+## Certified Snapshot Credential Schema
+
+The CDC schema contains the partial passport with different attributes, all them with the methods used for the ceritification, as well as as the signature of the data provider.
+
+Here we have an example of the generated CSC from the [previous CDC Aspect](#certified-data-credential-schema) the [Digital Product Passport v2.0.0](https://raw.githubusercontent.com/eclipse-tractusx/sldt-semantic-models/main/io.catenax.generic.digital_product_passport/2.0.0) Aspect Model.
+
+
+🚀 Expand Certified Snapshot Credential (CSC) Aspect Schema
+
+```json
+{
+ "id": "https://dpp-system-url.com/api/public/cx:mfg024:prt-30001",
+ "@context": [
+ "https://www.w3.org/2018/credentials/v1",
+ "http://json-schema.org/draft-04/schema",
+ "https://raw.githubusercontent.com/eclipse-tractusx/sldt-semantic-models/main/io.catenax.generic.digital_product_passport/2.0.0/gen/DigitalProductPassport-schema.json",
+ "https://w3c.github.io/vc-jws-2020/contexts/v1/"
+ ],
+ "type": [
+ "VerifiableCredential",
+ "CSC",
+ "DPP"
+ ],
+ "issuer": "did:web:wallet-url.test.com:BPNL000000086WTL",
+ "credentialSubject": {
+ "id": "did:web:dpp-test-system.com:BPNL000000000000:api:public:urn%3Auuid%3Acd1c0904-27e2-4ae2-8751-5c8c8e4b6812",
+ "checksum": "ac35e22f24fc4257e2759f7e7105f14568e5e86573fea4b05515697f254111c1f3490d28653b400cb9ddc9690760ef1390f5cac7a3d55966490dab994c1f5cd1",
+ "data": [
+ {
+ "path": "sustainability.PEF.carbon[0].value",
+ "proof": "112b7337ac2710961e728f5bf983ce1dbdef1972ed6ec949982faf7c80566b7f9146a781d40a3166a9b00286b46136be863c3ca16c6b9d13c218b675892a4fd9",
+ "method": [
+ {
+ "type": "Standard",
+ "name": "PCF Rulebook Standard",
+ "id": "CX-0029",
+ "url": "https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_September23/CX-0029-ProductCarbonFootprintRulebook-v2.0.0.pdf"
+ },
+ {
+ "type": "Regulation",
+ "name": "Ecodesign for Sustainable Products Regulation",
+ "id": "2009/125/EC",
+ "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:02009L0125-20121204&from=EN"
+ }
+ ]
+ },
+ {
+ "path": "sustainability.state",
+ "proof": "f4f14ed3c319f1f1cd4ee5a50353ec0147da5cb0f8da86a3161bd2c70c83026bc4bdf64c99a4a38fb10afc19f6e07e6cbf820981ab13468133da3a403036e9eb",
+ "method": [
+ {
+ "type": "Standard",
+ "name": "Secondary Material Content Standard",
+ "id": "CX-0098",
+ "url": "https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_Januar_2024/CX-0098-AspectModelSecondaryMaterialContent-v1.0.0.pdf"
+ }
+ ]
+ }
+ ]
+ },
+ "issuanceDate": "2024-02-15T00:00:00.000Z",
+ "proof": {
+ "type": "JsonWebSignature2020",
+ "created": "2024-02-15T12:35:39Z",
+ "verificationMethod": "did:web:wallet-url.test.com:BPNL000000086WTL#049f920c-e702-4e36-9b01-540423788a90",
+ "proofPurpose": "assertionMethod",
+ "jws": "eyJhbGciOiJFZERTQSJ9..4snTkqta4UwXIAtKJiIEDhiwmVtAC3kml0j7Wc25vmTbLbPlviXgL9he9X0A0xRTNlnsEwILf0NbPIyeztzJCw"
+ }
+}
+```
+
+
+
+## Attribute Certification Registry
+
+> [!WARNING]
+> The attribute certification registry details is still not available. It will contain the complete list of CSC certificates and also reference to the CDC or plain json submodel in the same digital twin.
+
+# Technical Integration Design
+
+> [!WARNING]
+> The complete technical integration design is still not available here!
+
+## Interfaces
+
+The digital product pass application would act in the dpp-verification concept as the "Verification System" which is able to communicate with different systems, behind or not behind a EDC connector. Data would be exchange using the EDC however components like the Wallet could be accessed using the "DID Web" method, or the Semantic Hub using the central interface provided by the operator of the network.
+
+
+
+## Certification Sequence Diagrams
+
+> [!WARNING]
+> Some details may be missing or incorrect, since that is the first implementation concept for the certification and verification. The concept is still being elaborated and will be determined in the new release with the actual implementation!
+
+
+### CSC Certification Sequence Diagram
+
+In this sequence diagram we can see how a data auditor retrieved the data as a normal Digital Product Pass Application. It will select then the different attributes and then sign his certificate against its own `decentral wallet`. After he will send it to the data provider.
+
+
+
+### CDC + CSC Certification Sequence Diagram
+
+In this sequence diagram we have the same as the first one, however the data auditor can also indicate which data needs to be updated in the original data for being `compliant`. Therefore the data provider can also update its data in the original data and verify it once again.
+
+
+
+## Verification Sequence Diagrams
+
+### CSC Verification Sequence Diagram
+
+In this verification sequence diagram we can observe the digital product pass application will retrieve the data first and then will request for any verification data available.
+
+
+
+### CDC + CSC Verification Sequence Diagram
+
+In this verification sequence diagram the complete verification is found. The CDC credential is retrieved in the first step and checked if it verified against a wallet. And then the data is displayed, after that the user requests more verification and gets it from the data provider if allowed.
+
+
+
+# References
+
+The following references were used as inspiration for understanding more how product credentials are done in the market. Is also included references to components in Tractus-X that were used to understand on how the different components behave in the network.
+
+No content with copyright was copied. All the information used as reference in this documentation is open source, is available for the public or released under creative commons license.
+
+| Name | Author | Date | Link |
+| :------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Data Integrity Demonstrator (TRS) in Supply Chain | [Matthias Binzer](https://github.com/matgnt) - Bosch | 2023 | https://github.com/boschresearch/cx-data-integrity-demonstrator |
+| ID Union Data Integrity Demonstrator | [Matthias Binzer](https://github.com/matgnt) - Bosch | 2023 | https://github.com/IDunion/i40-examples/tree/main/nameplate-vc |
+| Digital Product Passport Verifiable Credential Demo | Spherity | 2023 | https://acme.dpp.spherity.com/ |
+| Verifiable Credentials Data Model v1.1/v2.0 | W3C | 2022 - 2024 | https://www.w3.org/TR/vc-data-model/ https://www.w3.org/TR/vc-data-model-2.0/ |
+| Tractus-X SSI Documentation | Catena-X Core-ART Architects & Eclipse Tractus-X Contributors | 2023 | https://github.com/eclipse-tractusx/ssi-docu/tree/main/docs/architecture/cx-3-2 |
+| Ed25519: high-speed high-security signatures | Daniel J. Bernstein, University of Illinois at Chicago Niels Duif, Technische Universiteit Eindhoven Tanja Lange, TechnischeUniversiteit Eindhoven Peter Schwabe,National Taiwan UniversityBo-Yin Yang,Academia Sinica | 2017 | https://ed25519.cr.yp.to/ |
+| Digital Product Pass Documentation and Arc42 | [Mathias Brunkow Moser](https://github.com/matbmoser) & [Muhammad Saud Khan](https://github.com/saudkhan116) - CGI - Tractus-X Contributors | 2021-2024 | https://github.com/eclipse-tractusx/digital-product-pass/ https://github.com/eclipse-tractusx/digital-product-pass/blob/main/docs/arc42/Arc42.md |
+| Managed Identity Wallets | Tractus-X Contributors | 2022-2024 | https://github.com/eclipse-tractusx/managed-identity-wallet |
+| Digital Twin Registry | Bosch - Tractus-X Contributors | 2021-2024 | https://github.com/eclipse-tractusx/sldt-digital-twin-registry |
+| Tractus-X EDC | Tractus-X Contributors | 2021-2024 | https://github.com/eclipse-tractusx/tractusx-edc |
+| Eclipse Connector | Eclipse Foundation Contributors | 2021-2024 | https://github.com/eclipse-edc/Connector |
+| Universal Resolver for DIDs | Universal Resolver | 2017-2024 | https://dev.uniresolver.io/ https://github.com/decentralized-identity/universal-resolver |
+| Decentralized Identifiers (DIDs) v1.0 | W3C | 2022 | https://www.w3.org/TR/did-core/ |
+| Decentralized Identifier Resolution (DID Resolution) v0.3 | W3C | 2023 | https://w3c-ccg.github.io/did-resolution/ |
+| Self-Sovereign Identity - Decentralized Digital Identity and Verifiable Credentials v2 | Manning Publications: manning.com | 2020 | https://livebook.manning.com/book/self-sovereign-identity/chapter-8/v-2/7 |
+| EECC Verifier for Verifiable Credentials | Free Software Foundation, Inc (https://fsf.org) | 2022-2024 | https://github.com/european-epc-competence-center/vc-verifier [ssi.eecc.de/verifier](ssi.eecc.de/verifier/) |
+| Identity Resolution Verification | European EPC Competence Center GmbHhttps://eecc.info/ | 2022-2024 | https://id.eecc.de/ |
+| SuplyTree - The Inter-company Tamper-evidence Protocol for Supply Chain Traceability | Matthias Guenther, Robert Bosch GmbH, Economy of Things Dominie Woerner, Robert Bosch Switzerland, Economy of Things | 2023 | |
+| A Beginners Guide to Decentralized Identifiers (DIDs) | Amarachi Johnson-Ubah - Medium | 2022 | https://medium.com/veramo/a-beginners-guide-to-decentralized-identifiers-dids-5e842398e82c#:~:text=A%20decentralized%20identifier%20is%20an,the%20signatures%20of%20that%20subject |
+| Schema Organization for JSON-LD | W3C | 2021-2024 | https://schema.org/ |
+
+
+# Special Thanks
+We would like to thank [Matthias Binzer](https://github.com/matgnt) for contributing in the refactoring of the initial concept by giving some insights on how he has done the Supply Chain data integrity concept using Verifiable Credentials (TRS) Data Integrity Demonstrator. He supported us on finding a way and giving the hints for maintaining selective disclosure when it comes to verify specific attributes from a aspect.
+We also thank for all the Platform Capability Architects for their disposition for reviewing and supporting the concept from an architecture perspective. We thank the Wallet Catena-X Experts for the time they took review the concept and for the feedback that was given.
+We thank the managed identify wallets product owner for the support and availability for answering questions which were relevant to the adaptation of the concept to the architecture.
+Last but not least a special thanks for all the Tractus-X and Catena-X Stakeholders that participated in the elaboration and review of this concept.
+
+
+# Glossary
+
+Here are the abbreviations and complete terms used during the
+explanation of this Certification and Verification Concept.
+
+| **Abbreviation** | **Complete Term** |
+| --------------------- | ---------------------------------------------------------- |
+| AAS | Asset Administration Shell |
+| ACR | Attribute Certification Registry |
+| API | Application Programming Interfaces |
+| BPN(BPNL, BPNA, BPNS) | Business Partner Number (Legal Entities, Addresses, Sites) |
+| CSC | Certified Snapshot Credential |
+| CDC | Certified Data Credential |
+| DTR | Digital Twin Registry |
+| dDTR | Decentralized Digital Twin Registry |
+| DID | Decentral Identifier |
+| DPP | Digital Product Passport |
+| DT | Digital Twin |
+| EDC | Eclipse Data Space Connector |
+| IRS | Item Relationship Service |
+| JSON | JavaScript Object Notation |
+| JWT | JSON Web Token |
+| JWS | JSON Web Signature |
+| JSON-LD | JavaScript Object Notation for Linked Data |
+| MIW | Managed Identity Wallet |
+| PCF | Product Carbon Footprint |
+| SSI | Self-Sovereign Identity |
+| TRG | Tractus-X Release Guideline |
+| TTL | Terse RDF Triple Language |
+| VC | Verifiable Credential |
+| VP | Verifiable Presentation |
+| W3C | World Wide Web Consortium |
+
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/cdc-csc-workflow.svg b/dpp-verification/resources/processes/cdc-csc-workflow.svg
new file mode 100644
index 000000000..d970bb403
--- /dev/null
+++ b/dpp-verification/resources/processes/cdc-csc-workflow.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/cdc-csc-workflow.svg.license b/dpp-verification/resources/processes/cdc-csc-workflow.svg.license
new file mode 100644
index 000000000..5b528f257
--- /dev/null
+++ b/dpp-verification/resources/processes/cdc-csc-workflow.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/cdc-workflow.svg b/dpp-verification/resources/processes/cdc-workflow.svg
new file mode 100644
index 000000000..b2ce6f4d1
--- /dev/null
+++ b/dpp-verification/resources/processes/cdc-workflow.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/cdc-workflow.svg.license b/dpp-verification/resources/processes/cdc-workflow.svg.license
new file mode 100644
index 000000000..5b528f257
--- /dev/null
+++ b/dpp-verification/resources/processes/cdc-workflow.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/csc-workflow.svg b/dpp-verification/resources/processes/csc-workflow.svg
new file mode 100644
index 000000000..4cdbd7994
--- /dev/null
+++ b/dpp-verification/resources/processes/csc-workflow.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/csc-workflow.svg.license b/dpp-verification/resources/processes/csc-workflow.svg.license
new file mode 100644
index 000000000..5b528f257
--- /dev/null
+++ b/dpp-verification/resources/processes/csc-workflow.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/document-credential-resume.svg b/dpp-verification/resources/processes/document-credential-resume.svg
new file mode 100644
index 000000000..5f9b45c25
--- /dev/null
+++ b/dpp-verification/resources/processes/document-credential-resume.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/document-credential-resume.svg.license b/dpp-verification/resources/processes/document-credential-resume.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/processes/document-credential-resume.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/role-process-definition.svg b/dpp-verification/resources/processes/role-process-definition.svg
new file mode 100644
index 000000000..954b278b8
--- /dev/null
+++ b/dpp-verification/resources/processes/role-process-definition.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/role-process-definition.svg.license b/dpp-verification/resources/processes/role-process-definition.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/processes/role-process-definition.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/roles-business-interaction.svg b/dpp-verification/resources/processes/roles-business-interaction.svg
new file mode 100644
index 000000000..c095c87cf
--- /dev/null
+++ b/dpp-verification/resources/processes/roles-business-interaction.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/roles-business-interaction.svg.license b/dpp-verification/resources/processes/roles-business-interaction.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/processes/roles-business-interaction.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/roles-document-exchange-interaction.svg b/dpp-verification/resources/processes/roles-document-exchange-interaction.svg
new file mode 100644
index 000000000..de5301fe5
--- /dev/null
+++ b/dpp-verification/resources/processes/roles-document-exchange-interaction.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/roles-document-exchange-interaction.svg.license b/dpp-verification/resources/processes/roles-document-exchange-interaction.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/processes/roles-document-exchange-interaction.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/verification-process-cdc.svg b/dpp-verification/resources/processes/verification-process-cdc.svg
new file mode 100644
index 000000000..9c77b18d5
--- /dev/null
+++ b/dpp-verification/resources/processes/verification-process-cdc.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/verification-process-cdc.svg.license b/dpp-verification/resources/processes/verification-process-cdc.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/processes/verification-process-cdc.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/verification-process-csc.svg b/dpp-verification/resources/processes/verification-process-csc.svg
new file mode 100644
index 000000000..1a3f508b6
--- /dev/null
+++ b/dpp-verification/resources/processes/verification-process-csc.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/processes/verification-process-csc.svg.license b/dpp-verification/resources/processes/verification-process-csc.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/processes/verification-process-csc.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/complete-verification-CSC-CDC.svg b/dpp-verification/resources/technical/complete-verification-CSC-CDC.svg
new file mode 100644
index 000000000..eee86c594
--- /dev/null
+++ b/dpp-verification/resources/technical/complete-verification-CSC-CDC.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/complete-verification-CSC-CDC.svg.license b/dpp-verification/resources/technical/complete-verification-CSC-CDC.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/complete-verification-CSC-CDC.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/interfaces.svg b/dpp-verification/resources/technical/interfaces.svg
new file mode 100644
index 000000000..ed0123335
--- /dev/null
+++ b/dpp-verification/resources/technical/interfaces.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/interfaces.svg.license b/dpp-verification/resources/technical/interfaces.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/interfaces.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/simple-verification-CDC.svg b/dpp-verification/resources/technical/simple-verification-CDC.svg
new file mode 100644
index 000000000..4dec99a47
--- /dev/null
+++ b/dpp-verification/resources/technical/simple-verification-CDC.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/simple-verification-CDC.svg.license b/dpp-verification/resources/technical/simple-verification-CDC.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/simple-verification-CDC.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/simple-verification-CSC.svg b/dpp-verification/resources/technical/simple-verification-CSC.svg
new file mode 100644
index 000000000..239c8ef64
--- /dev/null
+++ b/dpp-verification/resources/technical/simple-verification-CSC.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/simple-verification-CSC.svg.license b/dpp-verification/resources/technical/simple-verification-CSC.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/simple-verification-CSC.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc+cdc-data-auditor.svg b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc-data-auditor.svg
new file mode 100644
index 000000000..49c9fc227
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc-data-auditor.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc+cdc-data-auditor.svg.license b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc-data-auditor.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc-data-auditor.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc+cdc.svg b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc.svg
new file mode 100644
index 000000000..953fd4fd4
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc+cdc.svg.license b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc+cdc.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc-data-auditor.svg b/dpp-verification/resources/technical/technical-integration-flow-csc-data-auditor.svg
new file mode 100644
index 000000000..664ef96c3
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc-data-auditor.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc-data-auditor.svg.license b/dpp-verification/resources/technical/technical-integration-flow-csc-data-auditor.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc-data-auditor.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc.svg b/dpp-verification/resources/technical/technical-integration-flow-csc.svg
new file mode 100644
index 000000000..f4c1f9761
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/dpp-verification/resources/technical/technical-integration-flow-csc.svg.license b/dpp-verification/resources/technical/technical-integration-flow-csc.svg.license
new file mode 100644
index 000000000..4bd508f93
--- /dev/null
+++ b/dpp-verification/resources/technical/technical-integration-flow-csc.svg.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
diff --git a/dpp-verification/resources/verification-logo.png b/dpp-verification/resources/verification-logo.png
new file mode 100644
index 000000000..d848f1540
Binary files /dev/null and b/dpp-verification/resources/verification-logo.png differ
diff --git a/dpp-verification/resources/verification-logo.png.license b/dpp-verification/resources/verification-logo.png.license
new file mode 100644
index 000000000..5b528f257
--- /dev/null
+++ b/dpp-verification/resources/verification-logo.png.license
@@ -0,0 +1,13 @@
+## NOTICE
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023, 2024 BMW AG
+- SPDX-FileCopyrightText: 2023, 2024 CGI Deutschland B.V. & Co. KG
+- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
+- Source URL: https://github.com/eclipse-tractusx/digital-product-pass
+
+## AUTHORS
+
+- [Mathias Brunkow Moser](https://github.com/matbmoser)
\ No newline at end of file
Digital Product Pass Application
+ 
+ 
+ 
+