# [Volute] r3558 - trunk/projects/dal/SODA

Volute commit messages volutecommits at g-vo.org
Wed Oct 26 18:05:46 CEST 2016

Author: francois
Date: Tue Sep 20 15:18:40 2016
New Revision: 3558

Log:

Modified:
trunk/projects/dal/SODA/SODA.tex

Modified: trunk/projects/dal/SODA/SODA.tex
==============================================================================
--- trunk/projects/dal/SODA/SODA.tex	Tue Sep 20 07:38:23 2016	(r3557)
+++ trunk/projects/dal/SODA/SODA.tex	Tue Sep 20 15:18:40 2016	(r3558)
@@ -449,7 +449,8 @@
\label{sec:POS}

The POS parameter defines the positional region(s) to be
-extracted from the data. The value is made up of a shape
+extracted from the data using the \xtype{region}
+xtype defined in \citep{std:DALI}. The value is made up of a shape
keyword followed by coordinate values . The
allowed shapes are:

@@ -650,25 +651,19 @@

Filtering parameters drive the generation of virtual datasets.  The ObsCore model is perfectly valid to  describe virtual data that SODA is able to generate. Hence all SODA Filtering parameters are coupled with some Obscore model concepts.

-The spatial parameters (CIRCLE, POLYGON and POS) constrain the spatial support of the output virtual dataset. (The ObsCore attribute name is s\_region - utype obscore:Char.SpatialAxis.Coverage.Support.Area'' -). The spatial support of the output dataset is included in the spatial support of the archived dataset.
+The spatial parameters (CIRCLE, POLYGON and POS) constrain the spatial support of the output virtual dataset. (The ObsCore attribute name is s\_region - utype "obscore:Char.SpatialAxis.Coverage.Support.Area" -). The spatial support of the output dataset is included in the spatial support of the archived dataset.
+

-<<<<<<< .mine
The TIME parameter constrains the time bounds of the SODA output virtual dataset (Obscore feature of utype: \\
"Char.TimeAxis.Coverage.Bounds.Limits"). The time bounds of the output dataset are limited by the time bounds of the archived dataset.
The BAND parameter constrains the spectral bounds of the SODA output virtual
-dataset (Obscore feature of utype "Char.spectralAxis.Coverage.Bounds.Limits").
-The spectral bounds of the output datasets are limited by the spectral bounds of
-the archived dataset.
-=======
-The TIME parameter constrains the time bounds of the SODA output virtual dataset (Obscore feature of utype "Char.TimeAxis.Coverage.Bounds.Limits"). The time bounds of the output dataset are limited by the time bounds of the archived dataset.
-The BAND parameter constrains the spectral bounds of the SODA output virtual
-dataset (Obscore feature of utype "Char.spectralAxis.Coverage.Bounds.Limits").
+dataset (Obscore feature of utype:  \\ "Char.spectralAxis.Coverage.Bounds.Limits").
The spectral bounds of the output datasets are limited by the spectral bounds of
the archived dataset.
->>>>>>> .r3531
+

The POL parameter constrain the  list of polarization states in  the output virtual dataset (ObsCore feature of name "pol\_states" \\
-- utypeobscore:Char.PolarizationAxis.stateList''). The
+- utype "obscore:Char.PolarizationAxis.stateList"). The
valid values for this param are included in the list given by the value
of the pol\_states attribute of the archived dataset.

@@ -687,7 +682,7 @@
in table~\ref{table:standardpars}.  Instructions for how to propose
additional standard parameters are given on the landing page of the IVOA
DAL working group\footnote{At the time of writing, this is
-\href{http://wiki.ivoa.net/twiki/bin/view/IVOA/IvoaResReg}{http://wiki.ivoa.net/twiki/bin/view/IVOA/IvoaResReg}.}.
+\href{http://wiki.ivoa.net/twiki/bin/view/IVOA/DefiningServiceParameters}{http://wiki.ivoa.net/twiki/bin/view/IVOA/DefiningServiceParameters}.}.

\begin{table}[mht]
\begin{tabular}{l l l l}
@@ -730,7 +725,7 @@
Here we describe these strategies and show how to use the standards
together.

-Wthin the IVOA architecture, SODA servces could be found and used in two
+Within the IVOA architecture, SODA services could be found and used in two
ways. First, a SODA service could be found in the IVOA Registry and used
directly. Second, a description of a SODA service may be found along
with specific dataset metadata; this is the primary anticipated usage:
@@ -777,7 +772,7 @@
datatype="double" arraysize="2"
xtype="interval" value="" />
<PARAM name="POL" ucd="meta.code;phys.polarization"
-            datatype="char" arraysize="2*" value="" />
+            datatype="char" arraysize="*" value="" />
</GROUP>
</RESOURCE>
\end{lstlisting}
@@ -785,7 +780,7 @@
This service descriptor is generic because the ID parameter uses a
\xmlel{ref} attribute to specify that identifier values come from
elsewhere in the document (usually this refers to a FIELD element that
-descrbes a table column within another RESOURCE element). Thus, this
+describes a table column within another RESOURCE element). Thus, this
descriptor can be used with any ID values in that column.

The PARAM with \texttt{name="standardID"} specifies that this service is
`