XML Schema "siri_time-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
1.2
Defined Components:
elements (1 global + 13 local), complexTypes (5), simpleTypes (5)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_time-v2.0.xsd; see XML source
Included in Schemas (1):
siri_reference-v2.0.xsd [src]
All Element Summary (local elements unified by type)
DayType
Tpeg DAY TYPE pti_table 34
Type:
Content:
simple
Defined:
globally; see XML source
Used:
EndTime (in Timeband)
Type:
xsd:time
Content:
simple
Defined:
locally at 2 locations
EndTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 3 locations
EndTimePrecision (in ValidityPeriod in SituationExchangeRequest)
Type:
Content:
simple
Defined:
locally at 2 locations
EndTimeStatus (type EndTimeStatusEnumeration)
If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation.
Type:
Content:
simple
Defined:
StartTime (in Timeband)
Type:
xsd:time
Content:
simple
Defined:
locally at 2 locations
StartTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 6 locations
Complex Type Summary
Type for a range of times.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
never
Type for a range of date and times.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for a range of times.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for a range of date times.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Type for a range of date times.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Simple Type Summary
Values for Day Type TPEG pti_table 34
Defined:
globally; see XML source
Used:
Values for Day Type TPEG pti_table 34
Defined:
globally; see XML source
Used:
Allowed values for EndTime Precision
Defined:
globally; see XML source
Used:
Allowed values for EndTime Status.
Defined:
globally; see XML source
Used:
Values for Day Type TPEG pti_table 34
Defined:
globally; see XML source
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_time" targetNamespace="http://www.siri.org.uk/siri" version="1.2" 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>
<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>2005-10-03</Created>
</Date>
<Date>
<Modified>2005-10-04</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Date>
<Modified>2008-11-10</Modified>
refine day types
</Date>
<Date>
<Modified>2014-06-20</Modified>
* [se] Add end time precision to halfopen time rangefor input a siri_time-v2.0.xsd.
* [se] Add end time status to halfopen time range output siri_time-v2.0.xsd.
</Date>
<Description>
<p>
SIRI is a European CEN standard for the exchange of real-time information .
</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_model/}siri_time-v1.2.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Derived from the VDV, RTIG CML and Trident standards.
</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 XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of time types.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
</xsd:annotation>
<!-- ======================================================================= -->
<!-- =====Times================================================================== -->
<xsd:complexType name="ClosedTimestampRangeStructure">
<xsd:annotation>
<xsd:documentation>
Type for a range of date and times. Both start and end time are required.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>The (inclusive) start date and time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EndTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>The (inclusive) end date and time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ClosedTimeRangeStructure">
<xsd:annotation>
<xsd:documentation>
Type for a range of times. Both start and end time are required.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StartTime" type="xsd:time">
<xsd:annotation>
<xsd:documentation>The (inclusive) start time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EndTime" type="xsd:time">
<xsd:annotation>
<xsd:documentation>The (inclusive) end time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="second" minOccurs="0" name="EndTimePrecision" type="EndTimePrecisionEnumeration">
<xsd:annotation>
<xsd:documentation>
Precision with which to interpret the inclusive end time. Default is to the second.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="HalfOpenTimeRangeStructure">
<xsd:annotation>
<xsd:documentation>
Type for a range of times. Start time must be specified, end time is optional.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StartTime" type="xsd:time">
<xsd:annotation>
<xsd:documentation>The (inclusive) start time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EndTime" type="xsd:time">
<xsd:annotation>
<xsd:documentation>
The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="HalfOpenTimestampInputRangeStructure">
<xsd:annotation>
<xsd:documentation>
Type for a range of date times. Start time must be specified, end time is optional.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>The (inclusive) start time stamp.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EndTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>The (inclusive) end time stamp.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="second" minOccurs="0" name="EndTimePrecision" type="EndTimePrecisionEnumeration">
<xsd:annotation>
<xsd:documentation>
Precision with which to interpret the inclusive end time. Default is to the second. (Siri 2.0++)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="HalfOpenTimestampOutputRangeStructure">
<xsd:annotation>
<xsd:documentation>
Type for a range of date times. Start time must be specified, end time is optional.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="StartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>The (inclusive) start time stamp.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EndTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
The (inclusive) end time stamp. If omitted, the range end is open-ended, that is, it should be interpreted as defined by end time status.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="undefined" minOccurs="0" name="EndTimeStatus" type="EndTimeStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="EndTimePrecisionEnumeration">
<xsd:annotation>
<xsd:documentation>Allowed values for EndTime Precision</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="day"/>
<xsd:enumeration value="hour"/>
<xsd:enumeration value="second"/>
<xsd:enumeration value="milliSecond"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="EndTimeStatusEnumeration">
<xsd:annotation>
<xsd:documentation>Allowed values for EndTime Status.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="undefined"/>
<xsd:enumeration value="longTerm"/>
<xsd:enumeration value="shortTerm"/>
</xsd:restriction>
</xsd:simpleType>
<!-- ======================================================================= -->
<xsd:element default="everyDay" name="DayType" type="DayTypeEnumeration">
<xsd:annotation>
<xsd:documentation>Tpeg DAY TYPE pti_table 34</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:simpleType name="DayTypeEnumeration">
<xsd:annotation>
<xsd:documentation>Values for Day Type TPEG pti_table 34</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="pti34_0"/>
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="pti34_1"/>
<xsd:enumeration value="monday"/>
<xsd:enumeration value="pti34_2"/>
<xsd:enumeration value="tuesday"/>
<xsd:enumeration value="pti34_3"/>
<xsd:enumeration value="wednesday"/>
<xsd:enumeration value="pti34_4"/>
<xsd:enumeration value="thursday"/>
<xsd:enumeration value="pti34_5"/>
<xsd:enumeration value="friday"/>
<xsd:enumeration value="pti34_6"/>
<xsd:enumeration value="saturday"/>
<xsd:enumeration value="pti34_7"/>
<xsd:enumeration value="sunday"/>
<xsd:enumeration value="pti34_8"/>
<xsd:enumeration value="weekdays"/>
<xsd:enumeration value="pti34_9"/>
<xsd:enumeration value="weekends"/>
<xsd:enumeration value="pti34_10"/>
<xsd:enumeration value="holiday"/>
<xsd:enumeration value="pti34_11"/>
<xsd:enumeration value="publicHoliday"/>
<xsd:enumeration value="pti34_12"/>
<xsd:enumeration value="religiousHoliday"/>
<xsd:enumeration value="pti34_13"/>
<xsd:enumeration value="federalHoliday"/>
<xsd:enumeration value="pti34_14"/>
<xsd:enumeration value="regionalHoliday"/>
<xsd:enumeration value="pti34_15"/>
<xsd:enumeration value="nationalHoliday"/>
<xsd:enumeration value="pti34_16"/>
<xsd:enumeration value="mondayToFriday"/>
<xsd:enumeration value="pti34_17"/>
<xsd:enumeration value="mondayToSaturday"/>
<xsd:enumeration value="pti34_18"/>
<xsd:enumeration value="sundaysAndPublicHolidays"/>
<xsd:enumeration value="pti34_19"/>
<xsd:enumeration value="schoolDays"/>
<xsd:enumeration value="pti34_20"/>
<xsd:enumeration value="everyDay"/>
<xsd:enumeration value="pti34_255"/>
<xsd:enumeration value="undefinedDayType"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DaysOfWeekEnumerationx">
<xsd:annotation>
<xsd:documentation>Values for Day Type TPEG pti_table 34</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="DayTypeEnumeration">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="monday"/>
<xsd:enumeration value="tuesday"/>
<xsd:enumeration value="wednesday"/>
<xsd:enumeration value="thursday"/>
<xsd:enumeration value="friday"/>
<xsd:enumeration value="saturday"/>
<xsd:enumeration value="sunday"/>
<xsd:enumeration value="mondayToFriday"/>
<xsd:enumeration value="mondayToSaturday"/>
<xsd:enumeration value="weekdays"/>
<xsd:enumeration value="weekends"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="HolidayTypeEnumerationx">
<xsd:annotation>
<xsd:documentation>Values for Day Type TPEG pti_table 34</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="DayTypeEnumeration">
<xsd:enumeration value="holiday"/>
<xsd:enumeration value="publicHoliday"/>
<xsd:enumeration value="religiousHoliday"/>
<xsd:enumeration value="federalHoliday"/>
<xsd:enumeration value="regionalHoliday"/>
<xsd:enumeration value="nationalHoliday"/>
<xsd:enumeration value="sundaysAndPublicHolidays"/>
<xsd:enumeration value="schoolDays"/>
<xsd:enumeration value="everyDay"/>
<xsd:enumeration value="undefinedDayType"/>
</xsd:restriction>
</xsd:simpleType>
</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/