XML Schema Documentation

Table of Contents

Master schema documentation file: ome.xsd.html

top

Schema Document Properties

Target Namespace http://www.openmicroscopy.org/XMLschemas/AnalysisModule/RC1/AnalysisModule.xsd
Version RC1
Element and Attribute Namespaces
  • Global element and attribute declarations belong to this schema's target namespace.
  • By default, local element declarations belong to this schema's target namespace.
  • By default, local attribute declarations have no namespace.
Schema Composition

Declared Namespaces

Prefix Namespace
Default namespace http://www.w3.org/2001/XMLSchema
xml http://www.w3.org/XML/1998/namespace
AML http://www.openmicroscopy.org/XMLschemas/AnalysisModule/RC1/AnalysisModule.xsd
CLI http://www.openmicroscopy.org/XMLschemas/CLI/RC1/CLI.xsd
Bin http://www.openmicroscopy.org/XMLschemas/BinaryFile/RC1/BinaryFile.xsd
MLI http://www.openmicroscopy.org/XMLschemas/MLI/IR2/MLI.xsd
xsd http://www.w3.org/2001/XMLSchema
Schema Component Representation
<schema targetNamespace="http://www.openmicroscopy.org/XMLschemas/AnalysisModule/RC1/AnalysisModule.xsd" version="RC1" elementFormDefault="qualified">
<import namespace="http://www.openmicroscopy.org/XMLschemas/CLI/RC1/CLI.xsd" schemaLocation="http://www.openmicroscopy.org/XMLschemas/CLI/RC1/CLI.xsd"/>
<import namespace="http://www.openmicroscopy.org/XMLschemas/BinaryFile/RC1/BinaryFile.xsd" schemaLocation="http://www.openmicroscopy.org/XMLschemas/BinaryFile/RC1/BinaryFile.xsd"/>
<import namespace="http://www.openmicroscopy.org/XMLschemas/MLI/IR2/MLI.xsd" schemaLocation="http://www.openmicroscopy.org/XMLschemas/MLI/IR2/MLI.xsd"/>
<import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>
...
</schema>
top

Global Declarations

Element: AnalysisModule

Name AnalysisModule
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Describes an interface to use with a program.
Logical Diagram
element_Description element_Declaration
XML Instance Representation
<AML:AnalysisModule
isStreamAlgorithm="boolean [0..1]

'This is a stub for future development. The database location doesn\'t even exist yet. If the output of the analysis will be the same when pixel positions are scrambled, the analysis is a stream algorithm. Examples of stream algorithms are: A statistics module that produces mean, geometric mean, standard deviation, etc. for pixel intensities. A module to cross correlate pixel intensities across wavelengths. Example of an algorithms that is not a stream algorithm is: FindSpots. (It\'s a module to find blobs in an image.) If a module is a stream algorithm, it can function across the x, y, z, and time dimensions. Tied to DB. Table PROGRAMS Column IS_STREAM_ALGORITHM'

"
ModuleType=" string (pattern = OME::Analysis::.+) [1]

'As more handlers, are added, this part of the schema needs to be changed Tied to DB. Table PROGRAMS Column MODULE_TYPE'

"
FeatureIterator=" string (length <= 128) [0..1]

'If the module iterates over a feature, specify the iterator here. It will reference a feature via the TAG column of the FEATURES table. An example of a module that does not iterate over a feature is Find Cells. It examines one image at a time, hence it iterates over an image, not a feature. It produces zero or more features (Çell) per image. These Cell features belong to an image. This module would not get a FeatureIterator attribute. An example of a module that iterates over a feature is Find Golgi. It examines one CELL at a time. A cell is a feature, hence the module iterates over features, not images or datasets. It produces zero or more Golgi features per Cell feature. These Golgi features belong to a Cell feature. This module would get a FeatureIterator attribute of \"CELL\". Tied to DB. Table PROGRAMS Column DEFAULT_ITERATOR'

"
NewFeatureName=" string (length <= 128) [0..1]

'If this module makes new features, then the new Feature\'s name needs to be specified here. If the module does not make new features, do not specify a value for this attribute. Tied to DB. PROGRAMS.NEW_FEATURE_TAG'

"
Category=" string (length <= 32) [0..1]

'References a Category.'

"
ProgramID="string [1]

'Eventually will refer to a program. Currently program installation is NOT implemented. So this value is the path to the installed binary file.'

