| Re: [railML3] InfrastructureVisualization [message #2640 is a reply to message #2255] |
Mon, 18 January 2021 15:49   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
individual discussions resulted in some new ideas for adapting the visualization model. Here, I want to present them and ask for your feedback:
1) The top level container element shall be <visualization> forming the route for the new visualization schema.
2) As a child element of <visualization> the element <views> shall be handled as container for all the different views of data. It is basically a re-naming of the element <visualizations> as known before.
3) The element <view> holds a graphical data representation. It is basically a re-naming of the element <visualization> as known before.
4) A <view> shall be of a specific type. Therefore, an enumeration attribute @type (values "infrastructure", "timetable", "rollingstock", ...) shall be added to <view>.
Any comments on these ideas are highly appreciated...
Thank you very much and best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
