# XML Schema Documentation

Printer-friendly Version

XML Instance Representation:
[ Expand All | Collapse All ]

Schema Component Representation:
[ Expand All | Collapse All ]

## Table of Contents

- Schema Document Properties
- Global Declarations
  - Element: resultset
- Global Definitions
  - Complex Type: AnyRecordType

- Legend

- Glossary

top

## Schema Document Properties

Target Namespace | ecogrid://ecoinformatics.org/ecogrid-resultset-1.0.0alpha1
Element and Attribute Namespaces | Global element and attribute declarations belong to this schema's target namespace. By default, local element declarations have no namespace. By default, local attribute declarations have no namespace.
Documentation | '$RCSfile: resultset.htm,v $' Copyright: 2003 Partnership for Biodiversity Informatics Project: http://seek.ecoinformatics.org/ '$Author: vieglais $' '$Date: 2003-05-10 19:08:01 $' '$Revision: 1.1 $' This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

### Declared Namespaces

Prefix | Namespace
--- | ---
Default namespace | ecogrid://ecoinformatics.org/ecogrid-resultset-1.0.0alpha1
xml | http://www.w3.org/XML/1998/namespace
xs | http://www.w3.org/2001/XMLSchema
r | ecogrid://ecoinformatics.org/ecogrid-resultset-1.0.0alpha1

Schema Component Representation
<xs:schema targetNamespace="ecogrid://ecoinformatics.org/ecogrid-resultset-1.0.0alpha1"> ... </xs:schema>

top

## Global Declarations

### Element: resultset

Name | resultset
Type | Locally-defined complex type
Nillable | no
Abstract | no

XML Instance Representation
<resultset resultsetId="xs:string [1]" system="xs:anyURI [1]"> <resultsetMetadata> [0..1] <sendTime> xs:dateTime </sendTime> [1] <recordCount> xs:long </recordCount> [1] </resultsetMetadata> <records startRecord="xs:long [1]" endRecord="xs:long [1]"> [0..1] <record> AnyRecordType </record> [0..*] </records> </resultset>

Schema Component Representation
<xs:element name="resultset"> <xs:complexType> <xs:sequence> <xs:element name="resultsetMetadata" minOccurs="0" maxOccurs="1"> <xs:complexType> <xs:sequence> <xs:element name="sendTime" type="xs:dateTime" minOccurs="1"/> <xs:element name="recordCount" type="xs:long" minOccurs="1"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="records" minOccurs="0" maxOccurs="1"> <xs:complexType> <xs:sequence> <xs:element name="record" type="AnyRecordType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="startRecord" type="xs:long" use="required"/> <xs:attribute name="endRecord" type="xs:long" use="required"/> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="resultsetId" type="xs:string" use="required"/> <xs:attribute name="system" type="xs:anyURI" use="required"/> </xs:complexType> </xs:element>

top

## Global Definitions

### Complex Type: AnyRecordType

Super-types: | xs:anyType < AnyRecordType (by restriction)
Sub-types: | None

Name | AnyRecordType
Abstract | no

XML Instance Representation
<... number="xs:long [1]" identifier="xs:string [1]"> <!-- 'xs:anyType' super type was not found in this schema. Some elements and attributes may be missing. --> Allow any elements from any namespace (lax validation). [0..*] </...>

Schema Component Representation
<xs:complexType name="AnyRecordType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="number" type="xs:long" use="required"/> <xs:attribute name="identifier" type="xs:string" use="required"/> </xs:restriction> </xs:complexContent> </xs:complexType>

top

## Legend

Complex Type: | AusAddress
Schema Component Type | Schema Component Name

Super-types: | Address < AusAddress (by extension)
Sub-types: | QLDAddress (by restriction)

If this schema component is a type definition, its type hierarchy is shown in a gray-bordered box.

Name | AusAddress
Abstract | no

The table above displays the properties of this schema component.

XML Instance Representation
<... country="Australia" > <unitNo> string </unitNo> [0..1] <houseNo> string </houseNo> [1] <street> string </street> [1] Start Choice [1] <city> string </city> [1] <town> string </town> [1] End Choice <state> AusStates </state> [1] <postcode> string <<pattern = [1-9][0-9]{3}>> </postcode> [1] ? </...>

The XML Instance Representation table above shows the schema component's content as an XML instance.

- The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
- Model group information are shown in gray, e.g. Start Choice ... End Choice.
- For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
- If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
- Otherwise, the type of the element/attribute is displayed.
  - If the element/attribute's type is in the schema, a link is provided to it.
  - For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
- If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.

Schema Component Representation
<complexType name="AusAddress"> <complexContent> <extension base="Address"> <sequence> <element name="state" type="AusStates"/> <element name="postcode"> <simpleType> <restriction base="string"> <pattern value="[1-9][0-9]{3}"/> </restriction> </simpleType> </element> </sequence> <attribute name="country" type="string" fixed="Australia"/> </extension> </complexContent> </complexType>

The Schema Component Representation table above displays the underlying XML representation of the schema component. (Annotations are not shown.)
top

## Glossary

Abstract (Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.

All Model Group Child elements can be provided in any order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-all.

Choice Model Group Only one from the list of child elements and model groups can be provided in instances. See: http://www.w3.org/TR/xmlschema-1/#element-choice.

Collapse Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.

Disallowed Substitutions (Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an `xsi:type` attribute.

Key Constraint Like Uniqueness Constraint, but additionally requires that the specified value(s) must be provided. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

Key Reference Constraint Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

Model Group Groups together element content, specifying the order in which the element content can occur and the number of times the group of element content may be repeated. See: http://www.w3.org/TR/xmlschema-1/#Model_Groups.

Nillable (Applies to element declarations). If an element declaration is nillable, instances can use the `xsi:nil` attribute. The `xsi:nil` attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an `xsi:nil` attribute set to true, it can be left empty, even though its element declaration may have required content.

Notation A notation is used to identify the format of a piece of data. Values of elements and attributes that are of type, NOTATION, must come from the names of declared notations. See: http://www.w3.org/TR/xmlschema-1/#cNotation_Declarations.

Preserve Whitespace Policy Preserve whitespaces exactly as they appear in instances.

Prohibited Derivations (Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.

Prohibited Substitutions (Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.

Replace Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32).

Sequence Model Group Child elements and model groups must be provided in the specified order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-sequence.

Substitution Group Elements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.

Substitution Group Exclusions (Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.

Target Namespace The target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.

Uniqueness Constraint Ensures uniqueness of an element/attribute value, or a combination of values, within a specified scope. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

top

Generated by xs3p. Last modified: