This charter is written in accordance with section 6.2.6 of the W3C Process Document.

Contents:

Background

Mission and Scope

Several requirements were identified in the WebCGM 2.0 timeframe that, for reasons finishing WebCGM expeditiously, were postponed from the WebCGM 2.0 specification. These requirements have been developed and further refined since the publication of WebCGM 2.0, and collected in the WebCGM 2.1 Requirements document.

The WebCGM 2.1 specification will be based on the WebCGM 2.0 Recommendation and will add the following features:

• substring hotspots (enabled by ISO defect correction.)
• text search: no new functionality but 2.0 code examples/tutorial.
• regex APS addressing: via regex in 'apsid' and/or 'name'.
• more DOM/XCF Style Properties: pan-zoom, access to more line/edge-type attributes, fill attributes.
• transform as DOM/XCF Style Property and/or new APS Attribute.
• font interchange: e.g., a font-substitution file (like the proprietary equivalents in many current viewers).
• default Styling Properties: something like a preferences file to supply specific defaults where such are lacking.
• z-compression: gzip compression of whole file as .cgmz.
• clarify interaction/priorization of various transparency functionalities.
• get object extents: utility function for DOM programmers.
• redraw control: when DOM-specified changes happen (immediate, no-redraw, full-redraw, redraw-changed, etc.)
• declarative animation: probably beyond 2.1, but there is persistent user interest (for a 3.0 project?) in a very small subset of declarative animation capabilities within or adjunct to WebCGM -- study to continue.

  Note : For more details on the above features, refer to the WebCGM 2.1 requirement document.

WebCGM 2.1 is intended to bring these additions quickly to completion and implementation. Schedule is considered to be a requirement of equal priority to any of the technical requirements. Any technical requirement that cannot be completed in the planned approximate year-long time frame will be considered "at risk".

The WebCGM 2.1 specification will also include the WebCGM 2.0 errata.

The completion of work on WebCGM 2.1 will bring further standardization and enable greater interoperability in the technical graphics application sectors that have standardized on WebCGM and closely related technical profiles.

Present state of the WebCGM 2.1 work:

• initial WebCGM 2.1 requirements document.
• WebCGM 2.0 errata
• Several active companies have committed to implement the above listed features of WebCGM 2.1, largely covering the added 2.1 functionality.

Duration

This Working Group is chartered until 30 April 2010. This includes a six month "life after Recommendation" phase.

Deliverables

The group will provide the following deliverables:

• a WebCGM 2.1 Test Suite.
• a WebCGM 2.1 W3C Recommendation simultaneously with an equivalent OASIS Standard.

Tracking and Maintenance Items

• The group anticipates drawing on existing externally produced test suites -- WebCGM 1.0 and its WebCGM 2.0 addendum.
• It will monitor implementations for conformance, interoperability and quality.
• It will publish Implementation Report(s) (at least one).
• It will collect and publish any pending WebCGM 2.0 errata.
• It will collecting and publish errata for the new WebCGM 2.1.
• The WebCGM WG may produce related usage guidelines as time, expertise, and other resources permit.

Success criteria

• Production of a stable document defining WebCGM 2.1, at W3C Recommendation status, technically identical and concurrent with the expected WebCGM 2.1 OASIS Standard.
• Availability of multiple, independent, interoperable implementations of WebCGM 2.1.
• Adoption of WebCGM 2.1 as a foundation for cascaded profiles of the specialized technical industry sectors that are currently using WebCGM 2.0 and closely-related CGM technical profiles.

Relationship to other forums

Groups within W3C

Hypertext Coordination Group

The WebCGM WG coordinates its work with other Working Groups primarily through participation in the Hypertext Coordination Group.

Internationalization Core Working Group

Feedback from the I18N Core WG be sought, to ensure that WebCGM 2.1 is suitable for use in an increasingly international technical industry.

Synchronized Multimedia Working Group

The Working Group coordinates with this group on animation issues.

Scalable Vector Graphics Working Group

The Working Group cooperates with this group on animation issues.

Forums outside W3C

Air Transport Association (ATA)

The ATA has a widely used profile of CGM, which was used as the basis for WebCGM 1.0. The additional capabilities of WebCGM 1.0 and 2.0 mean that the ATA could adopt WebCGM to replace its existing profile. Adoption of WebCGM 2.0, both by itself and as a cascading profile, is therefore desirable.

ASD

The Working Group will liaise with the Technical Publication Specification Maintenance Group (TPSMG) of ASD, who maintain the S1000D Standard for technical documentation of military and non military vehicles. .Adoption of WebCGM 2.0, both by itself and as a cascading profile, by ASD is desirable.

ISO/IEC JTC1 SC24

The working group will liaise with ISO/IEC JTC1 SC24, the part of ISO dealing with CGM.

Confidentiality

This group conducts its work in public, including Editorial Drafts and test suites.

Meetings

Face-to-face meetings

The group anticipates at least three face-to-face meetings, to elaborate First Public Draft, to process the feedback of Last Call review, resolve comments, and begin the process of preparing the CR implementation report and advancing to PR. The need for any additional face-to-face meeting(s) will be assessed, depending on the progress towards Recommendation. Meeting details will be made available on the W3C Member Calendar and from the WG page.

Remote meetings

Weekly 90-minutes teleconferences will be held.

Communication Mechanisms

A archived publicly readable mailing list public-webcgm@w3.org will be the primary means of discussion within the group.

There is a public page on WebCGM, maintained by the Chair.

Resources

Working Group participants are expected to contribute 20% of a Full-Time workload. The W3C Team will contribute 20% of a Full Time Equivalent (FTE).

The Chair of the group will be Lofton Henderson (Oasis/CGM Open). The Team Contact will be Thierry Michel (W3C).

Milestones

One or more public Working Drafts will be produced, existence of adequate associated Test Suites will be assured (likely externally, with some WG contribution), and Implementation Reports will be produced, to the schedule shown below:

• WecCGM WG starts -- Aug 2008
• Publish First Public and Last Call Working Draft ( and start 4-week Last Call Working Draft Review) -- September 2008
• Collect and write test cases -- November 2008
• Process LC comments, resolve, negotiate resolution -- December 2008
• Produce Disposition of Last Call comments -- February 2009
• Publish CR -- March 2009
• Produce Publish Test suite -- April 2009
• Provide Implementation Report demonstrating CR exit criteria met -- May 2009
• Publish PR (and start 4 weeks PR Review) - resume processing in OASIS -- July 2009
• Publish Rec (and OASIS Standard) -- September 2009
• Post-Rec publicity maintenance and evangelism -- to end 30 April 2010.

Patent Policy

This Working Group will operate under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.