potential items for TC/MS programme of work

[Lofton Henderson <lofton@rockynet.com>]

WebCGM-ers,

I'm responding to Stuart's call for input on the TC's future work priorities.

Below is a collection of everything that I have queued or heard of for the 
last several months.  It contains all sorts of stuff:  routine items like 
errata/maintenance, should-do items, may-do items.

The first section contains (potential) work items that I have extracted 
from the MS quarterly reports [1].  Some of these are definite "to-do" 
items, some are potential deliverables ("should" or "may").

Other sections contain ideas/proposals that some other TC members have 
expressed.  There are some good ideas there, but they need a bit of 
fleshing out.

Thoughts?  Additions?  Comments?  (Here by email and at the 3/31 telecon).

Extracted from 2009/Q4 quarterly report to the MS:
-----
QR1:  2.1 Test Suite maintenance.  Fix any bugs that arise.  (One pending.)
QR2:  2.1 Test Suite maintenance.  Clean up the whole thing so that all 
tests are 2.1-valid per MetaCheck.  (Moderate-size task.)

QR3:  Errata processing for any 2.1 errata that might be reported 
(pending:  several OASIS, one W3C).

QR4:  Refresh WebCGM product ICS pages and ensure current accuracy.  (Badly 
needed.)
QR5:  Revise and update the old ICS forms to be current/correct for 
2.0.  (Should do.)
QR6:  Design new 2.1 ICS forms.  (Should do.)

QR7:  Begin a wish list of post-2.1 WebCGM enhancements (noting that there 
is no active plan for a post-2.1 version at this time.)
QR8:  Examine "Compositing" proposal for a small 2.2 upgrade.  (See DL list 
below.)

QR9:  Update Web site with new WebCGM milestones (from 2010/Q1; already 
DONE for 2009/Q3,Q4).

QR10:  Planning for realignment of MS & TC resources following WebCGM 2.1 
completion.
QR11:  Recruit new members (esp. to the TC).
QR12:  Pursue and plan for a evangalism/marketing/education program.
QR13:  Write, review, and post the MS Quarterly Report.  (Regular item 
every quarter.)

 From Stuart/Boeing:
-----
SG1:  Boeing-driven interop and implementation problems tracking.
SG2:  Wish list for enhancements to 2.1 specification:
	-- small scope, e.g., datatype 'nodeList'

 From Dieter:
-----
DW1:  Sample code for integration,
DW2:  more DOM examples,
DW3:  tips for practical usage,
DW4:  anything that makes CGM easier to use

 From Don:
-----
DL1:  Wish list for enhancements to 2.1 specification:
	-- medium scope, e.g., compositing functionality
	-- (Requested by several A&D users of CGM/WebCGM.)

Via Lofton (original source: someone in TC, I forget whom):
-----
LH1:  Tools for working with CGMs:
	-- fix cgmconv bugs?  (Is there another available equivalent?)
	-- fix and release MetaWiz?

Regards,
-Lofton.