Schema "intenz.xsd"
Target Namespace:
http://www.ebi.ac.uk/intenz
Version:
0.2
Defined Components:
global elements, 2 local elements, 5 complexTypes
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
/Users/rafa/projects/intenz/intenz-xml/src/main/resources/intenz.xsd; see XML source
Includes Schema:
enzyme.xsd [src]
All Element Summary
i:data_description (in i:intenz) Description of the data included in the XML file.
Type:
Content:
mixed (allows character data), elem. wildcard
Defined:
locally witnin i:intenz element; see XML source
i:description A text description.
Type:
Content:
mixed (allows character data), elem. wildcard
Defined:
globally; see XML source
Used:
i:ec_class A class of enzymes according to the NC-IUBMB.
Type:
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Used:
i:ec_sub-subclass A subsubclass within the subclass.
Type:
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Used:
i:ec_subclass A subclass within the class.
Type:
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Used:
i:enzyme (in i:ec_sub-subclass) An enzyme within the subsubclass.
Type:
Content:
complex, 2 attributes, 12 elements
Defined:
locally witnin i:ecSubsubclassType complexType; see XML source
i:intenz The IntEnz database.
Type:
anonymous complexType
Content:
complex, 2 attributes, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 attributes, 2 elements
Used:
never
i:name The name of a class, subclass or subsubclass of enzymes.
Type:
Content:
mixed (allows character data), elem. wildcard
Defined:
globally; see XML source
Used:
Complex Type Summary
Enzyme class type.
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
Enzyme subclass type.
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
Enzyme subsubclass type.
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
Content:
complex, 2 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
Content:
mixed (allows character data), elem. wildcard
Defined:
globally; see XML source
Includes:
definition of elem. wildcard
Used:
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema elementFormDefault="qualified" targetNamespace="http://www.ebi.ac.uk/intenz" version="0.2" xmlns:i="http://www.ebi.ac.uk/intenz" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:include schemaLocation="enzyme.xsd"/>
<xs:complexType name="ecClassType">
<xs:annotation>
<xs:documentation>Enzyme class type.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" ref="i:name"/>
<xs:element minOccurs="0" ref="i:description"/>
<xs:element maxOccurs="unbounded" minOccurs="1" ref="i:ec_subclass"/>
</xs:sequence>
<xs:attribute name="ec1" type="xs:positiveInteger" use="required">
<xs:annotation>
<xs:documentation>
The first digit of the EC number.
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="ecSubclassType">
<xs:annotation>
<xs:documentation>Enzyme subclass type.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" ref="i:name"/>
<xs:element minOccurs="0" ref="i:description"/>
<xs:element maxOccurs="unbounded" minOccurs="1" ref="i:ec_sub-subclass"/>
</xs:sequence>
<xs:attribute name="ec2" type="xs:positiveInteger" use="required">
<xs:annotation>
<xs:documentation>
The second digit of the EC number.
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="ecSubsubclassType">
<xs:annotation>
<xs:documentation>Enzyme subsubclass type.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" ref="i:name"/>
<xs:element minOccurs="0" ref="i:description"/>
<xs:element maxOccurs="unbounded" minOccurs="1" name="enzyme" type="i:entryType">
<xs:annotation>
<xs:documentation>An enzyme within the subsubclass.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="ec3" type="xs:positiveInteger" use="required">
<xs:annotation>
<xs:documentation>The third digit of the EC number.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="entryType">
<xs:complexContent>
<xs:extension base="i:enzymeType">
<xs:attribute name="ec4" type="xs:positiveInteger" use="required">
<xs:annotation>
<xs:documentation>
The fourth digit of the EC number.
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute default="false" name="preliminary" type="xs:boolean">
<xs:annotation>
<xs:documentation>
Is this a preliminary - neither proposed nor
accepted by NC-IUBMB yet - EC number issued
by UniProt?
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType mixed="true" name="xmlContentType">
<xs:sequence>
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="skip">
<xs:annotation>
<xs:documentation>
Any markup is allowed here.
</xs:documentation>
</xs:annotation>
</xs:any>
</xs:sequence>
</xs:complexType>
<xs:element name="intenz">
<xs:annotation>
<xs:documentation>The IntEnz database.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence maxOccurs="1" minOccurs="1">
<xs:element minOccurs="0" name="data_description" type="i:xmlContentType">
<xs:annotation>
<xs:documentation>Description of the data included in the XML file.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="1" ref="i:ec_class"/>
</xs:sequence>
<xs:attribute name="release" type="xs:positiveInteger" use="required">
<xs:annotation>
<xs:documentation>The IntEnz release from which data come.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="date" type="xs:date" use="required">
<xs:annotation>
<xs:documentation>Date of the IntEnz release.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:unique name="uniqueEc1">
<xs:selector xpath="i:class"/>
<xs:field xpath="@ec1"/>
</xs:unique>
</xs:element>
<xs:element name="ec_class" type="i:ecClassType">
<xs:annotation>
<xs:documentation>
A class of enzymes according to the NC-IUBMB.
</xs:documentation>
</xs:annotation>
<xs:unique name="uniqueEc2">
<xs:selector xpath="i:sub-class"/>
<xs:field xpath="@ec2"/>
</xs:unique>
</xs:element>
<xs:element name="ec_subclass" type="i:ecSubclassType">
<xs:annotation>
<xs:documentation>
A subclass within the class.
</xs:documentation>
</xs:annotation>
<xs:unique name="uniqueEc3">
<xs:selector xpath="i:sub-sub-class"/>
<xs:field xpath="@ec3"/>
</xs:unique>
</xs:element>
<xs:element name="ec_sub-subclass" type="i:ecSubsubclassType">
<xs:annotation>
<xs:documentation>
A subsubclass within the subclass.
</xs:documentation>
</xs:annotation>
<xs:unique name="uniqueEc4">
<xs:selector xpath="i:enzyme"/>
<xs:field xpath="@ec4"/>
<xs:field xpath="@preliminary"/>
</xs:unique>
</xs:element>
<xs:element name="description" type="i:xmlContentType">
<xs:annotation>
<xs:documentation>
A text description.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="name" type="i:xmlContentType">
<xs:annotation>
<xs:documentation>
The name of a class, subclass or subsubclass of enzymes.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:schema>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which 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/