All Element Summary (local elements unified by type) |
||||||||||
|
||||||||||
Days type for monitoring availability.
|
||||||||||
|
||||||||||
Availability change for Equipment item.
|
||||||||||
Service Features associated with equipment.
|
||||||||||
Reference to an EQUIPMENT.
|
||||||||||
Availability status of the EQUIPMENT.
|
||||||||||
Reference to a TYPE OF EQUIPMENT.r.
|
||||||||||
|
||||||||||
A change to the availaibility of EQUIPMENT.
|
||||||||||
Type of facility (several types may be associated to a single facility)
|
||||||||||
Identfier of Facility.
|
||||||||||
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management.
|
||||||||||
Describes where the facility is located.
|
||||||||||
Reference to a Facility.
|
||||||||||
Status of Facility.
|
||||||||||
Description of the feauture of the facility.
|
||||||||||
Service or Stop features associated with equipment.
|
||||||||||
Features of service.
|
||||||||||
Holiday type for monitoring availability.
|
||||||||||
Limitation of facility.
|
||||||||||
Effect of change on impaired access users.
|
||||||||||
Whether stop or service is accessible to mobility impaired users.
|
||||||||||
Monitored (type xsd:boolean) |
|
|||||||||
Description of the mechanism used to monitor the change of the facility status.
|
||||||||||
Mean time interval between two measurements.
|
||||||||||
When the monitoring is in effect.
|
||||||||||
How monitoring is automatic, manual, etc..
|
||||||||||
Textual description of the owner of the facility.
|
||||||||||
Refererence to identifier of owner of facility.
|
||||||||||
|
||||||||||
Setup action to remedy the change of the facility status (if partialy or totaly anavailable)
|
||||||||||
Type of the remedy (repair/replacement/remove)
|
||||||||||
Status of the facility.
|
||||||||||
System identifier of Stop Place component.
|
||||||||||
|
||||||||||
Suitabilities of facility for specific passenger needs.
|
||||||||||
|
||||||||||
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.).
|
||||||||||
When Facility is normally avaialble.
|
||||||||||
|
Complex Type Summary |
||||||||||
Summary information about Facility.
|
||||||||||
Type for Availaibility Change of EQUIPMENT.
|
||||||||||
Type for change to equipment availability.
|
||||||||||
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management.
|
||||||||||
Location of the MONITORED FACILITY.
|
||||||||||
Type for reference to a Faclility.
|
||||||||||
Descriprion of the status of a MONITORED FACILITY.
|
||||||||||
Type for sescription the MONITORED FACILITY itself.
|
||||||||||
Type for effect of EQUIPMENT availability change on impaired access users.
|
||||||||||
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.
|
||||||||||
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.
|
||||||||||
Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable)
|
Simple Type Summary |
||||||
Generic catégory of a facility.
|
||||||
Type for identifier of a Faclility.
|
||||||
Allowed values for changes to the status of a facility.
|
||||||
Allowed values for the status of a MONITORED FACILITY.
|
||||||
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.
|
||||||
Allowed values for actions to remedy a faclity change.
|
Element Group Summary |
||||||||||
Elements describing nature of disruption.
|
||||||||||
Group of Facility accessibility elements.
|
||||||||||
Group of Facility accessibility elements.
|
||||||||||
Group of Facility accessibility elements.
|
<?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>
</xsd:annotation>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
</xsd:appinfo>
<Aggregation>main schema</Aggregation>
</Metadata>
<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>
</Date>
USe Accessibility assessment from ifopt
<Date>
<Modified>2011-01-19</Modified>
</Date>
TidyUp empty ValidtyConditionGroup
<Date>
<Modified>2012-03-23</Modified>
</Date>
+SIRI v2.0
remove unecesasry dependencies <Description>
<p>
</Description>
SIRI is a European CEN standard for the exchange of real-time information .
</p>
This is a package of type modules for equipment availability <Format>
<MediaType>text/xml</MediaType>
</Format>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
<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>
</Relation>
http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd
</Requires>
<Rights>
Unclassified
</Rights>
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
<Source>
<ul>
</Source>
<li>Derived from TransModel and Trident standards.</li>
</ul>
<Status>Version 2.0 Draft</Status>
<Subject>
<Category>
</Subject>
Arts, recreation and travel, Tourism, Travel (tourism), Transport,
</Category>
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 <Project>CEN TC278 WG3 SG7</Project>
<Title>
SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common Facility Elements
</Title>
<Type>Standard</Type>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<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"/>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<!-- Facilities related elements =============================================================== -->
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
</xsd:element>
<xsd:restriction base="xsd:NMTOKEN"/>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
</xsd:simpleContent>
<!-- ======================================================================= -->
<!-- = Definitions for with SIRI 1.1 - Facility Management Service ======================= -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="FacilityCode" type="FacilityCodeType">
</xsd:element>
</xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Textual description of the facility. (Unbounded since SIRI 2.0)
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="FacilityClass" type="FacilityCategoryEnumeration">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Type of facility (several types may be associated to a single facility)
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" name="Feature" type="AllFacilitiesFeatureStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of the feauture of the facility. Several features may be associated to a single facility.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
When Facility is normally avaialble. If not specified, default is 'always'. Values are Logically ANDed together.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Describes where the facility is located. The location is a Transmodel object reference or an IFOPT object reference.
</xsd:documentation>
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="StopPlaceRef" type="ifopt:StopPlaceRefStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
System identifier of Stop Place component. Unique at least within Stop Place and concrete component type.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="Limitations">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" name="Suitability" type="acsb:SuitabilityStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Type of specific need for wich the facility is appropriate.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
</xsd:restriction>
<xsd:enumeration value="fixedEquipment"/>
<xsd:enumeration value="serviceProvidedByIndividual"/>
<xsd:enumeration value="serviceForPersonalDevice"/>
<xsd:enumeration value="reservedArea"/>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element ref="FacilityRef"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether real-time data is available for the stop. Default is 'true'.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
</xsd:restriction>
<xsd:enumeration value="available"/>
<xsd:enumeration value="notAvailable"/>
<xsd:enumeration value="partiallyAvailable"/>
<xsd:enumeration value="added"/>
<xsd:enumeration value="removed"/>
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
</xsd:restriction>
<xsd:enumeration value="added"/>
<xsd:enumeration value="removed"/>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element name="Status" type="FacilityStatusEnumeration">
</xsd:element>
</xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of the facility Status. (Unbounded since SIRI 2.0)
</xsd:documentation>
<xsd:element minOccurs="0" name="AccessibilityAssessment" type="acsb:AccessibilityAssessmentStructure">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:group ref="FacilityScheduleRefGroup">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<!-- ====FACILITY CONDITION========================================= -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management.
</xsd:documentation>
<xsd:sequence>
<xsd:choice>
</xsd:sequence>
<xsd:element name="Facility" type="FacilityStructure">
</xsd:choice>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Setup action to remedy the change of the facility status (if partialy or totaly anavailable)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of the mechanism used to monitor the change of the facility status.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- ======================================================================= -->
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
</xsd:restriction>
<xsd:enumeration value="replace"/>
<xsd:enumeration value="repair"/>
<xsd:enumeration value="remove"/>
<xsd:enumeration value="otherRoute"/>
<xsd:enumeration value="otherLocation"/>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable)
</xsd:documentation>
<xsd:sequence>
<xsd:element minOccurs="0" name="RemedyType" type="RemedyTypeEnumeration">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Description of the set up remedy in natural language. (Unbounded since SIRI 2.0)
</xsd:documentation>
<!--= 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:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
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:sequence>
<xsd:element minOccurs="0" name="MonitoringInterval" type="xsd:duration">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:simpleType>
<xsd:documentation>
</xsd:annotation>
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:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="unknown"/>
</xsd:restriction>
<xsd:enumeration value="manual"/>
<xsd:enumeration value="automatic"/>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
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:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Period" type="HalfOpenTimestampOutputRangeStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
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:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- = Definitions For backward compatibility with SIRI 1.0 ====================================== -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="EquipmentRef" type="ifopt:EquipmentRefStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Description" type="NaturalLanguageStringStructure">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Availability status of the EQUIPMENT. Default is 'notAvailable'.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" name="FeatureRef" type="FeatureRefStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
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:complexType>
<xsd:documentation>
</xsd:annotation>
Type for change to equipment availability. Basic structure defined in the first 1.0 SIRI XSd.
</xsd:documentation>
<xsd:sequence>
<xsd:element minOccurs="0" name="EquipmentAvailability" type="EquipmentAvailabilityStructure">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!-- ===Mobility FACILITY (For backward compatibility with SIRI 1.0 =============================== -->
<!-- =For backward compatibility with SIRI 1.0 ====================================================================== -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Type for effect of EQUIPMENT availability change on impaired access users.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="MobilityImpairedAccess" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
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:documentation>
</xsd:annotation>
Classification of Mobility Facility type - Based on Tpeg pti23.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="FacilityConditionElement">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Information about a change of Equipment availabilti at stop or on vehicle that may affect access or use.
</xsd:documentation>
<xsd:sequence>
<xsd:annotation>
</xsd:sequence>
<xsd:documentation>
</xsd:annotation>
This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1
</xsd:documentation>
</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:
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/
|