Matt/NDRSC Team, The issue I am trying raise is when an engineering collaboration scenario requires sharing of structured data from engineering systems that CANNOT be pre-defined in a document per se (e.g., mass properties data, dimensions data, max/min temperature tolerances, etc). The example I provided is an attempt to illustrate one such scenario - very real within the aerospace industry as well as perhaps others such as automotive - both highly dependent on the sharing of engineering data - NOT the sharing of traditional transactions (such as those in your reply) that seem to be the only scope of interest to the ebXML community. I guess I am really trying to open the eyes of the ebXML community to a requirement (at least within the aerospace industry) to standardize XML tag structures for objects other than traditional EDI objects. For your consideration, the ebXML mission on the ebXML Web page states To provide an open XML-based infrastructure enabling the global use of electronic business information in an interoperable, secure and consistent manner by all parties. If engineering data is considered out-of-scope for ebXML, then I'll take my issue elsewhere and solve it elsewhere. Ronald L. Schuldt Senior Staff Systems Architect Lockheed Martin Enterprise Information Systems 11757 W. Ken Caryl Ave. #F521 MP DC5694 Littleton, CO 80127 303-977-1414
ron.l.schuldt@lmco.com