Use the Bosch AAS V3.0 API

In this section, you will learn how to register the Digital Twin Registry as a Provider for the EDC.

AAS V3.0 API

The Bosch implementation of the AAS V3.0 standard is documented at https://registry.bosch-semantic-stack.com/static/api-doc-aas-registry.htmlexternallink 20 and https://registry.bosch-semantic-stack.com/static/api-doc-aas-discovery.htmlexternallink 20.

General base URL:

https://registry.bosch-semantic-stack.com/aas-api/v3/

For your base URL, add your tenant ID to the general base URL:

https://registry.bosch-semantic-stack.com/aas-api/v3/<your-tenant-id>

Contract of Provider and Consumer EDCs

After a successful contract negotiation, a consumer connector would send a request to a provider connector to initiate the data transfer. Such a request would reference the requested Asset and ContractAgreement as well as information about the data destination (i.e., a pointer to the physical location where the asset is stored).

The public documentation for EDC is available at https://eclipse-edc.github.io/docs/#/READMEexternallink 20.

See also Catena-X info about EDCexternallink 20, Tractus-X Connector KITexternallink 20 and Digital Twin KITexternallink 20.

EDC Endpoint

The following snippet shows an example of how to register your Digital Twin Registry with EDC.

As a Provider you would create the Asset with a POST request.

POST /{{PROVIDER_DATA_MANAGEMT_URL}}/data/assets
{
    "asset": {
        "properties": {
            "asset:prop:id": "{{ASSET_ID}}",
            "asset:prop:type": "data.core.digitalTwinRegistry",
            "asset:prop:description": "Product EDC Demo Asset"
        }
    },
    "dataAddress": {
        "properties": {
            "type": "HttpData",
            "baseUrl": "https://<YOUR_REGISTRY_URL>",
            "proxyPath": true,
    		"proxyBody": true,
    		"proxyMethod": true,
    		"proxyQueryParams": true,
    		"oauth2:clientId": "REGISTRY_CLIENT_ID",
    		"oauth2:clientSecret": "REGISTRY_CLIENT_SECRET",
    		"oauth2:tokenUrl": "REGISTRY_TOKEN_ENDPOINT",
    		"oauth2:scope": "REGISTRY_TOKEN_SCOPE"
        }
    }
}

While the "asset:prop:id" property is required, and the value must be unique, the "asset:prop:type" property is optional, and helps to find the correct edc-asset, which points to the Digital Twin Registry you provide. However, in CX - 0002 Digital Twins in Catena-Xexternallink 20 it is mandatory to set the property "asset:prop:type".

Find a Postman collection of further EDC resources at https://github.com/catenax-ng/product-edc/tree/develop/docs/development/postmanexternallink 20.

Disclaimer: The interrelation between AAS API and EDC resources are still evolving and are subject to change.