Template:Table/Dev:SemanticConstraintsDeprecated

Return to article

Element	ID	Proposal date	Working groups	Date of acceptance	Date of deprecation	Description
<IS:trainProtectionElement>	IS:002	2021-02-26	2024-02-26 ETCS WG 2024-03-22 SCTP WG 2024-04-15 NEST WG		2025-02-03 Modelling coordination meeting	<trainProtectionElement> shall only be used for national and/or legacy train protection systems. ETCS-based systems must not be modeled using <trainProtectionElement>.
<IS:levelCrossingIS>	IS:003	2023-10-23	2024-02-26 ETCS WG 2024-03-22 SCTP WG 2024-04-15 NEST WG		2025-02-03 Modelling coordination meeting	<levelCrossingIS> should not have a <crossesElement> child of type railway. This case should be represented either by a <crossing> in case of a simple crossing, or by a <switchIS> of type doubleSwitchCrossing or singleSwitchCrossing.
<IS:underCrossing>, <IS:overCrossing>	IS:004	2023-10-23	declined		2024-02-26	should only have a <crossesElement> child of type railway when railway crosses railway (not on the same level!).
<IS:line>	IS:006	2024-01-29	2024-02-26 ETCS WG 2024-04-15 NEST WG		2025-04-11	each line with own mileage should always be associated with its own <linearPositioningSystem>, i.e. Advanced example of railML has three lines with their own mileages, thus should have thee <linearPositioningSystem>s.
<IS:gradientCurve>	IS:016	2024-05-31	declined		2024-12-06 SCTP WG	@gradient should not be used if @curveType="mixed". Instead of @gradient, @deltaGradient should be used.
<IS:speedSection>	IS:020	2022-04-25			2025-02-03 Modelling coordination meeting	Each railML® <speedSection> element must reference (at least) one global defined railML® <speedProfile> element.