/[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 5114 by msdemlei, Thu Aug 23 09:56:26 2018 UTC revision 5115 by msdemlei, Thu Aug 23 11:10:38 2018 UTC
# Line 1  Line 1 
1  \documentclass[11pt,a4paper]{ivoa}  \documentclass[11pt,a4paper]{ivoa}
2  \input tthdefs  \input tthdefs
3    % widen up the display a bit so that 75 column listings still fit on
4    % the page
5    \usepackage[width=14cm]{geometry}
6  \usepackage{listings}  \usepackage{listings}
7  \lstloadlanguages{XML}  \lstloadlanguages{XML}
8  \lstset{flexiblecolumns=true,tagstyle=\ttfamily,showstringspaces=False}  \lstset{flexiblecolumns=true,tagstyle=\ttfamily,showstringspaces=False}
# Line 22  Line 25 
25  \author[http://www.ivoa.net/twiki/bin/view/IVOA/TonyLinde]{Tony Linde}  \author[http://www.ivoa.net/twiki/bin/view/IVOA/TonyLinde]{Tony Linde}
26  \author[http://www.ivoa.net/twiki/bin/view/IVOA/GuyRixon]{Guy Rixon}  \author[http://www.ivoa.net/twiki/bin/view/IVOA/GuyRixon]{Guy Rixon}
27    
 \editor{Ray Plante}  
28  \editor{Markus Demleitner}  \editor{Markus Demleitner}
29    \editor{Ray Plante}
30    
31  \previousversion[http://www.ivoa.net/Documents/VODataService/20101202]{REC  \previousversion[http://www.ivoa.net/Documents/VODataService/20101202]{REC
32  1.1}  1.1}
# Line 114  Line 117 
117    
118  \section{Introduction}  \section{Introduction}
119    
120  The VOResource standard \citep{todo:VOR1.1} provides a means of  The VOResource standard \citep{2018ivoa.spec.0625P} provides a means of
121  encoding IVOA Resource Metadata\todo{decouple from RM} in XML.  encoding IVOA Resource Metadata\todo{decouple from RM} in XML.
122  VOResource uses XML Schema \citep{std:XSD} to define  VOResource uses XML Schema \citep{std:XSD} to define
123  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
# Line 220  Line 223 
223         documents used by this description,         documents used by this description,
224  \item the core VOResource metadata,  \item the core VOResource metadata,
225  \item an interface described by the  \item an interface described by the
226         VODataService interface type, \xmlel{vs:ParamHTTP}; this         VODataService type \xmlel{vs:ParamHTTP}; this
227         type can indicate input arguments it supports.         type can indicate input arguments it supports.
228  \item a description of the  \item a description of the
229         coverage, including quantitative coverage         coverage, including quantitative coverage
# Line 245  Line 248 
248  Authors of VOResource instance documents may choose to  Authors of VOResource instance documents may choose to
249  provide a location for the VOResource XML Schema document and its  provide a location for the VOResource XML Schema document and its
250  extensions using the  extensions using the
251  \xmlel{xsi:schemaLocation}</a> attribute.  While the choice of  \xmlel{xsi:schemaLocation} attribute.  While the choice of
252  the location value is the choice of the author, this specification  the location value is the choice of the author, this specification
253  recommends using the VODataService namespace URI as its location URL  recommends using the VODataService namespace URI as its location URL
254  (as illustrated in the example above), as in,  (as illustrated in the example above), as in,
# Line 277  Line 280 
280    
281    
282    
 \begin{admonition}{Note}  
 (todo: remove this; doesn't really apply any more; and there *really*  
 shouldn't be any VODS 1.0 around any more)  
   
 One reason one may \emph{not} be able to use \xmlel{vs}  
        to represent the VODataService schema, version 1.1, is because  
        it is already in defined to represent VODataService v1.0 and  
        cannot be overridden.  At this writing, there are no IVOA  
        applications in which this is the case.  Consult  
        appendix~\ref{vods10-compat} for more details on  
        compatibility issues.  
 \end{admonition}  
   
283    
284  As recommend by the VOResource standard, the  As recommend by the VOResource standard, the
285  VODataService schema sets \xmlel{elementFormDefault="unqualified"}.  VODataService schema sets \xmlel{element\-Form\-Default} to \emph{unqualified}.
286  This means that it is not necessary to qualify element names defined  This means that it is not necessary to qualify element names defined
287  in this schema with a namespace prefix (as there are no global  in this schema with a namespace prefix (as there are no global
288  elements defined).  The only place it is usually needed is as a  elements defined).  The only place it is usually needed is as a
# Line 988  Line 978 
978                                
979  \item[Comment]  \item[Comment]
980                    For instance, the Johnson V waveband (480 .. 730 nm)                    For instance, the Johnson V waveband (480 .. 730 nm)
981                    would be specified as {"}2.72e-19 4.14e-19{"}                    would be specified as “2.72e-19 4.14e-19“
982                                
983    
984  \end{description}  \end{description}
# Line 1031  Line 1021 
1021                   1 micron <= wavelength <= 100 micons                   1 micron <= wavelength <= 100 micons
1022                                
1023  \item[Optical]  \item[Optical]
                  0.3 microns <= wavelength <= 1 micon;  
1024                   300 nm <= wavelength <= 1000 nm;                   300 nm <= wavelength <= 1000 nm;
                  3000 Angstroms <= wavelength <= 10000 Angstroms  
1025                                
1026  \item[UV]  \item[UV]
1027                   0.1 microns <= wavelength <= 0.3 micon;                   100 nm <= wavelength <= 300 nm;
                  1000 nm <= wavelength <= 3000 nm;  
                  1000 Angstroms <= wavelength <= 30000 Angstroms  
1028                                
1029  \item[EUV]  \item[EUV]
                  100 Angstroms <= wavelength <= 1000 Angstroms;  
1030                   12 eV <= energy <= 120 eV                   12 eV <= energy <= 120 eV
1031                                
1032  \item[X-ray]  \item[X-ray]
                  0.1 Angstroms <= wavelength <= 100 Angstroms;  
1033                   0.12 keV <= energy <= 120 keV                   0.12 keV <= energy <= 120 keV
1034                                
1035  \item[Gamma-ray]  \item[Gamma-ray]
# Line 1434  Line 1418 
1418    
1419  The definitions of the \xmlel{tableset} elements used in  The definitions of the \xmlel{tableset} elements used in
1420  the \xmlel{vs:DataCollection} and  the \xmlel{vs:DataCollection} and
1421  \xmlel{vs:CatalogService} types  \xmlel{vs:Catalog\-Ser\-vice} types
1422  constrain certain names to be unique.  In particular, all schema names  constrain certain names to be unique.  In particular, all schema names
1423  within a \xmlel{tableset} element must be unique, and all  within a \xmlel{tableset} element must be unique, and all
1424  table names within a \xmlel{tableset} element must be  table names within a \xmlel{tableset} element must be
# Line 2369  Line 2353 
2353    
2354    
2355  \subsubsection{Table Column Data Types}  \subsubsection{Table Column Data Types}
2356  \label{tbldatatypes}  \label{sect:tbldatatypes}
2357    
2358    
2359  The VODataService schema defines two XML types that derive from  The VODataService schema defines two XML types that derive from

Legend:
Removed from v.5114  
changed lines
  Added in v.5115

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