The adoption of the new API version required the following updates:

Learn more: Asset Administration Shell API V3.1.0

The Asset Administration Shell Digital Twin Registry has implemented a custom PATCH REST endpoint for Asset Administration Shells that enables partial updates to existing Shells according to the RFC 7396 JSON Merge Patch standard.

Learn more: Update Asset Administration Shells via PATCH REST endpoint

You can now restrict the access to Shell groups and labels based on the newly implemented fine-grained access control rules.

Learn more: Restrict access to Asset Administration Shells

You can now search for specific elements of Aspect Models via the Element search. You can also use the filter function and search for types of Aspect Model element, which makes the search and implementation of elements into Aspect Models much faster and easier.

You can now check out Aspect Models' license information when you open them in Aspect Model view and click the License button. This feature enables you to look up license information and figure out which Aspect Models you can use or build up other ones, based on them.

You can now adjust the following new parameters in the OpenAPI specification generation dialog:

Learn more: Aspect Model Catalog API documentation

You can now look up this information at the top of each file.

You can now filter for BPNs and get only the Asset Administration Shell associated with them. This requires an additional access role.

You can now use the new Asynchrous API to create Twins more efficiently, providing seamless integration and enabling you to do so without waiting for immediate responses.

Read more: Async API descriptions

It is now easier to find the API description that you are looking for as we have refactored our API reference docs URLs. See our API docs for the Digital Twin Registry.

Also, we have introduced an additional entry page.

To query the Asset Administration Shell Registry API for Shells that were created after a specific date (timestamp), use the new createdAfter parameter.

Read more: Asset Administration Shell Registry API

The variable data in a template is defined in the href of its endpoints, in the form of placeholders. Endpoint placeholders can leverage runtime data coming from the Asset Administration Shell. This option is now available for specficAssetIds.

Read more: URL placeholders and syntax

Text/Turtle format is now supported as response to the getAspectModel API request. You can use that in tools like ESMF Java SDK.

They now conform to the current 3.0.2 version of the Asset Administration Shell specification that was recently published by IDTA. Changes include:

Their purpose is to enable scalability and maintainability for the management of Submodel Descriptors.

Read more: Use Submodel Descriptor Templates

Asset Administration Shells can now be filtered and found, using RQL (Resource Query Language).

Read more: Find Asset Administration Shells via RQL filtering

Fine-grained access control has been implemented to restrict the access and visibility of Shells and Twins, based on what access policies have been granted to the user.

Read more: Restrict access to Asset Administration Shells

You can now switch between tenants inside the Aspect Model Catalog UI via a dialog or by changing the tenant ID inside the URL.

Read more: Switch tenant

You can now access namespaces owned by you, as well as shared namespaces that can be used by all users. All namespaces accessible to you are stored in your tenant and can be found in the Namespaces Overview.

Read more: Namespace sharing

You can now see details about each element of a namespace by going to its Overview and clicking on an element.

The OpenAPI specification can now be downloaded for Digital Twin Registry and Asset Administration Shell from https://registry.bosch-semantic-stack.com/docs/rest/api-doc-registry.html.

The link is added to directly open the corresponding Aspect Model of a Twin’s aspect in the Aspect Model Catalog.

The new field was implemented to distinguish Twins of the types Instance and Type in order to facilitate searching for specific Twins.

The Digital Twin Registry now displays Asset Administration Shells and basic information about them.

If the mandatory EDC-BPN header is not provided, the error message displayed already states the reason behind it.

Asset Administration Shells can now be searched in the Digital Twin Registry using Bosch Semantic Stack RQL.

Read more: Find Asset Administration Shells in the Digital Twin Registry

The new endpointType for EDC is called "DSP" and was added to the Digital Twin Registry to provide EDC-specific information.

The following URL changes have been done to make the Digital Twin Registry compatible with the Catena-X specification:

The new URL is https://registry.bosch-semantic-stack.com/docs/rest/api-doc-aas-discovery.html.

The timestamp information of the last calculation is now displayed in the Digital Twin Registry Statistics API when the getTenantStatistic operation is performed.

Users can now access generally available namespaces in their tenant, e.g., the io.catenax namespace.

Generate two new artifacts out of Aspect Models:

Previously only packages containing TTL files with the same SAMM version could be uploaded to the Aspect Model Catalog. Now it is possible to do it even if the SAMM versions of some files differ.

Read more: Aspect Model Catalog

As previously announced, the Digital Twin Registry API (v1) got deprecated. From now on, it is not available anymore.

Use the Digital Twin Registry API (v2) instead.

The outdated AAS v1 API for managing Asset Administration Shells has been deprecated and is not available anymore.

Use our Catena-X certified implementation of the AAS v3.0 instead:

The Asset Administration Shell part of our documentation has been updated to capture the latest changes.

Read more: Catena-X and Asset Administration Shell

The search functionality has been updated to allow filtering based on the following criteria:

Also, a performance optimization has been implemented to improve the search speed for namespaces in the Aspect Model Catalog.

From now on, you can generate and download JSON sample values for your Aspect Models in the Aspect Model Catalog.

This feature has been implemented to protect the Bosch Semantic Stack infrastructure. By that, the overhead generated when the database is too loaded gets reduced.