group "JourneyEndNamesGroup"
Namespace:
http://www.siri.org.uk/siri
Content:
9 elements
Defined:
globally in siri_journey-v2.0.xsd; see XML source
Includes:
definitions of 9 elements
Used:
at 2 locations
Complex Content Model
OriginRef?, OriginName*, OriginShortName*, DestinationDisplayAtOrigin*, Via*, DestinationRef?, DestinationName*, DestinationShortName*, OriginDisplayAtDestination*
Content Model Elements (9):
DestinationDisplayAtOrigin (type NaturalLanguagePlaceNameStructure), DestinationName (type NaturalLanguageStringStructure), DestinationRef, DestinationShortName (type NaturalLanguagePlaceNameStructure), OriginDisplayAtDestination (type NaturalLanguagePlaceNameStructure), OriginName (type NaturalLanguagePlaceNameStructure), OriginRef, OriginShortName (type NaturalLanguagePlaceNameStructure), Via (type ViaNameStructure)
Known Usage Locations
Annotation
End names for journey.
XML Source (see within schema source)
<xsd:group name="JourneyEndNamesGroup">
<xsd:annotation>
<xsd:documentation>End names for journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="OriginRef"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Name of the origin of the journey. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplayAtOrigin" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
DIRECTION name shown for jurney at the origin. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Via" type="ViaNameStructure">
<xsd:annotation>
<xsd:documentation>
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="DestinationRef">
<xsd:annotation>
<xsd:documentation>Reference to a DESTINATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplayAtDestination" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Origin name shown for jourey at the destination +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; 9/9)
DestinationDisplayAtOrigin
Type:
NaturalLanguagePlaceNameStructure, simple content
Defined:
locally within (this) JourneyEndNamesGroup group
DIRECTION name shown for jurney at the origin. +SIRI v2.0
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplayAtOrigin" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
DIRECTION name shown for jurney at the origin. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DestinationName
Type:
NaturalLanguageStringStructure, simple content
Defined:
locally within (this) JourneyEndNamesGroup group
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DestinationRef
Type:
DestinationRefStructure, simple content
Defined:
by reference within (this) JourneyEndNamesGroup group
Reference to a DESTINATION.
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="DestinationRef">
<xsd:annotation>
<xsd:documentation>Reference to a DESTINATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
DestinationShortName
Type:
NaturalLanguagePlaceNameStructure, simple content
Defined:
locally within (this) JourneyEndNamesGroup group
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OriginDisplayAtDestination
Type:
NaturalLanguagePlaceNameStructure, simple content
Defined:
locally within (this) JourneyEndNamesGroup group
Origin name shown for jourey at the destination +SIRI v2.0
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplayAtDestination" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Origin name shown for jourey at the destination +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OriginName
Type:
NaturalLanguagePlaceNameStructure, simple content
Defined:
locally within (this) JourneyEndNamesGroup group
Name of the origin of the journey. (Unbounded since SIRI 2.0)
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Name of the origin of the journey. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OriginRef
Type:
JourneyPlaceRefStructure, simple content
Defined:
by reference within (this) JourneyEndNamesGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="OriginRef"/>
OriginShortName
Type:
NaturalLanguagePlaceNameStructure, simple content
Defined:
locally within (this) JourneyEndNamesGroup group
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Via
Type:
ViaNameStructure, complex content
Defined:
locally within (this) JourneyEndNamesGroup group
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Via" type="ViaNameStructure">
<xsd:annotation>
<xsd:documentation>
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.
</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/