/[volute]/trunk/projects/grid/vospace/doc/VOSpace.tex
ViewVC logotype

Diff of /trunk/projects/grid/vospace/doc/VOSpace.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 3103 by major.brian, Sun Oct 11 20:10:22 2015 UTC revision 3104 by major.brian, Sun Oct 11 21:49:13 2015 UTC
# Line 504  Line 504 
504      \item \emph{param}: a set of parameters for the capability      \item \emph{param}: a set of parameters for the capability
505  \end{itemize}  \end{itemize}
506    
507  \subsubsection{Example use cases}  \subsubsection{Example capability use cases}
508  \label{subsubsec:example use cases}  \label{subsubsec:example capability use cases}
509  A ContainerNode containing image files may offer a DAL SIAP capability so that the images in the container can be accessed using a SIAP service. In this way, a user could create a (DAL enabled) Container in VOSpace, transfer some images into it and then query the set of images using the SIAP interface.  A ContainerNode containing image files may offer a DAL SIAP capability so that the images in the container can be accessed using a SIAP service. In this way, a user could create a (DAL enabled) Container in VOSpace, transfer some images into it and then query the set of images using the SIAP interface.
510    
511  Another example is a DataNode that provides a OpenStack Swift capability so that the OpenStack service API is exposed on that node.  Another example is a DataNode that provides a OpenStack Swift capability so that the OpenStack service API is exposed on that node.
# Line 609  Line 609 
609      \item \emph{original}: a set of name-value pairs that can be used to specify additional arguments for the View      \item \emph{original}: a set of name-value pairs that can be used to specify additional arguments for the View
610  \end{itemize}  \end{itemize}
611    
612  \subsubsection{Example use cases}  \subsubsection{Example view use cases}
613  \label{subsubsec:example use cases}  \label{subsubsec:example view use cases}
614  A simple VOSpace system that stores data as a binary files can just return the contents of the original file. The client supplies a View identifier when it imports the data, and the service uses this information to describe the data to other clients.  A simple VOSpace system that stores data as a binary files can just return the contents of the original file. The client supplies a View identifier when it imports the data, and the service uses this information to describe the data to other clients.
615    
616  A file based system can use the special case identifier  A file based system can use the special case identifier
# Line 2201  Line 2201 
2201    <vos:provides />    <vos:provides />
2202  </vos:node>  </vos:node>
2203  * Closing connection #0  * Closing connection #0
2204  end{lstlisting}  \end{lstlisting}
2205    
2206  \subsubsection{findNodes}  \subsubsection{findNodes}
2207  \label{subsubsec:findnodes}  \label{subsubsec:findnodes}
# Line 2440  Line 2440 
2440      \item \emph{TARGET}: The value is the URI of the target node      \item \emph{TARGET}: The value is the URI of the target node
2441          \begin{itemize}          \begin{itemize}
2442             \item Example:  vos://example.com$\mathtt{\sim}$vospace/mydata1             \item Example:  vos://example.com$\mathtt{\sim}$vospace/mydata1
2443          \end {itemize}          \end{itemize}
2444      \item \emph{DIRECTION}: pushToVoSpace      \item \emph{DIRECTION}: pushToVoSpace
2445      \item \emph{PROTOCOL}: The standard URI of the protocol to use (see section ~\ref{subsubsec:standard protocols})      \item \emph{PROTOCOL}: The standard URI of the protocol to use (see section ~\ref{subsubsec:standard protocols})
2446          \begin{itemize}          \begin{itemize}
2447             \item Example: ivo://ivoa.net/vospace/core\#httpput             \item Example: ivo://ivoa.net/vospace/core\#httpput
2448          \end {itemize}          \end{itemize}
2449  \end{itemize}  \end{itemize}
2450  The service SHALL respond with the job containing the transfer results in the response body.  (See Example 3)  The service SHALL respond with the job containing the transfer results in the response body.  (See Example 3)
2451    
# Line 3037  Line 3037 
3037      \item \emph{TARGET}: The value is the URI of the target node      \item \emph{TARGET}: The value is the URI of the target node
3038          \begin{itemize}          \begin{itemize}
3039             \item Example:  vos://example.com$\mathtt{\sim}$vospace/mydata1             \item Example:  vos://example.com$\mathtt{\sim}$vospace/mydata1
3040          \end {itemize}          \end{itemize}
3041      \item \emph{DIRECTION}: pullFromVoSpace      \item \emph{DIRECTION}: pullFromVoSpace
3042      \item \emph{PROTOCOL}: The standard URI of the protocol to use (see section ~\ref{subsubsec:standard protocols})      \item \emph{PROTOCOL}: The standard URI of the protocol to use (see section ~\ref{subsubsec:standard protocols})
3043          \begin{itemize}          \begin{itemize}
3044             \item Example: ivo://ivoa.net/vospace/core\#httpget             \item Example: ivo://ivoa.net/vospace/core\#httpget
3045          \end {itemize}          \end{itemize}
3046  \end{itemize}  \end{itemize}
3047  The service SHALL respond with the job containing the transfer results in the response body.  (See Example 3)  The service SHALL respond with the job containing the transfer results in the response body.  (See Example 3)
3048  If the parameter key value REQUEST=redirect is included with the other transfer parameters, the service SHALL respond with an immediate redirect to the preferred protocol endpoint for data download.  (See Example 4)  If the parameter key value REQUEST=redirect is included with the other transfer parameters, the service SHALL respond with an immediate redirect to the preferred protocol endpoint for data download.  (See Example 4)
# Line 3902  Line 3902 
3902  8 & A DataNode has elements: uri, properties, capabilities, accepts, provides & ~\ref{subsec:nodes and node types} \\ \hline  8 & A DataNode has elements: uri, properties, capabilities, accepts, provides & ~\ref{subsec:nodes and node types} \\ \hline
3903  9 & A LinkNode has elements: uri, properties, capabilities and target & ~\ref{subsec:nodes and node types}* \\ \hline  9 & A LinkNode has elements: uri, properties, capabilities and target & ~\ref{subsec:nodes and node types}* \\ \hline
3904  10 & A ContainerNode and a LinkNode have no data bytes associated with them & ~\ref{subsec:nodes and node types}* \\ \hline  10 & A ContainerNode and a LinkNode have no data bytes associated with them & ~\ref{subsec:nodes and node types}* \\ \hline
3905  11 & A VOSpace service parses XML representations of all node types & ~\ref{subsec:node and nodes types} \\ \hline  11 & A VOSpace service parses XML representations of all node types & ~\ref{subsec:nodes and node types} \\ \hline
3906  12 & A VOSpace services does not throw a XML parser error in response to requests about unsupported node types & ~\ref{subsec:nodes and node types} \\ \hline  12 & A VOSpace services does not throw a XML parser error in response to requests about unsupported node types & ~\ref{subsec:nodes and node types} \\ \hline
3907  13 & A Property has elements:uri, endpoint and optional readonly flag & ~\ref{subsec:properties} \\ \hline  13 & A Property has elements:uri, endpoint and optional readonly flag & ~\ref{subsec:properties} \\ \hline
3908  14 & URIs must be valid (and unique) & ~\ref{subsubsec:property identifiers}, ~\ref{subsubsec:capability identifiers}, ~\ref{subsubsec:view identifiers}, ~\ref{subsubsec:protocol identifiers}, ~\ref{subsubsec:createnode}, ~\ref{subsubsec:pushtovospace}, ~\ref{subsubsec:pulltovospace} \\ \hline  14 & URIs must be valid (and unique) & ~\ref{subsubsec:property identifiers}, ~\ref{subsubsec:capability identifiers}, ~\ref{subsubsec:view identifiers}, ~\ref{subsubsec:protocol identifiers}, ~\ref{subsubsec:createnode}, ~\ref{subsubsec:pushtovospace}, ~\ref{subsubsec:pulltovospace} \\ \hline
# Line 3924  Line 3924 
3924  \hline  \hline
3925  \textbf{Item} & \textbf{Description} & \textbf{Occurs in section(s)} \\ \hline  \textbf{Item} & \textbf{Description} & \textbf{Occurs in section(s)} \\ \hline
3926  26 & A Protocol has elements: uri and and endpoint & ~\ref{subsec:protocols} \\ \hline  26 & A Protocol has elements: uri and and endpoint & ~\ref{subsec:protocols} \\ \hline
3927  27 & text/xml are represented by the specified URIs & ~\ref{subsubsec:text/xml} \\ \hline  27 & Standard Protocols are represented by the specified URIs & ~\ref{subsubsec:standard protocols} \\ \hline  
3928  28 & A Transfer UWS Job representation has elements: target, direction, view, protocol and keepBytes & ~\ref{subsec:transfers} \\ \hline  28 & A Transfer UWS Job representation has elements: target, direction, view, protocol and keepBytes & ~\ref{subsec:transfers} \\ \hline
3929  29 & A Transfer results representation has elements: target, direction, view, and protocol & ~\ref{subsec:transfers} \\ \hline  29 & A Transfer results representation has elements: target, direction, view, and protocol & ~\ref{subsec:transfers} \\ \hline
3930  30 & A server responds with a fault if it is unable to handle any of the requested protocols in a data transfer & ~\ref{subsubsec:service-initiated transfers}, ~\ref{subsubsec:client-initiated transfers} \\ \hline  30 & A server responds with a fault if it is unable to handle any of the requested protocols in a data transfer & ~\ref{subsubsec:service-initiated transfers}, ~\ref{subsubsec:client-initiated transfers} \\ \hline

Legend:
Removed from v.3103  
changed lines
  Added in v.3104

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