XML Schema "siri_facility-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (3 global + 44 local), complexTypes (12), simpleTypes (6), element groups (4)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_facility-v2.0.xsd; see XML source
Imports Schemas (2):
acsb_limitations-v0.2.xsd [src], ifopt_equipment-v0.3.xsd [src]
Includes Schemas (3):
siri_facilities-v1.2.xsd [src], siri_journey_support-v2.0.xsd [src], siri_utility-v1.1.xsd [src]
Included in Schemas (2):
siri_facilityMonitoring_service.xsd [src], siri_journey-v2.0.xsd [src]
Annotation
SIRi Facility model elemenys
All Element Summary (local elements unified by type)
AccessibilityAssessment (type acsb:AccessibilityAssessmentStructure)
Type:
Content:
complex, 4 elements
Defined:
locally at 7 locations
DayType (type DaysOfWeekEnumerationx)
Days type for monitoring availability.
Type:
Content:
simple
Defined:
Description (type NaturalLanguageStringStructure)
Type:
Content:
simple, 1 attribute
Defined:
locally at 6 locations
EquipmentAvailability (in FacilityChangeElement)
Availability change for Equipment item.
Type:
Content:
complex, 7 elements
Defined:
EquipmentFeatures (in EquipmentAvailability)
Service Features associated with equipment.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
Includes:
definition of 1 element
EquipmentRef (in EquipmentAvailability)
Reference to an EQUIPMENT.
Type:
Content:
simple
Defined:
EquipmentStatus (in EquipmentAvailability)
Availability status of the EQUIPMENT.
Type:
Content:
simple
Defined:
EquipmentTypeRef (in EquipmentAvailability)
Reference to a TYPE OF EQUIPMENT.r.
Type:
Content:
simple
Defined:
Facility (type FacilityStructure)
Type:
Content:
complex, 12 elements
Defined:
locally at 2 locations
FacilityChangeElement
A change to the availaibility of EQUIPMENT.
Type:
Content:
complex, 3 elements
Defined:
globally; see XML source
Used:
FacilityClass (in Facility)
Type of facility (several types may be associated to a single facility)
Type:
Content:
simple
Defined:
locally within FacilityStructure complexType; see XML source
FacilityCode (in Facility)
Identfier of Facility.
Type:
Content:
simple
Defined:
locally within FacilityStructure complexType; see XML source
FacilityConditionElement
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management.
Type:
Content:
complex, 8 elements
Defined:
globally; see XML source
Used:
FacilityLocation (in Facility)
Describes where the facility is located.
Type:
Content:
complex, 12 elements
Defined:
locally within FacilityStructure complexType; see XML source
FacilityRef
Reference to a Facility.
Type:
Content:
simple
Defined:
globally; see XML source
Used:
FacilityStatus (type FacilityStatusStructure)
Status of Facility.
Type:
Content:
complex, 4 elements
Defined:
Feature (in Features)
Description of the feauture of the facility.
Type:
Content:
complex, 16 elements
Defined:
locally within Features element; see XML source
FeatureRef (in EquipmentFeatures)
Service or Stop features associated with equipment.
Type:
Content:
simple
Defined:
Features (in Facility)
Features of service.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within FacilityStructure complexType; see XML source
Includes:
definition of 1 element
HolidayType (type HolidayTypeEnumerationx)
Holiday type for monitoring availability.
Type:
Content:
simple
Defined:
Limitations (in Facility)
Limitation of facility.
Type:
anonymous complexType
Content:
complex, 6 elements
Defined:
MobilityDisruption (in FacilityChangeElement)
Effect of change on impaired access users.
Type:
Content:
complex, 2 elements
Defined:
MobilityImpairedAccess (in MobilityDisruption)
Whether stop or service is accessible to mobility impaired users.
Type:
xsd:boolean
Content:
simple
Defined:
Monitored (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 8 locations
MonitoringInfo (type MonitoringInformationStructure)
Description of the mechanism used to monitor the change of the facility status.
Type:
Content:
complex, 4 elements
Defined:
MonitoringInterval (in MonitoringInfo)
Mean time interval between two measurements.
Type:
xsd:duration
Content:
simple
Defined:
MonitoringPeriod (in MonitoringInfo)
When the monitoring is in effect.
Type:
Content:
complex, 4 elements
Defined:
MonitoringType (in MonitoringInfo)
How monitoring is automatic, manual, etc..
Type:
Content:
simple
Defined:
OwnerName (in Facility)
Textual description of the owner of the facility.
Type:
Content:
simple, 1 attribute
Defined:
locally within FacilityStructure complexType; see XML source
OwnerRef (in Facility)
Refererence to identifier of owner of facility.
Type:
Content:
simple
Defined:
locally within FacilityStructure complexType; see XML source
Period (type HalfOpenTimestampOutputRangeStructure)
Type:
Content:
complex, 3 elements
Defined:
locally at 2 locations
Remedy (type RemedyStructure)
Setup action to remedy the change of the facility status (if partialy or totaly anavailable)
Type:
Content:
complex, 3 elements
Defined:
RemedyType (in Remedy)
Type of the remedy (repair/replacement/remove)
Type:
Content:
simple
Defined:
locally within RemedyStructure complexType; see XML source
Status (in FacilityStatus)
Status of the facility.
Type:
Content:
simple
Defined:
StopPlaceComponentId (in FacilityLocation)
System identifier of Stop Place component.
Type:
Content:
simple
Defined:
StopPlaceRef (type ifopt:StopPlaceRefStructure)
Type:
Content:
simple
Defined:
locally at 4 locations
Suitabilities (in Facility)
Suitabilities of facility for specific passenger needs.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
Includes:
definition of 1 element
Suitability (type acsb:SuitabilityStructure)
Type:
Content:
complex, 2 elements
Defined:
locally at 2 locations
Timeband (type HalfOpenTimeRangeStructure)
Monitoring period within a single day (monitoring may not be available at night, or may ony occur at certain time of day for manual monitoring, etc.).
Type:
Content:
complex, 2 elements
Defined:
ValidityCondition (in Facility)
When Facility is normally avaialble.
Type:
Content:
complex, 4 elements
Defined:
locally within FacilityStructure complexType; see XML source
ValidityPeriod (type HalfOpenTimestampOutputRangeStructure)
Type:
Content:
complex, 3 elements
Defined:
locally at 3 locations
Complex Type Summary
Summary information about Facility.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Type for Availaibility Change of EQUIPMENT.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 7 elements
Used:
Type for change to equipment availability.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management.
Content:
complex, 8 elements
Defined:
globally; see XML source
Includes:
definitions of 8 elements
Used:
Location of the MONITORED FACILITY.
Content:
complex, 12 elements
Defined:
globally; see XML source
Used:
Type for reference to a Faclility.
Content:
simple
Defined:
globally; see XML source
Used:
Descriprion of the status of a MONITORED FACILITY.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Type for sescription the MONITORED FACILITY itself.
Content:
complex, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 10 elements
Used:
Type for effect of EQUIPMENT availability change on impaired access users.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Allowed values for the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable)
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Simple Type Summary
Generic catégory of a facility.
Defined:
globally; see XML source
Used:
Type for identifier of a Faclility.
Defined:
globally; see XML source
Used:
Allowed values for changes to the status of a facility.
Defined:
globally; see XML source
Used:
never
Allowed values for the status of a MONITORED FACILITY.
Defined:
globally; see XML source
Used:
Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRi.
Defined:
globally; see XML source
Used:
Allowed values for actions to remedy a faclity change.
Defined:
globally; see XML source
Used:
Element Group Summary
Elements describing nature of disruption.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Group of Facility accessibility elements.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Group of Facility accessibility elements.
Content:
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Group of Facility accessibility elements.
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="siri_facility" targetNamespace="http://www.siri.org.uk/siri" version="2.0" xmlns="http://www.siri.org.uk/siri" xmlns:acsb="http://www.ifopt.org.uk/acsb" xmlns:ifopt="http://www.ifopt.org.uk/ifopt" 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>2005-11-15</Created>
</Date>
<Date>
<Modified>2005-11-20</Modified>
</Date>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Date>
<Modified>2008-01-11</Modified>
</Date>
<Date>
<Modified>2008-07-05</Modified>
USe Accessibility assessment from ifopt
</Date>
<Date>
<Modified>2011-01-19</Modified>
TidyUp empty ValidtyConditionGroup
</Date>
<Date>
<Modified>2012-03-23</Modified>
+SIRI v2.0
remove unecesasry dependencies
</Date>
<Description>
<p>
SIRI is a European CEN standard for the exchange of real-time information .

