group "CallPropertyGroup"
Namespace:
http://www.siri.org.uk/siri
Content:
5 elements
Defined:
globally in siri_journey-v2.0.xsd; see XML source
Includes:
definitions of 5 elements
Used:
at 4 locations
Complex Content Model
TimingPoint?, BoardingStretch?, RequestStop?, OriginDisplay*, DestinationDisplay*
Content Model Elements (5):
BoardingStretch (type xsd:boolean), DestinationDisplay (type NaturalLanguageStringStructure), OriginDisplay (type NaturalLanguageStringStructure), RequestStop (type xsd:boolean), TimingPoint
Known Usage Locations
Annotation
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
XML Source (see within schema source)
<xsd:group name="CallPropertyGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="TimingPoint"/>
<xsd:element default="false" minOccurs="0" name="BoardingStretch" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether this is a Hail and Ride Stop. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="RequestStop" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; 5/5)
BoardingStretch
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
locally within (this) CallPropertyGroup group
Whether this is a Hail and Ride Stop. Default is 'false'.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="BoardingStretch" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether this is a Hail and Ride Stop. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DestinationDisplay
Type:
NaturalLanguageStringStructure, simple content
Defined:
locally within (this) CallPropertyGroup group
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OriginDisplay
Type:
NaturalLanguageStringStructure, simple content
Defined:
locally within (this) CallPropertyGroup group
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
RequestStop
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
locally within (this) CallPropertyGroup group
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="RequestStop" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
TimingPoint
Type:
xsd:boolean, predefined, simple content
Default:
"true"
Defined:
by reference within (this) CallPropertyGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="TimingPoint"/>
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/