"
ModuleName=" string (length <= 64) [0..1]"
ID=" AML:ModuleID [1]">
<!--
Uniqueness Constraint - FormalInput
Selector - AML:Declaration/AML:FormalInput
Field(s) - @Name
-->
<!--
Uniqueness Constraint - FormalOutput
Selector - AML:Declaration/AML:FormalOutput
Field(s) - @Name
-->

<AML:Description> ... </AML:Description> [0..1]
<AML:Declaration> ... </AML:Declaration> [1]
Start Choice [0..1]
<CLI:ExecutionInstructions> ... </CLI:ExecutionInstructions> [1]
<MLI:ExecutionInstructions> ... </MLI:ExecutionInstructions> [1]
End Choice
</AML:AnalysisModule>
Diagram
element_Description element_Declaration element_ExecutionInstructions element_ExecutionInstructions type_ModuleID
Schema Component Representation
<element name="AnalysisModule">
<complexType>
<sequence>
<element ref=" AML:Description " minOccurs="0"/>
<element ref=" AML:Declaration "/>
<choice minOccurs="0">
<element ref=" CLI:ExecutionInstructions "/>
<element ref=" MLI:ExecutionInstructions "/>
</choice>
</sequence>
<attribute name="isStreamAlgorithm" type=" boolean " default="false"/>
<attribute name="ModuleType" use="required">
<simpleType>
<restriction base=" string ">
<pattern value="OME::Analysis::.+"/>
</restriction>
</simpleType>
</attribute>
<attribute name="FeatureIterator">
<simpleType>
<restriction base=" string ">
<maxLength value="128"/>
</restriction>
</simpleType>
</attribute>
<attribute name="NewFeatureName">
<simpleType>
<restriction base=" string ">
<maxLength value="128"/>
</restriction>
</simpleType>
</attribute>
<attribute name="Category">
<simpleType>
<restriction base=" string ">
<maxLength value="32"/>
</restriction>
</simpleType>
</attribute>
<attribute name="ProgramID" type=" string " use="required"/>
<attribute name="ModuleName">
<simpleType>
<restriction base=" string ">
<maxLength value="64"/>
</restriction>
</simpleType>
</attribute>
<attribute name="ID" type=" AML:ModuleID " use="required"/>
</complexType>
<unique name="FormalInput">
<selector xpath="AML:Declaration/AML:FormalInput"/>
<field xpath="@Name"/>
</unique>
<unique name="FormalOutput">
<selector xpath="AML:Declaration/AML:FormalOutput"/>
<field xpath="@Name"/>
</unique>
</element>
top

Element: AnalysisModuleLibrary

Name AnalysisModuleLibrary
Type Locally-defined complex type
Nillable no
Abstract no
Documentation An analysis module is defined by two things: 1) A program 2) An interface A single program may have multiple interfaces. Why do you need multiple interfaces? Pretend you have a program that calculates simple statistics on the pixels of an image. You can specify which statistics you want via parameters. Typing ./stats -mean -sigma image1 will ouput Image | mean | sigma image1 12.4 1 Typing ./stats -geomean -mean image1 will output Image | geomean | mean image1 12.2 12.4 The outputs are completely different. You need to specify an interface for each of these behaviors. Or pretend you have a powerful program that can do 10 unrelated tasks, each of which outputs an image. While the outputs are the same type and format, they represent 10 completely different things. In this case, it might make sense to define 10 corrosponding AnalysisModule to represent the 10 logical functions. In any case, use AnalysisModule to define an interface and Program to store installation software for a program.
Logical Diagram
element_AnalysisModule element_Category element_Program
XML Instance Representation
<AML:AnalysisModuleLibrary>
<!--
Uniqueness Constraint - AnalysisModule
Selector - AML:AnalysisModule
Field(s) - @AML:ModuleName
-->

<AML:AnalysisModule> ... </AML:AnalysisModule> [1..*]
<AML:Category> ... </AML:Category> [0..*]
<AML:Program> ... </AML:Program> [0..*]
</AML:AnalysisModuleLibrary>
Diagram
element_AnalysisModule element_Category element_Program
Schema Component Representation
<element name="AnalysisModuleLibrary">
<-- This was commented out by Josiah <siah@nih.gov> on July 3, 2003. We don't support Program installation yet, and are using the value of ProgramID in <AnalysisModule> to refer to the location of the installed program. A temporary hack to be sure, but that's the way it works for now. <keyref name = "ProgramRef" refer = "AML:Program"> <selector xpath = "AML:AnalysisModule"/> <field xpath = "@ProgramID"/> </keyref> <unique name = "Program"> <selector xpath = "AML:Program"/> <field xpath = "@ProgramID"/> </unique> -->
<complexType>
<sequence>
<element ref=" AML:AnalysisModule " maxOccurs="unbounded"/>
<element ref=" AML:Category " minOccurs="0" maxOccurs="unbounded"/>
<element ref=" AML:Program " minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<unique name="AnalysisModule">
<selector xpath="AML:AnalysisModule"/>
<field xpath="@AML:ModuleName"/>
</unique>
</element>
top

