Review the ConceptDescription value

Oct 13, 2025 by miodeya.com 129 views

[BUG] - SemanticId in Submodel Template: A Critical Analysis

In the realm of Asset Administration Shells (AAS), the concept of Submodel Templates plays a crucial role in defining the structure and behavior of Submodels. However, a recent discovery has raised questions about the validity of adding a specific semanticId to a Submodel Template. In this article, we will delve into the details of this issue, compare it to a similar problem reported on GitHub, and provide a comprehensive analysis of the implications.

The bug in question revolves around the addition of a semanticId to a Submodel Template. The code snippet provided is as follows:

    "semanticId": {
      "type": "GlobalReference",
      "keys": [
        {
          "type": "ConceptDescription",
          "value": "https://admin-shell.io/zvei/nameplate/2/0/Nameplate"
        }
      ]
    },
    "modelType": "Submodel"
  },

This code snippet suggests that the semanticId of a Submodel Template should be of type GlobalReference, with a ConceptDescription value pointing to a specific URL. However, this contradicts the current consensus, which states that the semanticId of a Submodel Template and Submodel guided by the Submodel Template should be semanticId/type = ModelReference and semanticId/keys[0].type = Submodel.

A similar issue was reported on GitHub in issue #231. In this issue, the problem of inconsistent semanticId types in Submodel Templates was discussed. The current consensus, as mentioned earlier, was that the semanticId of a Submodel Template and Submodel guided by the Submodel Template should be semanticId/type = ModelReference and semanticId/keys[0].type = Submodel. However, the code snippet provided in the GitHub issue suggests that the semanticId type should be GlobalReference, with a ConceptDescription value pointing to a specific URL.

The issue at hand raises several questions about the validity of adding a specific semanticId to a Submodel Template. Firstly, the code snippet provided suggests that the semanticId type should be GlobalReference, which contradicts the current consensus. Secondly, the ConceptDescription value points to a specific URL, which may not be relevant to the Submodel Template.

The issue is further complicated by the fact that the APPLICATION_CLASS category was defined in Part 3a of the AAS specification. This category was intended to represent a Submodel, but it was never used in practice to my knowledge. The table containing this category is deprecated, but it is still present in the specification.

In conclusion, the issue of adding a specific semanticId to a Submodel Template is a complex one. The code snippet provided suggests that the semanticId type should be GlobalReference, which contradicts the current consensus. The ConceptDescription value points to a specific URL, which may not be relevant to the Submodel Template. Furthermore, the APPLICATION_CLASS category, which was defined in Part 3a, is no longer relevant and should be removed from the table.

Based on the analysis provided, the following recommendations are made:

Remove the APPLICATION_CLASS category: The APPLICATION_CLASS category is no longer relevant and should be removed from the table.
Use the current consensus: The current consensus states that the semanticId of a Submodel Template and Submodel guided by the Submodel Template should be semanticId/type = ModelReference and semanticId/keys[0].type = Submodel. This should be used instead of the code snippet provided.
Review the ConceptDescription value: The ConceptDescription value points to a specific URL, which may not be relevant to the Submodel Template. This value should be reviewed and updated if necessary.

By following these recommendations, the issue of adding a specific semanticId to a Submodel Template can be resolved, and the AAS specification can be improved.
[BUG] - SemanticId in Submodel Template: A Critical Analysis - Q&A

In our previous article, we delved into the details of the issue surrounding the addition of a specific semanticId to a Submodel Template. We analyzed the code snippet provided, compared it to a similar problem reported on GitHub, and provided a comprehensive analysis of the implications. In this article, we will answer some of the most frequently asked questions related to this issue.

Q: What is the current consensus on the semanticId type for a Submodel Template?

A: The current consensus states that the semanticId of a Submodel Template and Submodel guided by the Submodel Template should be semanticId/type = ModelReference and semanticId/keys[0].type = Submodel.

Q: Why is the APPLICATION_CLASS category still present in the table?

A: The APPLICATION_CLASS category was defined in Part 3a of the AAS specification, but it was never used in practice. The table containing this category is deprecated, but it is still present in the specification.

Q: What is the purpose of the ConceptDescription value in the semanticId?

A: The ConceptDescription value is intended to provide a description of the semanticId. However, in the case of the code snippet provided, the value points to a specific URL, which may not be relevant to the Submodel Template.

Q: How can I resolve the issue of adding a specific semanticId to a Submodel Template?

A: To resolve this issue, you should follow the current consensus and use the semanticId/type = ModelReference and semanticId/keys[0].type = Submodel format. You should also review the ConceptDescription value and update it if necessary.

Q: What are the implications of not following the current consensus on the semanticId type?

A: If you do not follow the current consensus, you may encounter issues with data consistency and interoperability. This could lead to problems with data exchange and integration between different systems.

Q: Can I use the GlobalReference type for the semanticId?

A: No, the GlobalReference type is not recommended for the semanticId of a Submodel Template. The current consensus states that the semanticId type should be ModelReference.

Q: What is the best practice for defining the semanticId of a Submodel Template?

A: The best practice is to follow the current consensus and use the semanticId/type = ModelReference and semanticId/keys[0].type = Submodel format. You should also review the ConceptDescription value and update it if necessary.

In conclusion, the issue of adding a specific semanticId to a Submodel Template is a complex one. By answering some of the most frequently asked questions related to this issue, we hope to provide clarity and guidance on how to resolve this problem. Remember to follow the current consensus and best practices to ensure data consistency and interoperability.

Based on the analysis provided, the following recommendations are made:

Follow the current consensus: Use the semanticId/type = ModelReference and semanticId/keys[0].type = Submodel format for the semanticId of a Submodel Template.
Review the ConceptDescription value: Update the ConceptDescription value if necessary to ensure it is relevant to the Submodel Template.
Remove the APPLICATION_CLASS category: Remove the APPLICATION_CLASS category from the table as it is no longer relevant.

By following these recommendations, you can ensure that your Submodel Templates are defined correctly and that data consistency and interoperability are maintained.