CGM OPEN ACTIVITY REPORT - 2003
PITTSBURGH MEETING

Revision: 1.0

Date: April 6, 2003

Preface

This report describes activities of CGM Open meeting held on April 6, 2002 in Pittsburgh, Pennsylvania

Table of Contents

1 Meeting Details

1.1 Location and Dates

Pittsburgh, Pennsylvania, April 6, 2003

1.2 Meeting

• CGM Open 6 April 2003..

1.3 CGM Open Attendees

• Dave Cruikshank - Boeing (Chief Technical Officer)
• Lofton Henderson - (Program Director)
• Don Larson - Larson Software Technology
• Forrest Carpenter - SDI
• Benoit Bezaire - Corel Corp
• John Gebhardt - Corel Corp
• Andrew Moorehouse - Mod UK
• Kevin O'Kane - Auto-trol
• Tim Horsch - Auto-trol
• Stuart Galt - Boeing
• Doug Lieberg - Boeing

2 Agenda

The items on the agenda of the CGM Open meeting included:

• CGM Open governance & Bylaws
• Interoperability problem tracker
• Product/interoperability web pages
• Proposed home web page
• Proposed Navy XML-coded CGM
• Dieter/Lofton paper on Webcgm/SVG for Technical Graphics
• Dave/Lofton paper on Stylable CGM
• WebCGM DOM

3 Output and Action Items

4 Agenda discussions

4.1 CGM Open governance & Bylaws

A planned governance meeting did not occur due to the absence of the chairman. A governance meeting will probably take place at XML Europe 2003 in May. The governance structure of CGM Open will transition to a CEO plus two advisors. In addition, the voting process for approval of proposals will be modified. In order to do this the bylaws will be modified and approved by the membership. Lofton will submit proposed changes to the bylaws at the next governance meeting.

4.2 Interoperability problem tracker

The group reviewed the public interface designed by Franck and the Mantis application for tracking of interoperability problems.

Several comments arose surrounding the public interface. A teleconference will be scheduled for late April or early May to discuss the requirements for the required fields for the public interface. Some suggestions revolved around entry fields for versions, operating systems, and the ability to upload a file to demonstrate the issue. A question arose as to whether we wanted to give the public access to the actual problem tracker to check status. The group believes that another public interface needs to be developed to communicate status and final resolution without exposing the actual Mantis screens. Franck still needs to fix the login for the public interface so that users come in with reporting privileges only. Dave will summarize discussion and communicate with Franck.

The group entered a bug into the Mantis application and updated it. Each of the members needs to coordinate with Franck to be added to the access list in Mantis with their role defined. To prepare for going live with this service, Don will develop a proposal for publicizing its availability.

4.3 Product/interoperability web pages

During a review of the product pages on the CGM Open web site, a few of the products had links to incorrect blank implementation conformance statement (ICS). Each vendor should check their products and report problems to Lofton. Once the product owner fills out the ICS, it will be maintained on their own web server and the correct link will be provided to Lofton. Lofton will provide blank ICS forms to each vendor after adding the CGM Open logo. The vendor may add a company or product logo to the top of the ICS, but no links may be applied and the ICS will remain in the style of the CGM Open web site. The link from the CGM Open web site will open the ICS in a new window.

4.4 Proposed home web page

The group reviewed the proposed web pages provided by Gabriella. A comment was made that we might want to align the CGM Open home page with the style of the OASIS web pages. Lofton will determine the expectation from OASIS for all the links in the border. Dave will coordinate with Gabriella to analyze the possibility of applying her designs at the WebCGM home page.

4.5 Proposed Navy XML-coded CGM

The group reviewed the work done by the Navy for the XML encoding of CGM. A question came up on the motivation for that instigated this work. Ideas submitted were:

1. Hand-coding
2. Xml tools
   • Machine processible profile
   • Validation in XML
   • Access to common XML/DOM tools
3. Content integration

Dave will contact the Navy to determine the answer the answer to this question. It was noted that the XML DTD for the V4 CGM was aligned with the WebCGM test suite and was structured to conform to the elements appear on those files.

4.6 Dieter/Lofton paper on Webcgm/SVG for Technical Graphics

This paper will be presented at XML Europe 2003 in London on May 6, 2003. The content of the paper compares the applicability of WebCGM and SVG to the technical illustrating environment.

4.7 Dave/Lofton paper on Stylable CGM

This paper will be presented at XML Europe 2003 in London on May 6, 2003. The content of the paper describes the application of CSS2 to WebCGM for the external control of attributes.

4.8 WebCGM DOM

A discussion took place to determine the next steps in developing a WebCGM DOM based on the XML DOM. The project had a couple of outstanding action item that had not been completed. Dave will continue to pursue the application of DOM Core principles to the WebCGM DOM and Kevin and Don will pursue the event portions of XML DOM Levels 2 & 3.

4.9 Miscellaneous

An idea for the creation of an SVG profile aligned with the WebCGM profile was discussed. The project would involved doing a line by line analysis of the WebCGM profile and determine the SVG functionality required to support it. This is an activity that would also be of interest to the ATA and AECMA communities. John and Beniot volunteered to investigate this possibility. The final result should be expressible in either XML or XML Schema.

The date and venue of the next meeting will be determined at the next CGM Open telecon in late April.