Template:Switch/Dev:SemanticConstraints: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
|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}} | |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}} | ||
|IS:019={{DefSemcon|{{{1}}}|{{{2}}}|text=When calculating which <infrastructureState> of an <infrastructure> is valid on a particular time always a maximum of one active <infrastructureState> shall be the result.|status=proposed|proposed=2024-09-03|forum=https://www.railml.org/forum/index.php?t=msg&th=1033&start=0&}} | |IS:019={{DefSemcon|{{{1}}}|{{{2}}}|text=When calculating which <infrastructureState> of an <infrastructure> is valid on a particular time always a maximum of one active <infrastructureState> shall be the result.|status=proposed|proposed=2024-09-03|forum=https://www.railml.org/forum/index.php?t=msg&th=1033&start=0&}} | ||
|IS:021={{DefSemcon|{{{1}}}|{{{2}}}|text=The element {{IS:Tag|baliseGroup}} shall always use the railML option {{RTM:Tag|spotLocation}} to define the balise group location on the topology.|status=proposed|proposed=2025-04-30|id=IS:021|forum=https://www.railml.org/forum/index.php?t=msg&th=980&start=0&}} | |||
|#default={{fixme}} | |#default={{fixme}} | ||
}} | }} | ||
<noinclude>{{interwiki}}[[category:Template]]</noinclude> | <noinclude>{{interwiki}}[[category:Template]]</noinclude> | ||
Revision as of 15:15, 19 May 2025
FIXME