| railML 2.3 infrastructure extension proposal - "change" [message #1633] |
Thu, 31 August 2017 13:02  |
Torben Brand
Messages: 157
Registered: March 2016
|
Senior Member |
|
|
For the use case "capacity planning" we need to define workflow states that are not fixed in time but in a work flow.
Sometimes changes to elements must be made visible. This can either be made through two files and creating a delta or by declaring the changes in the new suggested attribute @nor:change that can be placed under any element.
Enumeration values:
"none": No changes to the model from its last state
"new": a new element has been added to the model
"modified": values if an existing element have been changed
"deleted": an element has been removed from the model
If no change values is defined the default value is "none".
This feature is usually used in the signalling workflow with the colours:
New = green
Modified = blue
Deleted = red
None (everything else) = black
Placing the new attribute nor:change
Changes are placed on the elements that have a change. For changes that span an entire track the change is placed on the track and all elements on the track inherit the change. For changes that span more than one ocp the change is placed on the infrastructure element.
|
|
|
|
Members
Search
Help
Login
Home
