Home » railML newsgroups » railml.timetable » train stablings (Representing train stablings and other track occupancies with trainParts)
Re: train stablings [message #1856 is a reply to message #1804] Tue, 26 June 2018 10:42 Go to previous messageGo to previous message
Heribert Neu is currently offline  Heribert Neu
Messages: 7
Registered: January 2018
Junior Member
The necessary change on the railML 2.4 schema is as follows:
when defining the child elements of rostering the element blocks gets the specification minOccurs="0", see below:
<xs:complexType name="eRostering">
  <xs:complexContent>
    <xs:extension base="rail:tRostering">
      <xs:sequence>
        ...
        <xs:element name="blocks" type="rail:eBlocks" minOccurs="0"> <---
          <xs:annotation>
            <xs:documentation source="http://wiki.railml.org/index.php?title=TT:blocks"/>
          </xs:annotation>
        </xs:element>
        <xs:element name="circulations" type="rail:eCirculations" minOccurs="0">
          <xs:annotation>
            <xs:documentation source="http://wiki.railml.org/index.php?title=TT:circulations"/>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

The circulations already have the entry minOccurs="0", here no change is necessary.

Best Regards
Heribert

[Updated on: Tue, 26 June 2018 10:44]

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: values 'earliest' and 'latest' of <ocpTT>.<times>.@scope
Next Topic: TrainPart:tProcessStatus semantic
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue May 07 16:57:34 CEST 2024