Home » railML newsgroups » railML.infrastructure » Use the concept of layer for splitting the data
Use the concept of layer for splitting the data [message #328] Wed, 04 July 2012 19:09 Go to next message
pierre.simon is currently offline  pierre.simon
Messages: 8
Registered: July 2012
Junior Member
After discussing it seems that the approach railML wants to follow is to
split the data into different layers for the next major release.
Regarding the infrastructure in Belgium, here are some layers which could
be identified:
- Topology
- Geometry (horizontal / vertical)
- Line side signalization
- Protection systems
- Speed
- Platforms
- Electrification
- Itineraries / Interlocking
- LEU
- Tunnels
- Bridges
- Level Crossings
- ...

Please implement a layer concept in the next railML's version.

[de: In der naechsten railML-Version sollte die Infrastrukturverwaltung
auf ein Layer-Konzept umgestellt werden. Diese sollte die oben genannten
Elemente getrennt beinhalten.]

--
----== posted via PHP Headliner ==----
Re: Use the concept of layer for splitting the data [message #339 is a reply to message #328] Thu, 05 July 2012 06:12 Go to previous messageGo to next message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Hello Pierre,

> Please implement a layer concept in the next railML's version.

thank you very much for your very important post. Especially the railML
infrastructure sub-schema needs to be updated and improved in many
cases, which are not compatible with railML 2.x. The layer concept is a
central issue which belongs to this next major release of railML 3.0. At
the moment, we are working on a railML 2.2. However, in order not to
forget about this layer approach, I created a trac ticket #154 [1].

[1] https://trac.assembla.com/railML/ticket/154

Regards

---
Christian Rahmig
railML.infrastructure coordinator
Re: Use the concept of layer for splitting the data [message #2106 is a reply to message #339] Fri, 18 January 2019 15:10 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear all,

Am 05.07.2012 um 06:12 schrieb Christian Rahmig:
> Hello Pierre,
>
>> Please implement a layer concept in the next railML's version.
>
> [...] However, in order not to
> forget about this layer approach, I created a trac ticket #154 [1].
>
> [1] https://trac.assembla.com/railML/ticket/154

upcoming railML 3.1 implements the layer concept for the infrastructure
domain. Furthermore, the layer approach has become a Modeling Design
Pattern for railML 3.x future development (see [2]).

Consequently, the Trac ticket #154 [1] can finally be closed.

[2]
http://forum.railml.org/userfiles/2019-01-16_railml_railml3- modelling-patterns.pdf

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: Multiple train protection systems
Next Topic: Infrastructure registers
Goto Forum:
  


Current Time: Thu Mar 28 16:44:35 CET 2024