SDT issueshttps://git.onem2m.org/MAS/SDT/-/issues2019-06-22T02:04:00Zhttps://git.onem2m.org/MAS/SDT/-/issues/8'@name' in 'Module' vs in 'ModuleClass'2019-06-22T02:04:00ZYongjing Zhang'@name' in 'Module' vs in 'ModuleClass'According to current definition, 'Module' is the subclass of 'ModuleClass'. So a 'Module' should inherit the '@name' attribute from 'ModuleClass'.
In the example of 'mseed.xml', 'extends' from ModuleClass "BooleanState", the 'name' at...According to current definition, 'Module' is the subclass of 'ModuleClass'. So a 'Module' should inherit the '@name' attribute from 'ModuleClass'.
In the example of 'mseed.xml', 'extends' from ModuleClass "BooleanState", the 'name' attribute is overridden as "power". Does this mean the Module "power" no longer contain the attribute 'name'="BooleanState", but only 'name'="Power"?
<Modules>
<Module name="power">
<extends domain="hgi.dal.core" class="BooleanState"/>
</Module>
</Modules>
Or should it be modeled as an extended attribute: "ModuleInstanceName" (according to TS-0023, or find another similar term) so as to keep the original *type* information (i.e. "BooleanState") in the Module subclass? In this case, "Module" really becomes something more than "ModuleClass".
<Modules>
<Module instanceName="power">
<extends domain="hgi.dal.core" class="BooleanState"/>
</Module>
</Modules>