Issue ID
28
Component
UML General
Category
Bug report
Priority
Normal
Status
Fixed
Source
Website
Description
The submitted Editorial changes to the CEN drafts leads to the following changes
1. modelBaseVersion tagged value should have the value 2 in the model
2. A new tagged value version in the model
Jonas comment: I suppose we create a new version tagged value on the D2LogicalModel class.
The tool will be updated to map the version tagged value to the schema version attribute.(own issue)
{"changeLogs":[{"date":1528364594494,"componentOLD":"- Select a value -","component":"UML General","categoryOLD":"- Select a value -","category":"Bug report","priorityOLD":"- None -","priority":"Normal","statusOLD":"- None -","status":"Fixed"},{"date":1537270405135}]}
#1
I prefer to name this tagged value modelVersion. The intial idea was to call it version, but in XMI/XML there is a lot of tagged values called version, so modelVersion would be easier and less rules needed to extract the "version" we need. modelVersion should still map to version attribute in XSD.
#2
Not possible. I see that in the CEN part that we states "The class shall furthermore have a UML Tagged
Value named "version" with a value of the full version".
So the tagged value should be "version"
#3
Fixed in v2.0!