/[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 5930 by msdemlei, Tue Feb 23 09:45:51 2021 UTC revision 5931 by msdemlei, Tue Feb 23 10:35:17 2021 UTC
# Line 7  Line 7 
7  \lstloadlanguages{XML}  \lstloadlanguages{XML}
8  \lstset{flexiblecolumns=true,tagstyle=\ttfamily,showstringspaces=False}  \lstset{flexiblecolumns=true,tagstyle=\ttfamily,showstringspaces=False}
9  \usepackage{amsmath}  \usepackage{amsmath}
 \usepackage{todonotes}  
10    
11  \iftth  \iftth
12  \newcommand{\tapschema}{TAP\_SCHE\-MA}  \newcommand{\tapschema}{TAP\_SCHE\-MA}
# Line 177  Line 176 
176  schema for the responses on the table metadata endpoint.  It also  schema for the responses on the table metadata endpoint.  It also
177  defines the ParamHTTP interface type currently used in the capabilities of most  defines the ParamHTTP interface type currently used in the capabilities of most
178  standard protocols.  standard protocols.
179  \item[RegTAP, v1.0 \citep{2014ivoa.spec.1208D}] RegTAP maps the concepts  \item[RegTAP, v1.1 \citep{2019ivoa.spec.1011D}] RegTAP maps the concepts
180  defined here into a relational structure.  In that sense it is the  defined here into a relational structure.  In that sense it is the
181  user interface to what is specified here.  user interface to what is specified here.  RegTAP will need an update
182    to support the space-time constraints added here.
183    \item[MOC, v1.1 \citep{2019ivoa.spec.1007F}] Multi-Order coverage maps
184    are used by VODataService to communicate spatial coverage.
185  \end{description}  \end{description}
186    
187  \subsection{Purpose}  \subsection{Purpose}
# Line 307  Line 309 
309  \paragraph{Facilitate discovery of full DALI services.}  The issue here  \paragraph{Facilitate discovery of full DALI services.}  The issue here
310  is that DALI forsees synchronous and asynchronous endpoints as the  is that DALI forsees synchronous and asynchronous endpoints as the
311  standard case for many protocols -- it already is standard for TAP.  standard case for many protocols -- it already is standard for TAP.
312  Also, several auxiliary endpoints (VOSI, examples) are declared as  Also, several auxiliary endpoints (mostly defined in VOSI) are declared as
313  separate capabilities and need to be matched with the functional  separate capabilities and need to be matched with the functional
314  endpoints.  This matching is becoming a problem when multiple  endpoints.  This matching is becoming a problem when multiple
315  authentication schemes or mirror sites necessitate multiple sync/async  authentication schemes or mirror sites necessitate multiple sync/async
# Line 423  Line 425 
425  the physical coverage of a resource on the sky (or on spherical bodies),  the physical coverage of a resource on the sky (or on spherical bodies),
426  in time, and in the energy of the messenger particle.  In addition, the  in time, and in the energy of the messenger particle.  In addition, the
427  element should contain a rough indication of the messenger type  element should contain a rough indication of the messenger type
428  (``Optical''), and it can contain a link to a footprint endpoint and an  (e.g., ``Optical''), and it can contain a link to a footprint endpoint and an
429  indication of the spatial resolution within a service.  indication of the spatial resolution within a service.
430    
431  VODataService has several classes for the declaration of the tabular  VODataService has several classes for the declaration of the tabular
# Line 460  Line 462 
462  alike, VODataService defines several type systems.  All of these are  alike, VODataService defines several type systems.  All of these are
463  basically just enumerations of type names, possibly with some additional  basically just enumerations of type names, possibly with some additional
464  metadata like VOTable-style array sizes.  In new resource records, only  metadata like VOTable-style array sizes.  In new resource records, only
465  \xmlel{vs:SimpleDataType} (for ParamHTTP interface parameters) and  \xmlel{vs:SimpleDataType} (for ParamHTTP parameters on non-DALI
466    interfaces) and
467  \xmlel{vs:VOTableType} (for table columns) should be used.  \xmlel{vs:VOTableType} (for table columns) should be used.
468    
469  \subsubsection{VODataService Resource Classes}  \subsubsection{VODataService Resource Classes}
# Line 490  Line 493 
493  i.e., a table of data on astronomical objects.  On the  i.e., a table of data on astronomical objects.  On the
494  contrary, CatalogX should also be used for collections of images,  contrary, CatalogX should also be used for collections of images,
495  spectra, time series, etc, as long as their metadata is sufficiently  spectra, time series, etc, as long as their metadata is sufficiently
496  structured.  Accessibility through IVOA standard protocols (ObsCore,  structured.  That a data collection ist published through the standard
497  SIAP, SSAP) certainly satisfies that requirement.  IVOA discovery protocols (ObsCore,
498    SIAP, SSAP) certainly is a strong indication that this requirement is
499    satisfied.
500    
501  The horizontal distinction (XResource vs.~XService) is somewhat more  The horizontal distinction (XResource vs.~XService) is somewhat more
502  subtle and will be discussed in sect.~\ref{sect:discoverdata}.  subtle and will be discussed in sect.~\ref{sect:discoverdata}.
# Line 744  Line 749 
749  \label{sect:CatalogResource}  \label{sect:CatalogResource}
750    
751    
752  The \xmlel{vs:CatalogResource} resource type is used to descre a  The \xmlel{vs:CatalogResource} resource type is used to describe a
753  resource containing astronomical data or metadata in a set of one or  resource containing astronomical data or metadata in a set of one or
754  more tables.  It extends \xmlel{vs:DataResource} and thus has metadata  more tables.  It extends \xmlel{vs:DataResource} and thus has metadata
755  on coverage and the facilities and instruments that produced the  on coverage and the facilities and instruments that produced the
# Line 907  Line 912 
912    
913  Spatial coverage is conveyed as a MOC.  To enable easy embedding into  Spatial coverage is conveyed as a MOC.  To enable easy embedding into
914  resource records written in VOResource (i.e., XML),  resource records written in VOResource (i.e., XML),
915  we represent MOCs in the ASCII convention  VODataService uses the string serialisation defined in section 2.3.2 of
916  proposed in MOC 1.0 \citep{2014ivoa.spec.0602F}\footnote{Version 1.1 of MOC  \citet{2019ivoa.spec.1007F}.
 will give a normative specification of ASCII MOCs, which is expected to  
 essentially match the non-normative proposal in version 1.0.}  
917    
918  By default, the MOCs are to be interpreted in the ICRS.  Future  By default, the MOCs are to be interpreted in the ICRS.  Future
919  extensions to non-celestial frames (e.g., on planet  extensions to non-celestial frames (e.g., on planet
# Line 2315  Line 2318 
2318  Since VODataService 1.2, input parameters can use any type system,  Since VODataService 1.2, input parameters can use any type system,
2319  where non-DALI-compliant services SHOULD use \xmlel{vs:SimpleDataType}  where non-DALI-compliant services SHOULD use \xmlel{vs:SimpleDataType}
2320  and DALI-compliant services SHOULD use \xmlel{vs:VOTableType}.  To  and DALI-compliant services SHOULD use \xmlel{vs:VOTableType}.  To
2321  ensure schema validation catches error, resource record authors are  ensure schema validation catches mistakes, resource record authors are
2322  advised to declare the type system intended using \xmlel{xsi:type}; for  advised to declare the type system intended using \xmlel{xsi:type}; for
2323  instance, an SSAP service might declare:  instance, a service accepting a DALI point might declare:
2324    
2325  \begin{lstlisting}[language=XML]  \begin{lstlisting}[language=XML]
2326    <param std="true">    <param std="true">
2327      <name>POS</name>      <name>pos</name>
2328      <description>ICRS position of target object</description>      <description>ICRS position of target object</description>
2329      <dataType arraysize="*"      <dataType arraysize="2"
2330        xsi:type="vs:VOTableType"        xsi:type="vs:VOTableType"
2331        extendedType="point">char</dataType>        extendedType="point">double</dataType>
2332    </param>    </param>
2333  \end{lstlisting}  \end{lstlisting}
2334    
# Line 2347  Line 2350 
2350           \par}           \par}
2351    
2352  \noindent{\small  \noindent{\small
2353                  DALI-compliant services should use vs:VOTableType here, others                  DALI-compliant services should use VOTableType here, others
2354                  should use vs:SimpleDataType.                  should use SimpleDataType.
2355           \par}           \par}
2356    
2357  \vspace{1ex}\noindent\textbf{\xmlel{vs:InputParam} Type Schema Definition}  \vspace{1ex}\noindent\textbf{\xmlel{vs:InputParam} Type Schema Definition}
# Line 2451  Line 2454 
2454      within this angular distance of the search position.      within this angular distance of the search position.
2455    </description>    </description>
2456    <ucd> phys.angSize </ucd>    <ucd> phys.angSize </ucd>
2457    <dataType> real </dataType>    <dataType xsi:type="vs:SimpleDataType"> real </dataType>
2458  </param>  </param>
2459  \end{lstlisting}  \end{lstlisting}
2460    

Legend:
Removed from v.5930  
changed lines
  Added in v.5931

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