Search results
Jump to navigation
Jump to search
- IS:designator state (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen).∞] FIXME(introduced with version 2.5) Please, be aware of the semantic constraint(s)! register: Name of the register, e.g. registers for OCPs: IBNR194 bytes (250 words) - 13:53, 14 May 2024
- TT:stopDescription ocpTT ocpsTT trainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)Durchfahrt) im aktuellen ocpTT charakterisieren. Please, be aware of the semantic constraint(s)! commercial: This characterizes the reason for the stop. It can11 KB (1,367 words) - 17:56, 24 September 2023
- TT:ocpTT ocpsTT patternTrainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)auftauchen.(introduced with version 2.5) Please, be aware of the semantic constraint(s)! ocpRef: This refers to the id attribute of the associated ocp5 KB (633 words) - 11:47, 9 October 2023
- TT:ocpTT ocpsTT trainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)the times do not contradict each other, i.e. ensure that also the semantic constraints TT:015 and TT:016 are taken into account. Eine Software, die ein12 KB (1,526 words) - 18:09, 7 March 2024
- IS:designator impairmentSection (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen).∞] FIXME(introduced with version 2.5) Please, be aware of the semantic constraint(s)! register: Name of the register, e.g. registers for OCPs: IBNR194 bytes (250 words) - 13:52, 14 May 2024
- IS:designator state (with length) (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen).∞] FIXME(introduced with version 2.5) Please, be aware of the semantic constraint(s)! register: Name of the register, e.g. registers for OCPs: IBNR232 bytes (250 words) - 13:53, 14 May 2024
- IS:designator ocp (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)of <ocp>.(introduced with version 2.2) Please, be aware of the semantic constraint(s)! register: Name of the register, e.g. registers for OCPs: IBNR5 KB (536 words) - 13:50, 14 May 2024
- TT:times ocpTT ocpsTT trainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)Abfahrtszeiten eines Zuges und ihre Interpretation. Please, be aware of the semantic constraint(s)! scope: The attribute @scope is used to distinguish different <times>23 KB (2,742 words) - 17:27, 24 September 2023
- TT:trackInfo stopDescription ocpTT ocpsTT patternTrainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)übergeordneten <ocpTT>.(introduced with version 2.5) Please, be aware of the semantic constraint(s)! track: Designation of the track. Bezeichnung des Bahnhofsgleises2 KB (234 words) - 18:19, 24 September 2023
- TT:trackInfo stopDescription ocpTT ocpsTT trainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)übergeordneten <ocpTT>.(introduced with version 2.4) Please, be aware of the semantic constraint(s)! operatingPeriodRef: Operating days on which the station track3 KB (319 words) - 18:20, 24 September 2023
- TT:times ocpTT ocpsTT patternTrainPart (category Semantic constraints) (section Semantic Constraints / Semantische Beschränkungen)Abfahrtszeiten eines Zuges und ihre Interpretation. Please, be aware of the semantic constraint(s)! scope: The attribute @scope is used to distinguish different <times>6 KB (594 words) - 20:48, 22 January 2024
- relevant für eine Erfüllung der Vorgaben. Semantic constraints: Shall contain semantic constraints. Semantic constraints should be added only by the subschema7 KB (871 words) - 16:02, 3 April 2023
- the track positioned at zero coordinate. But also, the additional semantic constraints apply like for the <speedChange>: • Only applies if speedChanges2 KB (276 words) - 14:28, 20 February 2024
- are two tracks. When choosing approach with two tracks be aware of semantic constraints e.g. IS:003 "If two <track>s are connected, the @absPos values of5 KB (507 words) - 15:11, 20 May 2024
- how to contribute to them. Certification guideline How to deal with Semantic Constraints Guidelines to enhance the wiki documentation How to join the railML®9 KB (916 words) - 12:29, 22 February 2024
- further restrictions of the operating period. Please, recognize the semantic constraint. endDate (deprecated with version 2.2): This describes optional further978 bytes (162 words) - 14:11, 10 August 2020
- </xs:element> Keys and its references (keyref) may be used to define some semantic constraints. They ensure, that a reference may not point to an id of another9 KB (1,033 words) - 17:59, 19 January 2024
- Fact: @basicSpeedProfile, @etcsTrainCategory and two semantic constraints have been added. <speedChange>@etcsTrainCategory has in turn been29 KB (97 words) - 19:00, 22 January 2024
- REDIRECT Template:Table/Dev:Semantic Constraints48 bytes (4 words) - 15:44, 16 April 2020
- formations within the timetable subschema TT New users Guide Dev:Semantic Constraints How to handle rules that do not fit into XSD All New users Concept8 KB (25 words) - 18:35, 5 February 2024