search

admin-shell-io / aas-specs

Repository of the Asset Administration Shell Specification IDTA-01001 - Metamodel
https://admin-shell-io.github.io/aas-specs-antora/index/home/index.html
Creative Commons Attribution 4.0 International
50 stars 26 forks source link

Submodel ID and Administrative Information: too restrict? #331

Open BirgitBoss opened 10 months ago

BirgitBoss commented 10 months ago

Context: Administrative Information Attributes, Notes

Note 1: two submodels with the same semanticId but different administrative information shall have different IDs (Submodel/id), since they denote that the submodel is not backward compatible or has some other major administrative changes. The idShort typically does not change. The same applies to other identifiables (Identifiable/id). Otherwise, the ID of a submodel would not be sufficient to identify the data or service provided by the submodel.

Note 2: since submodels with different versions shall have different identifiers, it is possible that an Asset Administration Shell has two submodels with the same semanticId but different versions, i.e. different administrative metainformation.

Note 3: some of the administrative information like the version number might need to be part of the identification. This is similar to the handling of identifiers for concept descriptions using IRDIs. In ECLASS, the IRDI 0173-1#02-AO677#002 contains the version information 002.

Note 4: the process of versioning or adding other administrative information to elements is done by external version or configuration management software and not by the Asset Administration Shell itself.

The attributeAdministrativeInformation/creatorand the AdministrativeInformation/templateId was added in V3.0 but the notes were not updated. So now it is requested that if the value of the creator or template ID attribute is changed that a new Submodel ID must be created.

Proposal: Substitute with the following rules:

If an AAS contains two different Submodels with the same semanticId (Submodel/semanticId) these two submodels shall have different IDs (Submodel/id) and differ in either their a) version (Submodel/administration/version) (revision is ignored) or b) their creator (Submodel/administration/creator). With a) both submodels shall have version information. With b) both submodels shall have a creator.

Note 1: typically, some of the administrative information like the version number might be part of the identification (Submodel/id). This is similar to the handling of identifiers for concept descriptions using IRDIs. In ECLASS, the IRDI 0173-1#02-AO677#002 contains the version information 002.

Note 2: since submodels with different versions shall have different identifiers, it is possible that an Asset Administration Shell has two submodels with the same semanticId but different versions.

If an AAS contains two different Submodels guided by the same SMT, i.e. have the same templateId value (Submodel/administration/templateId), then the two submodels shall have different IDs (Submodel/id). In this case both Submodels shall have a templateId assigned to them (Submodel/administration/templateId).

Note 1: In some cases there is neither a semanticId (Submodel/semanticId) nor a templateId (Submodel/administration/templateId) defined for the Submodel. In this case there is no way for the data consumer to formally see whether two Submodels are providing the same semantic information.

Note 2: If a template ID of one of the standardized Submodel Templates of the IDTA is used to guide the creation of a Submodel then there is also a semantic ID defined for the Submodel.

These rules are backward compatible since they are less restrictive then the current notes. No "shall-" rules should be contained in notes (conformant to IEC rules of writing standards)

alexgordtop commented 2 months ago

2024-09-04 - TF Part 1 of AAS Working Group: Approved