SLAP
xs
slap
XML Schema used to describe the capabilities of a service instance
conforming to the Simple Line Access Protocol (SLAP).
An abstract capability that fixes the standardID to the
IVOA ID for the SLAP standard.
See vr:Capability for documentation on inherited children.
The capabilities of an SLAP service implementation.
The category indicating the level to which this
service instance complies with the SLAP standard.
Allowed values are "minimal" and "full".
See definitions of allowed values for details.
The category specifying where the data accessed by
the service originally came from.
Allowed values are "observational/astrophysical",
"observational/laboratory", "theoretical"
The hard limit on the largest number of records that
the query operation will return in a single response.
Not providing this value means that there is no
effective limit.
This does not refer to the total number of spectra in
the archive but rather maximum number of records the
service is capable of returning. A limit that is
greater than the number of spectra available in the
archive is equivalent to their being no effective
limit. (See RM, Hanisch 2007.)
A set of queryData parameters that is expected to
produce at least one matched record which can be
used to test the service.
The value should include all parameters required
for the test query but should exclude the baseURL
and the REQUEST parameter.
The allowed values for indicating the level at which a service
instance complies with the SLAP standard.
The service supports all of the capabilities and features
of the SLAP protocol identified as "must" in the
specification.
In brief, this includes:
* implementing the GET interface,
* WAVELENGTH, REQUEST for input query,
* ssldm:Line.wavelength.value and ssldm:Line.title for output
fields
* supports the "FORMAT=METADATA" metadata query.
The service supports, at a minimum, all of the capabilities
and features of the SLAP protocol identified as "must" or
"should" in the specification.
The defined categories that specify where the line data
originally came from, i.e., the type of data collections to
which the service provides access.
Lines observed and identified in real spectra of
astrophysical observations by different
instrument/projects
Lines observed and identified in real spectra of
laboratory measurements
Servers containing theoretical spectral lines
A query to be sent to the service, e.g., a test query.
Spectral range in meters to be used to constrain the query
of spectral lines.
Fully specified queryData test query formatted as an URL
argument list in the syntax specified by the SLAP standard.
The list must exclude the REQUEST argument which is
assumed to be set to "queryData". VERSION may be
included if the test query applies to a specific version
of the service protocol.
If queryDataCmd is used to form a query, the default
value of WAVELENGTH specified above is not
used; if the test query requires WAVELENGTH it
should be included directly in queryDataCmd.
This value must be a string in the form of name=value
pairs delimited with ampersands (&). A query may
then be formed by appending to the baseURL the request
argument, "REQUEST=queryData&", followed by the
contents of this element.
Spectral range in meters to be used to constrain the query
of spectral lines
Minimum wavelength in meters to be used to constrain the query
of spectral lines
Maximum wavelength in meters to be used to constrain the query
of spectral lines