Namespace: |
|
Content: |
3 elements |
Defined: |
globally in siri_monitoredVehicleJourney-v2.0.xsd; see XML source |
Includes: |
definitions of 3 elements |
Used: |
at 1 location |
Complex Content Model |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Elements describing theProperties specific to a rail CALLs.
</xsd:documentation>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="ReversesAtStop" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether VEHICLE will reverse at stop. Default is 'false'.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Status of signal clearance for TRAIN. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green.
</xsd:documentation>
</xsd:group>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Default: |
"false" |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Whether VEHICLE will reverse at stop. Default is 'false'.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:NMTOKEN, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Status of signal clearance for TRAIN. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green.
</xsd:documentation>
</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:
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/
|