View source for Dev:changes/2.5

{{navi}}
{{head|{{rml}} schema changes between {{rml}} 2.4 and {{rml}} 2.5}}

This site is intended to collect the schema changes between {{rml}} 2.4 and {{rml}} 2.5.

A complete diff comparison will soon be available under [[Dev:changes/2.5/diff]].

Changes are also marked on the element pages with {{Vers|introduced with version 2.5}} for introduced components and {{depVers|deprecated with version 2.5}} for components that became obsolete. All occurances of these tags are listed in [[:Category:Intro/2.5]] respectively [[:Category:Depr/2.5]].

For changes with other version upgrades see [[Dev:changes]].

==Common Subschema==
===New element {{tag|CO|projects}}===
{{change
|fact=Describing the purpose of the model in a related project.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|390}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|CO|projects}}, {{tag|CO|project}}, {{tag|CO|designator}}, {{tag|CO|alternative}}, {{tag|CO|phase}}, {{tag|CO|revision}}, {{tag|CO|objectsRevised}}, {{tag|CO|revisedBy}}, {{tag|CO|checkedBy}}, {{tag|CO|approvedBy}}
|uelem=
}}

==Timetable Subschema==
===New {{@|onRequest|TT:trainPart}} for {{tag|TT|trainPart|attr=onRequest}}===
{{change|fact=new attribute {{@|onRequest}} (bool) has been added in element {{tag|TT|trainPart}} in order to allow for standardized modelling of onRequest journeys.|reason=Required by railML partner. Also this should help avoiding modelling of onRequest journeys using special train categories.
[[File:Anpassungen railML 2 -Bedarfszüge.pdf|thumb]]
|trac={{ticket|372}}|nattr={{@|onRequest|TT:trainPart}}|uelem={{tag|TT|trainPart|attr=onrequest}}}}

===New value {{enum|other:anything}} for {{Tag|TT|category|@=trainUsage}}===
{{change
|fact={{Tag|TT|category|@=trainUsage}} has been extended to allow for custom values
|reason=The demand for more distinguished categories appeared in {{site|1=https://www.railml.org/forum/index.php?t=msg&goto=2271&#msg_2271|2=this discussion}}
|recomendation=
|trac={{ticket|375}}
|svn={{SVN|1039}}
|example=
|xsd=railwayBaseTypes.xsd
|nattr=
|uattr={{Tag|TT|category|@=trainUsage}}
|nelem=
|uelem={{Tag|TT|category|attr=trainUsage}}
}}

===New values {{enum|conceptual}} and {{enum|offered}} for {{Tag|TT|trainPartSequence|@=pathStatus}}===
{{change
|fact={{Tag|TT|trainPartSequence|@=pathStatus}} has been extended to allow for the values {{enum|conceptual}} and {{enum|offered}} to improve how to express the state of an slot order
|reason=The demand for clearer modelling of the states for slot ordering showed up in {{site|https://www.railml.org/forum/index.php?t=msg&th=681&start=0|this discussion}}
|recomendation=
|trac={{ticket|378}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{Tag|TT|trainPartSequence|@=pathStatus}}
|nelem=
|uelem={{Tag|TT|trainPartSequence|@=pathStatus}}
}}
===New child {{TT:Tag|originalTrackInfo}} for {{Tag|TT|ocpTT}}===
{{change
|fact=New child {{TT:Tag|originalTrackInfo}} for {{Tag|TT|ocpTT}}
|reason=Allow for better communication of track changes
|recomendation=
|trac=
|svn=
|example=
|xsd=timetable.xsd
|nattr=
|uattr=
|nelem={{TT:Tag|originalTrackInfo}}
|uelem={{Tag|TT|ocpTT}}
}}
===New children {{tag|TT|origin}} and {{tag|TT|destination}} for {{tag|TT|trainPart}}===
{{change
|fact=New children {{tag|TT|origin}} and {{tag|TT|destination}} for {{tag|TT|trainPart}}
|reason=allows for specifying information about the origin/destination of the train if it cannot be derived from its path (trains entering/leaving the operated area).
|recomendation=
|trac=
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|origin}}, {{tag|TT|destination}} & their respective childs
|uelem={{tag|TT|trainPart}}
}}
===New Child {{tag|TT|announcementRef}} for {{tag|TT|stopDescription}} and {{tag|TT|trainPart}}===
{{change
|fact=New Child {{tag|TT|announcementRef}} for {{tag|TT|stopDescription}} and {{tag|TT|trainPart}}
|reason=broad revision of annotations
|recomendation=
|trac=
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|announcementRef}} & childs
|uelem={{tag|TT|stopDescription}}
}}

