Server-side Functions - Revision history

PatrickWest at 21:42, 12 May 2009

2009-05-12T21:42:37Z

← Older revision		Revision as of 21:42, 12 May 2009
Line 38:		Line 38:

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

			[[Category:Working Groups\|Server Side Functions]]

AntonioCofiño: /* Members */

2009-01-10T10:58:07Z

Members

← Older revision		Revision as of 10:58, 10 January 2009
Line 26:		Line 26:
	# [mailto:pwest@ucar.edu Patrick West]		# [mailto:pwest@ucar.edu Patrick West]
	# [mailto:rob@pydap.org Rob De Almeida]		# [mailto:rob@pydap.org Rob De Almeida]
			# [mailto:antonio.cofino@unican.es Antonio S. Cofiño]

	=== Resources ===		=== Resources ===

Jimg: /* Resources */

2007-10-27T01:49:55Z

Resources

← Older revision		Revision as of 01:49, 27 October 2007
Line 29:		Line 29:
	=== Resources ===		=== Resources ===

			* [mailto:opendap-functions@opendap.org The OPeNDAP Functions] mail list.
	* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]		* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]
	* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]		* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]

Roland at 20:11, 27 September 2007

2007-09-27T20:11:03Z

← Older revision		Revision as of 20:11, 27 September 2007
Line 17:		Line 17:
	#* Escaping to "native" scripts		#* Escaping to "native" scripts
	#* Security (syntax checking, OS "escapes", etc)		#* Security (syntax checking, OS "escapes", etc)
			#* Capabilities discovery
			#* Variable naming (client specified, best practices defaults, etc)
	# [[Proposed Syntax]]		# [[Proposed Syntax]]

Roland at 20:08, 27 September 2007

2007-09-27T20:08:29Z

← Older revision		Revision as of 20:08, 27 September 2007
Line 9:		Line 9:

	=== Working Documents ===		=== 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.		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.

			# [[Current Implementations]]
			# [[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)
			# [[Proposed Syntax]]


	=== Members ===		=== Members ===

Roland at 19:56, 27 September 2007

2007-09-27T19:56:58Z

← Older revision		Revision as of 19:56, 27 September 2007
Line 6:		Line 6:

	=== Statement of Work ===		=== 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.		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.

			=== 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.

	=== Members ===		=== Members ===

2007Workshop at 19:26, 25 September 2007

2007-09-25T19:26:49Z

← Older revision		Revision as of 19:26, 25 September 2007
Line 17:		Line 17:
	* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]		* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]
	* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]		* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]
			* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/sld_WZJ07b.pdf SWAMP Presentation from the OPeNDAP Meeting]
			* [http://dust.ess.uci.edu/ppr/ppr_WZJ073.pdf SWAMP Paper from Advances in Grid and Pervasive Computing, Second International Conference, GPC 2007]
	* [http://wiki.opendap.org/twiki/bin/view/Developers/DevMeeting2007Program See this section 1445-1715 Server-Side Operations with 1530-1600 Break]		* [http://wiki.opendap.org/twiki/bin/view/Developers/DevMeeting2007Program See this section 1445-1715 Server-Side Operations with 1530-1600 Break]

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

RobDeAlmeida: /* Members */

2007-09-25T02:43:24Z

Members

← Older revision		Revision as of 02:43, 25 September 2007
Line 11:		Line 11:
	# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]		# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]
	# [mailto:pwest@ucar.edu Patrick West]		# [mailto:pwest@ucar.edu Patrick West]
			# [mailto:rob@pydap.org Rob De Almeida]

	=== Resources ===		=== Resources ===

PatrickWest at 00:55, 25 September 2007

2007-09-25T00:55:07Z

← Older revision		Revision as of 00:55, 25 September 2007
Line 10:		Line 10:
	=== Members ===		=== Members ===
	# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]		# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]
			# [mailto:pwest@ucar.edu Patrick West]

	=== Resources ===		=== Resources ===

2007Workshop: New page: == Server-side Functions Working Group == === Motivation === May different OPeNDAP server implementations include the ability to request that the server process the data before returning t...

2007-09-25T00:20:51Z

New page: == Server-side Functions Working Group == === Motivation === May different OPeNDAP server implementations include the ability to request that the server process the data before returning t...

New page

== Server-side Functions Working Group ==
=== 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.

=== 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.

=== Members ===
# [mailto:Roland.Schweitzer@noaa.gov Roland Schweitzer]

=== Resources ===

* [http://wiki.opendap.org/twiki/pub/Developers/DevMeeting2007Program/RHS-OPeNDAP_Dev_Con.ppt "Server-side OPeNDAP Analysis - A General Approach Utilizing Legacy Applications through TDS" ppt presentation to OPeNDAP Developer's meeting 2007]
* [http://www.iges.org/grads/gadoc/users.html The GrADS Data Server]
* [http://wiki.opendap.org/twiki/bin/view/Developers/DevMeeting2007Program See this section 1445-1715 Server-Side Operations with 1530-1600 Break]

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