Element: Category

Name Category
Type Locally-defined complex type
Nillable no
Abstract no
Logical Diagram
element_Description
XML Instance Representation
<AML:Category
Path=" string (pattern = ^[A-Za-z0-9 ]+(\.[A-Za-z0-9 ]+)*$) [1]

'Categories are organized into heirarchical structures. This specifies the full path of this category in the following format. Path = \"GrandParent name.Parent name.Category name\" If you defined a sub category, we Strongly encourage you to also define all ancestor categories that are not part of the core OME specification.'

">
<AML:Description> ... </AML:Description> [1]
</AML:Category>
Diagram
element_Description
Schema Component Representation
<element name="Category">
<complexType>
<sequence>
<element ref=" AML:Description "/>
</sequence>
<attribute name="Path" use="required">
<simpleType>
<restriction base=" string ">
<pattern value="^[A-Za-z0-9 ]+(\.[A-Za-z0-9 ]+)*$"/>
</restriction>
</simpleType>
</attribute>
</complexType>
</element>
top

Element: Declaration

Name Declaration
Type Locally-defined complex type
Nillable no
Abstract no
Documentation States module requirements. Formal Inputs are optional because input requirements may be specified by guaranteed image attributes. For example, OME_Image_XYZ_stats requires a path to the OME repository file, and Dimensions. These are given by <RawImageFilePath>, <sizeX>, <sizeY>, <sizeZ>, <sizeT>, and <sizeW>.
Logical Diagram
element_FormalInput element_FormalOutput
XML Instance Representation
<AML:Declaration>
<AML:FormalInput> ... </AML:FormalInput> [0..*]
<AML:FormalOutput> ... </AML:FormalOutput> [0..*]
</AML:Declaration>
Diagram
element_FormalInput element_FormalOutput
Schema Component Representation
<element name="Declaration">
<complexType>
<sequence>
<element ref=" AML:FormalInput " minOccurs="0" maxOccurs="unbounded"/>
<element ref=" AML:FormalOutput " minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
</element>
top

Element: Description

Name Description
Type string
Nillable no
Abstract no
Documentation Just some free-form text to describe Images, Screens and Projects. The content model is ANY, which means that en entire XML sub-document can be placed here.
Logical Diagram
XML Instance Representation
<AML:Description> string </AML:Description>
Diagram
Schema Component Representation
<element name="Description" type=" string "/>
top

Element: Entry

Name Entry
Type Locally-defined complex type
Nillable no
Abstract no
Logical Diagram
XML Instance Representation
<AML:Entry
Value=" string (length <= 256) [1]

'Tied to DB. LOOKUP_TABLE_ENTRIES.VALUE'

"
Label=" string (length <= 256) [0..1]

'Tied to DB. LOOKUP_TABLE_ENTRIES.LABEL'

"/>
Diagram
Schema Component Representation
<element name="Entry">
<complexType>
<attribute name="Value" use="required">
<simpleType>
<restriction base=" string ">
<maxLength value="256"/>
</restriction>
</simpleType>
</attribute>
<attribute name="Label">
<simpleType>
<restriction base=" string ">
<maxLength value="256"/>
</restriction>
</simpleType>
</attribute>
</complexType>
</element>
top

Element: FormalInput

Name FormalInput
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Specifies an input requirement for a module. Image dimensions and image file locations (repository or other format) should not be specified with this. Image dimensions are intrisic to an image. They do not represent a special requirement. Image file locations and contents are specified by other elements. Specifically, RawImageFile, RawImageFilePath, XYPlaneFile, and XYPlaneFilePath.
Logical Diagram
element_LookupTable element_Description
XML Instance Representation
<AML:FormalInput
UserDefined="boolean [0..1]

'OME interprets this as a recommendation rather than a requirement. Tied to DB. Table FORMAL_INPUTS Column USER_DEFINED'

"
Count=" string (value comes from list: {'!'|'?'|'+'|'*'}) [0..1]

'Specifies how many counts of this formal input are expected. Meanings are specified below ! = exactly one ? = zero or one + = one or more * = zero or more'

"
Name=" string (pattern = [A-Za-z0-9\-\^\(\)_ ]+) [1]

