24.08. conformity: supported credential types

[jjeroch]

Description:
We need to update the seeding release data to align with the new 24.08 standard. The current implementation supports the 24.05 standard, which includes an enhanced set of credentials within the release image file. The new requirement is to move these credentials to the test data file. Going forward, the release image will only contain the "Framework" credential, specifically the "Framework Exchange Governance Credential".

Tasks:

1. Remove the enhanced set of credentials from the release image file which are available under "Framework" Credential.
2. Move the credentials to the test data file, ensuring proper security and access controls are in place.
3. Update the release image to only include the "Framework Exchange Governance Credential" as per the 24.08 standard.
4. Ensure that the credential is linked to all useCases; start date 16th of Oct. 2024 (for the release image file) ++ add additionally the same type inside the testDate file with the start date 16th of June 2024. Please be aware that no expiry date is defined currently
5. Ensure that the new credential schema is strictly followed, as defined below:

{
    "id": "uuid",
    "@context": [
        "https://www.w3.org/2018/credentials/v1",
        "https://w3id.org/catenax/credentials/v1.0.0"
        ],
    "type": ["VerifiableCredential", "{DataExchangeGovernanceCredential}"],
    "issuanceDate": "{issuance date - format: 2024-10-16T00:00:00Z}",
    "expirationDate": "{expiration date - format: 2025-10-15T00:00:00Z}",
    "issuer": "{did issuer}",
    "credentialSubject": {
        "id": "{did holder}",
        "holderIdentifier": "{bpn}",
        "group": "UseCaseFramework",
        "useCase": "DataExchangeGovernance",
        "contractTemplate": "{URL OF AGREEMENT/CONTRACT TEMPLATE}",
        "contractVersion": "{VERSION OF THE AGREEMENT TEMPLATE; format: x.x}"
    }
} 

**contractTemplateURL: https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/How_To_Conclude_Data_Exchange_Contracts.pdf

To be updated seeding files:

• use_cases.json
• verified_credential_external_type_detail_versions.consortia.json
• verified_credential_external_type_detail_versions.json
• verified_credential_type_assigned_external_types.consortia.json
• verified_credential_type_assigned_external_types.json
• verified_credential_type_assigned_kinds.consortia.json
• verified_credential_type_assigned_kinds.json
• verified_credential_type_assigned_use_cases.consortia.json
• verified_credential_type_assigned_use_cases.json

[jjeroch]

The current issuer component supports the following framework agreement credentials:

• "TRACEABILITY_CREDENTIAL"
• "PCF_CREDENTIAL"
• "BEHAVIOR_TWIN_CREDENTIAL"
• "CIRCULAR_ECONOMY"
• "DEMAND_AND_CAPACITY_MANAGEMENT"
• "DEMAND_AND_CAPACITY_MANAGEMENT_PURIS"
• "BUSINESS_PARTNER_DATA_MANAGEMENT"
• "QUALITY_CREDENTIAL"

Those need to get set to inactive by setting the "expiry date" to 16th of October 2024.
Beside that, a new credential is needed:

• "DATA_EXCHANGE_GOVERNANCE_CREDENTIAL"
  • version: 1.0
  • templateUrl: https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/How_To_Conclude_Data_Exchange_Contracts.pdf

When creating the credential, it must look like defined below:

{
    "id": "{uuid}",
    "@context": [
        "https://www.w3.org/2018/credentials/v1",
        "https://w3id.org/catenax/credentials/v1.0.0"
        ],
    "type": ["VerifiableCredential", "DataExchangeGovernanceCredential"],
    "issuanceDate": "{issuance date - format: 2024-10-16T00:00:00Z}",
    "expirationDate": "{expiration date - format: 2025-10-15T00:00:00Z}",
    "issuer": "{did issuer}",
    "credentialSubject": {
        "id": "{did holder}",
        "holderIdentifier": "{bpn}",
        "group": "UseCaseFramework",
        "useCase": "DataExchangeGovernance",
        "contractTemplate": "https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/How_To_Conclude_Data_Exchange_Contracts.pdf",
        "contractVersion": "1.0"
    }
} 

[Sebastian-Wurm]

@jjeroch: is this already done?

[evegufy]

@Sebastian-Wurm yes, it was part of the 24.08 release