Is your feature request related to a problem? Please describe.
Especially when developing SMT, it would be helpfull to work with a SM.json/.xml only and not to be forced to use an .aasx.
It is easier to synchronise only one "simple" file via git, to boost collaboration.
Furthermore, the mechanism of referencing from an AAS to the SM and from a SME to the ConceptDescription (as it is currently implemented), will be more present, when modelling i.e., the awareness that AAS, SM and ConceptDescriptions are standalone objects referencing to each other.
Debuging will become more effective as only the Submodel, not the AAS, nor the Concept Desciption will be part of the SM file.
On the other hand, the handling of the AASPE will differ, users need to "think" more in the way AAS is referencing to each or to files.
Working with .aasx files should be still possible.
Describe the solution you'd like
The AASPE should be able to load, let a user manipulate and safe an SM.json/.xml only.
Describe alternatives you've considered
Reform the process: Having a "dummy" .aasx file, load the SM.json/.xml, manipulate it and export just the SM.json/.xml.
Additional context
...
Is your feature request related to a problem? Please describe.
Especially when developing SMT, it would be helpfull to work with a SM.json/.xml only and not to be forced to use an .aasx.
It is easier to synchronise only one "simple" file via git, to boost collaboration.
Furthermore, the mechanism of referencing from an AAS to the SM and from a SME to the ConceptDescription (as it is currently implemented), will be more present, when modelling i.e., the awareness that AAS, SM and ConceptDescriptions are standalone objects referencing to each other.
Debuging will become more effective as only the Submodel, not the AAS, nor the Concept Desciption will be part of the SM file.
On the other hand, the handling of the AASPE will differ, users need to "think" more in the way AAS is referencing to each or to files.
Working with .aasx files should be still possible.
Describe the solution you'd like
The AASPE should be able to load, let a user manipulate and safe an SM.json/.xml only.
Describe alternatives you've considered
Reform the process: Having a "dummy" .aasx file, load the SM.json/.xml, manipulate it and export just the SM.json/.xml.
Additional context
...