Working Groups: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
m (Add Authentication topic and link)
No edit summary
 
(27 intermediate revisions by 12 users not shown)
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].
The OPeNDAP Working Group [[Terms of Reference]] Describe how the Executive will make decisions about the working groups.
== Active Working Groups ==
* [[Hyrax Administration]]
* [[Authentication]]
* [[Security]]
* [[Server-side Functions]]


== Possible Working Groups==
== Possible Working Groups==
Line 21: Line 33:
Add topics for possible working groups here.
Add topics for possible working groups here.


* Virtualization (Aggregation)
* Virtualization (Aggregation): [mailto:dnadeau@pop600.gsfc.nasa.gov Denis Nadeau] [mailto:rob@pydap.org Rob De Almeida] [mailto:antonio.cofino@unican.es Antonio S. Cofiño]
* Server-side processing
* Geospatial Interoperability [mailto:benno@iri.columbia.edu Benno Blumenthal] [mailto:rob@pydap.org Rob De Almeida]
* Geospatial Interoperability
* Security
* [[Authentication]]
* Hyrax and *DS (TDS, GDS, FDS, etc.)
* Hyrax and *DS (TDS, GDS, FDS, etc.)
* Semantics
* Semantics [mailto:benno@iri.columbia.edu Benno Blumenthal] [mailto:pfox@ucar.edu Peter Fox]
* DAPPER
* DAPPER [mailto:rob@pydap.org Rob De Almeida]
* netCDF C++ client
* netCDF C++ client
* Response types
* Response types [mailto:rob@pydap.org Rob De Almeida]
* Metrics
* Metrics
* Asynchronous transactions
* Asynchronous transactions [mailto:edavis@unidata.ucar.edu Ethan Davis] [mailto:antonio.cofino@unican.es Antonio S. Cofiño]
* DAP4
* DAP4 [mailto:benno@iri.columbia.edu Benno Blumenthal] [mailto:edavis@unidata.ucar.edu Ethan Davis]
* Relational Database access via DAP
* Relational Database access via DAP [mailto:rob@pydap.org Rob De Almeida]
 
== Related Documents ==
 
Here is an interesting document about the [http://www.ietf.org/IESG/content/ions/ion-procdocs.html IETF process].
 
[[Category:Working Groups|Working Groups]]

Latest revision as of 21:41, 12 May 2009

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.

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

Active Working Groups

Possible Working Groups

Add topics for possible working groups here.

Related Documents

Here is an interesting document about the IETF process.