three editorial corrections to PR3 text

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

WebCGM TC --

Here are three non-substantive editorial corrections to the PR3 text,
that we propose to apply for the CS2 text, that we will vote on next
week. (These have already been discussed and agreed by the W3C WebCGM
WG.)


1.) At the end of informative section 1.9 "Roadmap", add this
informative note about how to view the CGM examples:

[[[ 
Note about CGM examples. In Chapter 5, defining the WebCGM DOM, there
are examples that end with text lines, "View this example as HTML-CGM
(WebCGM-DOM-enabled browsers only.)" In document formats that support
external links (i.e., XHTML), each of these examples links to an XHTML
snippet that invokes WebCGM instances. To view them your browser must
have a WebCGM viewer plug-in, control, or appropriate equivalent
technology. To obtain such a viewer, see for example the
(non-exhaustive) CGM products directory on the OASIS/CGM Open Web site. 
]]]

The text "CGM products directory" will carry a hyperlink to
http://www.cgmopen.org/webcgm/products.html .

(Rationale: Mary suggested that it would be helpful for those who aren't
regular CGM practitioners.)

2.) In section 3.1.2.2, replace the definition of "_replace" (in the
definitions list) with:

[[[
When _replace occurs on a CGM-to-CGM link, a WebCGM viewer shall replace
the current CGM picture by the designated CGM picture in the same
rectangular area in the same frame as the picture which refers to this
target. If the ending resource (CGM) is the same as the linking
resource, the viewer shall not reload the resource. This is the default
behavior for such links. 
]]]

(Rationale: Chris Lilley pointed out that the old wording, left over
from 1999 WebCGM 1.0, incorrectly implies that the concept of _replace
exists only in WebCGM. This editorial change removes that implication,
without changing any normative requirements.)

3.) In section 3.4, remove the extraneous ";" after the 'type' attribute
in each of the two occurrences of the <object...> element.

(Rationale. It's a typo that has been in the document since 1999.)

Dave Cruikshank

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