===New {{@|type}} for {{tag|TT|annotation}}; changed multiplicity for {{tag|TT|text}}===
{{change
|fact=New {{@|type}} for {{tag|TT|annotation}}; multiplicity of {{tag|TT|text}} changed from [1..∞] to [0..∞]
|reason=broad revision of annotations: annotations should point to other content than text.
|recomendation=
|trac={{ticket|358}}
|svn=
|example=
|xsd=
|nattr={{tag|TT|annotation|@=type}}
|uattr=
|nelem=
|uelem={{tag|TT|annotation}}, {{tag|TT|text}}
}}

===New child {{tag|TT|announcements}} of {{tag|TT|timetable}}===
{{change
|fact=New child {{tag|TT|announcements}} of {{tag|TT|timetable}}
|reason=broad revision of annotations
|recomendation=
|trac=
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|announcements}}
|uelem={{tag|TT|timetable}}
}}

==={{@|processStatus}} set to deprecated for {{tag|TT|trainPart}}, {{tag|TT|train}} and {{tag|TT|trainGroup}}===
{{change
|fact=The attribute {{@|processStatus}} was set to deprecated for {{tag|TT|trainPart}}, {{tag|TT|train}} and {{tag|TT|trainGroup}}.
|reason=existing usage of attribute turned out to be non standardized. In order disencourage further use of the attribute it was decided to deprecate it as it seemed not feasible to unify its use.
|recomendation=
|trac={{ticket|364}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{Attr|processStatus}}
|nelem=
|uelem={{tag|TT|trainPart}}, {{tag|TT|train}}, {{tag|TT|trainGroup}}
}}

==={{@|onRequest}} set to deprecated for {{tag|TT|operatingDay}}===
{{change
|fact=The attribute {{@|onRequest}} was set to deprecated for {{tag|TT|operatingDay}}.
|reason=existing usage of attribute was deemed overly complicated and not widely used. In order disencourage further use of the attribute it was decided to deprecate it and recommend usage of the attribute {{@|onRequest}} of the {{tag|TT|trainPart}}.
|recomendation=
|trac={{ticket|372}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{Attr|onRequest}}
|nelem=
|uelem={{tag|TT|trainPart}}, {{tag|TT|operatingDay}}
}}

==={{@|shuntingTime|TT:ocpTT}} set to deprecated for {{tag|TT|ocpTT}}===
{{change
|fact=The attribute {{@|shuntingTime|TT:ocpTT}} was set to deprecated for {{tag|TT|ocpTT}}.
|reason=clarification of specification of shuntingTimes. There were actually 2 ways of specifying shunting times. {{@|shuntingTime|TT:ocpTT}} was deprecated in favor of {{@|shuntingTime|TT:stopTimes}}.
|recomendation=
|trac={{ticket|343}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{@|shuntingTime|TT:ocpTT}}
|nelem=
|uelem={{tag|TT|ocpTT}}
}}

===New attribute {{@|parentRef|TT:category}} added to {{tag|TT|category}}===
{{change
|fact=The attribute {{@|parentRef|TT:category}} was added in order to allow for hierarchies of categories.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|437}}
|svn=
|example=
|xsd=
|nattr={{@|parentRef|TT:category}}
|uattr=
|nelem=
|uelem={{tag|TT|category}}
}}

