complexType "FacilityRequestStructure"
Namespace:
Content:
complex, 1 attribute, 13 elements
Defined:
Includes:
definitions of 1 attribute, 1 element
Used:
XML Representation Summary
<...
   
 = 
xsd:NMTOKEN : "2.0"
   
>
   
Content: 
</...>
Content Model Elements (13):
AccountId (type xsd:NMTOKEN), AccountKey (type xsd:normalizedString), Address (type EndpointAddress), BoundingBox (type BoundingBoxStructure), Extensions, FacilityDetailLevel (in FacilityRequest), Language (type xsd:language), LineRef (type LineRefStructure), MessageIdentifier (type MessageQualifierStructure), OperatorRef (type OperatorRefStructure), PlaceRef (type xsd:normalizedString), RequestTimestamp, RequestorRef
All Direct / Indirect Based Elements (1):
FacilityRequest
Known Usage Locations
Annotation
Requests for info channels for use in service requests.
Type Definition Detail
Type Derivation Tree
AbstractRequestStructure (extension)
      AbstractDiscoveryRequestStructure (extension)
          FacilityRequestStructure
XML Source (see within schema source)
<xsd:complexType name="FacilityRequestStructure">
<xsd:annotation>
<xsd:documentation>
Requests for info channels for use in service requests.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractDiscoveryRequestStructure">
<xsd:sequence>
<xsd:group ref="FacilityRequestTopicGroup"/>
<xsd:group ref="FacilityRequestPolicyGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
<xsd:attribute default="2.0" name="version" type="VersionString">
<xsd:annotation>
<xsd:documentation>
Version number of request. Fixed
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Attribute Detail (all declarations; 1/1)
version
Type:
Use:
optional
Default:
"2.0"
Defined:
locally within (this) FacilityRequestStructure complexType
Version number of request. Fixed
XML Source (see within schema source)
<xsd:attribute default="2.0" name="version" type="VersionString">
<xsd:annotation>
<xsd:documentation>
Version number of request. Fixed
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
Content Element Detail (all declarations; 13/13)
AccountId
Type:
xsd:NMTOKEN, predefined, simple content
Defined:
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="AccountId" type="xsd:NMTOKEN">
<xsd:annotation>
<xsd:documentation>
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

AccountKey
Type:
xsd:normalizedString, predefined, simple content
Defined:
Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="AccountKey" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>
Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Address
Type:
EndpointAddress, simple content
Defined:
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="Address" type="EndpointAddress">
<xsd:annotation>
<xsd:documentation>
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

BoundingBox
Type:
BoundingBoxStructure, complex content
Defined:
Rectangle containing Facilities be returned. (+SIRI v2.0)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="BoundingBox" type="BoundingBoxStructure">
<xsd:annotation>
<xsd:documentation>
Rectangle containing Facilities be returned. (+SIRI v2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Extensions
Type:
ExtensionsStructure, complex content
Defined:
by reference within (this) FacilityRequestStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="Extensions"/>

FacilityDetailLevel
Type:
Default:
"normal"
Defined:
Level of detail to include in response. Default is 'normal'. +SIRI v2.0
XML Source (see within schema source)
<xsd:element default="normal" minOccurs="0" name="FacilityDetailLevel" type="FacilityDetailEnumeration">
<xsd:annotation>
<xsd:documentation>
Level of detail to include in response. Default is 'normal'. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

Language
Type:
xsd:language, predefined, simple content
Default:
"en"
Defined:
Preferred language in which to return text values. +SIRI v2.0
XML Source (see within schema source)
<xsd:element default="en" minOccurs="0" name="Language" type="xsd:language">
<xsd:annotation>
<xsd:documentation>
Preferred language in which to return text values. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>

LineRef
Type:
LineRefStructure, simple content
Defined:
Filter the results to include only Facilities for the given LINE. (+SIRI v2.0)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Facilities for the given LINE. (+SIRI v2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

MessageIdentifier
Type:
Defined:
Arbitrary unique identifier that can be used to reference this message in subsequent interactions.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="MessageIdentifier" type="MessageQualifierStructure">
<xsd:annotation>
<xsd:documentation>
Arbitrary unique identifier that can be used to reference this message in subsequent interactions.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

OperatorRef
Type:
OperatorRefStructure, simple content
Defined:
Filter the results to include only Facilities run by the specified OPERATOR. (+SIRI v2.0)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Facilities run by the specified OPERATOR. (+SIRI v2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

PlaceRef
Type:
xsd:normalizedString, predefined, simple content
Defined:
Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . (+SIRI v2.0)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="PlaceRef" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . (+SIRI v2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>

RequestorRef
Type:
ParticipantRefStructure, simple content
Defined:
XML Source (see within schema source)
<xsd:element ref="RequestorRef"/>

RequestTimestamp
Type:
xsd:dateTime, predefined, simple content
Defined:
XML Source (see within schema source)
<xsd:element ref="RequestTimestamp"/>

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/