XML Schema "siri_modelPermissions-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (20 global + 9 local), complexTypes (8)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_modelPermissions-v2.0.xsd; see XML source
Includes Schemas (2):
siri_permissions-v2.0.xsd [src], siri_reference-v2.0.xsd [src]
Included in Schemas (10):
siri_connectionTimetable_service.xsd [src], siri_connectionTimetable_service.xsd [src], siri_estimatedTimetable_service.xsd [src], siri_facilityMonitoring_service.xsd [src], siri_generalMessage_service.xsd [src], siri_productionTimetable_service.xsd [src], siri_situationExchange_service.xsd [src], siri_stopMonitoring_service.xsd [src], siri_stopTimetable_service.xsd [src], siri_vehicleMonitoring_service.xsd [src]
All Element Summary
CheckConnectionLinkRef
If access control is supported, whether access control by CONNECTION link is supported.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
CheckLineRef
If access control is supported, whether access control by LINE is supported.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
CheckMonitoringRef
If access control is supported, whether access control by monitoring point (LOGICAL DISPLAY) is supported.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
CheckOperatorRef
If access control is supported, whether access control by OPERATOR is supported.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
ConnectionLinkPermission (in ConnectionLinkPermissions)
Participant's permission for this CONNECTION link.
Type:
Content:
complex, 2 elements
Defined:
ConnectionLinkPermissions
The CONNECTION links that the participant may access.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
ConnectionLinkRef (type ConnectionLinkRefStructure)
Type:
Content:
simple
Defined:
locally at 15 locations
DirectionRef (type DirectionRefStructure)
Type:
Content:
simple
Defined:
locally at 20 locations
FilterByConnectionLinkRef
Whether results can be filtered by CONNECTION LINK.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByDestination
Whether results can be filtered by DESTINATION.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByDirectionRef
Whether results can be filtered by DIRECTION Default is 'true'.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByFacilityRef
Whether results can be filtered by Facility (EQUIPMENT).
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByInterchangeRef
Whether results can be filtered by SERVICE JOURNEY INTERCHANGE.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByLineRef
Whether results can be filtered by LINE.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByMonitoringRef
Whether results can be filtered by Monitoring point (LOGICAL DISPLAY).
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByOperatorRef
Whether results can be filtered by OPERATOR.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByStopPointRef
Whether results can be filtered by SCHEDULED STOP POINT.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByValidityPeriod
Whether results can be filtered by VALIDITY PERIOD.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByVehicleJourneyRef
Whether results can be filtered by VEHICLE JOURNEY.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
FilterByVehicleRef
Whether results can be filtered by VEHICLE.
Type:
xsd:boolean
Content:
simple
Defined:
globally; see XML source
Used:
LinePermission (in LinePermissions)
Participant's permission for this LINE.
Type:
Content:
complex, 3 elements
Defined:
locally within LinePermissions element; see XML source
LinePermissions
The LINEs that the participant may access.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
LineRef (type LineRefStructure)
Type:
Content:
simple
Defined:
locally at 23 locations
MonitoringRef (type MonitoringRefStructure)
Type:
Content:
simple
Defined:
locally at 12 locations
OperatorPermission (in OperatorPermissions)
Participant's permission for this OPERATOR.
Type:
Content:
complex, 2 elements
Defined:
OperatorPermissions
The OPERATOR data that the participant may access.
Type:
anonymous complexType
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
OperatorRef (type OperatorRefStructure)
Type:
Content:
simple
Defined:
locally at 12 locations
PermissionVersionRef (type VersionRefStructure)
Version of permission set.
Type:
Content:
simple
Defined:
locally within PermissionsStructure complexType; see XML source
ProductionTimetablePermission
Permission for a single participant or all participants to use an aspect of the service.
Type:
Content:
complex, 7 elements
Defined:
globally; see XML source
Used:
Complex Type Summary
Abstract type for capability access control.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Type for CONNECTION link Permission.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Type for Monitoring Service Permission.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Type for Line Permission.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Type for Monitoring Service Capability access control.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Type for OPERATOR Permission.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Type for abstract permissions.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 10 locations
Type for Monitoring Point (LOGICAL DISPLAY) Permission.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_permissions" targetNamespace="http://www.siri.org.uk/siri" version="2.0" xmlns="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="../siri_utility/siri_permissions-v2.0.xsd"/>
<xsd:include schemaLocation="siri_reference-v2.0.xsd"/>
<!-- ======================================================================= -->
<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 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk
</Creator>
<Date>
<Created>2005-03-18</Created>
</Date>
<Date>
<Modified>2005-03-20</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Description>
<p>
SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common permission processing elements for access control. Used for capability defintion and for confioguration access matrix.
</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_modelPermissions-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_types-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Derived from the VDV, RTIGXML 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. Common Permission elements.</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType name="PermissionsStructure">
<xsd:annotation>
<xsd:documentation>Type for abstract permissions.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="PermissionVersionRef" type="VersionRefStructure">
<xsd:annotation>
<xsd:documentation>Version of permission set.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<xsd:element name="LinePermissions">
<xsd:annotation>
<xsd:documentation>The LINEs that the participant may access.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice>
<xsd:element ref="AllowAll"/>
<xsd:element maxOccurs="unbounded" name="LinePermission" type="LinePermissionStructure">
<xsd:annotation>
<xsd:documentation>Participant's permission for this LINE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="LinePermissionStructure">
<xsd:annotation>
<xsd:documentation>Type for Line Permission.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractTopicPermissionStructure">
<xsd:sequence>
<xsd:element name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a LINE. whose data participant is allowed to access.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a DIRECTION of LINE. that participant is allowed to access.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="OperatorPermissions">
<xsd:annotation>
<xsd:documentation>
The OPERATOR data that the participant may access.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice>
<xsd:element ref="AllowAll"/>
<xsd:element maxOccurs="unbounded" name="OperatorPermission" type="OperatorPermissionStructure">
<xsd:annotation>
<xsd:documentation>Participant's permission for this OPERATOR.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="OperatorPermissionStructure">
<xsd:annotation>
<xsd:documentation>Type for OPERATOR Permission.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractTopicPermissionStructure">
<xsd:sequence>
<xsd:element name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to an OPERATOR whose data participant is allowed to access.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ConnectionLinkPermissions">
<xsd:annotation>
<xsd:documentation>
The CONNECTION links that the participant may access.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice>
<xsd:element ref="AllowAll"/>
<xsd:element maxOccurs="unbounded" name="ConnectionLinkPermission" type="ConnectionLinkPermissionStructure">
<xsd:annotation>
<xsd:documentation>
Participant's permission for this CONNECTION link.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ConnectionLinkPermissionStructure">
<xsd:annotation>
<xsd:documentation>Type for CONNECTION link Permission.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractTopicPermissionStructure">
<xsd:sequence>
<xsd:element name="ConnectionLinkRef" type="ConnectionLinkRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a CONNECTION link for which permission is made.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="StopMonitorPermissionStructure">
<xsd:annotation>
<xsd:documentation>
Type for Monitoring Point (LOGICAL DISPLAY) Permission.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractTopicPermissionStructure">
<xsd:sequence>
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to a Stop Monitoring point (LOGICAL DISPLAY) to which permission applies.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:element default="true" name="FilterByValidityPeriod" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by VALIDITY PERIOD. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="FilterByOperatorRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by OPERATOR. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="FilterByLineRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by LINE. Default is 'true'
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="FilterByDirectionRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by DIRECTION Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element fixed="true" name="FilterByMonitoringRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by Monitoring point (LOGICAL DISPLAY). Fixed as 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="FilterByConnectionLinkRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by CONNECTION LINK. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" name="FilterByDestination" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by DESTINATION. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" name="FilterByVehicleRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by VEHICLE. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="FilterByStopPointRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by SCHEDULED STOP POINT. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" name="FilterByInterchangeRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" name="FilterByVehicleJourneyRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="FilterByFacilityRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ======================================================================= -->
<xsd:annotation>
<xsd:documentation>
Type for Monitoring Service Capability access control.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CapabilityAccessControlStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="CheckOperatorRef"/>
<xsd:element minOccurs="0" ref="CheckLineRef"/>
<xsd:element minOccurs="0" ref="CheckMonitoringRef"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:annotation>
<xsd:documentation>
Permission for a single participant or all participants to use an aspect of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="ConnectionServicePermissionStructure">
<xsd:annotation>
<xsd:documentation>Type for Monitoring Service Permission.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractPermissionStructure">
<xsd:sequence>
<xsd:element ref="OperatorPermissions"/>
<xsd:element ref="LinePermissions"/>
<xsd:element ref="ConnectionLinkPermissions"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>Abstract type for capability access control.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CapabilityAccessControlStructure">
<xsd:sequence>
<xsd:element minOccurs="0" ref="CheckOperatorRef"/>
<xsd:element minOccurs="0" ref="CheckLineRef"/>
<xsd:element minOccurs="0" ref="CheckConnectionLinkRef">
<xsd:annotation>
<xsd:documentation>
If access control is supported, whether access control by CONNECTION LINK is supported. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:element default="true" name="CheckOperatorRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="CheckLineRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If access control is supported, whether access control by LINE is supported. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="CheckMonitoringRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If access control is supported, whether access control by monitoring point (LOGICAL DISPLAY) is supported. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="true" name="CheckConnectionLinkRef" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</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/