168 lines
4.6 KiB
Plaintext
168 lines
4.6 KiB
Plaintext
head 1.6;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
expand @o@;
|
|
|
|
|
|
1.6
|
|
date 2006.06.04.10.04.44; author StanleyBlum; state Exp;
|
|
branches;
|
|
next 1.5;
|
|
|
|
1.5
|
|
date 2006.05.15.06.23.59; author StanleyBlum; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2006.05.10.08.59.05; author RicardoPereira; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2006.05.09.08.40.57; author LeeBelbin; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2006.05.09.07.36.15; author StanleyBlum; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2006.05.06.21.20.53; author StanleyBlum; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="StanleyBlum" date="1149415484" format="1.1" version="1.6"}%
|
|
%META:TOPICPARENT{name="WebHome"}%
|
|
---+ Operational Recommendations
|
|
|
|
Operational recommendations are things that should improve the functioning of TDWG, but do not necessarily warrant specification in the Constitution or Process (Bylaws). We might consider these recommendations to constitute [[http://biodiv.hyam.net/standards/tdwg_admin_files/standard.xml#a_1.3]["type 3 documentation"]]; not normative or versioned, but still valuable.
|
|
|
|
---++ Recommendations concerning the Executive Committee
|
|
|
|
* Exec Comm Reviewing responsibilities:
|
|
* Interest and Task Group (TG) Charters for formation of new subgroups;
|
|
* Modifications of Charters;
|
|
* Interest and Task Group reports against Chaters every year after the formation of the subgroup;
|
|
* summaries of expert reviews
|
|
* Existing standards (annually)
|
|
|
|
* All decisions of the Executive Committee should be published on the TDWG web site and announced on the TDWG mailing list; i.e., both pushed to the membership and put in a permanent and well-organized repository. [Lee: we should treat the Executive Committee as if it were a subgroup in that it should have its own web pages]
|
|
|
|
* Minutes of any Executive Committee meeting should be published within 30 days, preferably sooner.
|
|
|
|
* One meeting of the Executive per year is insufficient if decisions are going to be independent of the annual meeting. Consideration should be given to at least 2-3 conference calls (Skype sessions) during the year.
|
|
|
|
etc.
|
|
|
|
|
|
---++ Recommendations concerning the Standards Process
|
|
|
|
|
|
|
|
-- Main.StanleyBlum - 06 May 2006
|
|
|
|
|
|
%META:TOPICMOVED{by="StanleyBlum" date="1147159232" from="Process.OperationOfInterestAndTaskGroups" to="Process.OperationalRecommendations"}%
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="StanleyBlum" date="1147674239" format="1.1" version="1.5"}%
|
|
d9 7
|
|
d18 1
|
|
a18 1
|
|
* All minutes of the Executive Committee should be published within 30 days of the meeting.
|
|
a26 4
|
|
---+++ Maintenance of Standards
|
|
|
|
Once a standard has been approved, experience with its application is likely to show that changes will be needed and revised standard should be developed. If the changes are minor, they can be incorporated into a revision directly by the Interest Group, without establishing another Task Group. The revision must be submitted to the The TAG, Editor, and Executive Committee, as with any specification, but the Executive Committee may decide that changes are minor and that the user-base is fully behind the changes, and therefore a full public review is not required. In these cases, the EC may approve the proposed revision as a TDWG standard.
|
|
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="RicardoPereira" date="1147251545" format="1.1" version="1.4"}%
|
|
d13 1
|
|
a13 1
|
|
* One meeting of the Executive per year is insufficient if decisions are going to be independent of the annual meeting. Consideration should be given to at least 2-3 Skype sessions during the year.
|
|
d17 9
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="LeeBelbin" date="1147164057" format="1.1" version="1.3"}%
|
|
d5 1
|
|
a5 1
|
|
Operational recommendations are things that should improve the functioning of TDWG, but do not necessarily warrant specification in the Constitution or Process (Bylaws). We might consider these recommendations to constitute "type 3 documentation"; not normative or versioned, but still valuable.
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="StanleyBlum" date="1147160175" format="1.1" version="1.2"}%
|
|
d9 1
|
|
a9 1
|
|
* All decisions of the Executive Committee should be published on the TDWG web site and announced on the TDWG mailing list; i.e., both pushed to the membership and put in a permanent and well-organized repository.
|
|
d11 3
|
|
a13 1
|
|
* All minutes of the Executive Committee should be published in a timely fashion.
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="StanleyBlum" date="1146950453" format="1.1" version="1.1"}%
|
|
d3 1
|
|
a3 1
|
|
---+ Operation of Interest and Task Groups
|
|
d5 1
|
|
a5 1
|
|
Stub
|
|
d7 7
|
|
d16 3
|
|
@
|