===New attribute {{@|organizationalUnitRef|TT:category}} added to {{tag|TT|category}}===
{{change
|fact=The attribute {{@|organizationalUnitRef|TT:category}} was added in order to differentiate between categories of the same name that are related to different organizationalUnits and thus may differ in semantics.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|436}}
|svn=
|example=
|xsd=
|nattr={{@|organizationalUnitRef|TT:category}}
|uattr=
|nelem=
|uelem={{tag|TT|category}}
}}

===New attribute {{@|parentRef|TT:trainGroup}} added to {{tag|TT|trainGroup}}===
{{change
|fact=The attribute {{@|parentRef|TT:trainGroup}} was added in order to allow for hierarchical train groups. It was also decided to change the cardinalities of {{tag|TT|trainGroup}} regarding its child {{tag|TT|trainRef}} to allow for {{tag|TT|trainGroup}}s that do not refer to any {{tag|TT|train}}s but rather are referred to by other {{tag|TT|trainGroup}}s as their parent.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|470}}
|svn=
|example=
|xsd=
|nattr={{@|parentRef|TT:trainGroup}}
|uattr=
|nelem=
|uelem={{tag|TT|trainGroup}}
}}

===New attribute {{@|lastModified|TT:trainPart}} added to {{tag|TT|trainPart}}===
{{change
|fact=In order to allow communication of changes to certain train parts a new optional attribute was added to {{tag|TT|trainPart}}. With this it is possible to specify the last change date for a trainParts change.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|471}}
|svn=
|example=
|xsd=
|nattr={{@|lastModified|TT:trainPart}}
|uattr=
|nelem=
|uelem={{tag|TT|trainPart}}
}}

===New element {{tag|TT|alternativeSectionsTT}} added to {{tag|TT|ocpTT}}===
{{change
|fact=In order to allow specification of alternative ways to reach the next OCP in an microscopic infrastructure model a new element was added to the {{tag|TT|ocpTT}} called {{tag|TT|alternativeSectionsTT}}. It serves as a container for a number of {{tag|TT|alternativeSectionTT}} elements that can each be annotated with a priority in order to describe the priority of their use by a managing TMS. It is important to note that the arrival and departure times of the following ocpTT must not be dependent on which way actually is chosen.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|381}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|alternativeSectionsTT}}
|uelem={{tag|TT|ocpTT}}
}}

===New element {{tag|TT|patternTrains}}===
{{change
|fact=Support for very early planning stages.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|432}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|patternTrains}}
|uelem=
}}

===New element {{tag|TT|patternTrainParts}}===
{{change
|fact=Support for very early planning stages.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|432}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|patternTrainParts}}
|uelem=
}}

===New element {{tag|TT|distributions}}===
{{change
|fact=Support for very early planning stages.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|433}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|TT|distributions}}
|uelem=
}}

===New enumeration value {{enum|expected}} for {{tag|TT|times}}/{{@|scope}}===
{{change
|fact=Support for forcasted arrival and departure times.
|reason=Requirement from the community.
|recomendation=
|trac={{ticket|472}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{@|scope|TT:times}}
|nelem=
|uelem=
}}

