/[volute]/trunk/projects/registry/VODataService/VODataService.tex
ViewVC logotype

Diff of /trunk/projects/registry/VODataService/VODataService.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 5191 by msdemlei, Thu Oct 25 12:10:40 2018 UTC revision 5192 by msdemlei, Thu Oct 25 12:38:16 2018 UTC
# Line 180  Line 180 
180  defines the ParamHTTP interface type used in the capabilities of most  defines the ParamHTTP interface type used in the capabilities of most
181  standard protocols.  standard protocols.
182  \item[RefTAP, v1.0 \citep{2014ivoa.spec.1208D}] RegTAP maps the concepts  \item[RefTAP, v1.0 \citep{2014ivoa.spec.1208D}] RegTAP maps the concepts
183  defined here into a relational structure.  defined here into a relational structure.  In that sense it provides the
184    user interface to what is specified here.
185  \end{description}  \end{description}
186    
187  \subsection{Purpose}  \subsection{Purpose}
# Line 193  Line 194 
194  sky with which the data are associated and the time and frequency ranges that  sky with which the data are associated and the time and frequency ranges that
195  were observed or modeled to create the data.  It also allows one to  were observed or modeled to create the data.  It also allows one to
196  describe tables in detail.  In particular, one can describe each of  describe tables in detail.  In particular, one can describe each of
197  the columns of a table--providing, for example, its name, type, UCD  the columns of a table -- providing, for example, its name, type, UCD
198  \citep{2005ivoa.spec.1231D},  \citep{2005ivoa.spec.1231D}, unit,
199  and textual description.  When this metadata is part of a resource  and textual description.  When this metadata is part of a resource
200  description in a registry, it becomes possible  description in a registry, it becomes possible
201  to discover tables that contain particular kinds of data.    to discover tables that contain particular kinds of data.  
202    
203    
204    
205  It is intended that VODataService will be central to describing  Resource records using VODataService types are commonly used to register
206  services that support standard IVOA data access layer protocols such  services that support standard IVOA data access layer protocols such
207  as Simple Image Access \citep{2015ivoa.spec.1223D} and Simple Cone Search  as Simple Image Access \citep{2015ivoa.spec.1223D} and Simple Cone Search
208  \citep{2008ivoa.specQ0222P}.  While other VOResource extensions would  \citep{2008ivoa.specQ0222P}.  As of October 2018, there are more than
209    20000~resources of type \xmlel{vs:CatalogService} in the VO Registry.
210    
211    While other VOResource extensions
212  define the protocol-specific metadata (encapsulated as a standard  define the protocol-specific metadata (encapsulated as a standard
213  \emph{capability} from VOResource), the general service  \emph{capability} from VOResource), the general service
214  resource description would share the common data concepts such as  resource description shares the common data concepts such as
215  coverage and tabular data.  Note, however, that a service described  coverage and tabular data.  Note, however, that a service described
216  using the VODataService schema need not support any standard  using the VODataService schema need not support any standard
217  protocols.  With the VODataService extension schema plus the core  protocols.  With the VODataService extension schema plus the core
# Line 263  Line 267 
267    
268  \paragraph{Find a large-scale survey of sources between 20 and 40 GHz.}  \paragraph{Find a large-scale survey of sources between 20 and 40 GHz.}
269  While the spectral constraint is easily satisfied by the new coverage  While the spectral constraint is easily satisfied by the new coverage
270  children, the ``large-scale'' part is much harder to operationalise.  children, the ``large-scale'' part is much harder to operationalize.
271  However, the plain table size often is a useful proxy in such discovery  However, the plain table size often is a useful proxy in such discovery
272  problems.  The new \xmlel{nrows} child of \xmlel{vs:Table} communicates  problems.  The new \xmlel{nrows} child of \xmlel{vs:Table} communicates
273  it.  it.
# Line 747  Line 751 
751  An important characteristic of MOCs is the order of the smallest scale  An important characteristic of MOCs is the order of the smallest scale
752  (the ``MOC resolution'').  Higher orders yield more faithful  (the ``MOC resolution'').  Higher orders yield more faithful
753  representations of the actual coverage, but also lead to a possibly  representations of the actual coverage, but also lead to a possibly
754  significant increase of the size of the serialised MOC.  We suggest a  significant increase of the size of the serialized MOC.  We suggest a
755  ``typical resolution'' of the Registry of about a degree (i.e., MOC  ``typical resolution'' of the Registry of about a degree (i.e., MOC
756  order 6), but resources are free to choose a higher maximum orders if  order 6), but resources are free to choose a higher maximum orders if
757  appropriate and the resource record size remains reasonable.  appropriate and the resource record size remains reasonable.
# Line 833  Line 837 
837  \begin{description}  \begin{description}
838  \item[Type] string: \xmlel{xs:string}  \item[Type] string: \xmlel{xs:string}
839  \item[Meaning]  \item[Meaning]
840                    An ASCII-serialised MOC defining the spatial coverage                    An ASCII-serialized MOC defining the spatial coverage
841                    of the resource.                    of the resource.
842                                
843  \item[Occurrence] optional  \item[Occurrence] optional

Legend:
Removed from v.5191  
changed lines
  Added in v.5192

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26