Home » railML newsgroups » railml.interlocking » aspectRelation - multiplicity of references
aspectRelation - multiplicity of references [message #3945] Sun, 22 March 2026 14:57 Go to next message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 123
Registered: March 2016
Senior Member
Dear all,

in course of discussing the use of <aspectRelation> the need of mandatory elements are questioned.
Currently we have the mandatory elements of <slaveAspect> and <masterAspect> in <aspectRelation>. They would be especially needed in case there is a real dependency between aspect at route start and aspect at route end, i.e. the signalling covers more than one section.
In <slaveAspect> and <masterAspect> we have the mandatory element <refersToSignal> which refers to the <signalIL> at route start respectively at route end. As we also have a reference to <appliesToRoute> this information is duplicated (already contained in referred route).
The proposal is to make <refersToSignal> an optional element.

Please let me know your opinion.
---
Jörg von Lingen - Interlocking scheme coordinator

Report message to a moderator

Re: aspectRelation - multiplicity of references [message #3960 is a reply to message #3945] Fri, 10 April 2026 05:33 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 123
Registered: March 2016
Senior Member
Dear all,

I have checked the modelling w.r.t. the elements in <aspectRelation>. There is no change of mandatory parts sensible.
There is a basic type designed representing the tupel of a track asset and its status/position. In this construct it is comprehensible that each part of the tupel is mandatory. When defining <slaveAspect> or <masterAspect> this basic type is used. To change parts from mandatory to optional would mean to define a new basic type in parallel to the existing one. This I would consider not practical.

---
Jörg von Lingen - Interlocking scheme coordinator

Report message to a moderator

Previous Topic: modelling route proceed speed and approach speed in railML3
Next Topic: Defining the AreaLocation of a IL:RestrictedArea
Goto Forum:
  

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

Current Time: Sat May 09 15:22:50 CEST 2026