group "TrainOperationalInfoGroup"
Namespace:
http://www.siri.org.uk/siri
Content:
10 elements
Defined:
globally in siri_monitoredVehicleJourney-v2.0.xsd; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
Complex Content Model
TrainBlockPart*, BlockRef?, CourseOfJourneyRef?, VehicleJourneyRef?, VehicleRef?, AdditionalVehicleJourneyRef*, DriverRef?, DriverName?, TrainNumbers?, JourneyParts?
Content Model Elements (10):
AdditionalVehicleJourneyRef (type FramedVehicleJourneyRefStructure), BlockRef (type BlockRefStructure), CourseOfJourneyRef (type CourseOfJourneyRefStructure), DriverName (type xsd:normalizedString), DriverRef (type xsd:normalizedString), JourneyParts (defined in TrainOperationalInfoGroup group), TrainBlockPart (in AffectedVehicle), TrainNumbers (defined in TrainOperationalInfoGroup group), VehicleJourneyRef, VehicleRef
Known Usage Locations
Annotation
Operational information about the monitored VEHICLE JOURNEY.
XML Source (see within schema source)
<xsd:group name="TrainOperationalInfoGroup">
<xsd:annotation>
<xsd:documentation>
Operational information about the monitored VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TrainBlockPart" type="TrainBlockPartStructure">
<xsd:annotation>
<xsd:documentation>
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="OperationalInfoGroup"/>
<xsd:element minOccurs="0" name="TrainNumbers">
<xsd:annotation>
<xsd:documentation>TRAIN NUMBERs for journey. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="TrainNumberRef" type="TrainNumberRefStructure">
<xsd:annotation>
<xsd:documentation>
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="JourneyParts">
<xsd:annotation>
<xsd:documentation>JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="JourneyPartInfo" type="JourneyPartInfoStructure">
<xsd:annotation>
<xsd:documentation>Information about Parts of JOURNEY +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; 10/10)
AdditionalVehicleJourneyRef
Type:
FramedVehicleJourneyRefStructure, complex content
Defined:
locally within OperationalInfoGroup group
Refercence to other VEHICLE Journeys (+SIRI v2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="AdditionalVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Refercence to other VEHICLE Journeys (+SIRI v2.0)</xsd:documentation>
</xsd:annotation>
</xsd:element>
BlockRef
Type:
BlockRefStructure, simple content
Defined:
locally within OperationalBlockGroup group
BLOCK that VEHICLE is running.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="BlockRef" type="BlockRefStructure">
<xsd:annotation>
<xsd:documentation>BLOCK that VEHICLE is running.</xsd:documentation>
</xsd:annotation>
</xsd:element>
CourseOfJourneyRef
Type:
CourseOfJourneyRefStructure, simple content
Defined:
locally within OperationalBlockGroup group
COURSE OF JOURNEY ('Run') that VEHICLE is running.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="CourseOfJourneyRef" type="CourseOfJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
COURSE OF JOURNEY ('Run') that VEHICLE is running.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DriverName
Type:
xsd:normalizedString, predefined, simple content
Defined:
locally within OperationalInfoGroup group
The name oo the Driver or Crew +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DriverName" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>The name oo the Driver or Crew +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
DriverRef
Type:
xsd:normalizedString, predefined, simple content
Defined:
locally within OperationalInfoGroup group
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DriverRef" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
JourneyParts
Type:
anonymous complexType, complex content
Defined:
locally within (this) TrainOperationalInfoGroup group
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="JourneyParts">
<xsd:annotation>
<xsd:documentation>JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="JourneyPartInfo" type="JourneyPartInfoStructure">
<xsd:annotation>
<xsd:documentation>Information about Parts of JOURNEY +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
TrainBlockPart
Type:
TrainBlockPartStructure, complex content
Defined:
locally within (this) TrainOperationalInfoGroup group
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="TrainBlockPart" type="TrainBlockPartStructure">
<xsd:annotation>
<xsd:documentation>
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
TrainNumbers
Type:
anonymous complexType, complex content
Defined:
locally within (this) TrainOperationalInfoGroup group
TRAIN NUMBERs for journey. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="TrainNumbers">
<xsd:annotation>
<xsd:documentation>TRAIN NUMBERs for journey. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="TrainNumberRef" type="TrainNumberRefStructure">
<xsd:annotation>
<xsd:documentation>
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
VehicleJourneyRef
Type:
VehicleJourneyRefStructure, simple content
Defined:
by reference within OperationalInfoGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="VehicleJourneyRef"/>
VehicleRef
Type:
VehicleRefStructure, simple content
Defined:
by reference within OperationalInfoGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="VehicleRef"/>
This XML schema documentation has been generated with DocFlex/XML 1.9.5 using DocFlex/XML XSDDoc 2.8.1 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/