Schema for the XML headers of the SDM Binary Data Format (vers. 0.94)

Table of Contents

top

Schema Document Properties

Target Namespace None
Version 0.9
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 This schema is intended for XML headers of the binary data originating from a correlator, baseband square-law detectors etc... A BLOB (implemented as a MIME document) is composed of a primary XML header followed by a sequence which is a set of subsets, a subset being composed of a secondary XML header and binary attachments. Typically, for the data originating from a correlator, a subset corresponds to a data-dump which is a single integration or sub-integration. The primary header provides all the informations necessary to determine the data structure. This header has an outbound link to the parent SDM dataset, the URI of the execblock (i.e. the URI of the SDM.xml document of the dataset) and it is specified following the XLink w3C recommendation (version 1.1, work in progress; note that with this version xlink:type="simple" is not mandatory). The binary attachments are for the data (visibilities, auto-correlations), metadata data and auxiliary data, all these having their own tree structures. There is no constraint on the order for these binary attachments, each having its content identifier. The main header gives all the attributes necessary to determine the positions of nodes in these tree structures. The secondary headers, entry points to access specific fragments, contain a reference to the main header and a set of references to the binary attachements. The Content-ID of these secondary headers is uniquely identified using the project path. They also contain time informations.
The present schema defines the structures for the primary XML header and the secondary headers. If these are extracted from the MIME message and recomposed in a single XML document, this assembly has a base-element named sdmDataObject which must conform to the present schema.
Note that the data format with version number higher that 0.93 is much less constrained compared to earlier versions. This is intended to be not telescope specific. To achieve this all the "factorizations" at the baseband level have been removed. The list of "axes" is now explicit for every type of binary data. An other new feature is the introduction of seven enumerations. With this version there are now types qualified not only by the CorrelationMode but also the SpectralResolution. An other new feature with this version is the introduction of type-hierarchies to make element names correltion-mode independent. This implies typing at the instance level.

Declared Namespaces

Prefix Namespace
xml http://www.w3.org/XML/1998/namespace
xs http://www.w3.org/2001/XMLSchema
xhtml http://www.w3.org/1999/xhtml
xlink http://www.w3.org/1999/xlink
Schema Component Representation
<xs:schema elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.9">
<xs:import namespace="http://www.w3.org/1999/xlink" schemaLocation="xlink_1.1.xsd"/>
<xs:include schemaLocation="AtmPhaseCorrection.xsd"/>
<xs:include schemaLocation="PrimitiveDataType.xsd"/>
<xs:include schemaLocation="AxisName.xsd"/>
<xs:include schemaLocation="BasebandName.xsd"/>
<xs:include schemaLocation="CorrelationMode.xsd"/>
<xs:include schemaLocation="SpectralResolution.xsd"/>
<xs:include schemaLocation="StokesParameter.xsd"/>
...
</xs:schema>
top