Template:Switch/Dev:SemanticConstraints: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
|IS:015={{DefSemcon|{{{1}}}|{{{2}}}|text=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 – Compare {{ticket|xxx}}|status=proposed|proposed=2021-04-22|forum={{ticket|xxx}}}} | |IS:015={{DefSemcon|{{{1}}}|{{{2}}}|text=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 – Compare {{ticket|xxx}}|status=proposed|proposed=2021-04-22|forum={{ticket|xxx}}}} | ||
|IS:017={{DefSemcon|{{{1}}}|{{{2}}}|text=Users can refer to the train protection system using the attribute {{@|trainProtectionSystem|IS:trainProtectionElement}} that shall link to the {{site|1=https://development.railml.org/railml/shared/-/tree/master/codelists|2=codelist}} TrainProtectionSystems.xml, 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|IS:trainProtectionElement}} and {{@|monitoring|IS:trainProtectionElement}}.|status=approved|proposed=2009-10-17|approved=2009-10-17|forum=https://www.railml.org/forum/index.php?t=msg&goto=3600&#msg_3600}} | |IS:017={{DefSemcon|{{{1}}}|{{{2}}}|text=Users can refer to the train protection system using the attribute {{@|trainProtectionSystem|IS:trainProtectionElement}} that shall link to the {{site|1=https://development.railml.org/railml/shared/-/tree/master/codelists|2=codelist}} TrainProtectionSystems.xml, 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|IS:trainProtectionElement}} and {{@|monitoring|IS:trainProtectionElement}}.|status=approved|proposed=2009-10-17|approved=2009-10-17|forum=https://www.railml.org/forum/index.php?t=msg&goto=3600&#msg_3600}} | ||
|IS:018={{DefSemcon|{{{1}}}|{{{2}}}|text=Any functional infrastructure element that belongs to an {{IS:Tag|operationalPoint}} may be listed as its equipment. This may be done by adding it to a specific container, such as {{GEN:Tag|ownsPlatform}}, {{GEN:Tag|ownsTrack}} and {{GEN:Tag|ownsSignal}} or it may be added to the generic container {{GEN:Tag|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 {{IS:Tag|signalIS}} must not be added to {{GEN:Tag|ownsInfrastructureElement}}. It shall be added to {{GEN:Tag|ownsSignal}}. As there is no container for levelCrossings a {{IS:Tag|levelCrossingIS}} belonging to an {{IS:Tag|operationalPoint}} shall be added to {{GEN:Tag|ownsInfrastructureElement}}.|status=proposed|proposed=2024-08-26|id=IS:018|forum=https://www.railml.org/forum/index.php?t=msg&goto=3286}} | |||
|#default={{fixme}} | |#default={{fixme}} | ||
}} | }} | ||
<noinclude>{{interwiki}}[[category:Template]]</noinclude> | <noinclude>{{interwiki}}[[category:Template]]</noinclude> | ||
Revision as of 15:09, 19 May 2025
FIXME