'Valid characters are alphanumeric and spaces.'

"
SemanticTypeName="string [1]">
<AML:LookupTable> ... </AML:LookupTable> [0..1]
<AML:Description> ... </AML:Description> [0..1]
</AML:FormalInput>
Diagram
element_LookupTable element_Description
Schema Component Representation
<element name="FormalInput">
<complexType>
<sequence>
<element ref=" AML:LookupTable " minOccurs="0"/>
<element ref=" AML:Description " minOccurs="0"/>
</sequence>
<attribute name="UserDefined" type=" boolean " default="false"/>
<attribute name="Count" default="+">
<simpleType>
<restriction base=" string ">
<enumeration value="!"/>
<enumeration value="?"/>
<enumeration value="+"/>
<enumeration value="*"/>
</restriction>
</simpleType>
</attribute>
<attribute name="Name" use="required">
<simpleType>
<restriction base=" string ">
<pattern value="[A-Za-z0-9\-\^\(\)_ ]+"/>
</restriction>
</simpleType>
</attribute>
<attribute name="SemanticTypeName" type=" string " use="required"/>
</complexType>
</element>
top

Element: FormalOutput

Name FormalOutput
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Specifies an output element of a module.
Logical Diagram
element_Description
XML Instance Representation
<AML:FormalOutput
IBelongTo=" string (value comes from list: {'[Feature]'|'[Iterator]'}) [0..1]

'Concerning MakeNewFeature attribute of ExecutionInstructions, if a new feature type is made, then there are two possible places a formal output attribute can be stored: It can be stored as an attribute of the FeatureIterator, or it can be stored as an attribute of the new Feature. This tag is supposed to specify which. Can be left blank if module does not make new iterator. Tied to DB. FORMAL_OUTPUTS.FEATURE_TAG Processed before storage to DB'

"
Count=" string (value comes from list: {'!'|'?'|'+'|'*'}) [0..1]

'Specifies how many counts of this formal output will be produced. Meanings are specified below ! = exactly one ? = zero or one + = one or more * = zero or more'

"
Name=" string (pattern = [A-Za-z0-9\-\^\(\)_ ]+) [1]"
SemanticTypeName="string [0..1]

'THIS IS REQUIRED for every formal output outside of the importer. The importer doesn\'t know what it will run into before it executes, so it can\'t declare the semantic type of its outputs. If you are writing a module, I HIGHLY HIGHLY recommend that you type your formal outputs.'

">
<AML:Description> ... </AML:Description> [0..1]
</AML:FormalOutput>
Diagram
element_Description
Schema Component Representation
<element name="FormalOutput">
<complexType>
<sequence>
<element ref=" AML:Description " minOccurs="0"/>
</sequence>
<attribute name="IBelongTo">
<simpleType>
<restriction base=" string ">
<enumeration value="[Feature]"/>
<enumeration value="[Iterator]"/>
</restriction>
</simpleType>
</attribute>
<attribute name="Count" default="+">
<simpleType>
<restriction base=" string ">
<enumeration value="!"/>
<enumeration value="?"/>
<enumeration value="+"/>
<enumeration value="*"/>
</restriction>
</simpleType>
</attribute>
<attribute name="Name" use="required">
<simpleType>
<restriction base=" string ">
<pattern value="[A-Za-z0-9\-\^\(\)_ ]+"/>
</restriction>
</simpleType>
</attribute>
<attribute name="SemanticTypeName" type=" string "/>
</complexType>
</element>
top

Element: InstallationFile

Name InstallationFile
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Contains a packaged or zipped installation files (binaries or source code).
Logical Diagram
element_BinaryFile
XML Instance Representation
<AML:InstallationFile
Format="string [0..1]

'This is a stub for future development. Don\'t bother with it unless you know more about it. Specifies the packaging and/or compression format of the Installation file.'

">
<Bin:BinaryFile> ... </Bin:BinaryFile> [1]
</AML:InstallationFile>
Diagram
element_BinaryFile
Schema Component Representation
<element name="InstallationFile">
<complexType>
<sequence>
<element ref=" Bin:BinaryFile "/>
</sequence>
<attribute name="Format" type=" string "/>
</complexType>
</element>
top

Element: InstallationScript

Name InstallationScript
Type Locally-defined complex type
Nillable no
Abstract no
Documentation The script should interface with the OME API to find all information it needs. (i.e. installation path) It also needs to set the location of the program after the program is installed. The location should be set through the API, but it will propogate to the LOCATION column of the PROGRAMS table.
Logical Diagram
element_BinaryFile
XML Instance Representation
<AML:InstallationScript>
<Bin:BinaryFile> ... </Bin:BinaryFile> [1]
</AML:InstallationScript>
Diagram
element_BinaryFile
Schema Component Representation
<element name="InstallationScript">
<complexType>
<sequence>
<element ref=" Bin:BinaryFile "/>
</sequence>
</complexType>
</element>
top

