Forum: railML.infrastructure » Mandatory elements for NEST UC

Home » railML newsgroups » railML.infrastructure » Mandatory elements for NEST UC (NEST)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Mandatory elements for NEST UC [message #3634]

Tue, 27 May 2025 16:53

Torben Brand
Messages: 214
Registered: March 2016

Senior Member

This is a posting To be discussed in common NEST SCTP meeting in June.

I think the following track@type [1] should be mandatory in NEST UC:
Main: yes
Siding: no
Secondary: optional
Connecting: optional/no (depends how modelled)

All signalIs<isMovementSignal> [2] should be optional/mandatory
all other signals: no (as covered in SCTP)
signalIL@function [3]: yes/optional Challenge is that we introduce a new subschema to the UC, but this should be ok for only one element

[1] https://wiki3.railml.org/wiki/IS:track#3.3-0
[2] https://wiki3.railml.org/wiki/IS:isTrainMovementSignal#3.3-0
[3] https://wiki3.railml.org/wiki/IL:signalIL#3.3-0

[Updated on: Mon, 23 June 2025 13:44]

Report message to a moderator

[Message index]

		Mandatory elements for NEST UC By: Torben Brand on Tue, 27 May 2025 16:53
		Re: Mandatory elements for NEST UC By: Fredrik Jönsson on Tue, 02 September 2025 08:48
		Re: Mandatory elements for NEST UC By: Silvan Gruber on Mon, 06 October 2025 08:57

Previous Topic:	[railML3] Making consistent linearPositioningSystem and linear coordinates
Next Topic:	Handling of netElement directions in switches and crossings

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Jul 19 06:04:30 CEST 2026