XML Schema "acsb_passengerMobility-v0.3.xsd"
Target Namespace:
http://www.ifopt.org.uk/acsb
Version:
0.3
Defined Components:
elements (11 local), complexTypes (3), simpleTypes (5), element groups (1)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\acsb\acsb_passengerMobility-v0.3.xsd; see XML source
Imported by Schemas (3):
siri_facilityMonitoring_service.xsd [src], siri_situationAffects-v2.0.xsd [src], siri_situationExchange_service.xsd [src]
Included in Schemas (2):
acsb_accessibility-v0.3.xsd [src], acsb_all-v0.3.xsd [src]
Annotation
Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport.
All Element Summary (local elements unified by type)
AccompaniedByCarer (in AccessibilityNeedFilter)
Whether the passenger is accompanied by a carer or assistant.
Type:
xsd:boolean
Content:
simple
Defined:
EncumbranceNeed (type EncumbranceEnumeration)
Passenger enceumbrance USER NEED for which SUITABILITY is specified.
Type:
Content:
simple
Defined:
locally within UserNeedGroup group; see XML source
Excluded (type xsd:boolean)
Whether USER NEED is included or excluded.
Type:
xsd:boolean
Content:
simple
Defined:
locally within UserNeedStructure complexType; see XML source
Extensions (type xsd:anyType)
Extensions to USETR NEED.
Type:
xsd:anyType
Content:
any
Defined:
locally within UserNeedStructure complexType; see XML source
MedicalNeed (defined in UserNeedGroup group)
Passenger medical USER NEED for which SUITABILITY is specified.
Type:
anonymous simpleType (restriction of MedicalNeedEnumeration)
Content:
simple
Defined:
locally within UserNeedGroup group; see XML source
MobilityNeed (type MobilityEnumeration)
Passenger mobility USER NEED for which SUITABILITY is specified.
Type:
Content:
simple
Defined:
locally within UserNeedGroup group; see XML source
NeedRanking (type xsd:integer)
Relative ranking of USER NEED on a sclae 1-5
Type:
xsd:integer
Content:
simple
Defined:
locally within UserNeedStructure complexType; see XML source
PsychosensoryNeed (type PyschosensoryNeedEnumeration)
Passenger mobility USER NEED for which SUITABILITY is specified.
Type:
Content:
simple
Defined:
locally within UserNeedGroup group; see XML source
Suitable (type SuitabilityEnumeration)
Whether the Facility is suitable.
Type:
Content:
simple
Defined:
locally within SuitabilityStructure complexType; see XML source
UserNeed (type UserNeedStructure)
Type:
Content:
complex, 7 elements
Defined:
locally at 2 locations
Complex Type Summary
Type for accessibility needs.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for of a specific SUITABILITY.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for of a specific need.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Simple Type Summary
Enumeration of specific encumbrances USER NEEDs.
Defined:
globally; see XML source
Used:
Enumeration of specific Medical USER NEEDs.
Defined:
globally; see XML source
Used:
Identification of mobility USER NEEDs.
Defined:
globally; see XML source
Used:
Enumeration of specific psychosensory USER NEEDs.
Defined:
globally; see XML source
Used:
Identification of specific SUITABILITY.
Defined:
globally; see XML source
Used:
Element Group Summary
Content:
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="passengerMobility" targetNamespace="http://www.ifopt.org.uk/acsb" version="0.3" xmlns="http://www.ifopt.org.uk/acsb" 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 common accessibility 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_accessibility-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 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 - Passenger Mobility Types.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>
Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport.
</xsd:documentation>
</xsd:annotation>
<!--======Point=======================================================================================-->
<xsd:complexType name="PassengerAccessibilityNeedsStructure">
<xsd:annotation>
<xsd:documentation>
Type for accessibility needs. Records the requirementrs of a passenger that may affect choice of facilities.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="UserNeed" type="UserNeedStructure">
<xsd:annotation>
<xsd:documentation>
Specific pyschosensory need that may constrain choice of services and facilities.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="AccompaniedByCarer" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the passenger is accompanied by a carer or assistant.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="UserNeedStructure">
<xsd:annotation>
<xsd:documentation>Type for of a specific need.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="UserNeedGroup">
<xsd:annotation>
<xsd:documentation>one of the following.</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:element minOccurs="0" name="Excluded" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether USER NEED is included or excluded. Default is 'included'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="NeedRanking" type="xsd:integer">
<xsd:annotation>
<xsd:documentation>Relative ranking of USER NEED on a sclae 1-5</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Extensions" type="xsd:anyType">
<xsd:annotation>
<xsd:documentation>Extensions to USETR NEED.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="UserNeedGroup">
<xsd:choice>
<xsd:element name="MobilityNeed" type="MobilityEnumeration">
<xsd:annotation>
<xsd:documentation>
Passenger mobility USER NEED for which SUITABILITY is specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Passenger mobility USER NEED for which SUITABILITY is specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MedicalNeed">
<xsd:annotation>
<xsd:documentation>
Passenger medical USER NEED for which SUITABILITY is specified.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="MedicalNeedEnumeration"/>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EncumbranceNeed" type="EncumbranceEnumeration">
<xsd:annotation>
<xsd:documentation>
Passenger enceumbrance USER NEED for which SUITABILITY is specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<!--======Point=======================================================================================-->
<xsd:simpleType name="MobilityEnumeration">
<xsd:annotation>
<xsd:documentation>Identification of mobility USER NEEDs.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="wheelchair"/>
<xsd:enumeration value="assistedWheelchair"/>
<xsd:enumeration value="motorizedWheelchair"/>
<xsd:enumeration value="walkingFrame"/>
<xsd:enumeration value="restrictedMobility"/>
<xsd:enumeration value="otherMobilityNeed"/>
</xsd:restriction>
</xsd:simpleType>
<!--======Point=======================================================================================-->
<xsd:simpleType name="PyschosensoryNeedEnumeration">
<xsd:annotation>
<xsd:documentation>Enumeration of specific psychosensory USER NEEDs.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="visualImpairment"/>
<xsd:enumeration value="auditoryImpairment"/>
<xsd:enumeration value="cognitiveInputImpairment"/>
<xsd:enumeration value="averseToLifts"/>
<xsd:enumeration value="averseToEscalators"/>
<xsd:enumeration value="averseToConfinedSpaces"/>
<xsd:enumeration value="averseToCrowds"/>
<xsd:enumeration value="otherPsychosensoryNeed"/>
</xsd:restriction>
</xsd:simpleType>
<!--======Medical Need=======================================================================================-->
<xsd:simpleType name="MedicalNeedEnumeration">
<xsd:annotation>
<xsd:documentation>Enumeration of specific Medical USER NEEDs.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="allergic"/>
<xsd:enumeration value="heartCondition"/>
<xsd:enumeration value="otherMedicalNeed"/>
</xsd:restriction>
</xsd:simpleType>
<!--======Encumbrance=======================================================================================-->
<xsd:simpleType name="EncumbranceEnumeration">
<xsd:annotation>
<xsd:documentation>Enumeration of specific encumbrances USER NEEDs.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="luggageEncumbered"/>
<xsd:enumeration value="pushchair"/>
<xsd:enumeration value="baggageTrolley"/>
<xsd:enumeration value="oversizeBaggage"/>
<xsd:enumeration value="guideDog"/>
<xsd:enumeration value="otherAnimal"/>
<xsd:enumeration value="otherEncumbrance"/>
</xsd:restriction>
</xsd:simpleType>
<!--======Suitability==================================================================================-->
<xsd:complexType name="SuitabilityStructure">
<xsd:annotation>
<xsd:documentation>Type for of a specific SUITABILITY.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Suitable" type="SuitabilityEnumeration">
<xsd:annotation>
<xsd:documentation>Whether the Facility is suitable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="UserNeed" type="UserNeedStructure">
<xsd:annotation>
<xsd:documentation>USER NEED for which SUITABILITY is specified.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="SuitabilityEnumeration">
<xsd:annotation>
<xsd:documentation>Identification of specific SUITABILITY.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="suitable"/>
<xsd:enumeration value="notSuitable"/>
</xsd:restriction>
</xsd:simpleType>
<!--======Point=======================================================================================-->
</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/