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
The xml description of a version of the REXS standard is called a "model", e.g. rexs_model_1.6.xml
A description of a gearbox, i.e. a REXS file, is called a "model", e.g. in the class RexsModel
This can lead to some misunderstanding as well as some overlapping class names and descriptions. I propose the following new wording, which then also needs to be rolled to the publich database:
A single REXS file myGearbox.rexs is called a "REXS Model" or short "Model". Consequently, the name of the class RexsModel can be kept, as it represents a single model of an actual gearbox.
The XML files defining a version of REXS will be called "REXS Schema". This means, that:
Files like rexs_model_1.6.xml should be renamed to rexs_schema_1.6.xml
Classes like DbModelRegistry need to be renamed to RexsSchemaRegistry
The packages and folders called db should be renamed to schema
The public database and help resources should be rewritten to consequently use the term "REXS Schema".
For completeness: The correct term for all XSD files should be "XML Schema" or in short just "XSD". Folders and packages containing/handling XSDs should be renamed to xsd.
Currently, the word "model" is used twice:
RexsModel
This can lead to some misunderstanding as well as some overlapping class names and descriptions. I propose the following new wording, which then also needs to be rolled to the publich database:
myGearbox.rexs
is called a "REXS Model" or short "Model". Consequently, the name of the classRexsModel
can be kept, as it represents a single model of an actual gearbox.rexs_model_1.6.xml
should be renamed torexs_schema_1.6.xml
DbModelRegistry
need to be renamed toRexsSchemaRegistry
db
should be renamed toschema
xsd
.To-Dos (@karstenroethig):
rexs_schema_X.X.xml
DbModelRegistry
(and connected) toRexsSchemaRegistry
db
toschema
(on various locations)The text was updated successfully, but these errors were encountered: