Search results

to describe and validate that a <train> must reference one or more <trainPart>s, that all <trackElements> must have a position on the <track>, that the

following characteristics of <blockPart> are allowed: <blockPart> as a reference to a <trainPart>: mission=timetable trainPartRef has to be used; the other

blockPartSequence   Parent: <block> Children: <blockPartRef>, <xs:any> (introduced with version 2.3) [1..∞] The element <blockPartSequence> groups the

Angabe bei blockPartSequence erfolgt defaultPostProcessingTime: This is the default duration from the end of blockPart until the end of blocking of the ressource

block   Parent: <blocks> Children: <additionalName> (introduced with version 2.1), <blockPartSequence>, <xs:any> [1..∞] The element <block> contains all

name, rail:lang, xsi:type <blockPartSequence> basicBlockRef, dayOffset, postProcessingTime, preProcessingTime, sequence <blockPartRef> ref <circulations> <circulation>

+ <xs:keyref name="vehicle-blockPartKeyref" refer="rail:vehicleKey"> + <xs:selector xpath=".//rail:blockParts/rail:blockPart" /> + <xs:field xpath="@vehicleRef"

</xs:keyref> + <xs:keyref name="ocp-blockPartStartKeyref" refer="rail:ocpKey"> + <xs:selector xpath=".//rail:blockParts/rail:blockPart" /> + <xs:field xpath="@startOcpRef"

blockPartRef   Parent: <blockPartSequence> Children: None [1..∞] The element <blockPartRef> refers to blockParts for building sequences of tasks. In dem

diff --git a/schema/timetable.xsd b/schema/timetable.xsd index 2a6c84d..30d721b 100644 --- a/schema/timetable.xsd +++ b/schema/timetable.xsd @@ -1,12 +1,16

<xs:selector xpath=".//rail:blockParts/rail:blockPart" /> <xs:field xpath="@endOcpRef" /> </xs:keyref> + <xs:keyref name="ocp-trainPartOrigin" refer="rail:ocpKey">

defined in the infrastructure part, providing some timetable related information for it. In the British railway timetabling system the ocpTT is called TIPLOC

description="Bern-Muensingen-Thun"> <trainPartSequence sequence="1"> <trainPartRef ref="trainPart1001"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef

name, rail:lang, xsi:type <blockPartSequence> basicBlockRef, dayOffset, postProcessingTime, preProcessingTime, sequence <blockPartRef> ref <circulations> <circulation>

name, rail:lang, xsi:type <blockPartSequence> basicBlockRef, dayOffset, postProcessingTime, preProcessingTime, sequence <blockPartRef> ref <circulations> <circulation>

+ </xs:sequence> + </xs:complexType> + <xs:complexType name="eTrainPartSequence"> <xs:complexContent> <xs:extension base="rail:tTrainPartSequence"> @@ -712

for RTPIS-own journeys. Commonly connections/transfers are not part of the imported timetable. These information belong to the responsibility of another RTPIS

defined in the infrastructure part, providing some timetable related information for it. In the British railway timetabling system the ocpTT is called TIPLOC

categoryKey category-trainPartKeyref category-trainPartSequenceKeyref category-formationKeyref speedProfileKey speedProfile-trainPartSequenceKeyref stopPostKey

/trains/train/trainPartSequence/brakeUsage/auxiliaryBrakes /rosterings/rostering/blockParts /rosterings/rostering/blocks/block/blockPartSequence /rosterings/ros