I have a suggestion. What about basing the sub-committees on products (e.g.
CAP, EDXL, etc.) and basing the task forces on issues that span multiple
products (e.g. geospatial representation, enumeration , etc.)?
That way subcommittees would span the life of a product while task forces
would be short lived to resolve specific issues. We would only need to go
through the trouble of initiating a subcommittee when we initiate work on a
new product.
Patti
Patti Iles Aymond, PhD
Senior Scientist
Bioterrorism Preparedness & Response
Innovative Emergency Management, Inc.
Managing Risk in a Complex World
8555 United Plaza Blvd. Suite 100
Baton Rouge, LA 70809
(225) 952-8228 (phone)
(225) 952-8122 (fax)
-----Original Message-----
From: Kon Wilms [mailto:]
Sent: Tuesday, June 28, 2005 12:35 PM
To:
Subject: Re: [emergency] RE: Structure
My 2c -
There are only about a dozen active people on the calls/message lists -
does it really make sense to split everything into 6 groups where there
may only be 2 people on a call? Seems like an over complication.
Comments below -
On Tue, 2005-06-28 at 16:14 +0000, wrote:
> Here's my take on potential sub-com structures
>
> Emergency Management
>
> Sub-Committees
> Messaging and Notification
> (communication with people)
Does it have to be with people?
> CAP
>
>
> Systems and Sensors
> (workflow and system communication)
Sensors are a specific implementation of systems.
>
> Metrics and Analysis
> (operational analysis)
Shouldn't workflow be part of this?
>
> Distribution and Infrastructure
> (protocol and architecture)
Which also involves targeting, networks and systems.
> EDXL
>
> Geopolitical Information System
> (targeting of messages)
Geographical targeting, nothing more.
> Task Forces
> Use Cases
> Demonstrations / Presentations
Cheers
Kon
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE:
http://www.ieminc.com/e_mail_confidentiality_notice.html
