complexType "ssap:ProtoSpectralAccess"

Namespace:	http://www.ivoa.net/xml/SSA/v1.1
Content:	complex, 1 attribute, 11 elements
Defined:	globally in SSA-v1.1.xsd; see XML source
Includes:	definitions of 8 elements
Used:	never

XML Representation Summary

<...

standardID

"ivo://ivoa.net/std/SSA"

Content:

validationLevel*, description?, interface*, dataSource+, creationType+, maxSearchRadius?, maxRecords, defaultMaxRecords, maxAperture?, maxFileSize?, testQuery?

</...>

Content Model Elements (11):

The capabilities of an proto-SSA service implementation. Clients may assume a particular interface for this type of service based on historical convention; however, no guarantees are made that the service is compliant with any IVOA standard.

This capability is for spectral access services developed prior to the completion of the SSA standard and, therefore, are not compliant with that standard.

Type Definition Detail

Type Derivation Tree

vr:Capability (restriction)

ssap:SSACapRestriction (extension)

ssap:ProtoSpectralAccess

XML Source (see within schema source)

<xs:complexType name="ProtoSpectralAccess">

<xs:annotation>

<xs:documentation>

The capabilities of an proto-SSA service implementation.
Clients may assume a particular interface for this type of
service based on historical convention; however, no
guarantees are made that the service is compliant with any
IVOA standard.

</xs:documentation>

<xs:documentation>

This capability is for spectral access services developed
prior to the completion of the SSA standard and,
therefore, are not compliant with that standard.

</xs:documentation>

</xs:annotation>

<xs:complexContent>

<xs:extension base="ssap:SSACapRestriction">

<xs:sequence>

<xs:element maxOccurs="unbounded" minOccurs="1" name="dataSource" type="ssap:DataSource">

<xs:annotation>

<xs:documentation>

The category specifying where the data originally
came from.

</xs:documentation>

<xs:documentation>

Allowed values are "survey", "pointed", "custom",
"theory", "artificial"

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element maxOccurs="unbounded" minOccurs="1" name="creationType" type="ssap:CreationType">

<xs:annotation>

<xs:documentation>

The category that describes the process used to
produce the dataset.

</xs:documentation>

<xs:documentation>

Typically this describes only the processing
performed by the data service, but it could
describe some additional earlier processing as
well, e.g., if data is partially precomputed.

</xs:documentation>

<xs:documentation>

Allowed values are "archival", "cutout", "filtered",
"mosaic", "projection", "spectralExtraction",
"catalogExtraction"

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element maxOccurs="1" minOccurs="0" name="maxSearchRadius" type="xs:double">

<xs:annotation>

<xs:documentation>

The largest search radius, in degrees, that will be
accepted by the service without returning an error
condition. Not providing this element or
specifying a value of 180 indicates that there
is no restriction.

</xs:documentation>

<xs:documentation>

Not providing a value is the prefered way to
indicate that there is no restriction.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element name="maxRecords" type="xs:positiveInteger">

<xs:annotation>

<xs:documentation>

The hard limit on the largest number of records that
the query operation will return in a single response

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element name="defaultMaxRecords" type="xs:positiveInteger">

<xs:annotation>

<xs:documentation>

The largest number of records that the service will
return when the MAXREC parameter not specified
in the query input.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element minOccurs="0" name="maxAperture" type="xs:double">

<xs:annotation>

<xs:documentation>

The largest aperture diameter that can be supported
upon request via the APERTURE input parameter by a
service that supports the spectral extraction
creation method. A value of 360 or not providing
a value means there is no theoretical limit.

</xs:documentation>

<xs:documentation>

Not providing a value is the preferred way to
indicate that there is no limit.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element maxOccurs="1" minOccurs="0" name="maxFileSize" type="xs:int">

<xs:annotation>

<xs:documentation>

The maximum image file size in bytes.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element maxOccurs="1" minOccurs="0" name="testQuery" type="ssap:Query">

<xs:annotation>

<xs:documentation>

a set of query parameters that is expected to
produce at least one matched record which can be
used to test the service.

</xs:documentation>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

Attribute Detail (all declarations; 1)

Type:	vr:IdentifierURI
Use:	required
Fixed:	"ivo://ivoa.net/std/SSA"
Defined:	locally within ssap:SSACapRestriction complexType

