Hi Leopold
Thank you for the proposal. I've just created a SVN branch and committed the first version.
Branch: https://trac.railml.org/browser/railML/railML2/branches/refe rencing-canceled-trains
Changeset: https://trac.railml.org/changeset/762/railML
Can you please review it? I'm not sure if I have defined the XSD-types correctly across the two files "timetableTypes.xsd" and "timetable.xsd". Thank you!
Here an example with unique train key and TAF/TAP TSI train id:
Update after timetable developer teclo from 18 December 2017:
operatingPeriodRef is now a child element of replacementOf because the operating period reference is also required for trains referenced by TAF/TAP TSI train id.
But: This way the Element uniqueTrainKey is not really "unique" because the operatingPeriodRef is not a part of it! (Should be discussed in the next telco... !?)
<train id="train-zug-BLSP-16321-001"
code="BLSP-16321-1"
type="commercial"
trainNumber="16321"
additionalTrainNumber="4"
cancellation="false"
processStatus="actual"
description="Bn-Mueb">
<trainPartSequence sequence="1">
<trainPartRef ref="train-part-1"/>
</trainPartSequence>
<replacements>
<replacementOf>
<operatingPeriodRef ref="operating-period-17" />
<uniqueTrainKey trainNumber="16320" scope="primary" additionalTrainNumber="7" />
</replacementOf>
<replacementOf>
<operatingPeriodRef ref="operating-period-17" />
<tafTapTsiTrainID objectType="TR"
companyCode="1185"
core="012345616320"
variant="01"
timetableYear="2017" />
</replacementOf>
</replacements>
</train>
Best regards,
Mico
[Updated on: Wed, 03 January 2018 13:33]
Report message to a moderator
Members
Search
Help
Login
Home
