Viewer behavior with WebCGM 1.0 files

["Cruikshank, David W" <david.w.cruikshank@boeing.com>]

This question started out as a dialog
(http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/email/archives
/200602/msg00010.html). 

Here is a statement of the issue.  Please follow up this message with
your opinion.

Obviously, when dealing with WebCGM 2.0 files, WebCGM 2.0 viewers will
implement the correct default behavior according to the 2.0 spec.  When
dealing the WebCGM 1.0 files, WebCGM 1.0 viewers will implement the
correct default behavior according to the 1.0 spec.

WebCGM 2.0 defined a mapping from WebCGM 1.0 default behavior when
dealing with WebCGM 1.0 files.

It was pointed out that when users upgrade their viewers to WebCGM 2.0
without upgrading to WebCGM 2.0 files, they will see a change in default
behavior.  Is this the desired result?

Should control of the default behavior in this case be offered to the
users by the vendors?  Should this be a business decision by the vendors
based on user requirements?

In any case, we may have to revisit this issue during the W3C
processing.

Thoughts?

Thx...Dave Cruikshank

Technical Fellow - Graphics/Digital Data Interchange
Boeing Commercial Airplane
206.544.3560, fax 206.662.3734  <-- NEW NUMBERS
david.w.cruikshank@boeing.com