XML Source (see within schema source)

<xs:attribute fixed="ivo://ivoa.net/std/SSA" name="standardID" type="vr:IdentifierURI" use="required"/>

Content Element Detail (all declarations; 11)

Type:	ssap:CreationType, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The category that describes the process used to produce the dataset.

Typically this describes only the processing performed by the data service, but it could describe some additional earlier processing as well, e.g., if data is partially precomputed.

Allowed values are "archival", "cutout", "filtered", "mosaic", "projection", "spectralExtraction", "catalogExtraction"

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="1" name="creationType" type="ssap:CreationType">

<xs:annotation>

<xs:documentation>

The category that describes the process used to
produce the dataset.

</xs:documentation>

<xs:documentation>

Typically this describes only the processing
performed by the data service, but it could
describe some additional earlier processing as
well, e.g., if data is partially precomputed.

</xs:documentation>

<xs:documentation>

Allowed values are "archival", "cutout", "filtered",
"mosaic", "projection", "spectralExtraction",
"catalogExtraction"

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	ssap:DataSource, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The category specifying where the data originally came from.

Allowed values are "survey", "pointed", "custom", "theory", "artificial"

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="1" name="dataSource" type="ssap:DataSource">

<xs:annotation>

<xs:documentation>

The category specifying where the data originally
came from.

</xs:documentation>

<xs:documentation>

Allowed values are "survey", "pointed", "custom",
"theory", "artificial"

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:positiveInteger, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The largest number of records that the service will return when the MAXREC parameter not specified in the query input.

XML Source (see within schema source)

<xs:element name="defaultMaxRecords" type="xs:positiveInteger">

<xs:annotation>

<xs:documentation>

The largest number of records that the service will
return when the MAXREC parameter not specified
in the query input.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within ssap:SSACapRestriction complexType

XML Source (see within schema source)

<xs:element minOccurs="0" name="description" type="xs:token"/>

Type:	vr:Interface, complex content
Defined:	locally within ssap:SSACapRestriction complexType

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="interface" type="vr:Interface"/>

Type:	xs:double, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The largest aperture diameter that can be supported upon request via the APERTURE input parameter by a service that supports the spectral extraction creation method. A value of 360 or not providing a value means there is no theoretical limit.

Not providing a value is the preferred way to indicate that there is no limit.

XML Source (see within schema source)

<xs:element minOccurs="0" name="maxAperture" type="xs:double">

<xs:annotation>

<xs:documentation>

</xs:documentation>

<xs:documentation>

Not providing a value is the preferred way to
indicate that there is no limit.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:int, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The maximum image file size in bytes.

XML Source (see within schema source)

<xs:element maxOccurs="1" minOccurs="0" name="maxFileSize" type="xs:int">

<xs:annotation>

<xs:documentation>

The maximum image file size in bytes.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:positiveInteger, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The hard limit on the largest number of records that the query operation will return in a single response

XML Source (see within schema source)

<xs:element name="maxRecords" type="xs:positiveInteger">

<xs:annotation>

<xs:documentation>

The hard limit on the largest number of records that
the query operation will return in a single response

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:double, simple content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

The largest search radius, in degrees, that will be accepted by the service without returning an error condition. Not providing this element or specifying a value of 180 indicates that there is no restriction.

Not providing a value is the prefered way to indicate that there is no restriction.

XML Source (see within schema source)

<xs:element maxOccurs="1" minOccurs="0" name="maxSearchRadius" type="xs:double">

<xs:annotation>

<xs:documentation>

</xs:documentation>

<xs:documentation>

Not providing a value is the prefered way to
indicate that there is no restriction.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	ssap:Query, complex content
Defined:	locally within (this) ssap:ProtoSpectralAccess complexType

a set of query parameters that is expected to produce at least one matched record which can be used to test the service.

XML Source (see within schema source)

<xs:element maxOccurs="1" minOccurs="0" name="testQuery" type="ssap:Query">

<xs:annotation>

<xs:documentation>

a set of query parameters that is expected to
produce at least one matched record which can be
used to test the service.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	vr:Validation, simple content
Defined:	locally within ssap:SSACapRestriction complexType

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevel" type="vr:Validation"/>

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/