This is a package of type modules for equipment availability
</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_facility-v2.0.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>CEN</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>Derived from TransModel 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. Common Facility Elements
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRi Facility model elemenys</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri_facilities-v1.2.xsd"/>
<xsd:include schemaLocation="siri_journey_support-v2.0.xsd"/>
<!-- ======================================================================= -->
<xsd:import namespace="http://www.ifopt.org.uk/ifopt" schemaLocation="../ifopt/ifopt_equipment-v0.3.xsd"/>
<!-- ======================================================================= -->
<!--Needed to work around import limitation in jaxb - all namespaces acsb needs to be after ifopt. -->
<xsd:import namespace="http://www.ifopt.org.uk/acsb" schemaLocation="../acsb/acsb_limitations-v0.2.xsd"/>
<!-- ======================================================================= -->
<xsd:include schemaLocation="../siri_utility/siri_utility-v1.1.xsd"/>
<!-- ======================================================================= -->
<!-- Facilities related elements =============================================================== -->
<xsd:simpleType name="FacilityCodeType">
<xsd:annotation>
<xsd:documentation>Type for identifier of a Faclility.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:element name="FacilityRef" type="FacilityRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a Facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="FacilityRefStructure">
<xsd:annotation>
<xsd:documentation>Type for reference to a Faclility.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="FacilityCodeType"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- ======================================================================= -->
<!-- = Definitions for with SIRI 1.1 - Facility Management Service ======================= -->
<xsd:complexType name="FacilityStructure">
<xsd:annotation>
<xsd:documentation>
Type for sescription the MONITORED FACILITY itself.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="FacilityCode" type="FacilityCodeType">
<xsd:annotation>
<xsd:documentation>Identfier of Facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Textual description of the facility. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="FacilityClass" type="FacilityCategoryEnumeration">
<xsd:annotation>
<xsd:documentation>
Type of facility (several types may be associated to a single facility)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Features">
<xsd:annotation>
<xsd:documentation>Features of service.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Feature" type="AllFacilitiesFeatureStructure">
<xsd:annotation>
<xsd:documentation>
Description of the feauture of the facility. Several features may be associated to a single facility.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="OwnerRef" type="OrganisationRefStructure">
<xsd:annotation>
<xsd:documentation>Refererence to identifier of owner of facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="OwnerName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Textual description of the owner of the facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ValidityCondition" type="MonitoringValidityConditionStructure">
<xsd:annotation>
<xsd:documentation>
When Facility is normally avaialble. If not specified, default is 'always'. Values are Logically ANDed together.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="FacilityLocation" type="FacilityLocationStructure">
<xsd:annotation>
<xsd:documentation>
Describes where the facility is located. The location is a Transmodel object reference or an IFOPT object reference.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="FacilityAccessibilityGroup"/>
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
<xsd:documentation>Accessibility of the facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="FacilityScheduleRefGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="LineRef"/>
<xsd:element minOccurs="0" ref="StopPointRef"/>
<xsd:element minOccurs="0" ref="VehicleRef"/>
<xsd:element minOccurs="0" ref="DatedVehicleJourneyRef"/>
<xsd:element minOccurs="0" ref="ConnectionLinkRef"/>
<xsd:element minOccurs="0" ref="InterchangeRef"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="FacilityStopPlaceRefGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="StopPlaceRef" type="ifopt:StopPlaceRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a Stop Place.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="StopPlaceComponentId" type="ifopt:StopPlaceComponentRefStructure">
<xsd:annotation>
<xsd:documentation>
System identifier of Stop Place component. Unique at least within Stop Place and concrete component type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="FacilityAccessibilityGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="Limitations">
<xsd:annotation>
<xsd:documentation>Limitation of facility.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:group ref="acsb:MobilityLimitationGroup"/>
<xsd:group ref="acsb:SensoryLimitationGroup"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="Suitabilities">
<xsd:annotation>
<xsd:documentation>
Suitabilities of facility for specific passenger needs.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Suitability" type="acsb:SuitabilityStructure">
<xsd:annotation>
<xsd:documentation>
Type of specific need for wich the facility is appropriate.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:simpleType name="FacilityCategoryEnumeration">
<xsd:annotation>
<xsd:documentation>Generic catégory of a facility.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="fixedEquipment"/>
<xsd:enumeration value="serviceProvidedByIndividual"/>
<xsd:enumeration value="serviceForPersonalDevice"/>
<xsd:enumeration value="reservedArea"/>
</xsd:restriction>
</xsd:simpleType>
<!-- ======================================================================= -->
<xsd:complexType name="AnnotatedFacilityStructure">
<xsd:annotation>
<xsd:documentation>
Summary information about Facility. Used in DISCOVERY used
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="FacilityRef"/>
<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'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Facility" type="FacilityStructure">
<xsd:annotation>
<xsd:documentation>Description of the facility (without its status)</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:simpleType name="FacilityStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
Allowed values for the status of a MONITORED FACILITY.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="available"/>
<xsd:enumeration value="notAvailable"/>
<xsd:enumeration value="partiallyAvailable"/>
<xsd:enumeration value="added"/>
<xsd:enumeration value="removed"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="FacilityStatusChangeEnumeration">
<xsd:annotation>
<xsd:documentation>
Allowed values for changes to the status of a facility.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="added"/>
<xsd:enumeration value="removed"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="FacilityStatusStructure">
<xsd:annotation>
<xsd:documentation>
Descriprion of the status of a MONITORED FACILITY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Status" type="FacilityStatusEnumeration">
<xsd:annotation>
<xsd:documentation>Status of the facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the facility Status. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
<xsd:documentation>Accessibility of the facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="FacilityLocationStructure">
<xsd:annotation>
<xsd:documentation>Location of the MONITORED FACILITY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="FacilityScheduleRefGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:group ref="FacilityStopPlaceRefGroup">
<xsd:annotation>
<xsd:documentation>Group of Facility accessibility elements.</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:group ref="ServiceInfoGroup"/>
</xsd:sequence>
</xsd:complexType>
<!-- ====FACILITY CONDITION========================================= -->
<xsd:annotation>
<xsd:documentation>
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="FacilityConditionStructure">
<xsd:annotation>
<xsd:documentation>
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:element name="Facility" type="FacilityStructure">
<xsd:annotation>
<xsd:documentation>Facility affected by condition.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="FacilityRef"/>
</xsd:choice>
<xsd:element name="FacilityStatus" type="FacilityStatusStructure">
<xsd:annotation>
<xsd:documentation>Status of Facility.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="SituationRef"/>
<xsd:element minOccurs="0" name="Remedy" type="RemedyStructure">
<xsd:annotation>
<xsd:documentation>
Setup action to remedy the change of the facility status (if partialy or totaly anavailable)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MonitoringInfo" type="MonitoringInformationStructure">
<xsd:annotation>
<xsd:documentation>
Description of the mechanism used to monitor the change of the facility status.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ValidityPeriod" type="HalfOpenTimestampOutputRangeStructure">
<xsd:annotation>
<xsd:documentation>
Period (duration) of the status change for the facility.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:simpleType name="RemedyTypeEnumeration">
<xsd:annotation>
<xsd:documentation>
Allowed values for actions to remedy a faclity change.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="replace"/>
<xsd:enumeration value="repair"/>
<xsd:enumeration value="remove"/>
<xsd:enumeration value="otherRoute"/>
<xsd:enumeration value="otherLocation"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="RemedyStructure">
<xsd:annotation>
<xsd:documentation>
Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable)
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="RemedyType" type="RemedyTypeEnumeration">
<xsd:annotation>
<xsd:documentation>Type of the remedy (repair/replacement/remove)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the set up remedy in natural language. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<!--= Definition of Monitoring Information ===========================================-->
<!--= First used by Facility Management service, but may be used by other services later, and then may be moved to a more generic file in the future-->
<xsd:complexType name="MonitoringInformationStructure">
<xsd:annotation>
<xsd:documentation>
Allowed values for the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="MonitoringInterval" type="xsd:duration">
<xsd:annotation>
<xsd:documentation>Mean time interval between two measurements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MonitoringType" type="MonitoringTypeEnumeration">
<xsd:annotation>
<xsd:documentation>How monitoring is automatic, manual, etc..</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="MonitoringPeriod" type="MonitoringValidityConditionStructure">
<xsd:annotation>
<xsd:documentation>
When the monitoring is in effect. If absent always.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="MonitoringTypeEnumeration">
<xsd:annotation>
<xsd:documentation>
Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRi.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
<xsd:enumeration value="manual"/>
<xsd:enumeration value="automatic"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="MonitoringValidityConditionStructure">
<xsd:annotation>
<xsd:documentation>
Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Period" type="HalfOpenTimestampOutputRangeStructure">
<xsd:annotation>
<xsd:documentation>
Date and tme range within which condition is available.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Timeband" type="HalfOpenTimeRangeStructure">
<xsd:annotation>
<xsd:documentation>
Monitoring period within a single day (monitoring may not be available at night, or may ony occur at certain time of day for manual monitoring, etc.). Several periods can be defined.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DayType" type="DaysOfWeekEnumerationx">
<xsd:annotation>
<xsd:documentation>Days type for monitoring availability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="HolidayType" type="HolidayTypeEnumerationx">
<xsd:annotation>
<xsd:documentation>Holiday type for monitoring availability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- = Definitions For backward compatibility with SIRI 1.0 ====================================== -->
<xsd:annotation>
<xsd:documentation>
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="EquipmentAvailabilityStructure">
<xsd:annotation>
<xsd:documentation>Type for Availaibility Change of EQUIPMENT.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="EquipmentRef" type="ifopt:EquipmentRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to an EQUIPMENT.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of EQUIPMENT. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EquipmentTypeRef" type="ifopt:EquipmentTypeRefStructure">
<xsd:annotation>
<xsd:documentation>Reference to a TYPE OF EQUIPMENT.r.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ValidityPeriod" type="HalfOpenTimestampOutputRangeStructure">
<xsd:annotation>
<xsd:documentation>
Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="notAvailable" name="EquipmentStatus" type="ifopt:EquipmentStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
Availability status of the EQUIPMENT. Default is 'notAvailable'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EquipmentFeatures">
<xsd:annotation>
<xsd:documentation>Service Features associated with equipment.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="FeatureRef" type="FeatureRefStructure">
<xsd:annotation>
<xsd:documentation>
Service or Stop features associated with equipment. Recommended values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="FacilityChangeStructure">
<xsd:annotation>
<xsd:documentation>
Type for change to equipment availability. Basic structure defined in the first 1.0 SIRI XSd.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="EquipmentAvailability" type="EquipmentAvailabilityStructure">
<xsd:annotation>
<xsd:documentation>Availability change for Equipment item.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="SituationRef"/>
<xsd:element minOccurs="0" name="MobilityDisruption" type="MobilityDisruptionStructure">
<xsd:annotation>
<xsd:documentation>Effect of change on impaired access users.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ===Mobility FACILITY (For backward compatibility with SIRI 1.0 =============================== -->
<!-- =For backward compatibility with SIRI 1.0 ====================================================================== -->
<xsd:complexType name="MobilityDisruptionStructure">
<xsd:annotation>
<xsd:documentation>
Type for effect of EQUIPMENT availability change on impaired access users.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="MobilityImpairedAccess" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether stop or service is accessible to mobility impaired users. This may be further qualified by one ore more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or 'tepFreeAccess.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="AccessFacility">
<xsd:annotation>
<xsd:documentation>
Classification of Mobility Facility type - Based on Tpeg pti23.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="DisruptionGroup">
<xsd:annotation>
<xsd:documentation>Elements describing nature of disruption.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="FacilityConditionElement">
<xsd:annotation>
<xsd:documentation>
Information about a change of Equipment availabilti at stop or on vehicle that may affect access or use.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1
</xsd:documentation>
</xsd:annotation>
<xsd:element minOccurs="0" ref="FacilityChangeElement"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="SituationRef"/>
</xsd:sequence>
</xsd:sequence>
</xsd:group>
</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/