You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi in #85 I voiced my confusion about how the modelling of Provision of 3dModels.
It did not let me go so I dug deep into the metamodel and tried to find out what led to this way of modelling and I believe with more intuitive naming the problem could be helped.
My Proposal is to rename some Entities and Change the way Submodel Element Lists are documented in this template.
The Issue that I have with the naming right now is:
The ID short of the submodel does not match the actual name of the Submodel. This creates confusion and also blocks the name "simpler" name to be used when an Entity actually describes that "simpler" thing.
A Container should be named in a way that makes you undestand what it contains. eg. the list Model3D does not contain a model but can contain multiple. So it should be called Models3D.
The Tables for SMLs in this specification take a shortcut by skipping to describe its childs. Instead they desribe the childs of the child, which leads to multiple problems. For one applicants now dont know what semantic ID to give the childs. Same goes for the explanation. secondly you loose the chance to specify the cardinality, which will lead to a number of problems. I cant find anything suggesting this shortcut in the Guidon how to write a submodel template and also no hint to handle SML in this special way in the metamodel.
In the following I will demonstrate with a few pictures my proposed changes:
renaming the Submodel
renaming all SML containers if their names don't represent the entities they contain.
Changing the way the Entities of SMLs are modeled and documented and therefore giving them an explicit semantic ID, Explanation and Cardinality.
Of course I wont go through the whole submodel, but the provided pictures should demonstrate the principle.
The digital nameplate, Provisioning of 3D models and the BOM are entrypoint to the AAS and should not require the digging i had to do to undestand what is meant and why there are unnamed entities in the AASX i get provided.
I hope this helps you increase the quality of your informationmodel.
Best regards MWLY
Edit: Spelling
The text was updated successfully, but these errors were encountered:
Hi in #85 I voiced my confusion about how the modelling of Provision of 3dModels.
It did not let me go so I dug deep into the metamodel and tried to find out what led to this way of modelling and I believe with more intuitive naming the problem could be helped.
My Proposal is to rename some Entities and Change the way Submodel Element Lists are documented in this template.
The Issue that I have with the naming right now is:
In the following I will demonstrate with a few pictures my proposed changes:
Of course I wont go through the whole submodel, but the provided pictures should demonstrate the principle.
The digital nameplate, Provisioning of 3D models and the BOM are entrypoint to the AAS and should not require the digging i had to do to undestand what is meant and why there are unnamed entities in the AASX i get provided.
I hope this helps you increase the quality of your informationmodel.
Best regards MWLY
Edit: Spelling
The text was updated successfully, but these errors were encountered: