complexType "vs:Coverage"
Namespace:
http://www.ivoa.net/xml/VODataService/v1.1
Content:
complex, 7 elements
Defined:
globally in VODataService-v1.2.xsd; see XML source
Includes:
definitions of 7 elements
Used:
never
XML Representation Summary
<...>
   
Content: 
 stc:STCResourceProfile?, spatial?, temporal*, spectral*, footprint?, waveband*, regionOfRegard?
</...>
Content Model Elements (7):
footprint (type vs:ServiceReference),
regionOfRegard (type xs:float),
spatial (type vs:SpatialCoverage),
spectral (type vs:FloatInterval),
stc:STCResourceProfile,
temporal (type vs:FloatInterval),
waveband (type xs:token)
Annotation
A description of how a resource's contents or behavior maps to the sky, to time, and to frequency space, including coverage and resolution.
XML Source (see within schema source)
<xs:complexType name="Coverage">
<xs:annotation>
<xs:documentation>
A description of how a resource's contents or behavior maps
to the sky, to time, and to frequency space, including
coverage and resolution.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" ref="stc:STCResourceProfile">
<xs:annotation>
<xs:documentation>
An STC 1.0 description of the location of the resource's
data on the sky, in time, and in frequency space,
including resolution. This is deprecated in favour
of the separate spatial, temporal, and spectral elements.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="spatial" type="vs:SpatialCoverage">
<xs:annotation>
<xs:documentation>
An ASCII-serialized MOC defining the spatial coverage
of the resource.
</xs:documentation>
<xs:documentation>
The MOC is to be understood in the ICRS reference frame
unless a frame attribute is given.
Resources should give the coverage at least to order 6
(a resolution of about one degree). The order should be
chosen so as to keep the resulting MOC smaller than a few
dozens of kB. If desired, a more precise MOC can be provided
on a dedicated endpoint declared in the footprint element.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="temporal" type="vs:FloatInterval">
<xs:annotation>
<xs:documentation>
A pair of lower, upper limits of a time interval
for which the resource offers data.
</xs:documentation>
<xs:documentation>
This is written as for VOTable tabledata (i.e.,
whitespace-separated C-style floating point literals), as
in &#8220;47847.2 51370.2&#8221;.
The limits must be given as MJD. While they
are not intended to be precise, they are to be understood
in TDB for the solar system barycenter. The total coverage
of the resource is the union of all such intervals.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="spectral" type="vs:FloatInterval">
<xs:annotation>
<xs:documentation>
A pair of lower, upper limits of a spectral interval
for which the resource offers data.
</xs:documentation>
<xs:documentation>
This is written as for VOTable tabledata (i.e.,
whitespace-separated C-style floating point literals).
The limits must be given in Joules of particle
energies. While the limits are not intended
to be precise, they are to be understood for the
solar system barycenter.
</xs:documentation>
<xs:documentation>
For instance, the Johnson V waveband (480 .. 730 nm)
would be specified as &#8220;2.72e-19 4.14e-19&#8221;
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="footprint" type="vs:ServiceReference">
<xs:annotation>
<xs:documentation>
A reference to a footprint service for retrieving
precise and up-to-date description of coverage.
</xs:documentation>
<xs:documentation>
The ivo-id attribute here refers to the standard in which
the footprint is given. The only value defined by
VODataService at this point is ivo://ivoa.net/std/moc,
which indicates that retrieving the footprint URL will return
a MOC (any IVOA-approved serialisation is legal). Note that
the ivo-id attribute was intended to have a different
function in VODataService 1.1. The current meaning is what
implementors actually adopted.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="waveband" type="xs:token">
<xs:annotation>
<xs:appinfo>
<vm:dcterm>Coverage.Spectral</vm:dcterm>
</xs:appinfo>
<xs:documentation>
A name of a messenger that the resource is relevant for
(e.g., was used in the measurements). Terms must
be taken from the vocabulary at
http://www.ivoa.net/rdf/messenger.
</xs:documentation>
<xs:documentation>
It is a bit unfortunate that the element is still called
waveband when it is now also coverage non-electromagnetic
messengers. It was deemed that this slight notional
sloppiness is preferable to introducing new and
deprecating old elements.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="regionOfRegard" type="xs:float">
<xs:annotation>
<xs:appinfo>
<vm:dcterm>Coverage.RegionOfRegard</vm:dcterm>
</xs:appinfo>
<xs:documentation>
A single numeric value representing the angle, given
in decimal degrees, by which a positional query
against this resource should be &#8220;blurred&#8221; in order
to get an appropriate match.
</xs:documentation>
<xs:documentation>
In the case of image repositories, it might refer to
a typical field-of-view size, or the primary beam
size for radio aperture synthesis data. In the case
of object catalogues RoR should normally be the
largest of the typical size of the objects, the
astrometric errors in the positions, or the
resolution of the data.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
Content Element Detail (all declarations; 7)
footprint
Type:
vs:ServiceReference, simple content
Defined:
locally within (this) vs:Coverage complexType
Annotation 1 [src]:
A reference to a footprint service for retrieving precise and up-to-date description of coverage.
Annotation 2 [src]:
The ivo-id attribute here refers to the standard in which the footprint is given. The only value defined by VODataService at this point is ivo://ivoa.net/std/moc, which indicates that retrieving the footprint URL will return a MOC (any IVOA-approved serialisation is legal). Note that the ivo-id attribute was intended to have a different function in VODataService 1.1. The current meaning is what implementors actually adopted.
XML Source (see within schema source)
<xs:element minOccurs="0" name="footprint" type="vs:ServiceReference">
<xs:annotation>
<xs:documentation>
A reference to a footprint service for retrieving
precise and up-to-date description of coverage.
</xs:documentation>
<xs:documentation>
The ivo-id attribute here refers to the standard in which
the footprint is given. The only value defined by
VODataService at this point is ivo://ivoa.net/std/moc,
which indicates that retrieving the footprint URL will return
a MOC (any IVOA-approved serialisation is legal). Note that
the ivo-id attribute was intended to have a different
function in VODataService 1.1. The current meaning is what
implementors actually adopted.
</xs:documentation>
</xs:annotation>
</xs:element>
regionOfRegard
Type:
xs:float, simple content
Defined:
locally within (this) vs:Coverage complexType
Annotation 1 [src]:
A single numeric value representing the angle, given in decimal degrees, by which a positional query against this resource should be “blurred” in order to get an appropriate match.
Annotation 2 [src]:
In the case of image repositories, it might refer to a typical field-of-view size, or the primary beam size for radio aperture synthesis data. In the case of object catalogues RoR should normally be the largest of the typical size of the objects, the astrometric errors in the positions, or the resolution of the data.
XML Source (see within schema source)
<xs:element minOccurs="0" name="regionOfRegard" type="xs:float">
<xs:annotation>
<xs:appinfo>
<vm:dcterm>Coverage.RegionOfRegard</vm:dcterm>
</xs:appinfo>
<xs:documentation>
A single numeric value representing the angle, given
in decimal degrees, by which a positional query
against this resource should be &#8220;blurred&#8221; in order
to get an appropriate match.
</xs:documentation>
<xs:documentation>
In the case of image repositories, it might refer to
a typical field-of-view size, or the primary beam
size for radio aperture synthesis data. In the case
of object catalogues RoR should normally be the
largest of the typical size of the objects, the
astrometric errors in the positions, or the
resolution of the data.
</xs:documentation>
</xs:annotation>
</xs:element>
spatial
Type:
vs:SpatialCoverage, simple content
Defined:
locally within (this) vs:Coverage complexType
Annotation 1 [src]:
An ASCII-serialized MOC defining the spatial coverage of the resource.
Annotation 2 [src]:
The MOC is to be understood in the ICRS reference frame unless a frame attribute is given. Resources should give the coverage at least to order 6 (a resolution of about one degree). The order should be chosen so as to keep the resulting MOC smaller than a few dozens of kB. If desired, a more precise MOC can be provided on a dedicated endpoint declared in the footprint element.
XML Source (see within schema source)
<xs:element minOccurs="0" name="spatial" type="vs:SpatialCoverage">
<xs:annotation>
<xs:documentation>
An ASCII-serialized MOC defining the spatial coverage
of the resource.
</xs:documentation>
<xs:documentation>
The MOC is to be understood in the ICRS reference frame
unless a frame attribute is given.
Resources should give the coverage at least to order 6
(a resolution of about one degree). The order should be
chosen so as to keep the resulting MOC smaller than a few
dozens of kB. If desired, a more precise MOC can be provided
on a dedicated endpoint declared in the footprint element.
</xs:documentation>
</xs:annotation>
</xs:element>
spectral
Type:
vs:FloatInterval, simple content
Defined:
locally within (this) vs:Coverage complexType
Annotation 1 [src]:
A pair of lower, upper limits of a spectral interval for which the resource offers data.
Annotation 2 [src]:
This is written as for VOTable tabledata (i.e., whitespace-separated C-style floating point literals). The limits must be given in Joules of particle energies. While the limits are not intended to be precise, they are to be understood for the solar system barycenter.
Annotation 3 [src]:
For instance, the Johnson V waveband (480 .. 730 nm) would be specified as “2.72e-19 4.14e-19”
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="spectral" type="vs:FloatInterval">
<xs:annotation>
<xs:documentation>
A pair of lower, upper limits of a spectral interval
for which the resource offers data.
</xs:documentation>
<xs:documentation>
This is written as for VOTable tabledata (i.e.,
whitespace-separated C-style floating point literals).
The limits must be given in Joules of particle
energies. While the limits are not intended
to be precise, they are to be understood for the
solar system barycenter.
</xs:documentation>
<xs:documentation>
For instance, the Johnson V waveband (480 .. 730 nm)
would be specified as &#8220;2.72e-19 4.14e-19&#8221;
</xs:documentation>
</xs:annotation>
</xs:element>
stc:STCResourceProfile
Type:
stc:astroSTCDescriptionType, complex content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within (this) vs:Coverage complexType
An STC 1.0 description of the location of the resource's data on the sky, in time, and in frequency space, including resolution. This is deprecated in favour of the separate spatial, temporal, and spectral elements.
XML Source (see within schema source)
<xs:element minOccurs="0" ref="stc:STCResourceProfile">
<xs:annotation>
<xs:documentation>
An STC 1.0 description of the location of the resource's
data on the sky, in time, and in frequency space,
including resolution. This is deprecated in favour
of the separate spatial, temporal, and spectral elements.
</xs:documentation>
</xs:annotation>
</xs:element>
temporal
Type:
vs:FloatInterval, simple content
Defined:
locally within (this) vs:Coverage complexType
Annotation 1 [src]:
A pair of lower, upper limits of a time interval for which the resource offers data.
Annotation 2 [src]:
This is written as for VOTable tabledata (i.e., whitespace-separated C-style floating point literals), as in “47847.2 51370.2”. The limits must be given as MJD. While they are not intended to be precise, they are to be understood in TDB for the solar system barycenter. The total coverage of the resource is the union of all such intervals.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="temporal" type="vs:FloatInterval">
<xs:annotation>
<xs:documentation>
A pair of lower, upper limits of a time interval
for which the resource offers data.
</xs:documentation>
<xs:documentation>
This is written as for VOTable tabledata (i.e.,
whitespace-separated C-style floating point literals), as
in &#8220;47847.2 51370.2&#8221;.
The limits must be given as MJD. While they
are not intended to be precise, they are to be understood
in TDB for the solar system barycenter. The total coverage
of the resource is the union of all such intervals.
</xs:documentation>
</xs:annotation>
</xs:element>
waveband
Type:
xs:token, simple content
Defined:
locally within (this) vs:Coverage complexType
Annotation 1 [src]:
A name of a messenger that the resource is relevant for (e.g., was used in the measurements). Terms must be taken from the vocabulary at http://www.ivoa.net/rdf/messenger.
Annotation 2 [src]:
It is a bit unfortunate that the element is still called waveband when it is now also coverage non-electromagnetic messengers. It was deemed that this slight notional sloppiness is preferable to introducing new and deprecating old elements.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="waveband" type="xs:token">
<xs:annotation>
<xs:appinfo>
<vm:dcterm>Coverage.Spectral</vm:dcterm>
</xs:appinfo>
<xs:documentation>
A name of a messenger that the resource is relevant for
(e.g., was used in the measurements). Terms must
be taken from the vocabulary at
http://www.ivoa.net/rdf/messenger.
</xs:documentation>
<xs:documentation>
It is a bit unfortunate that the element is still called
waveband when it is now also coverage non-electromagnetic
messengers. It was deemed that this slight notional
sloppiness is preferable to introducing new and
deprecating old elements.
</xs:documentation>
</xs:annotation>
</xs:element>
This XML schema documentation has been generated with DocFlex/XML RE 1.8.0 using DocFlex/XML XSDDoc 2.2.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/