Home » railML newsgroups » railML.infrastructure » Stopping Place use cases (What is the difference, from a semantic point of view, among PlatformEdge/StoppingPlace/OperationalPoint?)
Stopping Place use cases [message #2292] Thu, 12 December 2019 08:32 Go to previous message
Luca Carbone is currently offline  Luca Carbone
Messages: 2
Registered: December 2019
Junior Member
Greetings,
I am a new user working for Hitachi Rail STS, in particular I am part of the SW development pool dealing with system integration and how railML can support our workflow, nice to meet you all.

While working on the implementation of <StoppingPlace> a few questions came to mind and I was hoping that somebody may be able to help.

Coming also from a quick search on the forum for previous questions, there seems to be some possible overlap between <StoppingPlace> itself and both <PlatformEdge> (which it actually refers to via <aStoppingPlace>@PlatformEdgeRef) and an <OperationalPoint> with an <OpOperation>@operationalType=="StoppingPoint" child.

What is the difference, from a semantic point of view, among the three objects: <PlatformEdge>, <StoppingPlace>, <OperationalPoint>@operationalType=="StoppingPoint" and when do they need to be used? Are there different use cases for the above elements? Which would be the more general case?

Thanks and best regards,
Luca Carbone

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: [railML2] @dir
Next Topic: extension of <levelCrossing> in railML2.4nor
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Apr 20 16:09:43 CEST 2024