element <AffectedVehicle> (local)
Namespace:
http://www.siri.org.uk/siri
Type:
AffectedVehicleStructure
Content:
complex, 20 elements
Defined:
locally within Vehicles element in siri_situation-v2.0.xsd; see XML source
XML Representation Summary
<AffectedVehicle>
   
Content: 
</AffectedVehicle>
Content model elements (20):
AccessibilityAssessment (type acsb:AccessibilityAssessmentStructure), BlockRef (type BlockRefStructure), CourseOfJourneyRef (type CourseOfJourneyRefStructure), CurrentLocation (in AffectedVehicle), Extensions, FramedVehicleJourneyRef (type FramedVehicleJourneyRefStructure), HeadwayService (type xsd:boolean), IPAddress (in AffectedVehicle), InCongestion (in AffectedVehicle), InPanic (in AffectedVehicle), Location (type LocationStructure), OperatorRef (type OperatorRefStructure), PhoneNumber (type PhoneType), ProductCategoryRef (type ProductCategoryRefStructure), RadioAddress (in AffectedVehicle), ServiceFeatureRef, TrainBlockPart (in AffectedVehicle), VehicleFeatureRef (type VehicleFeatureRefStructure), VehicleRef (type VehicleRefStructure), VehicleRegistrationNumberPlate (in AffectedVehicle)
Included in content model of elements (1):
Vehicles (in Affects)
Annotation
Vehicles affected by the SITUATION. (+SIRi v2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" name="AffectedVehicle" type="AffectedVehicleStructure">
<xsd:annotation>
<xsd:documentation>Vehicles affected by the SITUATION. (+SIRi v2.0)</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 20/20)
AccessibilityAssessment
Type:
acsb:AccessibilityAssessmentStructure, complex content
Defined:
locally within AffectedVehicleStructure complexType
Current Accessibility assessment of vehicle.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
<xsd:documentation>Current Accessibility assessment of vehicle.</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>
CurrentLocation
Type:
LocationStructure, complex content
Defined:
locally within AffectedVehicleStructure complexType
Current Location of the VEHICLE
XML Source (see within schema source)
<xsd:element minOccurs="0" name="CurrentLocation" type="LocationStructure">
<xsd:annotation>
<xsd:documentation>Current Location of the VEHICLE</xsd:documentation>
</xsd:annotation>
</xsd:element>
Extensions
Type:
ExtensionsStructure, complex content
Defined:
by reference within AffectedVehicleStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="Extensions"/>
FramedVehicleJourneyRef
Type:
FramedVehicleJourneyRefStructure, complex content
Defined:
locally within AffectedVehicleStructure complexType
Reference to VEHICLE JOURNEY that VEHICLE is making.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="FramedVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to VEHICLE JOURNEY that VEHICLE is making.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
HeadwayService
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
locally within AffectedVehicleStructure complexType
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="HeadwayService" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
InCongestion
Type:
xsd:boolean, predefined, simple content
Defined:
locally within AffectedVehicleStructure complexType
Whether the VEHICLE is in traffic congestion. If not, present, not known.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="InCongestion" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the VEHICLE is in traffic congestion. If not, present, not known.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
InPanic
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
locally within AffectedVehicleStructure complexType
Whether the panic alarm on the VEHICLE is activated. Default is 'false'.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="InPanic" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the panic alarm on the VEHICLE is activated. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
IPAddress
Type:
xsd:NMTOKEN, predefined, simple content
Defined:
locally within AffectedVehicleStructure complexType
Internet protocol address of the VEHICLE in form 000.000.000.000
XML Source (see within schema source)
<xsd:element minOccurs="0" name="IPAddress" type="xsd:NMTOKEN">
<xsd:annotation>
<xsd:documentation>
Internet protocol address of the VEHICLE in form 000.000.000.000
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Location
Type:
LocationStructure, complex content
Defined:
locally within AffectedVehicleStructure complexType
Location where the VEHICLE was when the situation arosse
XML Source (see within schema source)
<xsd:element minOccurs="0" name="Location" type="LocationStructure">
<xsd:annotation>
<xsd:documentation>
Location where the VEHICLE was when the situation arosse
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OperatorRef
Type:
OperatorRefStructure, simple content
Defined:
locally within BasicServiceInfoGroup group
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
PhoneNumber
Type:
PhoneType, simple content
Defined:
locally within AffectedVehicleStructure complexType
(Mobile) phone number on which the vehicle can be called
XML Source (see within schema source)
<xsd:element minOccurs="0" name="PhoneNumber" type="PhoneType">
<xsd:annotation>
<xsd:documentation>
(Mobile) phone number on which the vehicle can be called
</xsd:documentation>
</xsd:annotation>
</xsd:element>
ProductCategoryRef
Type:
ProductCategoryRefStructure, simple content
Defined:
locally within BasicServiceInfoGroup group
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="ProductCategoryRef" type="ProductCategoryRefStructure">
<xsd:annotation>
<xsd:documentation>
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
RadioAddress
Type:
xsd:NMTOKEN, predefined, simple content
Defined:
locally within AffectedVehicleStructure complexType
Radio address of the VEHICLE
XML Source (see within schema source)
<xsd:element minOccurs="0" name="RadioAddress" type="xsd:NMTOKEN">
<xsd:annotation>
<xsd:documentation>Radio address of the VEHICLE</xsd:documentation>
</xsd:annotation>
</xsd:element>
ServiceFeatureRef
Type:
ServiceFeatureRefStructure, simple content
Defined:
by reference within BasicServiceInfoGroup group
Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Corresponds to NeTEX TYPE OF SERVICe.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="ServiceFeatureRef">
<xsd:annotation>
<xsd:documentation>
Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
Corresponds to NeTEX TYPE OF SERVICe.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
TrainBlockPart
Type:
TrainBlockPartStructure, complex content
Defined:
locally within AffectedVehicleStructure complexType
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>
VehicleFeatureRef
Type:
VehicleFeatureRefStructure, simple content
Defined:
locally within ServiceInfoGroup group
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleFeatureRef" type="VehicleFeatureRefStructure">
<xsd:annotation>
<xsd:documentation>
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
VehicleRef
Type:
VehicleRefStructure, simple content
Defined:
locally within AffectedVehicleStructure complexType
Reference to a specific VEHICLE affected by an SITUATION.
XML Source (see within schema source)
<xsd:element name="VehicleRef" type="VehicleRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a specific VEHICLE affected by an SITUATION.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
VehicleRegistrationNumberPlate
Type:
xsd:normalizedString, predefined, simple content
Defined:
locally within AffectedVehicleStructure complexType
Registration plate of VEHICLE
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleRegistrationNumberPlate" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>Registration plate of VEHICLE</xsd:documentation>
</xsd:annotation>
</xsd:element>
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/