XML Schema "ifopt_time-v0.2.xsd"
Target Namespace:
http://www.ifopt.org.uk/ifopt
Version:
0.2
Defined Components:
elements (8 local), complexTypes (4)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\ifopt\ifopt_time-v0.2.xsd; see XML source
Includes Schemas (1):
ifopt_types-v0.2.xsd [src]
Imported by Schemas (1):
acsb_accessibility-v0.3.xsd [src]
Included in Schemas (3):
ifopt_allStopPlace-v0.3.xsd [src], ifopt_checkpoint-v0.3.xsd [src], ifopt_equipment-v0.3.xsd [src]
Annotation
Basic Time types for IFOPT Fixed Objects in Public Transport.
All Element Summary
DayType (type xsd:NMTOKEN)
Day type for which timeband applies.
Type:
xsd:NMTOKEN
Content:
simple
Defined:
EndTime (in Timeband)
The (inclusive) end time.
Type:
xsd:time
Content:
simple
Defined:
FromDateTime (type xsd:dateTime)
The (inclusive) start date and time.
Type:
xsd:dateTime
Content:
simple
Defined:
StartTime (in Timeband)
The (inclusive) start time.
Type:
xsd:time
Content:
simple
Defined:
Timeband (in Timebands)
Timeband during which element is available or in effect.
Type:
Content:
complex, 2 elements
Defined:
locally within Timebands element; see XML source
Timebands (defined in ValidityConditionStructure complexType)
Any timebands which further qualify the validity condition.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
Includes:
definition of 1 element
ToDateTime (type xsd:dateTime)
The (inclusive) end time.
Type:
xsd:dateTime
Content:
simple
Defined:
ValidityCondition (in ValidityConditions)
Type:
Content:
complex, 4 elements
Defined:
locally at 2 locations
Complex Type Summary
Type for a range of times.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for a timeband.
Content:
complex, 2 elements
Defined:
globally; see XML source
Used:
A collection of one or more validity conditions.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Type for a validity condition.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="ifopt_time" targetNamespace="http://www.ifopt.org.uk/ifopt" version="0.2" xmlns="http://www.ifopt.org.uk/ifopt" xmlns:siri="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 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk
</Creator>
<Date>
<Created>2006-08-12</Created>
</Date>
<Date>
<Modified>2006-09-22</Modified>
</Date>
<Description>
<p>
Fixed Objects in Public Transport. This subschema defines. Time base types.
</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/ifopt}ifopt_types-v0.2.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Rights>
Unclassified
<Copyright>CEN, Crown Copyright 2006-2012</Copyright>
</Rights>
<Source>
<ul>
<li>Derived from the SIRI 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 SG6</Project>
</Subject>
<Title>
IFOPT Fixed Objects in Public Transport - Time Base Types.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>
Basic Time types for IFOPT Fixed Objects in Public Transport.
</xsd:documentation>
</xsd:annotation>
<xsd:include schemaLocation="ifopt_types-v0.2.xsd"/>
<!-- ======================================================================= -->
<!-- This structure is replicated from SIRI as some validators dont pic, up indirect extension-->
<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 specifed by the EndTimeStatus
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType name="ValidityConditionStructure">
<xsd:annotation>
<xsd:documentation>Type for a validity condition.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="FromDateTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>The (inclusive) start date and time.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ToDateTime" type="xsd:dateTime">
<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:element minOccurs="0" name="DayType" type="xsd:NMTOKEN">
<xsd:annotation>
<xsd:documentation>
Day type for which timeband applies. If absent all day types in context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Timebands">
<xsd:annotation>
<xsd:documentation>
Any timebands which further qualify the validity condition.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Timeband" type="TimebandStructure">
<xsd:annotation>
<xsd:documentation>
Timeband during which element is available or in effect.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="TimebandStructure">
<xsd:annotation>
<xsd:documentation>Type for a timeband.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="HalfOpenTimeRangeStructure"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ValidityConditionsStructure">
<xsd:annotation>
<xsd:documentation>A collection of one or more validity conditions.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="ValidityCondition" type="ValidityConditionStructure">
<xsd:annotation>
<xsd:documentation>
Reference to the identifier of an administrative area.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ====STOP POINTs========================================================= -->
</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/