Re: [cgmo-webcgm] Ideas about issue CL-c10

[Lofton Henderson <lofton@rockynet.com>]

Thanks Benoit.

I have a couple of questions.  First, the simple/trivial ones...

what is a pane?
what is a tab?

I.e., are there standards-based definitions of these?  I know 'tab' from 
Geko-based browsers (NN7 and Firefox).  I searched W3C site for 'pane', and 
quick-look didn't give reveal any standardized thingy.  I ask because I 
assume that we would want to limit any WebCGM list of such target thingies 
to standard-defined ones?  And not suggest mandatory support of 
browser-dependent ones (i.e., if we add language like "This attribute 
specifies the name or portion of the target window, frame, pane, tab, or 
other relevant presentation context.")

More substantive questions...

That aside, as we discussed in telecon, in 1999 even <object> was an 
afterthought, introduced by Chris.  It doesn't surprise me that we don't 
give it the same treatment as windows and frames.  So the interesting 
questions are:

1.) What level of support, as suggested by Chris, according to Benoit's 
analysis?  Support linking to an <object>?  Example:

someHTMLdoc.html contains:
<p>...stuff...</p>
<object id="someObjectElement" data="someInitialCGM.cgm" ..../>

CGM someOtherCGM.cgm contains (conceptually) something like:

1a.)
BegAps id="someApsId";
ApsAttr type="linkuri" URI="someHTMLdoc.html#someObjectElement" 
linkTitle="" behavior="_replace";

or

1b.)
BegAps id="someApsId";
ApsAttr type="linkuri" URI="someHTMLdoc.html" linkTitle="" 
behavior="someObjectElement";

Is this the sort of generalization that we're looking at?  (Implementors, 
who could support this in the near future, if it were generalized?)

2.)  would WebCGM 2.0 want to intentionally limit itself to some *subset* 
of the standardized set:  window, frame, object, iframe?  (Accepting for 
now that the current limitation, excluding object, is accidental and 
unintended.)  Imposing a limitation would need some specific requirements 
to back it, as Chris, SVG, and CDF seem to frown on such limitations.

3.) what changes would we need to make to the document?  Does it need to 
say anything more than SVG did?  Do we need to look at the applicability of 
the keywords _replace, _self, _parent, _top, _blank, <frame-target> to the 
target object type?  (For example, _replace is only defined for C-to-C 
links -- should it be other than _self for a C-to-H <object> link? )  I'm 
unclear what would happen with the whole behavior table in 3.1.2.2.

http://www.w3.org/Submission/2006/SUBM-WebCGM20-20060313/WebCGM20-IC.html#webcgm_3_1_2_2

Regards,
-Lofton.

At 04:05 PM 5/17/2006 -0400, Benoit Bezaire wrote:
>On the call today... I agreed to take an action item to look into this
>a bit deeper.
>
>I suspect that Chris doesn't like our wording because is it specific
>to HTML frames (4.01)... where the W3C CDF (Compound Document Formats)
>specified that compound documents must either i) use mixed
>namespace XML (not possible for us since we are a binary format) or
>ii) using the <object> tag.
>
>However, our linking sections never talk about <object>.
>Section 3.1.2.7 says:
>HTML-to-CGM: 'target' attribute of a element [ref]; not applicable
>(n/a) for object element.
>
>Chris would probably argue that this is wrong and that it needs to
>work with the <object> tag.
>
>As I said, the WebCGM 2.0 spec relies heavily on references to HTML
>4.01, the SVG 1.2 spec does not. Our definition only talks about
>frame, we don't mention iframe, pane, or <object> etc...
>
>Here's the current SVG 1.2 wording:
>
>---
>
>target = '_replace' | '_self' | '_parent' | '_top' | '_blank' |
>"<frame-target>"
>
>This attribute should be used when there are multiple possible targets
>for the ending resource, such as when the parent document is a
>multi-frame HTML or XHTML document. This attribute specifies the name
>or portion of the target window, frame, pane, tab, or other relevant
>presentation context (e.g., an HTML or XHTML frame, iframe, or object
>element) into which a document is to be opened when the link is
>activated. The values and semantics of this attribute are the same as
>the WebCGM Picture Behavior values [WebCGM]:
>
><snip>
>
>"<frame-target>"
>  Specifies the name of the frame, pane, or other relevant presentation
>  context for display of the linked content. If this already exists, it
>  is re-used, replacing the existing content. if it does not exist, it
>  is created (the same as _blank, except that it now has a name). Note
>  that frame-target must be an XML Name [XML11].
>
>Note: The value _new is not a legal value for target (use _blank).
>
>--
>  Benoit   mailto:benoit@itedo.com
>
>This e-mail and any attachments are confidential and may be protected
>by legal privilege. If you are not the intended recipient, be aware
>that any disclosure, copying, distribution or use of this e-mail or
>any attachment is prohibited. If you have received this e-mail in
>error, please notify us immediately by returning it to the sender and
>delete this copy from your system. Thank you for your cooperation.