RE: [cgmo-webcgm] ISSUE: aci/viewer association

[Lofton Henderson <lofton@rockynet.com>]

At 10:06 AM 5/20/2008 -0700, Cruikshank, David W wrote:
>Sorry for introducing the concept of "user" requirements into the
>process.

Actually, we do have approved user requirement documents:
[1] 
http://www.oasis-open.org/committees/download.php/26392/WebCGM%202_1%20Requirements.htm
[2] 
http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/download.php/26099/Attributes_Table.pdf

The first time I saw this detail of the font-sub requirement articulated 
was in your message of two days ago.  Perhaps concern with this is what 
Benoit was trying to express?

There is no hint in [1] and [2] of the additional requirement detail 
(same-invocation-method-on-every-OS).

I had a similar issue with the defaults stuff, binding LETD to line types 
1..5.  The endorsed requirements seem pretty clear about making "dash" look 
uniform on every system.  There is a proposal that it should allow the 
reassignment of any line type to 1..5.  (The proposal is actually in the 
CD01 text, which no one had a chance to review before inclusion in the 
published CD01.)

To me, such modifications of requirements should get TC endorsement.  It is 
just a matter of good process.

-Lofton.

>Technical Fellow - Graphics/Digital Data Interchange
>Boeing Commercial Airplane
>206.544.3560, fax 206.662.3734
>david.w.cruikshank@boeing.com
>
>-----Original Message-----
>From: Bezaire, Benoit [mailto:bbezaire@ptc.com]
>Sent: Tuesday, May 20, 2008 6:25 AM
>To: CGM Open WebCGM TC
>Subject: RE: [cgmo-webcgm] ISSUE: aci/viewer association
>
>Hi Dieter, Dave,
>
>Option 2 and 3 could imply that the ACI is applied 'per CGM file'; that
>would increase the complexity of the implementation (for all vendors).
>
>Can't the website provide a hyperlink to the ACI file? The user would
>download the ACI and save it in the appropriate location for that
>viewer?
>
>Dave, I think you are 'stretching' the requirements. The group agreed to
>standardize our preferences files, which meets the requirement. You are
>now asking about a common association... Please suggest something that
>addresses your concern with minimal implementation work from vendors;
>i.e., does not require to apply the ACI each time a CGM is loaded.
>
>I think it is fair to say that vendors have a limited number of
>resources. I would have thought the goal of a new specification was to
>encourage the creation of new interactive CGM files; as oppose to
>encouraging the circulation of older (valid?) files.
>
>This issue/feature has been the most active topic since the WebCGM 2.1
>re-charter. I, myself, am looking for closure on it.
>
>Benoit
>
>
>-----Original Message-----
>From: Weidenbrueck, Dieter [mailto:dweidenbrueck@ptc.com]
>Sent: Monday, May 19, 2008 5:06 PM
>To: Cruikshank, David W; CGM Open WebCGM TC
>Subject: RE: [cgmo-webcgm] ISSUE: aci/viewer association
>
>David,
>
>I can see several ways forward here:
>
>(setting an environment variable is not one of them because IT folks
>don't like if we intrude the system more then necessary)
>
>1. Standardize the location
>Agree on a single location that a viewer has to look at for the file.
>Don't think this would work, too many variants here with Vmware and with
>server hosted prefs.
>
>2. Use a URL to tell the viewer about a prefs file Create a URI that
>would tell the viewer where to find a prefs file, e.g.
>...dummy.cgm#acifile(pathToFile)
>The viewer could ignore dummy.cgm and only download the aci file I
>consider this to be a hack (possibly a bad one)
>
>3. Create a DOM call to tell the viewer
>myViewer.loadACIFile(fullPath);
>This would be a straightforward way to tell the viewer where to find the
>file and what to do with it.
>The viewer could then copy the file into a location that it likes, and
>merge the content with whatever ist own prefs are.
>
>4. Simply provide the aci file to the end user and ask him to store it
>in a special location Not a good solution, we could stay with what we
>have now, should be more reliable.
>
>Did I miss an option?
>
>Regards,
>Dieter
>
>-----Original Message-----
>From: Cruikshank, David W [mailto:david.w.cruikshank@boeing.com]
>Sent: Montag, 19. Mai 2008 22:56
>To: CGM Open WebCGM TC
>Subject: [cgmo-webcgm] ISSUE: aci/viewer association
>
> >From the minutes of the TC telecon of 14 May:
>
>AI - Someone should draft an informative annex on how an environmental
>variable or some such method could be used to specify the file
>
>I think this tells me that the result of the discussion was that we
>could standardize the format of the the aci, but how it was attached to
>a viewer was "unspecified" except for an informative suggestion?
>
>Can the viewer vendors not implement a common association method?
>
>In the case of myself building an IETP, there is probably not a problem
>if I have to deal with a different method for each vendor, because my
>IETP is going to use a single viewer.
>
>However, remember, my use case is delivering a web site to a customer
>with the only requirement that he have an html browser with a WebCGM
>plugin.
>
>I don't think an informative annex solves this problem.  Or am I missing
>something?
>
>Dave
>Technical Fellow - Graphics/Digital Data Interchange Boeing Commercial
>Airplane 206.544.3560, fax 206.662.3734 david.w.cruikshank@boeing.com
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php