XML Schema "ifopt_equipment-v0.3.xsd"
Target Namespace:
http://www.ifopt.org.uk/ifopt
Version:
0.3
Defined Components:
elements (2 global + 6 local), complexTypes (6), simpleTypes (3), element groups (2)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\ifopt\ifopt_equipment-v0.3.xsd; see XML source
Imports Schemas (2):
siri_feature_support-v2.0.xsd [src], siri_types-v2.0.xsd [src]
Includes Schemas (2):
ifopt_administration-v0.3.xsd [src], ifopt_time-v0.2.xsd [src]
Imported by Schemas (2):
siri_facility-v2.0.xsd [src], siri_situationAffects-v2.0.xsd [src]
Included in Schemas (1):
ifopt_allStopPlace-v0.3.xsd [src]
Annotation
Equipment types for IFOPT Fixed Objects in Public Transport.
All Element Summary
EquipmentId (type EquipmentIdType)
Identifer of EQUIPMENT.
Type:
Content:
simple
Defined:
EquipmentName (type siri:NaturalLanguageStringStructure)
Name of EQUIPMENT.
Type:
Content:
simple, 1 attribute
Defined:
FeatureRef (in FeatureRefs)
Features of LOCAL SERVICe.
Type:
Content:
simple
Defined:
locally within FeatureRefs element; see XML source
FeatureRefs (in LocalService)
Classification of features.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
Includes:
definition of 1 element
LocalService
LOCAL SERVICe.
Type:
Content:
complex, 5 attributes, 8 elements
Defined:
globally; see XML source
Used:
never
OtherPlaceEquipment
EQUIPMENT. that may be in a fixed within a SITe.
Type:
Content:
complex, 5 attributes, 6 elements
Defined:
globally; see XML source
Used:
never
TypeOfEquipment (type EquipmentTypeRefStructure)
Type for reference to TYPE OF EQUIPMENT.
Type:
Content:
simple
Defined:
ValidityConditions (in LocalService)
Conditison governing availability of serevice.
Type:
Content:
complex, 1 element
Defined:
Complex Type Summary
Type for abstract EQUIPMENT.
Content:
complex, 5 attributes, 5 elements
Abstract:
(cannot be assigned directly to elements used in instance XML documents)
Defined:
globally; see XML source
Used:
Type for reference to a EQUIPMENT.
Content:
simple
Defined:
globally; see XML source
Used:
Type for TYPE OF EQUIPMENT.
Content:
simple
Defined:
globally; see XML source
Used:
Type for INSTALLED EQUIPMENT.
Content:
complex, 5 attributes, 5 elements
Abstract:
(cannot be assigned directly to elements used in instance XML documents)
Defined:
globally; see XML source
Used:
Type for LOCAL SERVICE.
Content:
complex, 5 attributes, 8 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Type for SITE EQUIPMENT.
Content:
complex, 5 attributes, 6 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Simple Type Summary
Type for identifier of EQUIPMENT.
Defined:
globally; see XML source
Used:
Availabilityload status of a EQUIPMENT.
Defined:
globally; see XML source
Used:
Type for a identifier of EQUIPMENT.
Defined:
globally; see XML source
Used:
Element Group Summary
Coomon Elements for EQUIPMENt.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Element for LOCAL SERVICe.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="ifopt_equipment" targetNamespace="http://www.ifopt.org.uk/ifopt" version="0.3" 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>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Description>
<p>
Fixed Objects in Public Transport. This subschema defines equipment 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_equipment-v0.3.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 TransModel 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 - Equipment Base Types.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>
Equipment types for IFOPT Fixed Objects in Public Transport.
</xsd:documentation>
</xsd:annotation>
<xsd:include schemaLocation="ifopt_time-v0.2.xsd"/>
<xsd:include schemaLocation="ifopt_administration-v0.3.xsd"/>
<xsd:import namespace="http://www.siri.org.uk/siri" schemaLocation="../siri_utility/siri_types-v2.0.xsd"/>
<!-- ======================================================================= -->
<xsd:simpleType name="EquipmentIdType">
<xsd:annotation>
<xsd:documentation>Type for identifier of EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="EquipmentRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="EquipmentIdType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:simpleType name="EquipmentTypeCodeType">
<xsd:annotation>
<xsd:documentation>Type for a identifier of EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:complexType name="EquipmentTypeRefStructure">
<xsd:annotation>
<xsd:documentation>Type for TYPE OF EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="EquipmentTypeCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:simpleType name="EquipmentStatusEnumeration">
<xsd:annotation>
<xsd:documentation>Availabilityload status of a EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="available"/>
<xsd:enumeration value="notAvailable"/>
</xsd:restriction>
</xsd:simpleType>
<!-- ======================================================================= -->
<xsd:group name="AbstractEquipmentGroup">
<xsd:annotation>
<xsd:documentation>Coomon Elements for EQUIPMENt.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="EquipmentId" type="EquipmentIdType">
<xsd:annotation>
<xsd:documentation>Identifer of EQUIPMENT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EquipmentName" type="siri:NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Name of EQUIPMENT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="TypeOfEquipment" type="EquipmentTypeRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to TYPE OF EQUIPMENT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType abstract="true" name="AbstractEquipmentStructure">
<xsd:annotation>
<xsd:documentation>Type for abstract EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="DataManagedObjectStructure">
<xsd:sequence>
<xsd:group ref="AbstractEquipmentGroup"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType abstract="true" name="InstalledEquipmentStructure">
<xsd:annotation>
<xsd:documentation>Type for INSTALLED EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractEquipmentStructure"/>
</xsd:complexContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType abstract="false" name="PlaceEquipmentStructure">
<xsd:annotation>
<xsd:documentation>Type for SITE EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="InstalledEquipmentStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="OtherPlaceEquipment" type="PlaceEquipmentStructure">
<xsd:annotation>
<xsd:documentation>EQUIPMENT. that may be in a fixed within a SITe.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ======================================================================= -->
<xsd:element name="LocalService" type="LocalServiceStructure">
<xsd:annotation>
<xsd:documentation>LOCAL SERVICe.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="LocalServiceGroup">
<xsd:annotation>
<xsd:documentation>Element for LOCAL SERVICe.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="ValidityConditions" type="ValidityConditionsStructure">
<xsd:annotation>
<xsd:documentation>Conditison governing availability of serevice.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="FeatureRefs">
<xsd:annotation>
<xsd:documentation>Classification of features.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="FeatureRef" type="siri:ServiceFeatureRefStructure">
<xsd:annotation>
<xsd:documentation>Features of LOCAL SERVICe.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType abstract="false" name="LocalServiceStructure">
<xsd:annotation>
<xsd:documentation>Type for LOCAL SERVICE.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="InstalledEquipmentStructure">
<xsd:sequence>
<xsd:group ref="LocalServiceGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</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/