/[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 5190 by msdemlei, Wed Oct 24 14:00:42 2018 UTC revision 5191 by msdemlei, Thu Oct 25 12:10:40 2018 UTC
# Line 23  Line 23 
23  \title{VODataService: A VOResource Schema Extension for Describing  \title{VODataService: A VOResource Schema Extension for Describing
24  Collections and Services}  Collections and Services}
25    
26  \ivoagroup{registry}  \ivoagroup{Registry}
27    
28  \author[http://www.ivoa.net/twiki/bin/view/IVOA/RayPlante]{Raymond Plante}  \author[http://www.ivoa.net/twiki/bin/view/IVOA/RayPlante]{Raymond Plante}
29  \author[http://www.ivoa.net/twiki/bin/view/IVOA/MarkusDemleitner]{Markus Demleitner}  \author[http://www.ivoa.net/twiki/bin/view/IVOA/MarkusDemleitner]{Markus Demleitner}
# Line 55  Line 55 
55  extension of the IVOA Resource Metadata that is useful for describing  extension of the IVOA Resource Metadata that is useful for describing
56  data collections and the services that access them.  It is defined as  data collections and the services that access them.  It is defined as
57  an extension of the core resource metadata encoding standard known as  an extension of the core resource metadata encoding standard known as
58  VOResource \citep{2008ivoa.spec.0222P} using XML Schema.  VOResource \citep{2018ivoa.spec.0625P} using XML Schema.
59  The specialized resource types defined by the VODataService schema  The specialized resource types defined by the VODataService schema
60  allow one to describe how the data underlying the resource cover the  allow one to describe how the data underlying the resource cover the
61  sky as well as cover frequency and time.    sky and the frequency and time axes.  
62  VODataService also enables detailed  VODataService also enables detailed
63  descriptions of tables that includes information useful to the  descriptions of tables that includes information useful to the
64  discovery of tabular data.  It is intended that the VODataService data  discovery of tabular data.  It is intended that the VODataService data
# Line 103  Line 103 
103    
104  \section*{Syntax Notation Using XML Schema}  \section*{Syntax Notation Using XML Schema}
105    
106  The eXtensible Markup Language, or XML, is document syntax for marking  The eXtensible Markup Language, or XML, is a document syntax for marking
107  textual information with named tags and is defined by \citet{std:XML}.  textual information with named tags and is defined by \citet{std:XML}.
108  The set of XML tag names and the syntax  The set of XML tag names and the syntax
109  rules for their use is referred to as the document schema.  One way to  rules for their use is referred to as the document schema.  One way to
# Line 122  Line 122 
122    
123  References to specific elements and types defined in the VOResource  References to specific elements and types defined in the VOResource
124  schema include the namespaces prefix \xmlel{vr} as in  schema include the namespaces prefix \xmlel{vr} as in
125  \xmlel{vr:Resource} (a type defined in the VOResource schema; the  \xmlel{vr:Resource} (a type defined in the VOResource schema).
126    
127    The
128  recommended namespace prefix for VODataService as per Registry  recommended namespace prefix for VODataService as per Registry
129  Interfaces 1.1 \citep{2018ivoa.spec.0723D}, sect.~2.2, is \xmlel{vs}.  Interfaces 1.1 \citep{2018ivoa.spec.0723D}, sect.~2.2, is \xmlel{vs}.
130    
# Line 137  Line 139 
139  for creating extensions to the core VOResource metadata.  This allows  for creating extensions to the core VOResource metadata.  This allows
140  for the standardization of new metadata for describing specialized  for the standardization of new metadata for describing specialized
141  kinds of resources in a modular way without deprecating the core  kinds of resources in a modular way without deprecating the core
142  schema or other extensions.  This document defines one such extension  schema or other extensions.  
 referred to as VODataService.  
143    
144  \subsection{The Role in the IVOA Architecture}  This document defines one such extension referred to as VODataService.
145    It provides types to define data services, their underlying tabular
146    structures, their service interfaces, and the location of the data
147    served in space, time, and energy.
148    
149  The IVOA Architecture \citep{note:VOARCH} provides a high-level  
150  view of how IVOA standards work together to connect users and  \subsection{The Role in the IVOA Architecture}
 applications with providers of data and services, as depicted in the  
 diagram in Fig.~\ref{fig:archdiag}.  
151    
152  \begin{figure}  \begin{figure}
153  \centering  \centering
# Line 154  Line 156 
156  \label{fig:archdiag}  \label{fig:archdiag}
157  \end{figure}  \end{figure}
158    
159    Fig.~\ref{fig:archdiag} shows the role VODataService plays within the
160    IVOA Architecture \citep{note:VOARCH}.
161    
162    VODataService directly depends on the following other VO standards
163    (unless specified otherwise, the dependency is on the major version of
164    the cited standard rather than on the exact version):
165    
166    \begin{description}
167    \item[VOResource, v1.1 \citep{2018ivoa.spec.0625P}] VOResource provides
168    the fundamental types and structures extended here.
169    \item[STC, v1.33 \citep{2007ivoa.spec.1030R}] The deprecated mechanism
170    for declaring coverage through STCResourceProfile still uses concepts
171    from verion 1 of the IVOA data model for Space-Time Coordinates.  The
172    updated mechanism has no such dependence any more.
173    \end{description}
174    
175  In this architecture, users can leverage a variety of tools (from the  VODataService is closely related to the following other VO standards:
176  User Layer) to discover archives and services of interest (represented  
177  in the Resource Layer); registries provide the means for this  \begin{description}
178  discovery.  A registry is a repository of descriptions of resources  \item[VOSI, v1.1 \citep{2017ivoa.spec.0524G}] VODataService defines the
179  that can be searched based on the metadata in those descriptions.  The  schema for the responses on the table metadata endpoint.  It also
180  Resource Metadata standard \citep{2007ivoa.spec.0302H} defines the core  defines the ParamHTTP interface type used in the capabilities of most
181  concepts used in the resource descriptions, and the VOResource  standard protocols.
182  standard defines the XML format.  As an  \item[RefTAP, v1.0 \citep{2014ivoa.spec.1208D}] RegTAP maps the concepts
183  extension of VOResource, the VODataService standard, defined in this  defined here into a relational structure.
184  document, specifically supports descriptions of data collections and  \end{description}
 services.    
185    
186  \subsection{Purpose}  \subsection{Purpose}
187    
# Line 676  Line 690 
690  For CatalogService's content model, refer to  For CatalogService's content model, refer to
691  sect.~\ref{sect:CatalogResource}.  sect.~\ref{sect:CatalogResource}.
692    
 \subsection{Coverage}  
 \label{sect:cover}  
   
   
   
693  \subsubsection{DataCollection}  \subsubsection{DataCollection}
694  \label{sect:datacollection}  \label{sect:datacollection}
695    
# Line 700  Line 709 
709  data model was never promoted to an IVOA recommendation, there also is  data model was never promoted to an IVOA recommendation, there also is
710  no properly standardised way of creating such records.  no properly standardised way of creating such records.
711    
712    
713    
714  \subsection{Coverage in Space, Time, and Spectrum}  \subsection{Coverage in Space, Time, and Spectrum}
715    \label{sect:cover}
716    
717  The \xmlel{vs:Coverage} type summarily describes how the data served is  The \xmlel{vs:Coverage} type summarily describes how the data served is
718  distributed on the  distributed on the

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

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