Documentation for XCEDE2 - xcede-2.0-core.xsd - Complex Type mappedBinaryDataResource_t

# Documentation for XCEDE2

### Complex Type: mappedBinaryDataResource_t

#### [Table of contents]

Super-types: | abstract_tagged_entity_t < resource_t (by extension) < dataResource_t (by extension) < binaryDataResource_t (by extension) < mappedBinaryDataResource_t (by extension)
Sub-types: | None

Name | mappedBinaryDataResource_t
Abstract | no
Documentation | This type places the multi-dimensional data array (say a 3-dimensional cube) into a coordinate space (say MR scanner coordinates).

XML Instance Representation
<...
ID=" xs:string [0..1]"
name=" xs:string [0..1]"
description=" xs:string [0..1]"
level=" levelDescriptor_t [0..1]"
projectID=" xs:string [0..1]

'The content of this attribute should match the ID attribute of the project_t to which this element is associated.'

"
projectURI=" xs:string [0..1]

'This is the location of a document where to find an element matching the projectID (see projectID attribute).'

"
subjectID=" xs:string [0..1]

'The content of this attribute should match the ID attribute of the subject_t to which this element is associated.'

"
subjectURI=" xs:string [0..1]

'This is the location of a document where to find an element matching the subjectID (see subjectID attribute).'

"
subjectGroupID=" xs:string [0..1]

'content of this attribute should match the ID of one of the subject groups listed in the project_t associated with this element (see projectID and project_t).'

"
visitID=" xs:string [0..1]

'The content of this attribute should match the ID attribute of the visit_t to which this element is associated.'

"
visitURI=" xs:string [0..1]

'This is the location of a document where to find an element matching the visitID (see visitID attribute).'

"
studyID=" xs:string [0..1]

'The content of this attribute should match the ID attribute of the study_t to which this element is associated.'

"
studyURI=" xs:string [0..1]

'This is the location of a document where to find an element matching the studyID (see studyID attribute).'

"
episodeID=" xs:string [0..1]

'The content of this attribute should match the ID attribute of the episode_t to which this element is associated.'

"
episodeURI=" xs:string [0..1]

'This is the location of a document where to find an element matching the episodeID (see episodeID attribute).'

"
acquisitionID=" xs:string [0..1]

'The content of this attribute should match the ID attribute of the acquisition_t to which this element is associated.'

"
acquisitionURI=" xs:string [0..1]

'This is the location of a document where to find an element matching the acquisitionID (see acquisitionID attribute).'

"
format=" xs:string [0..1]

'Format of file. E.g. DICOM, Analyze, 4dfp'

"
content=" xs:string [0..1]

'Code indicating the contents of the image. E.g. GFC, T88'

"
cachePath=" xs:string (length <= 255) [0..1]">
<metaFields> [0..1]
Start Sequence [0..1]
<metaField
name=" xs:string [0..1]"> [0..*]
xs:string
</metaField>
End Sequence
</metaFields>
<uri> frag_uri_t </uri> [0..*]
<provenance> provenance_t </provenance> [0..1]
<elementType> xs:string (value comes from list: {'int8'|'uint8'|'int16'|'uint16'|'int32'|'uint32'|'int64'|'uint64'|'float32'|'float64'|'ascii'}) </elementType> [0..1]

'This element describes the type of individual data elements in the data record. For numeric data types, this indicates whether the element type is a signed integer (\"int\"), unsigned integer (\"uint\"), or floating-point (\"float\"), as well as the number of bits allocated to each element.'

<byteOrder> xs:string (value comes from list: {'lsbfirst'|'msbfirst'}) </byteOrder> [0..1]

'This element describes whether the individual data elements in the data record are stored with the most-significant-byte first (msbfirst) or least-significant-byte first (lsbfirst). This element is required if the the data type given by the \"elementtype\" element has a size larger than one byte.'

<compression> xs:string </compression> [0..1]

'If this element is present, the files pointed to by the uri elements are compressed data files. The only compression method specifically named by this specification is \"gzip\". As a special case for binaryDataResource_t and derived types, files compressed with gzip and containing a .gz suffix can be referenced in the uri element without the suffix. If a file pointed to by the URI does not exist, the application should search for the same file with the .gz suffix appended — if it exists, use that file and act as if the compression element had been specified with the value \"gzip\". This allows the referenced files to be compressed or uncompressed at will (as long as the .gz suffix is appropriately added/removed from the filename), without needing to change the URI\'s in this element.'

<dimension> mappedBinaryDataDimension_t </dimension> [1..*]
<originCoords> xs:string </originCoords> [0..1]

'This is a coordinate tuple giving the location of the first item in the data. For example, if this is an MR volume, this could be a triple giving the location in RAS coordinates of the first voxel in the data.'

</...>
Diagram
Schema Component Representation
<xs:complexType name="mappedBinaryDataResource_t">
<xs:complexContent>
<xs:extension base=" binaryDataResource_t ">
<xs:sequence>
<xs:element name="dimension" type=" mappedBinaryDataDimension_t " maxOccurs="unbounded"/>
<xs:element name="originCoords" type=" xs:string " minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>