Element: Installed

Name Installed
Type Locally-defined complex type
Nillable no
Abstract no
Logical Diagram
XML Instance Representation
<AML:Installed
location="string [1]"/>
Diagram
Schema Component Representation
<element name="Installed">
<complexType>
<attribute name="location" type=" string " use="required"/>
</complexType>
</element>
top

Element: LookupTable

Name LookupTable
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Describes valid values for an input. Think enumerations, (a list of valid values).
Logical Diagram
element_Entry element_Description
XML Instance Representation
<AML:LookupTable
Name=" string (length <= 64) [1]

'Tied to DB. LOOKUP_TABLES.NAME'

">
<AML:Entry> ... </AML:Entry> [1..*]
<AML:Description> ... </AML:Description> [0..1]
</AML:LookupTable>
Diagram
element_Entry element_Description
Schema Component Representation
<element name="LookupTable">
<complexType>
<sequence>
<element ref=" AML:Entry " maxOccurs="unbounded"/>
<element ref=" AML:Description " minOccurs="0"/>
</sequence>
<attribute name="Name" use="required">
<simpleType>
<restriction base=" string ">
<maxLength value="64"/>
</restriction>
</simpleType>
</attribute>
</complexType>
</element>
top

Element: Program

Name Program
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Stores an installation package and installation script for a program. This currently is NOT implemented.
Logical Diagram
element_Installed
XML Instance Representation
<AML:Program
Name=" string (length <= 64) [0..1]

'Program name. Unclear how this would be used. DB location PROGRAMS.PROGRAM_NAME is populated by XML attribute AnalysisModule.Name.'

"
Version="string [0..1]

'Currently unused'

"
ProgramID="string [1]">
Start Choice [1]
<AML:InstallationScript> ... </AML:InstallationScript> [1]
<AML:InstallationFile> ... </AML:InstallationFile> [1]
<AML:Installed> ... </AML:Installed> [1]
End Choice
</AML:Program>
Diagram
element_InstallationScript element_InstallationFile element_Installed
Schema Component Representation
<element name="Program">
<complexType>
<choice>
<sequence>
<element ref=" AML:InstallationScript "/>
<element ref=" AML:InstallationFile "/>
</sequence>
<element ref=" AML:Installed "/>
</choice>
<attribute name="Name">
<simpleType>
<restriction base=" string ">
<maxLength value="64"/>
</restriction>
</simpleType>
</attribute>
<attribute name="Version" type=" string "/>
<attribute name="ProgramID" type=" string " use="required"/>
</complexType>
</element>
top

Global Definitions

Simple Type: Hex40

Super-types: hexBinary < Hex40 (by restriction)
Sub-types: None
Name Hex40
Content
  • Base XSD Type: hexBinary
  • length = 20
Diagram
Schema Component Representation
<simpleType name="Hex40">
<restriction base=" hexBinary ">
<length value="20"/>
</restriction>
</simpleType>
top

Simple Type: LSID

Super-types: string < LSID (by restriction)
Sub-types:
Name LSID
Content
  • Base XSD Type: string
  • pattern = (urn:lsid:)?(\S+\.\S+)+(:\S+)(:\S+)
Diagram
Schema Component Representation
<simpleType name="LSID">
<restriction base=" string ">
<pattern value="(urn:lsid:)?(\S+\.\S+)+(:\S+)(:\S+)"/>
</restriction>
</simpleType>
top

Simple Type: ModuleID

Super-types: string < LSID (by restriction) < ModuleID (by restriction)
Sub-types: None
Name ModuleID
Content
  • Base XSD Type: string
  • pattern = (urn:lsid:)?(\S+\.\S+)+(:\S+)(:\S+)
  • pattern = (urn:lsid:)?(\S+\.\S+)+(:Module)(:\S+)
Diagram
Schema Component Representation
<simpleType name="ModuleID">
<restriction base=" AML:LSID ">
<pattern value="(urn:lsid:)?(\S+\.\S+)+(:Module)(:\S+)"/>
</restriction>
</simpleType>
top

Legend

Complex Type:

Schema Component Type

AusAddress

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.

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 <oXygen/> XML Editor using a modified version of xs3p that adds schema diagrams and chunking support. Last modified: