Formulation of Working Groups - Revision history

Jimg at 04:21, 29 March 2007

2007-03-29T04:21:36Z

← Older revision		Revision as of 04:21, 29 March 2007
Line 11:		Line 11:

	# OPeNDAP working groups (OWG) should be formed with a specific focus, deliverables, timeframe and minimum membership. OPeNDAP would welcome agency, project or institutional sponsorship and/or co-sponsorship.		# OPeNDAP working groups (OWG) should be formed with a specific focus, deliverables, timeframe and minimum membership. OPeNDAP would welcome agency, project or institutional sponsorship and/or co-sponsorship.
	## Specific focus - The working groups must define the areas of their work efforts as covering a) OPeNDAP the software, b) OPeNDAP (DAP) the ~~reference implementation~~, or c) both. Working Groups should only be formed for well-defined topics where the community feels the development of a deliverable is a high priority.		## Specific focus - The working groups must define the areas of their work efforts as covering a) OPeNDAP the software, b) OPeNDAP (DAP) the specification, or c) both. Working Groups should only be formed for well-defined topics where the community feels the development of a deliverable is a high priority.
	## Deliverables/outcomes - Deliverables produced by a OWG fall into two categories. First, an OWG may produce software, either prototype or production. Second, an OWG may produce documentation including: Software specifications; Standard Operating Procedure documents; Best Practices documents; and Technical Notes. In some cases the OWG may reccommend that the ideas developed be taken to a more formal standards organization to be developed further.		## Deliverables/outcomes - Deliverables produced by a OWG fall into two categories. First, an OWG may produce software, either prototype or production. Second, an OWG may produce documentation including: Software specifications; Standard Operating Procedure documents; Best Practices documents; and Technical Notes. In some cases the OWG may reccommend that the ideas developed be taken to a more formal standards organization to be developed further.
	## Timeframe - OWGs should aim to complete their discussions, white papers, documents/proposals within a nominal 3 month timeframe. In cases where prototypes/software are to be produced the timeframe can be extended with OWG executive (see next item) approval), especially where funding is sought to complete the project. The intent is not to have stagnant or dormant efforts.		## Timeframe - OWGs should aim to complete their discussions, white papers, documents/proposals within a nominal 3 month timeframe. In cases where prototypes/software are to be produced the timeframe can be extended with OWG executive (see next item) approval), especially where funding is sought to complete the project. The intent is not to have stagnant or dormant efforts.

Jimg: /* Possible OPeNDAP Working Groups */

2007-03-21T00:03:49Z

Possible OPeNDAP Working Groups

← Older revision		Revision as of 00:03, 21 March 2007
Line 22:		Line 22:
	# The only requirement for participation and comment on OWG forums is to be a registered user on the opendap.org provided wiki.		# The only requirement for participation and comment on OWG forums is to be a registered user on the opendap.org provided wiki.
	# The approval and decision making process may vary depending on the scope of the subject area. The OWG proposers must identify a suitable decision making process (if it is required) and the OWG executive must approve that process before the OWG can be chartered. In some cases, standards and specifications must have broad community comment and consensus before being adopted.		# The approval and decision making process may vary depending on the scope of the subject area. The OWG proposers must identify a suitable decision making process (if it is required) and the OWG executive must approve that process before the OWG can be chartered. In some cases, standards and specifications must have broad community comment and consensus before being adopted.

	~~== Possible OPeNDAP Working Groups==~~

	* 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

Jimg at 00:03, 21 March 2007

2007-03-21T00:03:20Z

← Older revision		Revision as of 00:03, 21 March 2007
Line 5:		Line 5:
	The OPeNDAP community process draws on experience from other community processes: e.g. IETF,		The OPeNDAP community process draws on experience from other community processes: e.g. IETF,
	OGC, ISO, JCP, Unidata.		OGC, ISO, JCP, Unidata.

			==Working Group Attributes==

	To meet the needs of the OPeNDAP community, the following attributes of the process had broad agreement:		To meet the needs of the OPeNDAP community, the following attributes of the process had broad agreement:
Line 21:		Line 23:
	# The approval and decision making process may vary depending on the scope of the subject area. The OWG proposers must identify a suitable decision making process (if it is required) and the OWG executive must approve that process before the OWG can be chartered. In some cases, standards and specifications must have broad community comment and consensus before being adopted.		# The approval and decision making process may vary depending on the scope of the subject area. The OWG proposers must identify a suitable decision making process (if it is required) and the OWG executive must approve that process before the OWG can be chartered. In some cases, standards and specifications must have broad community comment and consensus before being adopted.

	Possible ~~OWGs:~~		== Possible OPeNDAP Working Groups==

	* Virtualization (Aggregation)		* Virtualization (Aggregation)

Jimg at 00:01, 21 March 2007

2007-03-21T00:01:15Z

@@ Line 1: / Line 1: @@
-Community forums for deciding on standards/ processes within (and  beyond) the OPeNDAP community
+Community forums for deciding on standards/processes within (and  beyond) the OPeNDAP community
 The OPeNDAP community process draws on experience from other  community processes: e.g. IETF,
@@ Line 6: / Line 8: @@
 To meet the needs of the OPeNDAP community, the following attributes of the process had broad agreement:
-== Working Group Attributes ==
+# OPeNDAP working groups (OWG) should be formed with a specific focus, deliverables, timeframe and minimum membership. OPeNDAP would welcome agency, project or institutional sponsorship and/or co-sponsorship.
+## Specific focus - The working groups must define the areas of their work efforts as covering a) OPeNDAP the software, b) OPeNDAP (DAP) the reference  implementation, or c) both. Working Groups should only be formed for well-defined topics where the community feels the development of a deliverable is a high priority.
-- OPeNDAP working groups (OWG) should be formed with a specific focus, deliverables, timeframe and minimum membership. OPeNDAP would welcome agency, project or institutional sponsorship and/or co-sponsorship.
+## Deliverables/outcomes - Deliverables produced by a OWG fall into two categories. First, an OWG may produce software, either prototype or production. Second, an OWG may produce documentation including: Software specifications; Standard Operating Procedure documents; Best Practices documents; and Technical Notes. In some cases the OWG may reccommend that the ideas developed be taken to a more formal standards organization to be developed further.
+## Timeframe - OWGs should aim to complete their discussions, white papers, documents/proposals within a nominal 3 month timeframe. In cases where prototypes/software are to be produced the timeframe can be extended with OWG executive (see next item) approval), especially where funding is sought to complete the project. The intent is not to have stagnant or dormant efforts.
- + Specific focus - The working groups must define the areas of their work efforts as covering a) OPeNDAP the software, b) OPeNDAP (DAP) the reference  implementation, or c) both. Working Groups should only be formed for well-defined topics where the community feels the development of a deliverable is a high priority.
+## Minimum membership is 3 people.
+# The OWG executive is nominated by the community and appointed by the OPeNDAP advisory board, with membership of 5-7 people, a nominal term limit for membership is 2 years. Members may serve more than one term (with board approval). The first task of the executive is to formalize the OWG Terms of Reference.
- + Deliverables/outcomes - Deliverables produced by a OWG fall into two categories. First, an OWG may produce software, either prototype or production. Second, an OWG may produce documentation including: Software specifications; Standard Operating Procedure documents; Best Practices documents; and Technical Notes. In some cases the OWG may reccommend that the ideas developed be taken to a more formal standards organization to be developed further.
+# The OWG executive will make recommendations on how to take OWG outcomes to standards processes and other relevant organizations for  broader community comment, adoption, etc.
+# The OPeNDAP advisory board membership will be broadened (serves  OPeNDAP Inc.) to accommodate this expanded role and term limits will be applied to the board.
-+ Timeframe - OWGs should aim to complete their discussions, white papers, documents/proposals within
+# OWGs can be proposed by anyone but must be chartered within the  OPeNDAP community by the OWG executive.
-a nominal 3 month timeframe. In cases where prototypes/software are to be produced the timeframe
+# OWG forums should be public (via opendap.org supported wiki) EXCEPT  for any OWG which addresses security of data service systems (discussion on if we can/should use  US-CERT as an announcement forum for security matters is an item to be pursued).
-can be extended with OWG executive (see next item) approval), especially where funding is sought to complete the project. The intent is not to have stagnant or dormant efforts.
+# The only requirement for participation and comment on OWG forums is  to be a registered user on the opendap.org provided wiki.
+# The approval and decision making process may vary depending on the  scope of the subject area. The OWG proposers must identify a suitable decision making process (if it  is required) and the OWG executive must approve that process before the OWG can be chartered. In some  cases, standards and specifications must have broad community comment and consensus before being adopted.
-*Asynchronous transactions
+Possible OWGs:
-*DAP4
+* Virtualization (Aggregation)

