Template:Table/Dev:SemanticConstraints

Return to article

Element	ID	Proposal date	Working groups	Date of acceptance	Date of deprecation	Description
<TT:operationalTrainSectionPart>	TT:001	2022-09-15	2022-10-13			@next shall reference an <operationalTrainSectionPart> that is not referenced by any other @next-reference. In other words: Within the chain of <operationalTrainSectionPart> elements linked by the @next, there can be no element that has more than one predecessor. The @next reference must establish a one to one relationship between two <operationalTrainSectionPart>s.
<TT:operationalTrainVariant>	TT:002	2023-01-12	2023-04-06			When calculating which <operationalTrainVariant> of an <operationalTrain> is valid on a particular day always a maximum of one active <operationalTrainVariant> shall be the result. If the result is more than one <operationalTrainVariant>, all except one shall be marked as <isCancelled> or <isOnRequest>.
<TT:commercialTrainVariant>	TT:003	2023-01-12	2023-04-06			When calculating which <commercialTrainVariant> of a <commercialTrain> is valid on a particular day always a maximum of one active <commercialTrainVariant> shall be the result. If the result is more than one <commercialTrainVariant>, all except one shall be marked as <isCancelled> or <isOnRequest>.
<TT:operationalTrainSection>	TT:004	2022-01-12		2023-03-09		The itinerary sections of an <operationalTrainVariant>, defined by the <operationalTrainSection>s and their respective <range>s, that are not <isCancelled> and not marked as <isOnRequest>, must be pairwise disjoint, except for their respective first and last <baseItineraryPoint>s.
<TT:operationalTrainSection>	TT:005	2022-01-12		2023-03-09		The first(last) <baseItineraryPoint> of each <operationalTrainSection> within an <operationalTrainVariant> must either be the referenced <itinerary>'s first(last) <baseItineraryPoint>, or coincide with another section's last(first) <baseItineraryPoint>.
<TT:commercialTrainSection>	TT:006	2022-01-12		2023-03-09		The itinerary sections of a <commercialTrainVariant>, defined by the <commercialTrainSection>s and their respective <range>s, that are not <isCancelled> and not marked as <isOnRequest>, must be pairwise disjoint, except for their respective first and last <baseItineraryPoint>s.
<TT:commercialTrainSection>	TT:007	2022-01-12		2023-03-09		The first(last) <baseItineraryPoint> of each <commercialTrainSection> within a <commercialTrainVariant> must either be the referenced <itinerary>'s first(last) <baseItineraryPoint>, or coincide with another section's last(first) <baseItineraryPoint>.
<RTM:isValid>, <CO:validityTime:period>	IS:001	2024-01-15	2024-02-26 ETCS WG 2024-03-22 SCTP WG 2024-04-15 NEST WG			Starting time stamp (e.g. "from") shall be lower or equal any ending time stamp (e.g. "to") if both are given. Must not overlap with other validity periods.
<IS:signalConstruction>	IS:005	2024-01-22	2024-03-22 SCTP WG 2024-04-15 NEST WG	2025-02-03 Modelling coordination meeting		@height and @positionAtTrack should not be used with @type=virtual.
<IS:border>	IS:007	2024-01-29	2024-08-09 SCTP WG 2025-01-28 NEST WG			If the attribute @isOpenEnd="true" then the value of @type shall be set to "area".
<IS:netElement>	IS:008	2024-02-02	2024-08-09 SCTP WG			Aggregation of net elements should follow the tree data structure. See figure below. This means that no two (mesoscopic) net elements can aggregate same (microscopic) net element. In other words, (microscopic) net element can be aggregated by at most one (mesoscopic) net element.
<IS:netElement>	IS:009	2024-02-02	2024-08-09 SCTP WG			Linear (geometric) coordinates (explicit or implicit, e.g. calculated as a sum of the coordinate of beginning and the length of the net element) of the same place represented at different levels of aggregation should have the same value. In the figure below (linear) coordinate the coordinate of e.g. end of ne1 should be same as one of ne1.2.
<IS:netElement>	IS:010	2024-02-26				Difference of linear coordinates if the beginning and end of <netElement>, represented by <intrinsicCoordinate> / @intrinsicCoord = 0 and 1 correspondingly, should equal the the @length of <netElement> if all are present in the data. For each case when a difference of linear coordinates if the beginning and end of <netElement>, represented by <intrinsicCoordinate> / @intrinsicCoord = 0 and 1 correspondingly, does not equal the the @length of <netElement> if all are present in the data, a <mileageChange> of <anchor> should be present explaining anomaly
<IS:netElement>	IS:011	2024-02-29	2024-08-09 SCTP WG			Aggregation must not happen within the same level of detail. In the figure below, element 1.1 must not aggregate element 1.2. This means that aggregating and aggregated net elements must not be referred from the same <level>
<RTM:spotLocation>	IS:012	2024-03-04	2024-04-19 SCTP WG 2024-05-13 ETCS WG			@pos should have only positive values because it's a distance, thus -1 is not a valid value
<RTM:linearPositioningSystem>	IS:014	2024-04-08	2024-04-15 NEST WG 2024-04-19 SCTP WG			@startMeasure and @endMeasure are start and end values of a railway <IS:line> associated with <RTM:linearPositioningSystem> not max and min values of a current file with e.g. line section.
<IS:netRelation>	IS:015	2024-04-22	2024-08-09 SCTP WG			There must be no "inverse" net relations in the topology, i.e. if "nr1 elemeneA ne1", "nr1 elementB ne2" and "nr2 elemeneA ne2", "nr2 elementB ne1" then topology is not valid. See invalid code below.
<IS:trainProtectionElement>	IS:017	2009-10-17	2009-10-17			Users can refer to the train protection system using the attribute @trainProtectionSystem that shall link to the codelist (link to the railML® website) TrainProtectionSystems.xml (link to the railML® website), section trainProtectionSystemsAtTrack. Only if this list does not contain the specific train protection system to be modelled, it shall be described in its functionality using attributes @medium and @monitoring.
<IS:opEquipment>	IS:018	2024-08-26				Any functional infrastructure element that belongs to an <operationalPoint> may be listed as its equipment. This may be done by adding it to a specific container, such as <ownsPlatform>, <ownsTrack> and <ownsSignal> or it may be added to the generic container <ownsInfrastructureElement>. Any such added infrastructure element must be added to the most specific container available. No element shall be part of two such containers. If no specific container for the functional infrastructure element exists, it shall be listed in the generic container. Example: a <signalIS> must not be added to <ownsInfrastructureElement>. It shall be added to <ownsSignal>. As there is no container for levelCrossings a <levelCrossingIS> belonging to an <operationalPoint> shall be added to <ownsInfrastructureElement>.
<IS:infrastructureState>	IS:019	2024-09-03	2024-09-13 SCTP WG			When calculating which <infrastructureState> of an <infrastructure> is valid on a particular time always a maximum of one active <infrastructureState> shall be the result.
<TT:times>	TT:008	2024-11-21	2024-12-19	2025-04-07		No two attributes //<times>@scope of the same enclosing <baseItineraryPoint> element shall have the same value.