| <?xml version="1.0" encoding="UTF-8"?> <xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://www.ivoa.net/xml/SLAP/v1.0" version="1.0" xmlns:slap="http://www.ivoa.net/xml/SLAP/v1.0" xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1" xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <!-- First version 09/09/09 Authors: Jesus Salgado/Aurelien Stebe (ESAVO) --> <xs:annotation> <xs:appinfo> <vm:schemaName>SLAP</vm:schemaName> <vm:schemaPrefix>xs</vm:schemaPrefix> <vm:targetPrefix>slap</vm:targetPrefix> </xs:appinfo> <xs:documentation> XML Schema used to describe the capabilities of a service instance conforming to the Simple Line Access Protocol (SLAP). </xs:documentation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v1.0" schemaLocation="http://www.ivoa.net/xml/VOResource/v1.0"/> <!-- Set the Capability standardID to indicate the SLAP protocol. --> <xs:annotation> <xs:documentation> An abstract capability that fixes the standardID to the IVOA ID for the SLAP standard. </xs:documentation> <xs:documentation> See vr:Capability for documentation on inherited children. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> </xs:sequence> <xs:attribute fixed="ivo://ivoa.net/std/SLAP" name="standardID" type="vr:IdentifierURI" use="required"/> </xs:restriction> </xs:complexContent> </xs:complexType> <!-- SLAP Capabilities --> <xs:annotation> <xs:documentation> The capabilities of an SLAP service implementation. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:annotation> <xs:documentation> The category indicating the level to which this service instance complies with the SLAP standard. </xs:documentation> <xs:documentation> Allowed values are "minimal" and "full". See definitions of allowed values for details. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> The category specifying where the data accessed by the service originally came from. </xs:documentation> <xs:documentation> Allowed values are "observational/astrophysical", "observational/laboratory", "theoretical" </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> 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. </xs:documentation> <xs:documentation> 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.) </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A set of queryData parameters that is expected to produce at least one matched record which can be used to test the service. </xs:documentation> <xs:documentation> The value should include all parameters required for the test query but should exclude the baseURL and the REQUEST parameter. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> The allowed values for indicating the level at which a service instance complies with the SLAP standard. </xs:documentation> </xs:annotation> <xs:enumeration value="minimal"> <xs:annotation> <xs:documentation> The service supports all of the capabilities and features of the SLAP protocol identified as "must" in the specification. </xs:documentation> <xs:documentation> 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. </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="full"> <xs:annotation> <xs:documentation> The service supports, at a minimum, all of the capabilities and features of the SLAP protocol identified as "must" or "should" in the specification. </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:annotation> <xs:documentation> 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. </xs:documentation> </xs:annotation> <xs:enumeration value="observational/astrophysical"> <xs:annotation> <xs:documentation> Lines observed and identified in real spectra of astrophysical observations by different instrument/projects </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="observational/laboratory"> <xs:annotation> <xs:documentation> Lines observed and identified in real spectra of laboratory measurements </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="theoretical"> <xs:annotation> <xs:documentation> Servers containing theoretical spectral lines </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:annotation> <xs:documentation> A query to be sent to the service, e.g., a test query. </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> Spectral range in meters to be used to constrain the query of spectral lines. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> 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. </xs:documentation> <xs:documentation> 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. </xs:documentation> <xs:documentation> 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. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:annotation> <xs:documentation> Spectral range in meters to be used to constrain the query of spectral lines </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> Minimum wavelength in meters to be used to constrain the query of spectral lines </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> Maximum wavelength in meters to be used to constrain the query of spectral lines </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:schema> |
| 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:
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/ |