XML Schema "ConeSearch-v1.0.xsd"
Target Namespace:
http://www.ivoa.net/xml/ConeSearch/v1.0
Version:
1.00r2
Defined Components:
13 local elements, 3 complexTypes
Default Namespace-Qualified Form:
Local Elements: unqualified; Local Attributes: unqualified
Schema Location:
/home/msdemlei/gavo/trunk/gavo/resources/schemata/ConeSearch-v1.0.xsd; see XML source
Imports Schema:
VOResource-v1.1.xsd [src]
Annotation
Annotation 1 [src]:
Implementation of an XML Schema describing a Cone Search Service. Based on "Simple Cone Search: a First Guide for Data Curators", http://www.us-vo.org/metadata/conesearch/.
Annotation 2 [src]:
This schema defines a Capability type that is specific to Cone Search. A service that has ConeSearch capability should be registered as a TabularSkyService. The ConeSearch capability element must include a ParamHTTP interface.
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://www.ivoa.net/xml/ConeSearch/v1.0" version="1.00r2" xmlns:cs="http://www.ivoa.net/xml/ConeSearch/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">
<xs:annotation>
<xs:appinfo>
<vm:schemaName>ConeSearch</vm:schemaName>
<vm:schemaPrefix>xs</vm:schemaPrefix>
<vm:targetPrefix>cs</vm:targetPrefix>
</xs:appinfo>
<xs:documentation>
Implementation of an XML Schema describing a Cone Search Service.
Based on "Simple Cone Search: a First Guide for Data Curators",
http://www.us-vo.org/metadata/conesearch/.
</xs:documentation>
<xs:documentation>
This schema defines a Capability type that is specific to Cone
Search. A service that has ConeSearch capability should be
registered as a TabularSkyService. The ConeSearch capability
element must include a ParamHTTP interface.
</xs:documentation>
</xs:annotation>
<xs:complexType abstract="true" name="CSCapRestriction">
<xs:annotation>
<xs:documentation>
an abstract capability that fixes the standardID to the
IVOA ID for the ConeSearch standard.
</xs:documentation>
<xs:documentation>
See vr:Capability for documentation on inherited children.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="vr:Capability">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevel" type="vr:Validation"/>
<xs:element minOccurs="0" name="description" type="xs:token"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="interface" type="vr:Interface"/>
</xs:sequence>
<xs:attribute fixed="ivo://ivoa.net/std/ConeSearch" name="standardID" type="vr:IdentifierURI" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ConeSearch">
<xs:annotation>
<xs:documentation>
The capabilities of a Cone Search implementation.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="cs:CSCapRestriction">
<xs:sequence>
<xs:element name="maxSR" type="xs:float">
<xs:annotation>
<xs:documentation>
The largest search radius, in degrees, that will be
accepted by the service without returning an error
condition.
</xs:documentation>
<xs:documentation>
Use 180.0 if there is no restriction.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="maxRecords" type="xs:int">
<xs:annotation>
<xs:documentation>
The largest number of records that the service will
return.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="verbosity" type="xs:boolean">
<xs:annotation>
<xs:documentation>
True if the service supports the VERB keyword;
false, otherwise.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="testQuery" type="cs:Query">
<xs:annotation>
<xs:documentation>
A query that will result in at least on
matched record that can be used to test the
service.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Query">
<xs:annotation>
<xs:documentation>
A query to be sent to the service
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="ra" type="xs:double">
<xs:annotation>
<xs:documentation>
the right ascension of the search cone's center in
decimal degrees.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="dec" type="xs:double">
<xs:annotation>
<xs:documentation>
the declination of the search cone's center in
decimal degrees.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="sr" type="xs:double">
<xs:annotation>
<xs:documentation>
the radius of the search cone in decimal degrees.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="verb" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>
the verbosity level to use where 1 means the bare
minimum set of columns and 3 means the full set of
available columns.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="catalog" type="xs:string">
<xs:annotation>
<xs:documentation>
the catalog to query.
</xs:documentation>
<xs:documentation>
When the service can access more than one catalog,
this input parameter, if available, is used to
indicate which service to access.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="extras" type="xs:string">
<xs:annotation>
<xs:documentation>
any extra (non-standard) parameters that must be
provided (apart from what is part of base URL given
by the accessURL element).
</xs:documentation>
<xs:documentation>
this value should be in the form of name=value
pairs delimited with ampersands (&amp;).
</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:
  • 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/