Home » railML newsgroups » railml.common » [railML 3.4 beta 4] topology netelements no longer have validity
[railML 3.4 beta 4] topology netelements no longer have validity [message #4044] Tue, 16 June 2026 21:15 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
Senior Member
Hello,

I'm trying to make sense of the changes in the rtm4railml3 schema. It seems RTM_NetworkResource now still extends from RTM_NamedResource but it no longer adds the element:

<xs:element name="isValid" type="rail3:RTM_Validity" minOccurs="0" maxOccurs="unbounded"/>

I'm guessing that this is due to RTM_NetEntity receiving the elementState element:

	<xs:complexType name="RTM_NetEntity">
		<xs:annotation>
			<xs:documentation>Objects like infrastructure assets can be located on the network as NetEntities</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="rail3:RTM_NamedResource">
				<xs:sequence>
					<xs:element name="elementState" type="rail3:SubSchemaElementState" minOccurs="0" maxOccurs="unbounded"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

However, this means that it's no longer possible to assign validity periods to other elements that are inheriting from RTM_NamedResource, such as RTM_NetElement, RTM_Network, RTM_Relation, ...

This is a major change! I'm guessing that this was an accident and perhaps the intention was to put the new elementState element on the RTM_NamedResource where previously the validity was?


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

[Updated on: Tue, 16 June 2026 21:16]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Designator for linearPositioningSystem
Next Topic: [Ontology v0.6] minor comments on Classes & their definition
Goto Forum:
  


Current Time: Wed Sep 09 15:22:36 CEST 2026