Problem
Some of the Submodel Templates (SMTs) of the Digital Battery Passport carry the same semantic ID as the SMTs that they derived from. This is the case for Handover Documentation and Carbon Footprint.
Why this is an issue
For many operations, it is necessary to identify the associated SMT for a submodel instance (SMI), for example to retrieve omitted semantic information or template qualifiers. Per standard, there are two options to do so:
- Comparing the SMI's administration.templateId with the SMT's submodel id
- Comparing the SMI's semantic Id with the SMT's semantic id
Neither attributes (templateId, semantic Id) must be set for an instance. (However, arguably, there is no proper way to interpret submodels/submodel elements without semantics, anyway.) As such, it is of utmost importance that an SMI has a semantic ID that allows for a unique mapping to a SMT.
In the current situation, DBP HandoverDocumentation/Carbon Footprint SMIs are ambigious wrt. to their defining SMTs (wrt. to the semantic id). Thus it is unclear whether an SMI describes a DBP HandoverDocumentation/Carbon Footprint, or a general HandoverDocumentation/Carbon Footprint. This has direct consequences when working with the data: when using a more permissive SMTs as the basis to modify a specialized SMI, the specialized SMI potentially no longer conforms to the specialized SMT.
What change do we expect
All SMTs, also specialized ones, should have a unique Semantic ID.
Additional Considerations
The DBP SMTs use inconsistent patters for their IDs/semantic ids. Ideally, a consistent scheme is applied for the creation of these identifiers throughout all DBP SMTs. The formats found in the SMTs are:
- Digital Nameplate (same pattern schema as for Technical Data, Product Carbon Footprint)
- id:
https://admin-shell.io/idta/SubmodelTemplate/DigitalBatteryPassport/DigitalNameplate/1/0
- semantic id:
https://admin-shell.io/idta/digitalbatterypassport/nameplate/1/0/Nameplate
- Handover Documentation:
- semantic id: "0173-1#01-AHF578#003"
- Product Condition (same pattern schema as for Material Composition, Circularity):
- id:
urn:samm:io.admin-shell.idta.batterypass.product_condition:1.0.0#ProductCondition/submodel
- semantic id:
urn:samm:io.admin-shell.idta.batterypass.product_condition:1.0.0#ProductCondition
Note
Changes here also affect [https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.2/annex/dpp.html](AAS Spec 3.2 Part 1 Annex DPP); where the DBP Carbon Footprint Semantic ID is supposed to look as above.
Problem
Some of the Submodel Templates (SMTs) of the Digital Battery Passport carry the same semantic ID as the SMTs that they derived from. This is the case for Handover Documentation and Carbon Footprint.
Why this is an issue
For many operations, it is necessary to identify the associated SMT for a submodel instance (SMI), for example to retrieve omitted semantic information or template qualifiers. Per standard, there are two options to do so:
Neither attributes (templateId, semantic Id) must be set for an instance. (However, arguably, there is no proper way to interpret submodels/submodel elements without semantics, anyway.) As such, it is of utmost importance that an SMI has a semantic ID that allows for a unique mapping to a SMT.
In the current situation, DBP HandoverDocumentation/Carbon Footprint SMIs are ambigious wrt. to their defining SMTs (wrt. to the semantic id). Thus it is unclear whether an SMI describes a DBP HandoverDocumentation/Carbon Footprint, or a general HandoverDocumentation/Carbon Footprint. This has direct consequences when working with the data: when using a more permissive SMTs as the basis to modify a specialized SMI, the specialized SMI potentially no longer conforms to the specialized SMT.
What change do we expect
All SMTs, also specialized ones, should have a unique Semantic ID.
Additional Considerations
The DBP SMTs use inconsistent patters for their IDs/semantic ids. Ideally, a consistent scheme is applied for the creation of these identifiers throughout all DBP SMTs. The formats found in the SMTs are:
https://admin-shell.io/idta/SubmodelTemplate/DigitalBatteryPassport/DigitalNameplate/1/0https://admin-shell.io/idta/digitalbatterypassport/nameplate/1/0/Nameplateurn:samm:io.admin-shell.idta.batterypass.product_condition:1.0.0#ProductCondition/submodelurn:samm:io.admin-shell.idta.batterypass.product_condition:1.0.0#ProductConditionNote
Changes here also affect [https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.2/annex/dpp.html](AAS Spec 3.2 Part 1 Annex DPP); where the DBP Carbon Footprint Semantic ID is supposed to look as above.