Jimg: /* Formulation of Working Groups */

2007-03-20T23:59:33Z

Formulation of Working Groups

← Older revision		Revision as of 23:59, 20 March 2007
Line 1:		Line 1:
	~~=Formulation of Working Groups =~~

	Community forums for deciding on standards/ processes within (and beyond) the OPeNDAP community		Community forums for deciding on standards/ processes within (and beyond) the OPeNDAP community

Jimg: New page: =Formulation of Working Groups = Community forums for deciding on standards/ processes within (and beyond) the OPeNDAP community The OPeNDAP community process draws on experience from o...

2007-03-20T23:51:54Z

New page: =Formulation of Working Groups = Community forums for deciding on standards/ processes within (and beyond) the OPeNDAP community The OPeNDAP community process draws on experience from o...

New page

=Formulation of Working Groups =

Community forums for deciding on standards/ processes within (and beyond) the OPeNDAP community

The OPeNDAP community process draws on experience from other community processes: e.g. IETF,
OGC, ISO, JCP, Unidata.

To meet the needs of the OPeNDAP community, the following attributes of the process had broad agreement:

== Working Group Attributes ==

- OPeNDAP working groups (OWG) should be formed with a specific focus, deliverables, timeframe and minimum membership. OPeNDAP would welcome agency, project or institutional sponsorship and/or co-sponsorship.

+ Specific focus - The working groups must define the areas of their work efforts as covering a) OPeNDAP the software, b) OPeNDAP (DAP) the reference implementation, or c) both. Working Groups should only be formed for well-defined topics where the community feels the development of a deliverable is a high priority.

+ Deliverables/outcomes - Deliverables produced by a OWG fall into two categories. First, an OWG may produce software, either prototype or production. Second, an OWG may produce documentation including: Software specifications; Standard Operating Procedure documents; Best Practices documents; and Technical Notes. In some cases the OWG may reccommend that the ideas developed be taken to a more formal standards organization to be developed further.

+ Timeframe - OWGs should aim to complete their discussions, white papers, documents/proposals within
a nominal 3 month timeframe. In cases where prototypes/software are to be produced the timeframe
can be extended with OWG executive (see next item) approval), especially where funding is sought to complete the project. The intent is not to have stagnant or dormant efforts.

+ Minimum membership is 3 people.

- The OWG executive is nominated by the community and appointed by the OPeNDAP advisory board, with
membership of 5-7 people, a nominal term limit for membership is 2 years. Members may serve
more than one term (with board approval). The first task of the executive is to formalize the OWG Terms of Reference.

- The OWG executive will make recommendations on how to take OWG outcomes to standards processes and other relevant organizations for broader community comment, adoption, etc.

- The OPeNDAP advisory board membership will be broadened (serves OPeNDAP Inc.) to accommodate
this expanded role and term limits will be applied to the board.

- OWGs can be proposed by anyone but must be chartered within the OPeNDAP community by the OWG
executive.

- OWG forums should be public (via opendap.org supported wiki) EXCEPT for any OWG which addresses
security of data service systems (discussion on if we can/should use US-CERT as an announcement forum
for security matters is an item to be pursued).

- The only requirement for participation and comment on OWG forums is to be a registered user on the
opendap.org provided wiki.

- The approval and decision making process may vary depending on the scope of the subject area. The
OWG proposers must identify a suitable decision making process (if it is required) and the OWG executive
must approve that process before the OWG can be chartered. In some cases, standards and specifications
must have broad community comment and consensus before being adopted.

==Possible <nop>OPeNDAP Working Groups ==

*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