XML Schema "siri_feature-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (3 global + 9 local), complexTypes (3)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model_discovery\siri_feature-v2.0.xsd; see XML source
Includes Schemas (2):
siri_feature_support-v2.0.xsd [src], siri_types-v2.0.xsd [src]
Included in Schemas (3):
siri_connectionLink-v2.0.xsd [src], siri_discovery.xsd [src], siri_stopPoint-v2.0.xsd [src]
Annotation
SIRI subschema with view of classifiers for use in Discovery service
All Element Summary (local elements unified by type)
Icon (type xsd:anyURI)
Type:
xsd:anyURI
Content:
simple
Defined:
locally at 4 locations
Name (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 6 locations
ProductCategory
Category for classification of a journey as a Product
Type:
ProductCategoryStructure
Content:
complex, 3 elements
Defined:
globally; see XML source
Used:
never
ProductCategoryCode (in ProductCategory)
Identifier of TYPE OF PRODUCT CATEGORY classification.
Type:
ProductCategoryCodeType
Content:
simple
Defined:
locally within ProductCategoryStructure complexType; see XML source
ServiceFeature
Service Feature description.
Type:
ServiceFeatureStructure
Content:
complex, 3 elements
Defined:
globally; see XML source
Used:
never
ServiceFeatureCode (type ServiceFeatureCodeType)
Identifier of classification.
Type:
ServiceFeatureCodeType
Content:
simple
Defined:
locally within ServiceFeatureStructure complexType; see XML source
VehicleFeature
Vehicle Feature description.
Type:
VehicleFeaturesStructure
Content:
complex, 3 elements
Defined:
globally; see XML source
Used:
never
VehicleFeatureCode (in VehicleFeature)
Identifier of feature of VEHICLE.
Type:
VehicleFeatureCodeType
Content:
simple
Defined:
locally within VehicleFeaturesStructure complexType; see XML source
Complex Type Summary
ProductCategoryStructure
Type for TYPE OF PRODUCT CATEGORY description.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
ServiceFeatureStructure
Type for Service Feature description.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 2 locations
VehicleFeaturesStructure
Type for description of feature of VEHICLE.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_feature" 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: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>2012-03-23</Created>
</Date>
<Date>
<Modified>2008-11-17</Modified>
Revise to support substitution groups
Correct Type on VEHICLE features delivery structure
</Date>
<Date>
<Modified>2012-03-23</Modified>
+SIRI v2.0
Factored out from siri_discovery
Make Product category icon optional
</Date>
<Description>
<p>
SIRI is a European CEN technical standard for the exchange of real-time information.
</p>
<p>
This subschema describes soem code value models used by different SIRI functional services
<ul>
<li>SERVICE FEATURE discovery</li>
<li>TYPE OF PRODUCT CATEGORY Discovery</li>
</ul>
</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_discovery.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd
</Requires>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Discovery services Derived from the NaPTAN standard .
</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_DS XML schema. Service Interface for Real-time Information. Discovery subschema.
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>
SIRI subschema with view of classifiers for use in Discovery service
</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="../siri_model/siri_feature_support-v2.0.xsd"/>
<xsd:include schemaLocation="../siri_utility/siri_types-v2.0.xsd"/>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<!-- ==== PRODUCT CATE GOIRY =================================================== -->
<xsd:element name="ProductCategory" type="ProductCategoryStructure">
<xsd:annotation>
<xsd:documentation>
Category for classification of a journey as a Product
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="ProductCategoryStructure">
<xsd:annotation>
<xsd:documentation>Type for TYPE OF PRODUCT CATEGORY description.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ProductCategoryCode" type="ProductCategoryCodeType">
<xsd:annotation>
<xsd:documentation>
Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" name="Name" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name of classification (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Icon" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>Icon used to represent TYPE OF PRODUCT CATEGORY.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- =====SERVICE FEATURE =========================================== -->
<xsd:element name="ServiceFeature" type="ServiceFeatureStructure">
<xsd:annotation>
<xsd:documentation>Service Feature description.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="ServiceFeatureStructure">
<xsd:annotation>
<xsd:documentation>Type for Service Feature description.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ServiceFeatureCode" type="ServiceFeatureCodeType">
<xsd:annotation>
<xsd:documentation>
Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" name="Name" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name of classification. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Icon" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>Icon associated with feature.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ====VEHICLE FEATURE =========================================== -->
<xsd:element name="VehicleFeature" type="VehicleFeaturesStructure">
<xsd:annotation>
<xsd:documentation>Vehicle Feature description.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="VehicleFeaturesStructure">
<xsd:annotation>
<xsd:documentation>Type for description of feature of VEHICLE.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="VehicleFeatureCode" type="VehicleFeatureCodeType">
<xsd:annotation>
<xsd:documentation>
Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" name="Name" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Name of feature of VEHICLE. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Icon" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>Icon used to represent feature of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</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/