[Volute] r3943 - trunk/projects/dal/DALI

Volute commit messages volutecommits at g-vo.org
Thu Apr 13 07:56:35 CEST 2017


Author: pdowler.cadc
Date: Thu Apr 13 07:56:35 2017
New Revision: 3943

Log:
removed repetition of UWS spec, change vocab url from ivoid to http, remove extraneous contet from continuation example, remove VOSI-tables scalability comment, change max circle radius from 90 to180 (all sky), clarify UPLOAD URI scheme requirements and require http or https for sites that must switch to https, fix some other awkward senetences

Modified:
   trunk/projects/dal/DALI/DALI.tex
   trunk/projects/dal/DALI/Makefile

Modified: trunk/projects/dal/DALI/DALI.tex
==============================================================================
--- trunk/projects/dal/DALI/DALI.tex	Wed Apr 12 14:02:09 2017	(r3942)
+++ trunk/projects/dal/DALI/DALI.tex	Thu Apr 13 07:56:35 2017	(r3943)
@@ -184,8 +184,7 @@
 
 As specified in UWS, a job is created by using the HTTP POST method to modify 
 the job list. The response will always be an HTTP redirect (status code 303) and 
-the Location (HTTP header) will contain the URL to the job (a child resource of 
-the job list).
+the Location (HTTP header) will contain the URL to the job.
 
 \begin{verbatim}
 POST http://example.com/base/async-jobs
@@ -317,15 +316,18 @@
 they desire in addition and within the example elements defined here.
 
 The elements containing examples must be descendants of an element that has a 
-\xmlel{vocab} attribute with the value equal to the DALI-examples capability identifier 
-(above), for example:
+\xmlel{vocab} attribute with the value as shown below:
 
 \begin{lstlisting}[language=XML]
-<div vocab="ivo://ivoa.net/std/DALI#examples">
+<div vocab="http://www.ivoa.net/rdf/examples">
 ...
 </div>
 \end{lstlisting}
 
+In future, this URL may resolve to an RDFa vocabulary document in human and 
+machine-readable format(s) and if so will contain the normative list of values 
+for the property attribute and will supersede the ones specified below.
+
 No other \xmlel{vocab} attributes are allowed in the document. Each example resides in 
 an element that has a \xmlel{typeof} attribute with the value
 \emph{example}. All such elements 
@@ -472,22 +474,9 @@
 examples).
 
 \begin{lstlisting}[language=XML,basicstyle=\footnotesize]
-<div vocab="ivo://ivoa.net/std/DALI#examples">
+<div vocab="http://www.ivoa.net/rdf/examples">
   <div id="x" resource="#x" typeof="example">
-   <h2 property="name">Synchronous TAP query</h2>
-     <p property="capability">ivo://ivoa.net/std/TAP/v1.0</p>
-     <p property="generic-parameter" typeof="keyval">
-        <span property="key">REQUEST</span>=<span
-            property="value">doQuery</span>
-     </p>
-     <p property="generic-parameter" typeof="keyval">
-        <span property="key">LANG</span>=<span
-            property="value">ADQL</span>
-     </p>
-     <p property="generic-parameter" typeof="keyval">
-        <span property="key">QUERY</span>=<span
-          property="value">SELECT * from tap_schema.tables</span>
-     </p>
+    ...
   </div>
   <a property="continuation"
      href="simple_examples.html">Simple examples</a>
@@ -592,9 +581,7 @@
 
 A concrete DAL service specification will specify if the VOSI-tables resource is 
 permitted or required and may restrict the resource name or location.
-The current VOSI-tables specification has some scalablity 
-issues for services with many or large tables, so that specification is subject 
-to change in future. Since DAL services with a VOSI-tables resource will specify 
+Since DAL services with a VOSI-tables resource will specify 
 in the capabilities which version they are using, DAL services can make use of 
 new versions without change to the DAL service specification.
 
@@ -796,7 +783,8 @@
 \xmlel{FIELD} element: \verb|datatype="double"| or \verb|datatype="float"|, \verb|arraysize="3"|,
 \verb|xtype="circle"|. For circles 
 in a spherical coordinate system, the values are ordered as: longitude latitude 
-radius; longitude values must fall within [0,360], latitude values within [-90,90], and radius values in (0, 90]. For example:
+radius; longitude values must fall within [0,360], latitude values 
+within [-90,90], and radius values in (0,180]. For example:
 
 \begin{verbatim}
 12.3 45.6 0.5
@@ -946,8 +934,8 @@
 simple strings made up of alphabetic, numeric, and the underscore characters 
 only and must start with an alphabetic character.
 
-Services that implement UPLOAD must support http as a URI scheme (e.g., must 
-support treating an http URI as a URL). A VOSpace URI (vos:<something>)  is a 
+Services that implement UPLOAD must support http or https as a URI scheme. 
+A VOSpace URI (vos:<something>)  is a 
 more generic example of a URI that requires more service-side functionality; 
 support for the vos scheme is optional.
 
@@ -992,9 +980,9 @@
 
 Services may limit the size and number of uploaded resources; if the service 
 refuses to accept the upload, it must respond with an error as described in 
-Section \ref{sec:response-error}. Specific service specifications specify how uploaded resources are 
-referenced in other request parameters (for example, in a query), and 
-interpreted.
+Section \ref{sec:response-error}. Concrete service specifications will 
+typically provide a mechanism for referring to uploaded resources (e.g. in 
+other request parameters) where necessary.
 
 \subsubsection{RUNID}
 \label{sec:RUNID}
@@ -1013,11 +1001,12 @@
 
 \section{Responses}
 \label{sec:responses}
-All DAL service requests eventually result in one of three kinds of responses: 
+All DAL service requests eventually (after zero or more HTTP redirects) result 
+in one of three kinds of responses: 
 successful HTTP status code (200) and a service- and resource-specific 
-representation of the results, an HTTP status code and a standard error document 
-(see below) or a  service- and resource-specific error document, or a redirect 
-HTTP status code (302 or 303) with a URL in the HTTP Location header.
+representation of the results, or an HTTP status code and a standard error 
+document (see below), or an HTTP status code and a service- and 
+resource-specific error document.
 
 \subsection{Successful Requests}
 \label{sec:response-ok}

Modified: trunk/projects/dal/DALI/Makefile
==============================================================================
--- trunk/projects/dal/DALI/Makefile	Wed Apr 12 14:02:09 2017	(r3942)
+++ trunk/projects/dal/DALI/Makefile	Thu Apr 13 07:56:35 2017	(r3943)
@@ -7,7 +7,7 @@
 DOCVERSION = 1.1
 
 # Publication date, ISO format; update manually for "releases"
-DOCDATE = 2016-11-01
+DOCDATE = 2017-04-12
 
 # What is it you're writing: NOTE, WD, PR, or REC
 DOCTYPE = PR


More information about the Volutecommits mailing list