Server-side Functions

From OPeNDAP Documentation

1 Server-side Functions Working Group

1.1 Motivation

May different OPeNDAP server implementations include the ability to request that the server process the data before returning the data to the requesting client. In some implementations, the client requests the processing by embedding the instructions into the URL of the request (GDS, F-TDS) . Other implementations favor putting the processing request into the query string of the URL(pyDAP, I think).

This working group will explorer the feasibility of developing a single method and syntax to request server-processing for common types of transformations. For client writers and more importantly for users, this would be a tremendous advantage to be able to make server-side requests using one syntax regardless of the underlying server implementation.

1.2 Statement of Work

Identify those implementations which offer server-side processing. Identify a common subset of processing requests. Develop a common mechanism for embedding the request into the URL and a common syntax for the identified processing types. Some candidate for requests that could have a common syntax are sum, average, minimum and maximum along one or more axes.

1.3 Working Documents

In this section we should build documents that represent the consensus of our work. Rather than be an open-ended exchange the goal is to continue to shape these documents so that when consensus is reached, these documents can be put forward as the specification of the capabilities and syntax that we agreed should be implemented by those choosing to participate. Please use the discussion tab and email for the initial exchange of ideas and consensus building.

  1. Current Implementations
  2. Proposed Capabilities
    • "Server as client" to read other OPeNDAP data sets as part of the analysis.
    • Standard functions
    • Escaping to "native" scripts
    • Security (syntax checking, OS "escapes", etc)
    • Capabilities discovery
    • Variable naming (client specified, best practices defaults, etc)
  3. Proposed Syntax


1.4 Members

  1. Roland Schweitzer
  2. Patrick West
  3. Rob De Almeida
  4. Antonio S. Cofiño

1.5 Resources

--Roland Schweitzer (Mon Sep 24 14:21:10 CDT 2007)