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

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


Author: jdempsey
Date: Wed Sep  7 10:46:05 2016
New Revision: 3529

Log:
Correct accessURL case in examples, update section 1.3 title, small edits in sections 1.1.1, 4.1 and 4.3

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

Modified: trunk/projects/dal/SODA/SODA.tex
==============================================================================
--- trunk/projects/dal/SODA/SODA.tex	Tue Sep  6 18:07:08 2016	(r3528)
+++ trunk/projects/dal/SODA/SODA.tex	Wed Sep  7 10:46:05 2016	(r3529)
@@ -95,7 +95,7 @@
 \subsubsection{SODA Service in the Registry}
 
 Resources in the IVOA Registry may include SODA capabilites. In order to
-use such services, clients require a priori knowledge of suitable
+use such services, clients require prior knowledge of suitable
 identifiers that are usable with a registered SODA service. This
 scenario is described in more detail below in
 Section~\ref{sec:reg-soda}.
@@ -151,7 +151,9 @@
 This is a special case of \ref{sec:use-cube},
 where the cutout is only in the spectral axis.
 
-\subsection{Provide the data in different formats}
+\subsection{Anticipated Future Use Cases}
+
+\subsubsection{Provide the data in different formats}
 
 Examples are images in PNG, or JPEG instead of FITS and spectra in csv,
 FITS or VOTable.     
@@ -337,17 +339,17 @@
   
   <capability standardid="ivo://ivoa.net/std/SODA#sync-1.0">
     <interface xsi:type="vod:ParamHTTP" role="std" version="1.0">
-      <accessurl use="full">
+      <accessURL use="full">
         http://example.com/data/sync
-      </accessurl>
+      </accessURL>
     </interface>
   </capability>
   
   <capability standardid="ivo://ivoa.net/std/SODA#async-1.0">
     <interface xsi:type="vod:ParamHTTP" role="std" version="1.0">
-      <accessurl use="full">
+      <accessURL use="full">
         http://example.com/data/async
-      </accessurl>
+      </accessURL>
     </interface>
   </capability>
 </capabilities>
@@ -792,7 +794,7 @@
 \label{sec:reg-soda}
 
 Resources in the IVOA Registry may include SODA capabilites. In order to
-use such services, clients require a priori knowledge of suitable
+use such services, clients require prior knowledge of suitable
 identifiers that are usable with a registered SODA service. Finding and
 using a SODA service via the registry is not expected to be a common
 usage pattern unless 
@@ -838,12 +840,12 @@
 \label{sec:disc-links-soda}
 
 In the general case, data discovery responses may contain usable HTTP
-URL(s) (e.g. in an Obscore \citep{std:OBSCORE} response, the
+URL(s), e.g. in an Obscore \citep{std:OBSCORE} response, the
 \texttt{access\_url} contains a link that invokes a DataLink
 \citep{std:DataLink} links resource and the access\_format column
-contains the standard DataLink \citep{std:DataLink} content-type) or the
-document may contain a service descriptor for an associated DataLink
-links capability. For example, the latter:
+contains the standard DataLink \citep{std:DataLink} content-type. Alternatively the
+response document may contain a service descriptor for an associated DataLink
+links capability. The following example shows the second form:
 
 \begin{lstlisting}[language=XML]
 <RESOURCE type="results">


More information about the Volutecommits mailing list