Home » railML newsgroups » railML.infrastructure » [railML3] Proposal of a semantic constraint for <baliseGroup>
[railML3] Proposal of a semantic constraint for <baliseGroup> [message #3329] Fri, 27 September 2024 12:28
Milan Wölke is currently offline  Milan Wölke
Messages: 146
Registered: April 2007
Senior Member
Hi all,

the ETCS working group introduced a semantic constraint for balise groups documented in the working groups documentation for the element <baliseGroup> and <balise>. The following wording was proposed:

Quote:

The element "baliseGroup" shall always use the railML option "spotLocation" to define the balise group location on the topology.
The same wording would apply for "balise".

The following reasoning was given by the working group:

According to UNISIG-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 3.4.2.2.1 and UNISIG-040 (versions 2.3.0, 3.3.0 or 3.4.0) section 3.3.1.3, a balise group (represented by the railML element "baliseGroup") shall be considered as point-shaped element without extension. The reference location of the balise group is the location of the balise with N_PIG=0.

In extension the balise also is considered a point-shaped element.

Therefore I would propose to add the quoted wording above as a semantic constraint for balise and balise group.

What do you think? Are there objections to this?

Best regards, Milan


Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Proposal of a semantic constraint for mileageChange
Next Topic: [railML3] Mandatory stop at level crossing
Goto Forum:
  


Current Time: Mon Oct 14 13:19:05 CEST 2024