complexType "FacilityLocationStructure"
Namespace:
Content:
complex, 12 elements
Defined:
Used:
XML Representation Summary
<...>
   
Content: 
</...>
Content Model Elements (12):
ConnectionLinkRef, DatedVehicleJourneyRef, InterchangeRef, LineRef, OperatorRef (type OperatorRefStructure), ProductCategoryRef (type ProductCategoryRefStructure), ServiceFeatureRef, StopPlaceComponentId (in FacilityLocation), StopPlaceRef (type ifopt:StopPlaceRefStructure), StopPointRef, VehicleFeatureRef (type VehicleFeatureRefStructure), VehicleRef
All Direct / Indirect Based Elements (1):
FacilityLocation (in Facility)
Known Usage Locations
Annotation
Location of the MONITORED FACILITY.
XML Source (see within schema source)
<xsd:complexType name="FacilityLocationStructure">
<xsd:annotation>
<xsd:documentation>Location of the MONITORED FACILITY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="FacilityScheduleRefGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:group ref="FacilityStopPlaceRefGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:group ref="ServiceInfoGroup"/>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 12/12)
ConnectionLinkRef
Type:
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="ConnectionLinkRef"/>

DatedVehicleJourneyRef
Type:
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DatedVehicleJourneyRef"/>

InterchangeRef
Type:
InterchangeRefStructure, simple content
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="InterchangeRef"/>

LineRef
Type:
LineRefStructure, simple content
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="LineRef"/>

OperatorRef
Type:
OperatorRefStructure, simple content
Defined:
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>

ProductCategoryRef
Type:
Defined:
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>

ServiceFeatureRef
Type:
Defined:
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>

StopPlaceComponentId
Type:
Defined:
System identifier of Stop Place component. Unique at least within Stop Place and concrete component type.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="StopPlaceComponentId" type="ifopt:StopPlaceComponentRefStructure">
<xsd:annotation>
<xsd:documentation>
System identifier of Stop Place component. Unique at least within Stop Place and concrete component type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

StopPlaceRef
Type:
Defined:
Reference to a Stop Place.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="StopPlaceRef" type="ifopt:StopPlaceRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a Stop Place.</xsd:documentation>
</xsd:annotation>
</xsd:element>

StopPointRef
Type:
StopPointRefStructure, simple content
Defined:
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="StopPointRef"/>

VehicleFeatureRef
Type:
Defined:
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:
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/