[cgmopen-members] CGM Interoperability Problems

[Lofton Henderson <lofton@rockynet.com>]

CGM Open Members --

I am requesting that each of you take a minute and make a small 
contribution for next week's TC meeting, for the interoperability parts.

We expecting a few interop problem files, from a couple of sources at 
least.  Due to some confusion about scope, we will probably have less than 
we want next week -- in addition to launching and planning a (one-year?) 
interoperability project, we want to actually start with some hands-on work 
in Frankfurt.

So each member (user and vendor alike):  please send at least one CGM 
interoperability problem to us.  You all must have a favorite -- a file 
from "A" that is valid but doesn't work in "B"; a file from "C" that 
doesn't accurately reflect the intended picture; an application "D" that 
degenerates high-level primitives intended for round-tripping.  Etc.  Or 
problems of some other ilk altogether.

We don't want to embarrass any particular party here.  But we'd like to 
have specifics about the problem.  For this reason, I was thinking that it 
might be good to send the stuff directly to Dave, who is both our TC chair 
and one of our relatively vendor-neutral members.  For any "publication" of 
the material outside of our working group, we can sanitize the specifics 
(e.g., change "that rotten HSI software" to "vendor 'A'").  I think, 
working within the group, we can handle the real identities okay.  By 
"publication" I mean writing about the problems or the project, posting a 
project archive on Web site, etc.  (This aspect of a long-term project 
would be one to discuss at Frankfurt.)

So to recap -- at least one.  More is better!

Thanks,
-Lofton.