\documentclass{beamer}
\mode<presentation>{
  \usetheme{Copenhagen}
  % or ...
%   \usecolortheme{seagull}

  \setbeamercovered{transparent}
  % or whatever (possibly just delete it)
}

\usepackage[english]{babel}
% or whatever

\usepackage[latin1]{inputenc}
% or whatever

\usepackage{times}
\usepackage[T1]{fontenc}

\usepackage{soul}
\usepackage{beamertexpower}

\title % (optional, use only with long paper titles)
{SimDAP et S3}
\subtitle{Can they merge?}

\author[R. Wagner] % (optional, use only with lots of authors)
{Rick Wagner}

\institute[Universities of California, San Diego] % (optional, but mostly needed)
{
  Laboratory for Computational Astrophysics,\\
  San Diego Supercomputer Center \\
}
\date[SimDAP] % (optional)
{May 25, 2009}

\subject{Talks}

\begin{document}

\begin{frame}[t]
  \titlepage
\end{frame}

\section{Overview}

\begin{frame}[t]
  \frametitle{SimDAP Summary}
  \begin{itemize}
    \item Goals
      \begin{itemize}
      \item Provide a service standard for retrieving simulation data
      \item Mimic other second generation DAL protocols (e.g., TAP, SSAP, etc.)
      \item Low technical overhead for implementation
      \end{itemize}

    {\item Important Data Model Elements}
      \begin{description}
      \item[Protocol] A piece of software (Enzo, Gadge, halo finders)
      \item[Experiment] (i.e., Simulation) the process of running a piece of software with a set of input parameters
      \item[Snapshot] Results of the simulation at some point in time. Could be in files or a database
      \end{description}
    \end{itemize}
\end{frame}

\begin{frame}[t]
  \frametitle{Current SimDAP Operations}
  \begin{tabular}{ l | l | l  }
    {\small Required?} & Operation &  {\small Input Parameters} \\ \hline
    Yes & GetAvailability &  \\
    Yes & GetCapabilties &  \\
    Yes & ListExperiments &  {\tiny {\tt INPUTDATASET} (O) }\\
    Yes & ListSnapshots & {\tiny {\tt EXPERIMENT} (R) } \\
    Yes & QueryData & {\tiny {\tt EXPERIMENT} (R), {\tt SNAPSHOT} (O), {\tt PROPERTIES} (O) }\\
    No & Cutout & {\tiny {\tt EXPERIMENT} (R), {\tt SNAPSHOT} (O), {\tt PROPERTIES} (O), {\tt VOLUME} (O)} \\
    No & Preview & {\tiny {\tt EXPERIMENT} (R), {\tt SNAPSHOT} (O), {\tt PROPERTIES} (O) }\\
    No & Custom & {\tiny {\tt EXPERIMENT} (R), {\tt SNAPSHOT} (O), {\tt PROPERTIES} (O) }\\
  \end{tabular}
\end{frame}

\begin{frame}[t]
  \frametitle{VOTable Response}
  \begin{itemize}
    {\item My current suggestion is for nested RESOURCE elements}
       \begin{itemize}
        {\item RESOURCE utype=''simdb:Simulation''}
     \begin{itemize}
        {\item RESOURCE utype=''simdb:Snapshot'}
        {\item RESOURCE utype=''simdb:Snapshot'}
      \end{itemize}
       \end{itemize}
     {\item However, this is very different from other DAL services,}
    {\item and is harder for client tools to interpret.}
    {\item But I think this is the correct way to serialize the data
      model to XML, and for Claudio's TDFF}
  \end{itemize}
\end{frame}

\begin{frame}[t]
  \frametitle{Comments on S3}
  \begin{itemize}
    {\item Focuses user interaction, but}
    \begin{itemize}
      {\item each operation should be independent, i.e., recursion is
        optional and automatable.}
    \end{itemize}
    {\item Very similar to SIAP, SSAP with custom parameters}
    {\item Likewise, VODataService supports a complete description of
      tables and parameters.}
  \end{itemize}
\end{frame}

\section{Proposal}
\begin{frame}[t]
  \frametitle{Proposal}
  Priority: {\emph{One}} service for simulation (theory) data access (I don't care
  what it's called).
  \begin{block}{Two Purposes}
    \begin{description}
      {\item[A:] Data access to existing data, including pre-defined
        operations (e.g., preview, cutout)}
      {\item[B:] Self-describing custom operations
        \begin{itemize}
          {\item special operations on existing data (halo finding,
            ionization levels)}
          {\item parameterized queries for data ($h_0 < 0.7$)}
          {\item dynamically generating data (spectra)}
        \end{itemize}
      }
    \end{description}   
\end{block}
\end{frame}

\begin{frame}[t]
  \frametitle{Key Points/Ideas}
  \begin{itemize}
    {\item Service response is the same for all data queries both SimDAP-like
      and S3-like.}
    {\item Push desciptions of the data to the other side of the
      access URL  (cómo S3).}
    {\item Access URL can lead to anything\ldots
      \begin{itemize}
        {\item \ldots image}
        {\item \ldots VOTable of spectra, particles, etc.}
        {\item \ldots file describing binary data, VOTable con un TDFF description,
          VisIVO binary table and data.}
      \end{itemize}
    }
    {\item Describing custom operations (S3-like) is done using GetCapabilites.}
  \end{itemize}
\end{frame}

\begin{frame}[t]
  \frametitle{Importance of the Data Model}
  \begin{itemize}
    {\item Key Point: All theory tools should talk the same language;
      the woorden and concepten come from the data model.}
    {\item Queries for existing data are really queries against the data
      model.}   
    {\item Service operations which modify or create data are protocols.}
    {\item Calling these operations creates a new experiment.}
  \end{itemize}
\end{frame}

\begin{frame}[t]
  \frametitle{Relax}
  \begin{itemize}
    {\item Using the data model doesn't require managing a relational
      database.}
    {\item Using the data model doesn't mean a different XML format.}
    {\item But, using the concepts from the data model means that services
      can be related.}
    {\item E.g., standard SimDAP operation can use data from a SimDB service.}
  \end{itemize}
\end{frame}

\section{Summary}

\begin{frame}[t]
  \frametitle{One Data Access Service}
  \begin{itemize}
    {\item My suggestion: Merge S3 and SimDAP.}
    {\item Can be view as S3 plus some standard operation,}
    {\item or, as SimDAP, plus service-defined custom operations.}
    {\item Either way, service return access to theory data.}
    {\item Unified interface and response means clients can access
      more services.}
  \end{itemize}
\end{frame}

\begin{frame}[t]
  \frametitle{Questions \& Decisions}
  \begin{enumerate}
    {\item Is this reasonable, does it meet our needs?}
    {\item Can we use the simulation data model?}
    {\item Pick a name (again, I don't care what it is).}
    {\item Agree on required and optional service operations.}
    {\item What are the required and suggested columns of the VOTable
      response?}
    {\item Implementations, VODataService extension schema, lots of talking\ldots}
  \end{enumerate}
\end{frame}

\begin{frame}[t]
  \frametitle{Discussion Time}
  La Vache Qui Rit image removed to avoid copyright infringement.
\end{frame}

\end{document}
