Working Groups: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
m (Add Authentication topic and link)
No edit summary
Line 16: Line 16:


The executive can be reached collectively at [mailto:owg-executive@opendap.org owg-executive at opendap dot org].
The executive can be reached collectively at [mailto:owg-executive@opendap.org owg-executive at opendap dot org].
== Active Working Groups ==
* [[Authentication]]


== Possible Working Groups==
== Possible Working Groups==
Line 25: Line 29:
* Geospatial Interoperability
* Geospatial Interoperability
* Security
* Security
* [[Authentication]]
* Hyrax and *DS (TDS, GDS, FDS, etc.)
* Hyrax and *DS (TDS, GDS, FDS, etc.)
* Semantics
* Semantics

Revision as of 19:12, 23 April 2007

Formulation of Working Groups

The process for establishing and running a working group was developed at the 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 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:

The executive can be reached collectively at owg-executive at opendap dot org.

Active Working Groups

Possible Working Groups

Add topics for possible working groups here.

  • Virtualization (Aggregation)
  • Server-side processing
  • Geospatial Interoperability
  • Security
  • Hyrax and *DS (TDS, GDS, FDS, etc.)
  • Semantics
  • DAPPER
  • netCDF C++ client
  • Response types
  • Metrics
  • Asynchronous transactions
  • DAP4
  • Relational Database access via DAP