Documentation for OME Schemas

Table of Contents

Master schema documentation file: ome.xsd.html

top

Schema Document Properties

Target Namespace http://www.openmicroscopy.org/Schemas/BinaryFile/2008-09
Version 1
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
Documentation The elements in this file are not yet represented by classes in the EA diagrams - ajp

Declared Namespaces

Prefix Namespace
xml http://www.w3.org/XML/1998/namespace
Bin http://www.openmicroscopy.org/Schemas/BinaryFile/2008-09
xsd http://www.w3.org/2001/XMLSchema
Schema Component Representation
<xsd:schema targetNamespace="http://www.openmicroscopy.org/Schemas/BinaryFile/2008-09" version="1" elementFormDefault="qualified">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>
...
</xsd:schema>
top

Global Declarations

Element: BinData

Name BinData
Used by (from the same schema document) Element BinaryFile
Type Locally-defined complex type
Nillable no
Abstract no
Documentation The contents of this element are base64-encoded. These are not CDATA sections, just a base64 stream.
Logical Diagram
XML Instance Representation
<Bin:BinData
Compression=" xsd:string (value comes from list: {'zlib'|'bzip2'|'none'}) [0..1]

'Specifies the compression scheme used to encode the data.'

"

Length=" xsd:nonNegativeInteger [1]

'Character count attribute for the BinData field. This is the length of the base-64 encoded block. It allows easy skipping of the block when parsing the file. Added in response to Evolution document - ajp'

"
>
xsd:base64Binary
</Bin:BinData>
Diagram
Schema Component Representation
<xsd:element name="BinData">
<-- top level definition -->
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base=" xsd:base64Binary ">
<xsd:attribute name="Compression" default="none" use="optional">
<xsd:simpleType>
<xsd:restriction base=" xsd:string ">
<xsd:enumeration value="zlib"/>
<xsd:enumeration value="bzip2"/>
<xsd:enumeration value="none"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="Length" use="required">
<xsd:simpleType>
<xsd:restriction base=" xsd:nonNegativeInteger "/>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
top

Element: BinaryFile

Name BinaryFile
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Describes a binary file.
Logical Diagram
element_External element_BinData
XML Instance Representation
<Bin:BinaryFile
FileName=" xsd:string (length <= 64) [1]"
Size=" xsd:integer [1]

'Size (in bytes) of the uncompressed file.'

"
>
Start Choice [1]
<Bin:External> ... </Bin:External> [1]
<Bin:BinData> ... </Bin:BinData> [1]
End Choice
</Bin:BinaryFile>
Diagram
element_External element_BinData
Schema Component Representation
<xsd:element name="BinaryFile">
<-- top level definition -->
<xsd:complexType>
<xsd:choice minOccurs="1" maxOccurs="1">
<xsd:element ref=" Bin:External " minOccurs="1" maxOccurs="1"/>
<xsd:element ref=" Bin:BinData " minOccurs="1" maxOccurs="1"/>
</xsd:choice>
<xsd:attribute name="FileName" use="required">
<xsd:simpleType>
<xsd:restriction base=" xsd:string ">
<xsd:maxLength value="64"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="Size" type=" xsd:integer " use="required"/>
</xsd:complexType>
</xsd:element>
top

Element: External

Name External
Used by (from the same schema document) Element BinaryFile
Type Locally-defined complex type
Nillable no
Abstract no
Documentation Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file.
Logical Diagram
XML Instance Representation
<Bin:External
href=" xsd:anyURI [1]

'file location'

"

SHA1=" Bin:Hex40 [1]

'The digest of the file specified in href.'

"

Compression=" xsd:string (value comes from list: {'zlib'|'bzip2'|'none'}) [0..1]

'Specifies the compression scheme used to encode the data.'

"
/>
Diagram
type_Hex40
Schema Component Representation
<xsd:element name="External">
<-- top level definition -->
<xsd:complexType>
<xsd:attribute name="href" type=" xsd:anyURI " use="required"/>
<xsd:attribute name="SHA1" type=" Bin:Hex40 " use="required"/>
<xsd:attribute name="Compression" default="none" use="optional">
<xsd:simpleType>
<xsd:restriction base=" xsd:string ">
<xsd:enumeration value="zlib"/>
<xsd:enumeration value="bzip2"/>
<xsd:enumeration value="none"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
top

Global Definitions

Simple Type: Hex40

Super-types: xsd:hexBinary < Hex40 (by restriction)
Sub-types: None
Name Hex40
Used by (from the same schema document) Element External
Content
  • Base XSD Type: hexBinary
  • length = 20
Diagram
Schema Component Representation
<xsd:simpleType name="Hex40">
<xsd:restriction base=" xsd:hexBinary ">
<xsd:length value="20"/>
</xsd:restriction>
</xsd: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