Potential table 3.1.2.7

["Galt, Stuart A" <stuart.a.galt@boeing.com>]

Hello,

After playing with the table in 3.1.2.7 and trying all sorts of things
made it much worse I finally began to understand it (I think).  I left
the targets of the links the same, but changed the callouts a bit to
help
if it was used in printed form. 

--
Stuart Galt
SGML Resource Group
stuart.a.galt@boeing.com
(206) 544-3656

Title: OASIS CGM Open specification - WebCGM 2.0 - WebCGM Intelligent Content

3.1.2.7 Summary of behaviors

The following informative table summarizes the rules for how the picture and object behaviors are expressed for links of different types, i.e., depending on the source and destination media types of the link. References are provided to the locations of the rules.

Type of link	picBehavior / HTML target **	objBehavior
HTML-to-CGM	Specified by the 'target' attribute of the <a> element; and is not applicable (n/a) for the <object> element [ref] 3.1.2.2	URI fragment, form without picterm [ref] 3.1.1.2
CGM-to-HTML	Specified by the 3rd parameter of 'linkuri' [ref] 3.2.2.3;	not applicable (n/a)
CGM-to-CGM	The preferred method is to use the 3rd parameter of 'linkuri' [ref] 3.2.2.3 Use of the picTerm of URI fragment in 1st parameter [ref] 3.2.2.3 is discouraged.	URI fragment in 1st parameter of 'linkuri' [ref] 3.2.2.3
DOM-script-CGM	Prohibited: The 'src' attribute of the WebCGM interface is the URI of the current document — only "_replace" supported [ref] 5.7.3; (DOM changes to 'linkuri' follow 'linkuri' rules 3.2.2.3.)	URI fragment on 'src' [ref] 5.7.3; (DOM changes to 'linkuri' follow 'linkuri' rules 3.2.2.3)
XCF-to-CGM	n/a (prohibited) — XCF can only edit 'linkuri' [ref] 3.2.2.3	(XCF changes to 'linkuri' follow 'linkuri' rules 3.2.2.3)

** The behavior, as defined in section 3.1.2.2, depends upon the target content type. For HTML link targets it effectively matches HTML's "Frame Target Names", and for CGM link targets it is an extended derivative of that specification."

---