RE: [cgmo-webcgm] QUESTION: cascading profile

[Robert Orosz <roboro@AUTO-TROL.com>]

Dave,

I'm not sure that I follow this completely.  You say that the ATA PPF is now
identical to WebCGM 2.0 except for T.16.2 (METAFILE DESCRIPTION).  This
implies that T.24.1 (APPLICATION STRUCTURE ATTRIBUTE) is identical, and the
ATA has abandoned the refloc APS attribute in favor of the linkuri APS
attribute.  Then you make this statement:

"We could handle the linkuri/refloc debate through the ATA XCF, for
example."

Please explain and elaborate.

Thanks,

Rob

-----Original Message-----
From: Cruikshank, David W [mailto:david.w.cruikshank@boeing.com]
Sent: Tuesday, October 25, 2005 6:11 AM
To: CGM Open WebCGM TC
Subject: [cgmo-webcgm] QUESTION: cascading profile


All,

The ATA graphics group went through the PPF yesterday and  could
conceivably reduce the ATA delta profile down to the single table entry
of METAFILE DESCRIPTION.  At that point, does it make sense to even
specify an ATA PPF?  Or just reference the WebCGM 2.0 PPF?  There are a
few places where we could provide a delta, but nothing significant.  We
could handle the linkuri/refloc debate through the ATA XCF, for example.
There will still be an XCF, so it probably makes sense to specifiy an
ATA profile just to with a ProfileID just to introduce the XCF.

Thoughts?

Thx....Dave

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