/[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 5160 by msdemlei, Thu Oct 4 15:37:24 2018 UTC revision 5161 by msdemlei, Fri Oct 5 11:27:11 2018 UTC
# Line 58  Line 58 
58  VOResource \citep{2008ivoa.spec.0222P} using XML Schema.  VOResource \citep{2008ivoa.spec.0222P} 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.  This coverage description  sky as well as cover frequency and time.  
62  leverages heavily the Space-Time Coordinates (STC) standard  VODataService also enables detailed
 schema\todo{Fix this}.  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
65  types will be particularly useful in describing services that support  types will be particularly useful in describing services that support
# Line 130  Line 129 
129  \section{Introduction}  \section{Introduction}
130    
131  The VOResource standard \citep{2018ivoa.spec.0625P} provides a means of  The VOResource standard \citep{2018ivoa.spec.0625P} provides a means of
132  encoding IVOA Resource Metadata\todo{decouple from RM} in XML.  encoding resource metadata as defined by DataCite \citep{std:DataCite40}
133    and the VO-specific IVOA Resource Metadata \citep{2007ivoa.spec.0302H} in XML.
134  VOResource uses XML Schema \citep{std:XSD} to define  VOResource uses XML Schema \citep{std:XSD} to define
135  most of the XML syntax rules (while a few of the syntax rules are  most of the XML syntax rules (while a few of the syntax rules are
136  outside the scope of Schema).  VOResource also describes mechanisms  outside the scope of Schema).  VOResource also describes mechanisms
# Line 330  Line 330 
330    
331  \begin{bigdescription}  \begin{bigdescription}
332  \item[\xmlel{vs:DataCollection}]  \item[\xmlel{vs:DataCollection}]
333  This resource declares the existence of a collection of data, what  This resource was used in version 1.1 of this standard to define simple
334         it represents, and how to get it.  The access to the data may be  collections of data, perhaps available through ftp services or offline.
335         limited to a human-readable web page (given by  It might still be used as such, although the utility of such a
336         \xmlel{content/referenceURL}); however, if the  registration is questioinable at present.  With the Endorsed Note on
337         contents of the collection are available statically via a  discovering data collections \citep{todo:DDC}, a more capabable type for
338         URL (e.g. an FTP URL to a directory containing all the files),  reigstering data collections independent of services is necessary, and
339         that URL can be provided.  It can also provide pointers to  in general it is desirable to attach actionable properties (i.e.,
340         other IVOA registered services that can be used to access the data.  capabilities) to resource records.  Therefore, version 1.2 of
341         \todo{deprecate}  VODataService deprecates \xmlel{vs:DataCollection} for use with data
342    available online.  Use \xmlel{vs:TODOTODO} instead, with auxiliary
343    capabilities if available through IVOA standard services, or with a
344    basic capability having a WebBrowser interface if only nonstandard
345    access modes are supported.
346          
347    
348  \item[\xmlel{vs:StandardSTC}]  \item[\xmlel{vs:StandardSTC}]
349  This resource type was intended to declare standard combinations of  This resource type was intended to declare standard combinations of

Legend:
Removed from v.5160  
changed lines
  Added in v.5161

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