Documentation for XCEDE2 - xcede-2.0-core.xsd

# Documentation for XCEDE2

## Table of Contents

- Schema Document Properties
- Global Declarations
  - Element: XCEDE
- Global Definitions
  - Attribute Group: ID_name_description
  - Attribute Group: acquisitionExternalIDs_ag
  - Attribute Group: allLevelExternalIDs_ag
  - Attribute Group: authoredText_ag
  - Attribute Group: episodeExternalIDs_ag
  - Attribute Group: levelRef_ag
  - Attribute Group: studyExternalIDs_ag
  - Attribute Group: terminology_ag
  - Attribute Group: visitExternalIDs_ag
  - Complex Type: abstract_annotation_t
  - Complex Type: abstract_container_t
  - Complex Type: abstract_data_t
  - Complex Type: abstract_entity_t
  - Complex Type: abstract_geometry_t
  - Complex Type: abstract_info_t
  - Complex Type: abstract_protocol_t
  - Complex Type: abstract_tagged_entity_t
  - Complex Type: acquisitionInfo_t
  - Complex Type: acquisition_t
  - Complex Type: analysisRef_t
  - Complex Type: analysis_t
  - Complex Type: anatomicalEntity_t
  - Complex Type: argumentsType_t
  - Complex Type: assessmentDescItem_t
  - Complex Type: assessmentInfo_t
  - Complex Type: assessmentItem_t
  - Complex Type: assessment_t
  - Complex Type: atlasEntity_t
  - Complex Type: authoredText_t
  - Complex Type: binaryDataDimension_t
  - Complex Type: binaryDataResource_t
  - Complex Type: catalog_t
  - Complex Type: dataResource_t
  - Complex Type: dcResource_t
  - Complex Type: dimensionedBinaryDataResource_t
  - Complex Type: episodeInfo_t
  - Complex Type: episode_t
  - Complex Type: eventParams_t
  - Complex Type: eventValue_t
  - Complex Type: event_t
  - Complex Type: events_t
  - Complex Type: format_t
  - Complex Type: frag_uri_t
  - Complex Type: generator_t
  - Complex Type: informationResource_t
  - Complex Type: mappedBinaryDataDimension_t
  - Complex Type: mappedBinaryDataResource_t
  - Complex Type: measurementGroup_t
  - Complex Type: metadataList_t
  - Complex Type: nameValue_t
  - Complex Type: nomenclature_t
  - Complex Type: nsOntologyAnnotation_t
  - Complex Type: nsTermAnnotation_t
  - Complex Type: observation_t
  - Complex Type: orderedString_t
  - Complex Type: person_t
  - Complex Type: processStep_t
  - Complex Type: projectInfo_t
  - Complex Type: project_t
  - Complex Type: protocolItemChoice_t
  - Complex Type: protocolItemRange_t
  - Complex Type: protocolItem_t
  - Complex Type: protocolOffset_t
  - Complex Type: protocol_t
  - Complex Type: provenance_t
  - Complex Type: ref_t
  - Complex Type: resource_t
  - Complex Type: revision_t
  - Complex Type: studyInfo_t
  - Complex Type: study_t
  - Complex Type: subjectGroup_t
  - Complex Type: subjectInfo_t
  - Complex Type: subject_t
  - Complex Type: terminologyString_t
  - Complex Type: textAnnotation_t
  - Complex Type: unitString_t
  - Complex Type: value_t
  - Complex Type: versionedEntity_t
  - Complex Type: versionedProgramEntity_t
  - Complex Type: visitInfo_t
  - Complex Type: visit_t
  - Simple Type: laterality_t
  - Simple Type: levelDescriptor_t
  - Simple Type: listoffloats_t
  - Simple Type: tissueType_t
  - Simple Type: valueTypes_t

- Legend

- Glossary

top

## Schema Document Properties

Target Namespace | http://www.xcede.org/xcede-2
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.
Documentation | The XCEDE schema provides an extensive metadata hierarchy for describing and documenting research and clinical studies. The schema organizes information into five general hierarchical levels: a complete project; studies within a project; subjects involved in the studies; visits for each of the subjects; the full description of the subject's participation during each visit Each of these sub-schemas is composed of information relevant to that aspect of an experiment and can be stored in separate XML files or spliced into one large file allowing for the XML data to be stored in a hierarchical directory structure along with the primary data. Each sub-schema also allows for the storage of data provenance information allowing for a traceable record of processing and/or changes to the underlying data. Additionally, the sub-schemas contain support for derived statistical data in the form of human imaging activation maps and simple statistical value lists. XCEDE was originally designed in the context of neuroimaging studies and complements the Biomedical Informatics Research Network (BIRN) Human Imaging Database, an extensible database and intuitive web-based user interface for the management, discovery, retrieval, and analysis of clinical and brain imaging data. This close coupling allows for an interchangeable source-sink relationship between the database and the XML files, which can be used for the import/export of data to/from the database, the standardized transport and interchange of experimental data, the local storage of experimental information within data collections, and human and machine readable description of the actual data. ********* Protocol types ********* ********* Assessment types ********* ********* Analysis types ********* ********* Terminology types ********* ********* Misc. types *********

### Declared Namespaces

Prefix | Namespace
--- | ---
Default namespace | http://www.xcede.org/xcede-2
xml | http://www.w3.org/XML/1998/namespace
xs | http://www.w3.org/2001/XMLSchema
sch | http://purl.oclc.org/dsdl/schematron
gml | http://www.opengis.net/gml

Schema Component Representation
<xs:schema targetNamespace="http://www.xcede.org/xcede-2" elementFormDefault="qualified" attributeFormDefault="unqualified">
...
</xs:schema>
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.

- 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