Re: Final Review

[Dieter@isodraw.de (Dieter Weidenbrueck)]

I agree with this approach, however, the linkURI uses the URI in general,
and that may point to anything.

There is actually something that is not absolutely clear right now. The
WebCGM spec talks about "the viewer displays ... in a new window" etc.
In fact, this would only apply to standalone viewers that could handle the
respective MIME types. The normal case is that the viewer initiates the
navigation process and lets somebody else take care of it, which may
actually be a programm that resides on the local hard disc (in the
file://... cases).

So what is the expected, and what is the testable behavior in the following
case taken from the CGM to HTML part:

"The viewer shall load the designated document in a new, unnamed window."

1. The URL may point to anything, not just a document, it could be a query
as well.
2. Do we REQUIRE the viewer itself to open a new window and display whatever
the URL points to?
3. or do we REQUIRE the viewer to initiate a navigation process that
eventually makes some other program display the target?
4. If 3 is true, are there any testable requirements as to which
communication interfaces / which browsers / which script languages must be
supported?

This may be overreacting, however, if Lofton writes a test case for this
feature, how would you do it?

Dieter

----- Original Message -----
From: "Lofton Henderson" <lofton@rockynet.com>
To: "Cruikshank, David W" <David.Cruikshank@PSS.Boeing.com>
Cc: <cgmopen-members@lists.oasis-open.org>
Sent: Tuesday, April 17, 2001 12:23 AM
Subject: RE: Final Review


> At 02:45 PM 4/16/01 -0700, you wrote:
> >I'm thinking that maybe, since HTML the most common mime type we are
> >interacting with, we should just add a note that indicates that non-cgm
> >mime type links shall have the same behavior as described for HTML
> >interactions?
>
> I like this approach.
>
> I recall that we talked of other mime types, but we were really designing
> WebCGM 1.0 specifically so that it would (at least) be fully specified for
> combination with HTML.
>
> -Lofton.
>
> >thx...dave
> >
> > > ----------
> > > From:         Dieter@isodraw.de[SMTP:Dieter@isodraw.de]
> > > Reply To:     Dieter
> > > Sent:         Monday, April 16, 2001 12:39 PM
> > > To:   Cruikshank, David W; cgmopen-members@lists.oasis-open.org
> > > Subject:      Re: Final Review
> > >
> > > David,
> > >
> > > unfortunately, I can't find the time right now to read everything.
> > >
> > > However, I spotted one small thing that's possibly worth changing:
> > > In one area we are talking about CGM to HTML links (the table and the
text
> > > around it). This should probably be changed to CGM to Non-CGM links,
> > because
> > > the logic behind these paragraphs is not restricted to HTML at all and
does
> > > apply to any MIME type that is not CGM for that matter.
> > >
> > > Dieter
> > >
> > > ----- Original Message -----
> > > From: "Cruikshank, David W" <David.Cruikshank@PSS.Boeing.com>
> > > To: <cgmopen-members@lists.oasis-open.org>
> > > Sent: Thursday, April 12, 2001 10:05 PM
> > > Subject: Final Review
> > >
> > >
> > > > Members,
> > > >
> > > > Attached are two zip files containing the WebCGM Second Release html
> > > pages.  The file forward.zip contains the page that is retrieved by
> > clicking
> > > on WebCGM on the w3.org site.  The webcgm.zip file contains the cover
page
> > > (REC-WebCGM.html), the expanded table of contents
> > (REC-WebCGM-TOC.html), the
> > > errata (editing directives), and the four parts of the
> > specification.  Links
> > > between the four parts should now all work and be consistent.  Links
to the
> > > cover page information and forward will have to be cleaned up by Chris
when
> > > he installs in on the w3c web site.
> > > >
> > > > Please review the specification for correctness and clarity.
Anything
> > > beyond that gets stacked for WebCGM 2.0.  Since we've got a weekend
coming
> > > up, I'm giving everyone a chance to review it over the weekend.  I
need any
> > > and all comments by COB Monday, April 16.
> > > >
> > > > thx...Dave
> > > >  <<forward.zip>>  <<webcgm.zip>>
> > > > Technical Fellow - Graphics/Digital Data Interchange
> > > > Boeing Commercial Airplane Company
> > > > 206.544.8876, fax 206.544.9878
> > > > david.w.cruikshank@boeing.com
> > > >
> > >
> >
> >------------------------------------------------------------------
> >To unsubscribe from this elist send a message with the single word
> >"unsubscribe" in the body to:
cgmopen-members-request@lists.oasis-open.org
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: cgmopen-members-request@lists.oasis-open.org