==Infrastructure Subschema==
===New {{@|trainProtectionSystem}} for {{tag|IS|trainProtectionChange}} and {{tag|IS|trainProtection}}===
{{change
|fact=new attribute {{@|trainProtectionSystem}} (string) has been added in elements {{tag|IS|trainProtectionChange}} and {{tag|IS|trainProtection}}.

{{@|trainProtectionSystem}} shall reference values from [[codelist]] [[TrainProtectionSystems.xml]].
|reason={{tag|IS|trainProtectionChange}} and {{tag|IS|trainProtection}} were missing a parameter to reference the train protection system – compare {{site|1=https://www.railml.org/forum/index.php?t=msg&goto=1910&&srch=trainProtection#msg_1910|2=the forum discussion}}.
|recomendation=
|trac={{ticket|356}}
|svn=
|example=
|xsd=
|nattr={{@|trainProtectionSystem}}
|uattr=
|nelem=
|uelem=<nowiki />
*{{tag|IS|trainProtectionChange}}
*{{tag|IS|trainProtection}}
}}
==={{@|dir}} deprecated for many elements===
{{change
|fact=For many Elements {{@|dir}} gets deprecated according to the following guidelines:
*Rule 1: @dir is usefull as application direction.<br>Applies for elements without extent (without @length attribute)<br>examples: balise, border, derailer, signal, stopPost... usage: @dir describes the direction of travel, for which the element applies. Possible values are "up", "down" and "both". A missing @dir attribute means that the application direction of this element is unknown.
*Rule 2: (short) linear elements 🡪 no usage of {{@|dir}}.<br>Elements with extent (with @length attribute) examples: bridge, levelCrossing, platformEdge, serviceSection... By standard, the elements' orientation (not their application direction!) shall be always in direction of track orientation (from trackBegin towards trackEnd).<br>E.g.: {{tag|IS|levelCrossing|attr=dir}}, {{tag|IS|platformEdge|attr=dir}}.<br>The position value {{@|pos}} defines the center point of the linear element.
*Rule 3: (long) linear elements 🡪 use {{@|dir}} if modelling „portals“ (usually Changes), where the elements' orientation can differ from track orientation.<br>Refers to Elements that describe a change.<br>Examples: axleWeightChange, clearanceGaugeChange, electrificationChange, gaugeChange, speedChange...<br>By standard (except for speedChange), the change elements' orientation (not their application direction!) shall be always in direction of track orientation (from trackBegin towards trackEnd).<br>E.g. {{tag|IS|tunnel|attr=dir}}: locate tunnel portal with {{@|pos}} and point {{@|dir}} towards center.
|reason=There are some elements, where the @dir attribute does not make much sense. Either, because the element is valid for both directions of travel or because the element shall be only defined for one direction. So, the task is to identify elements where the @dir attribute shall be marked DEPRECATED.
|recomendation=
|trac={{ticket|357}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{@|dir}}
|nelem=
|uelem={{tag|IS|trackCircuitBorder|attr=dir}}, {{tag|IS|brigde|attr=dir}}, {{tag|IS|levelCrossing_levelCrossings|attr=dir}}, {{tag|IS|platformEdge|attr=dir}}, {{tag|IS|serviceSection|attr=dir}}, {{tag|IS|tunnel|attr=dir}}, {{tag|IS|axleWeightChange|attr=dir}}, {{tag|IS|clearanceGaugeChange|attr=dir}}, {{tag|IS|electrificationChange|attr=dir}}, {{tag|IS|gaugeChange|attr=dir}}, {{tag|IS|ownerChange|attr=dir}}, {{tag|IS|powerTransmissionChange|attr=dir}}, {{tag|IS|radiusChange|attr=dir}}
}}

===New Attribute {{tag|IS|levelCrossing|levelCrossings|@=offset}}===
{{change
|fact=New optional attribute {{tag|IS|levelCrossing|levelCrossings|@=offset}}
|reason=Attributes @pos and @absPos shall describe by default the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.

In order to define a different setting, the new optional attribute <levelCrossing>@offset can be used. It describes how many metres of the @length is before @pos. If @offset is not given, the default value shall apply.
|recomendation=
|trac={{ticket|374}}
|svn=
|example=
|xsd=
|nattr={{@|offset|IS:levelCrossing_levelCrossings}}
|uattr=
|nelem=
|uelem={{tag|IS|levelCrossing|levelCrossings|attr=offset}}
}}
===Updated definitions for the values of {{tag|IS|track|@=type}}===
{{change
|fact=The definitions of the values of {{tag|IS|track|@=type}} have been updated
|reason=Definitions of track types in railML 2 wiki differ from consensus in forum and best practices in wiki → to be consolidated.
|recomendation=
|trac={{ticket|376}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{@|type|IS:track}}
|nelem=
|uelem={{tag|IS|track|attr=type}}
}}

===Value {{enum|unknown}} of {{tag|IS|track|@=mainDir}} removed===
{{change
|fact=The value {{enum|unknown}} of {{tag|IS|track|@=mainDir}} has been '''removed'''.
|reason={{enum|unknown}} has the same meaning as a missing {{@|mainDir|IS:track}}.
|recomendation=Despite the value {{enum|unknown}} still exists in older schemas, consider it deprecated retroactively.
|trac={{ticket|324}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{@|mainDir|IS:track}}
|nelem=
|uelem={{tag|IS|track|attr=mainDir}}
}}
==={{@|rampType|IS:serviceSection}} added to {{tag|IS|serviceSection|attr=rampType}}===
{{change
|fact={{@|rampType|IS:serviceSection}} added to {{tag|IS|serviceSection|attr=rampType}}
|reason=Result of a reasoning how to model car ramps. A possibility to model the type of ramp was missing.
|recomendation=Model car ramps as described [[IS:serviceSection#Modelling_a_car_ramp|here]]
|trac={{ticket|362}}
|svn=
|example=
|xsd=
|nattr={{@|rampType|IS:serviceSection}}
|uattr=
|nelem=
|uelem=
}}
==={{tag|IS|ocpVis}} replaced with {{tag|IS|objectVis}}===
{{change
|fact={{tag|IS|ocpVis}} has been replaced with {{tag|IS|objectVis}}.
|reason=Makes the purpose of the element clearer and allowes for mor general modelling.
|recomendation=Use {{tag|IS|objectVis}} in place of {{tag|IS|ocpVis}}
|trac={{ticket|373}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|IS|objectVis}}
|uelem={{tag|IS|ocpVis}}
}}
==={{tag|IS|genericAreas}} has been introduced===
{{change
|fact=Element {{tag|IS|genericAreas}} and its recursive Children have been introduced
|reason=This element is a new high-level grouping element. The element describes several different types of areas, e.g. specification of specially controlled areas within the network.
|recomendation=Employ {{tag|IS|genericAreas}}>{{tag|IS|genericArea}}>{{tag|is|limitedBy|@=re}} to reference any [[infrastructure]]-elements that limit the respective {{tag|IS|genericArea}}.
|trac=
|svn={{ticket|393}}, {{ticket|396}}
|example=
|xsd=
|nattr=
|uattr=
|nelem=<nowiki />
*{{tag|is|genericArea}} + recursive childs;
*Referencing elements: {{tag|is|informationArea}}, {{tag|IS|impairmentSections}}, {{tag|is|trackVacancyDetectionArea}}, {{tag|is|localOperationalArea}}, {{tag|is|workZone}}, {{tag|co|projectArea}}
|uelem={{tag|is|infrastructure}}, {{tag|is|controller}} and others
}}

==={{tag|is|track}} extended by child {{tag|is|impairmentSections}}===
{{change
|fact={{tag|is|track}} has been extended by child {{tag|is|impairmentSections}} (container) and childs.
|reason=Element {{tag|IS|impairmentSection}} is designed to address sections with impaired railway operations.
|recomendation=Employ {{tag|is|impairmentSection|@=areaRef}} to reference a {{tag|is|genericArea}} and {{tag|is|impairmentSection}}>{{tag|is|additionalRunningTime|@=value}} to indicate the delay.
|trac={{ticket|395}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|is|impairmentSections}} & recursive childs
|uelem={{tag|is|track}}
}}

==={{@|startDateTime|IS:state}} and {{@|endDateTime|IS:state}} have been added to {{tag|is|state}}===
{{change
|fact={{@|startDateTime|IS:state}} and {{@|endDateTime|IS:state}} have been added to {{tag|is|state}}
|reason=The time aspect of {{tag|is|state}} was previously not modelled properly, e.g. missing a clear start and end time of a certain state (independent from [[timetable]])
|recomendation=<nowiki />
*Use {{@|startDateTime|IS:state}} and/or {{@|endDateTime|IS:state}} to specify an open or closed timespan for validity '''independent''' from an {{tag|tt|operatingPeriod}}
*Use {{@|startTime|IS:state}} and/or {{@|endTime|IS:state}} to specify an open or closed timespan for state validity '''linked''' with an {{tag|tt|operatingPeriod}}
|trac={{ticket|394}}
|svn=
|example=
|xsd=
|nattr={{@|startDateTime|IS:state}}, {{@|endDateTime|IS:state}}
|uattr=
|nelem=
|uelem={{tag|IS|state}}
}}
===Turning restistances added to {{tag|is|ocp}}===
{{change
|fact={{tag|is|ocp}} > {{tag|is|propOther}} has been extended by child {{tag|is|relation}}
|reason=In purely mesoscopic or macroscopic railway network descriptions a detailed description of operational routing (e.g. change of driving direction) was not possible; especially within OCP. Therefore {{tag|is|ocp}} has been extended with an „inner topology description“ related to possible train runs.
|recomendation=
|trac={{ticket|413}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem={{tag|is|relation}} & recursive childs
|uelem={{tag|is|propOther}}
}}
==={{tag|IS|line|@=belongsToParent}} has been added===
{{change
|fact={{tag|IS|line}} has been extended by {{@|belongsToParent}} and the definition of {{Tag|IS|line}} has been generalized.
|reason=This change allows to segment lines and address the complete line and single segments simultaneously.
|recomendation=
|trac={{ticket|414}}
|svn=
|example=
|xsd=
|nattr={{@|belongsToParent|IS:line}}
|uattr=
|nelem=
|uelem={{tag|IS|line|attr=belongsToParent}}
}}
==={{tag|IS|propOperational}} extended by {{@|remoteControlled|IS:propOperational}} and {{@|simultaneousEntry|IS:propOperational}}===
{{change
|fact={{tag|IS|propOperational}} has been extended by {{@|remoteControlled|IS:propOperational}} and {{@|simultaneousEntry|IS:propOperational}}
|reason=Provides additional operational attributes for an {{tag|IS|ocp}}.
|recomendation=
|trac={{ticket|416}}
|svn=
|example=
|xsd=
|nattr={{@|remoteControlled|IS:propOperational}}, {{@|simultaneousEntry|IS:propOperational}}
|uattr=
|nelem=
|uelem={{tag|IS|propOperational}}
}}
==={{tag|IS|border|@=type}} extended by value ''project''===
{{change
|fact={{tag|IS|border|@=type}} has been extended by value ''project''.
|reason=Allows to employ {{tag|IS|border}} to clarify borders of/between projects.
|recomendation=
|trac={{ticket|418}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{@|type|IS:border}}
|nelem=
|uelem={{tag|IS|border}}
}}
==={{tag|is|state|@=status}} has been extended by the value {{enum|unknown}}===
{{change
|fact={{tag|is|state|@=status}} has been extended by the value {{enum|unknown}}
|reason=Allows to mark the respective element as explicitely unknown.
|recomendation=
|trac={{ticket|421}}
|svn=
|example=
|xsd=
|nattr=
|uattr={{tag|is|state|@=status}}
|nelem=
|uelem=
}}

==Rollingstock Subschema==
==={{tag|RS|segmentTable}} introduced===
{{change
|fact=Several instances of {{tag|RS|segmentTable}} have been introduced.
|reason=There was demand for an alternative to {{tag|RS|valueTable}}
|recomendation=
|trac={{ticket|385}}
|svn=
|example=
|xsd=
|nattr=
|uattr=
|nelem=Several instances of {{tag|RS|segmentTable}}
|uelem=The respective parents, comp. {{tag|RS|segmentTable}}
}}