Home » RailTopoModel newsgroup » RailTopoModel » Network location
Network location [message #1887] Mon, 06 August 2018 11:40 Go to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 205
Registered: January 2016
Senior Member
Dear RTM colleagues,

RTM 1.1 model contains SpotLocations, LinearLocations and AreaLocations.
Although this approach covers all eventualities, there is potential for
simplification:

A new EntityLocation sub-class NetworkLocation would reference a
LocatedNetEntity to the whole Network (or LevelNetwork) without
explicitly naming all the contained NetElements. This approach will be
useful to define "global values", e.g. the railway electrification
parameters or the track gauge for the whole railway network.

Consequently, I suggest to improve RTM 1.2 by adding a new
EntityLocation sub-class NetworkLocation. Any comments are highly
appreciated...

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
Re: Network location [message #1898 is a reply to message #1887] Thu, 16 August 2018 10:36 Go to previous messageGo to next message
Airy Magnien is currently offline  Airy Magnien
Messages: 18
Registered: September 2016
Junior Member
Located net entities are net entities, and Net Entities are Network Resources. As such, they can be unambiguously associated with any Network or LevelNetwork without referring to any particular Net Element.

In your quoted example, a "global parameter" or (rather) "global subsystem description" would rather correspond with the Net Entity class. So far, I thought NetEntity to be an abstract class, but you just provided an example by which it could be meaningfully instantiated.

Provisional conclusion : your need seems to be fulfilled by the current version (RTM 1.1) without any changes.

If you agree with this conclusion, I'll update the wiki accordingly (or you - we'll toss it up).

[Updated on: Thu, 16 August 2018 10:42]

Report message to a moderator

Re: Network location [message #1971 is a reply to message #1898] Mon, 17 September 2018 13:37 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 205
Registered: January 2016
Senior Member
Dear RTM Expert Group,

Am 16.08.2018 um 10:36 schrieb Airy Magnien:
> Located net entities are net entities, and Net Entities are
> Network Resources. As such, they can be unambiguously associated with
> any Network or LevelNetwork without
> referring to any particular Net Element.
>
> [...]
>
> Provisional conclusioin : your requirement seems to be
> fulfilled by the current version (RTM 1.1) without any
> changes.

I am not sure whether my requirement is fulfilled by current RTM 1.1
without any changes. EntityLocation derived classes may only refer to an
instance of PositioningNetElement via "netElement". If I read the RTM
UML correctly, this reference cannot be used to refer to a Network or
LevelNetwork. Secondly, referencing a Network or LevelNetwork does not
require an attribute "applicationDirection" (SpotLocation and
LinearLocation) or "associatedNetElements" (AreaLocation).

So, to cut it short: I don't see how to use existing *Location classes
to model a reference to a Network in whole. Please correct me if I am wrong.

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
Previous Topic: Reference to PositioningSystem
Next Topic: Harmonize rolenames for association between *Location and *AssociatedNetElement
Goto Forum:
  


Current Time: Sat Feb 16 14:36:38 CET 2019