XML Schema "siri_stopPoint-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (1 global + 11 local), complexTypes (1)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model_discovery\siri_stopPoint-v2.0.xsd; see XML source
Includes Schemas (2):
siri_feature-v2.0.xsd [src], siri_reference-v2.0.xsd [src]
Included in Schemas (2):
siri_discovery.xsd [src], siri_line-v2.0.xsd [src]
Annotation
SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service
All Element Summary
AnnotatedStopPointRef
SCHEDULED STOP POINT definition.
Type:
Content:
complex, 9 elements
Defined:
globally; see XML source
Used:
never
Features (defined in AnnotatedStopPointStructure complexType)
Service features of stop.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
LineDirection (type LineDirectionStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 4 locations
LineRef (type LineRefStructure)
Type:
Content:
simple
Defined:
locally at 23 locations
Lines (defined in AnnotatedStopPointStructure complexType)
LINEs that use stop.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
Includes:
definitions of 2 elements
Location (type LocationStructure)
Type:
Content:
complex, 2 attributes, 4 elements
Defined:
locally at 5 locations
Monitored (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 8 locations
ServiceFeature (in Features defined in AnnotatedStopPointStructure complexType)
Description of Service features of stop.
Type:
Content:
complex, 3 elements
Defined:
locally within Features element; see XML source
StopAreaRef (type StopAreaRefStructure)
Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs.
Type:
Content:
simple
Defined:
StopName (type NaturalLanguageStringStructure)
Name of SCHEDULED STOP POINT.
Type:
Content:
simple, 1 attribute
Defined:
StopPointRef (type StopPointRefStructure)
Type:
Content:
simple
Defined:
locally at 5 locations
Url (type xsd:anyURI)
Type:
xsd:anyURI
Content:
simple
Defined:
locally at 3 locations
Complex Type Summary
View of a SCHEDULED STOP POINT description.
Content:
complex, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 9 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_feature" targetNamespace="http://www.siri.org.uk/siri" version="2.0" xmlns="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:appinfo>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
<Aggregation>main schema</Aggregation>
<Audience>e-service developers</Audience>
<Contributor>CEN TC278 WG3 SG7 Team</Contributor>
<Coverage>Europe</Coverage>
<Creator>
Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk
</Creator>
<Date>
<Created>2012-03-23</Created>
</Date>
<Date>
<Modified>2008-11-17</Modified>
Revise to support substitution groups
Correct Type on VEHICLE features delivery structure
</Date>
<Date>
<Modified>2012-03-23</Modified>
+SIRI v2.0
Factored out from siri_discovery
Add Location, Add StopLine Direction
</Date>
<Date>
<Modified>2012-06-12</Modified>
+SIRI v2.0
Factored out from siri_discovery
Add StopLine Direction
</Date>
<Description>
<p>
SIRI is a European CEN technical standard for the exchange of real-time information.
</p>
<p>
This subschema describes soem code value models used by different SIRI functional services
<ul>
<li>Service Feature discovery</li>
<li>TYPE OF PRODUCT CATEGORY Discovery</li>
</ul>
</p>
</Description>
<Format>
<MediaType>text/xml</MediaType>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
</Format>
<Identifier>
{http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Discovery services Derived from the NaPTAN standard .
</li>
</ul>
</Source>
<Status>Version 2.0 Draft</Status>
<Subject>
<Category>
Arts, recreation and travel, Tourism, Travel (tourism), Transport,
Air transport, Airports,
Ports and maritime transport, Ferries (marine),
Public transport, Bus services, Coach services, Bus stops and stations,
Rail transport, Railway stations and track, Train services, Underground trains,
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
Rail transport, Roads and road transport
</Category>
<Project>CEN TC278 WG3 SG7</Project>
</Subject>
<Title>
SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>
SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service
</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri_feature-v2.0.xsd"/>
<xsd:include schemaLocation="../siri_model/siri_reference-v2.0.xsd"/>
<!-- === VIEW of SCHEDULED STOP POINT============================================== -->
<xsd:annotation>
<xsd:documentation>SCHEDULED STOP POINT definition.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="AnnotatedStopPointStructure">
<xsd:annotation>
<xsd:documentation>View of a SCHEDULED STOP POINT description.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StopPointRef" type="StopPointRefStructure">
<xsd:annotation>
<xsd:documentation>Identifer of the stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="TimingPoint"/>
<xsd:element default="true" minOccurs="0" name="Monitored" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="StopName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="StopAreaRef" type="StopAreaRefStructure">
<xsd:annotation>
<xsd:documentation>
Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Features">
<xsd:annotation>
<xsd:documentation>Service features of stop. Detail level is 'full'</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element maxOccurs="1" minOccurs="1" name="ServiceFeature" type="ServiceFeatureStructure">
<xsd:annotation>
<xsd:documentation>Description of Service features of stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="1" ref="ServiceFeatureRef"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="Lines">
<xsd:annotation>
<xsd:documentation>LINEs that use stop. Detail level is 'full'</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element maxOccurs="1" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a LINE that calls at stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="LineDirection" type="LineDirectionStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a LINE that calls at stop. and its direction +SIRI V2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="Location" type="LocationStructure">
<xsd:annotation>
<xsd:documentation>
Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Url" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>
Web page associated with Stop. Detail level is 'full'+SIRI.v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
</xsd:schema>

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/