OPeNDAP Documentation - User contributions [en]

Working Groups

2007-04-26T14:53:38Z

JerryPan: /* Possible Working Groups */

== Formulation of Working Groups ==

The process for establishing and running a working group was developed at the [[Report_on_the_2007_OPeNDAP_Developer%27s_Workshop|2007 Developer's Workshop]]. The essence of the process is that a small group is formed to work on a problem and agrees to reach a conclusion within a short time frame. See [[Formulation_of_Working_Groups|Formulation of Working Groups]] for more information about the process.

== The Working Group Executive ==

Working groups can be proposed by anyone but must be chartered within the OPeNDAP community by the executive.
The Working Group Executive is nominated by the community and appointed by the OPeNDAP advisory board. There is a nominal term limit for membership is 2 years. Members may serve more than one term (with advisory board approval). The executive makes recommendations on how to take working group outcomes to standards processes and other relevant organizations for broader community comment, adoption, etc.

The current Working Group Executive members are:
* James Gallagher (OPeNDAP, [mailto:jgallagher@opendap.org jgallagher at opendap dot org])
* Steve Hankin (NOAA, [mailto:Steven.C.Hankin@noaa.gov Steven.C.Hankin at noaa dot gov])
* Denis Nadeau (NASA, [mailto:dnadeau@pop600.gsfc.nasa.gov dnadeau at pop600 dot gsfc dot nasa dotgov])
* Tim Pugh (Bureau of Meteorology, Australia, [mailto:T.Pugh@bom.gov.au T.Pugh at bom dot gov dot au])
* Russ Rew (Unidata, UCAR, [mailto:russ@unidata.ucar.edu russ at unidata dot ucar dot edu])

The executive can be reached collectively at [mailto:owg-executive@opendap.org owg-executive at opendap dot org].

The OPeNDAP Working Group [[Terms of Reference]] Describe how the Executive will make decisions about the working groups.

== Active Working Groups ==

* [[Authentication]]

== Possible Working Groups==

Add topics for possible working groups here.

* Virtualization (Aggregation)
* Server-side processing
* Geospatial Interoperability
* Security: [mailto:jgallagher@opendap.org James Gallagher], [mailto:pany@ornl.gov Jerry Pan]
* Hyrax and *DS (TDS, GDS, FDS, etc.)
* Semantics
* DAPPER
* netCDF C++ client
* Response types
* Metrics
* Asynchronous transactions
* DAP4
* Relational Database access via DAP

Authentication

2007-04-23T15:17:59Z

JerryPan: /* Members */

== Authentication Working Group ==
=== Motivation ===
When it is necessary to restrict access to OPeNDAP datasets, the server must challenge the user to '''authenticate''', and process the request (or not) based on whether the user is '''authorized''' to access the dataset. Unless there is a specified standard, it is possible that the various servers and clients may not be able to interoperate.

=== Statement of Work ===
This working group will propose a standard on how OPeNDAP servers and clients authenticate. The standard will allow any conformant OPeNDAP server and client to interoperate. It will specify the interaction between client and server, not the implementation. However, it may also provide a "best practices" or "experience to date" document to guide implementation.

=== Members ===
# John Caron
# Patrick West
# Nathan Potter
# Bryan Lawrence
# Jerry Pan (mailto:pany@ornl.gov)

=== Resources ===

* [http://www.unidata.ucar.edu/staff/caron/presentations/OpendapSecurity.ppt "TDS and OPeNDAP security" ppt presentation to OPeNDAP Developer's meeting 2007]
* [http://www.unidata.ucar.edu/software/netcdf-java/reference/HTTPauthentication.html HTTP Authentication in Netcdf-Java library]

--[[User:JohnCaron|JohnCaron]] 14:54, 20 April 2007 (PDT)

Authentication

2007-04-23T15:08:57Z

JerryPan: /* Members */

== Authentication Working Group ==
=== Motivation ===
When it is necessary to restrict access to OPeNDAP datasets, the server must challenge the user to '''authenticate''', and process the request (or not) based on whether the user is '''authorized''' to access the dataset. Unless there is a specified standard, it is possible that the various servers and clients may not be able to interoperate.

=== Statement of Work ===
This working group will propose a standard on how OPeNDAP servers and clients authenticate. The standard will allow any conformant OPeNDAP server and client to interoperate. It will specify the interaction between client and server, not the implementation. However, it may also provide a "best practices" or "experience to date" document to guide implementation.

=== Members ===
# John Caron
# Patrick West
# Nathan Potter
# Bryan Lawrence
# Jerry Pan

=== Resources ===

* [http://www.unidata.ucar.edu/staff/caron/presentations/OpendapSecurity.ppt "TDS and OPeNDAP security" ppt presentation to OPeNDAP Developer's meeting 2007]
* [http://www.unidata.ucar.edu/software/netcdf-java/reference/HTTPauthentication.html HTTP Authentication in Netcdf-Java library]

--[[User:JohnCaron|JohnCaron]] 14:54, 20 April 2007 (PDT)