Home » railML newsgroups » railml.timetable » Connections to external trains (Connections to external trains, not included in the file)
Connections to external trains [message #1343] Wed, 03 February 2016 11:57 Go to next message
Joachim.Rubröder is currently offline  Joachim.Rubröder
Messages: 29
Registered: September 2004
Junior Member
Conclusion of the discussion during the timetable-developer meeting on 22.01.2016 in Berlin:

Dear railML users.
We were looking for a way to reference a connection to an external train (bus, ship, etc.) that is not listed as train within the same railML file.

The idea is to have a sub element <externalReferences> with a choice of different elements to reference an external train via:
* unique tafTapTsiTrainID
* trainNumber (and maybe the related IM)
* lineNumber, e.g. a connection to the trains of the line 'S6'
* information, e.g. 'Connection to Berlin via Wolfsburg'

Do you have any remarks on this approach?

Kind regards,
Joachim Rubröder

The XSD would look like this:
  <xs:complexType name="eConnectionTT">
    <xs:complexContent>
      <xs:extension base="rail:tConnectionTT">
        <xs:sequence>
          <xs:element name="externalReferences" minOccurs="0">
            <xs:complexType>
              <xs:choice maxOccurs="4">
                <xs:element name="tafTapTsiTrainID" type="rail:eTapTsiTransportOperationalIdentifier"/>
                <xs:element name="trainNumber">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="organizationalUnitBinding" type="rail:eOrganizationalUnitBinding" minOccurs="0">
                        <xs:annotation>
                          <xs:documentation source="http://wiki.railml.org/index.php?title=TT:organizationalUnitBinding"/>
                        </xs:annotation>
                      </xs:element>
                    </xs:sequence>
                    <xs:attribute name="trainNumber" type="xs:string"/>
                  </xs:complexType>
                </xs:element>
                <xs:element name="lineNumber">
                  <xs:complexType>
                    <xs:attribute name="lineNumber" type="xs:string"/>
                  </xs:complexType>
                </xs:element>
                <xs:element name="information">
                  <xs:complexType>
                    <xs:attribute name="description" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>Enter the description of the connection - e.g. 'Connection to Berlin via Wolfsburg'</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
              </xs:choice>
            </xs:complexType>
          </xs:element>
          <xs:element name="annotationRef" type="rail:tAnnotationRef" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>refers to the id attribute of an annotation element</xs:documentation>
              <xs:documentation source="http://wiki.railml.org/index.php?title=TT:annotationRef_connection"/>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>



Re: Connections to external trains [message #1344 is a reply to message #1343] Fri, 12 February 2016 10:26 Go to previous messageGo to next message
Philip Wobst is currently offline  Philip Wobst
Messages: 36
Registered: November 2013
Location: Hanover, Germany
Member
Hello Joachim,

I would like to suggest to change the choice to a normal sequence and then making the individual reference elements
optional. That way each externalReferences sub-element can be supplied only once. The approach with the choice element
would allow for up to four tafTapTsiTrainIDs.

          <xs:element name="externalReferences" minOccurs="0">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="tafTapTsiTrainID" type="rail:eTapTsiTransportOperationalIdentifier" minOccurs="0" />
                <xs:element name="trainNumber" minOccurs="0">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="organizationalUnitBinding" type="rail:eOrganizationalUnitBinding" minOccurs="0">
                        <xs:annotation>
                          <xs:documentation source="http://wiki.railml.org/index.php?title=TT:organizationalUnitBinding"/>
                        </xs:annotation>
                      </xs:element>
                    </xs:sequence>
                    <xs:attribute name="trainNumber" type="xs:string"/>
                  </xs:complexType>
                </xs:element>
                <xs:element name="lineNumber" minOccurs="0">
                  <xs:complexType>
                    <xs:attribute name="lineNumber" type="xs:string"/>
                  </xs:complexType>
                </xs:element>
                <xs:element name="information" minOccurs="0">
                  <xs:complexType>
                    <xs:attribute name="description" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>Enter the description of the connection - e.g. 'Connection to Berlin via Wolfsburg'</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>

BR, Philip

Screenshot showing the choice element on the left (post by Joachim) and the suggested change on the right (image is attached to the TRAC ticket #244):
https://trac.railml.org/raw-attachment/ticket/244/Connections_to_external_trains_Screenshot.png
Re: Connections to external trains [message #1345 is a reply to message #1344] Fri, 12 February 2016 10:29 Go to previous messageGo to next message
Philip Wobst is currently offline  Philip Wobst
Messages: 36
Registered: November 2013
Location: Hanover, Germany
Member
Hello all,

please note, that the inline image display is not shown in my newsreader client. To view the message with the image please see here:
http://www.railml.org/forum/index.php?t=msg&goto=1344#msg_1344

BR, Philip
Re: Connections to external trains [CLOSED] [message #1346 is a reply to message #1345] Tue, 16 February 2016 16:40 Go to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 36
Registered: November 2013
Location: Hanover, Germany
Member
Dear TT developers,

the discussion regarding the external connection reference has been finalized. The following final changes have been made and implemented in reviesion #651 (see http://trac.railml.org/ticket/244):
1. References are provided in the new Element externalReference
2. References for one connection can be made as one or more of the following
  • externalReference/tafTapTsiTrainID
  • externalReference/trainNumber
  • externalReference/lineNumber
  • externalReference/information
3. Type added for externalReference for the connection (eExternalReference)

BR, Philip Wobst
Previous Topic: [Request for railML3] Clearer description of chained <trainPart>s
Next Topic: Additional commercial attributes from TAP TSI for timetables
Goto Forum:
  


Current Time: Wed Aug 16 23:44:23 CEST 2017