[Volute] r3520 - trunk/projects/dal/SODA

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


Author: jdempsey
Date: Tue Sep  6 11:23:56 2016
New Revision: 3520

Log:
Minor corrections
* spelling and punctuation
* POLY->POLYGON
* CIRC->CIRCLE
* Add previous version entry for PR 1.0

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

Modified: trunk/projects/dal/SODA/SODA.tex
==============================================================================
--- trunk/projects/dal/SODA/SODA.tex	Mon Sep  5 14:28:29 2016	(r3519)
+++ trunk/projects/dal/SODA/SODA.tex	Tue Sep  6 11:23:56 2016	(r3520)
@@ -21,6 +21,7 @@
 
 \editor{Fran\c cois Bonnarel}
 
+\previousversion{PR-SODA-1.0-20160429}
 \previousversion{WD-SODA-1.0-20151221}
 \previousversion{WD-AccessData-1.0-20151021}
 \previousversion{WD-AccessData-1.0-20140730}
@@ -112,9 +113,9 @@
 In the general case, data discovery responses may direct clients to an
 associated DataLink service where access details can be obtained. The
 DataLinks output will in turn provide service descriptor(s) of the
-associated SODA service(s). Service providers may chose this approach
+associated SODA service(s). Service providers may choose this approach
 for several reasons; for example, one entry from data discovery may lead
-to multiple files or resources or access via services such as SODA may
+to multiple files or resources, or access via services such as SODA may
 be considered the primary access mode and direct download is not
 available or discouraged. This scenario is described in detail in
 Section~\ref{sec:disc-links-soda}.
@@ -279,7 +280,7 @@
 \label{sec:examples}
 
 SODA services should provide a DALI-examples resource
-with one example invocation that shows the variety
+with one example invocation that shows the variety of
 operations the service can perform. Example operations using
 the \{sync\} resource and that output a small data stream are
 preferred, as the examples may be used by automatic validators doing
@@ -366,7 +367,7 @@
 The \{sync\} and \{async\} resources accept the same set of
 parameters. Support for multiple values of parameters is optional. 
 If a request includes multiple values for a parameter and the 
-service does not support multipe values for that parameter, the 
+service does not support multiple values for that parameter, the 
 request must fail with the MultiValuedParamNotSupported error listed
 below (\ref{sec:error-codes}). For example, a service may 
 allow only single values for ID but multiple values for cutout parameters. 
@@ -721,7 +722,7 @@
 clients discover applicable SODA services while doing data discovery
 queries.
 
-The DatatLink \citep{std:DataLink} recommendation provides a mechanism
+The DataLink \citep{std:DataLink} recommendation provides a mechanism
 to include ``a description of a SODA service'' using a standard resource
 called a service descriptor. The service descriptor is included in any
 VOTable \citep{std:VOTable} output and can describe the parameters for
@@ -748,10 +749,10 @@
             datatype="char" arraysize="*" value="" />
     <PARAM name="POS" ucd="phys.angArea;obs" 
             datatype="char" arraysize="*" value="" />
-    <PARAM name="CIRC" unit="deg" ucd="phys.angArea;obs" 
+    <PARAM name="CIRCLE" unit="deg" ucd="phys.angArea;obs" 
             datatype="double" arraysize="3" 
             xtype="circle" value="" />
-    <PARAM name="POLY"  unit="deg" ucd="phys.angArea;obs"
+    <PARAM name="POLYGON"  unit="deg" ucd="phys.angArea;obs"
             datatype="double" arraysize="*" 
             xtype="polygon"  value="" />
     <PARAM name="BAND" unit="m" ucd="em.wl" 
@@ -877,7 +878,7 @@
 In this case, the response containing the links will not include all the
 dataset metadata necessary to determine values for SODA filtering
 parameters. While generic service descriptors (see above) are still
-permitted, it is much ore useful if the links response contains data- or
+permitted, it is much more useful if the links response contains data- or
 file-specific service descriptors that make use of the ability to
 include metadata in the parameter descriptions. Thus, the provider will
 normally include one or more data-specific service descritors for each
@@ -927,10 +928,10 @@
 resource (soda-xdk48g) is generated and would be referenced from the
 \texttt{service\_def} column of the links table. Since this is a
 data-specific descriptor, the ID parameter has a fixed value instead of
-a ref attribute, and the CIRC, POLY, and BAND parameters have suggested
+a ref attribute, and the CIRCLE, POLYGON, and BAND parameters have suggested
 values. The suggested values are the nominal maximum values which are
-interpretted as values of the regions or intervals that contain the
-data. For example, the value given for the POLY parameter is the
+interpreted as values of the regions or intervals that contain the
+data. For example, the value given for the POLYGON parameter is the
 bounding polygon for this data. The absence of a POL parameter means
 that polarization cutout is either not supported or not applicable to
 this data.


More information about the Volutecommits mailing list