Issue 4401: package may fail to permit definition of transformations (cwm-rtf) Source: Unisys (Dr. Doug Tolbert, dtolbert408(at)gmail.com) Nature: Enhancement Severity: Significant Summary: Usage experience with the CWM 1.0 Transformation package has uncovered several situations in which the package may fail to permit definition of transformations that fully capture the intent of implementors. Such problems have appeared in several unrelated modeling venues and have led some implementors to seek alternative means for describing transformations. The existing transformation package should be reviewed by the RTF and changed as needed to improve its ability to represent the breadth of transformation semantics found in practical usage scenarios. As part of this effort, the RTF should consider incorporating the existing TypeMapping package into an evolved Transformation package -- TypeMappings are, after all, really just lightweight transformations. Resolution: Revised Text: Actions taken: July 18, 2001: received issue Discussion: End of Annotations:===== From: "Tolbert, Doug M" To: issues@omg.org Subject: New Issue for CWM Revision Task Force Date: Wed, 18 Jul 2001 16:56:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: 6A3!!blN!!![\d9L-C!! Source: Unisys Corp. (Doug Tolbert, doug.tolbert@unisys.com) Nature: Extension Severity: Significant Summary: Usage experience with the CWM 1.0 Transformation package has uncovered several situations in which the package may fail to permit definition of transformations that fully capture the intent of implementors. Such problems have appeared in several unrelated modeling venues and have led some implementors to seek alternative means for describing transformations. The existing transformation package should be reviewed by the RTF and changed as needed to improve its ability to represent the breadth of transformation semantics found in practical usage scenarios. As part of this effort, the RTF should consider incorporating the existing TypeMapping package into an evolved Transformation package -- TypeMappings are, after all, really just lightweight transformations. Resolution: Revised Text: Actions taken: Subject: issue 4401 To: Doug.Tolbert@unisys.com Cc: cwm-rtf@omg.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Dan Chang" Date: Wed, 25 Jul 2001 12:47:48 -0700 X-MIMETrack: Serialize by Router on D03NM069/03/M/IBM(Release 5.0.8 |June 18, 2001) at 07/25/2001 01:47:50 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-UIDL: WlW!!pjJ!!c10!!HT]!! Doug, I am responsible for resolving this issue. Thank you for raising it. Regarding your suggestion on moving the TypeMapping package into the Transformation package, the CWM RTF can discuss this in Toronto. Doing so means that anyone who needs to use the TypeMapping package will have a dependency on the Transformation package. I am not sure this is desirable. As to the rest of the issue, since it is nonspecific, it cannot be addressed. If you have specific examples of people using the Transformation package to interchange metadata for data warehouse transformations but failed, please send them to me. Please note that: (1) The scope of the Transformation package is the data warehousing domain. (The AB has previously emphasized this point a number of times in relation to the BusinessInformation and BusinessNomenclature packages.) (2) The Transformation package has been successfully used in the OLAP package. (3) The Transformation package has been successfully used in the Warehouse Process package. (4) IBM has successfully implemented the Transformation package in DB2 Data Warehouse Center and used it to interchange metadata for data warehouse transformations. (5) SAS and IBM have successfully demonstrated interchanging warehouse process metadata in the CWM Enablement Showcase, which includes transformation metadata using the Transformation package. (6) All constructs in the Transformation package have been validated and used with the exception of TransformationTree. Regards, Dan e-business Data Technology and Standard IBM Silicon Valley Laboratory Notes: Dan Chang/Santa Teresa/IBM@IBMUS Internet: dtchang@us.ibm.com VM: IBMUSM50(DTCHANG) Phone: (408)-463-2319 Juergen Boldt cc: Subject: issues 4400 - 4405 CWM RTF issues 07/24/01 02:26 PM This is issue # 4400 "Tolbert, Doug M" XML Schema package issue The planned XML Schema package proposed for inclusion in CWM 1.1 should be cognizant of and wherever possible, equivalent to, the XML Schema model planned for the inclusion in the XMI specification. Within reason, corresponding XML Schema-specific class in the two specifications show share the same names, attributes, and relationships to other classes. From: "Tolbert, Doug M" To: Dan Chang , "Tolbert, Doug M" Cc: cwm-rtf@omg.org Subject: RE: issue 4401 Date: Wed, 25 Jul 2001 16:11:42 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: CTQd9+@Le9n^~!!h4Y!! Dan, I believe there will be some details of less-than-successful usages of the Transformation package following by email in the next few days. Please be patient until they arrive on the reflector. Regards, Doug -----Original Message----- From: Dan Chang [mailto:dtchang@us.ibm.com] Sent: Wednesday, July 25, 2001 12:48 PM To: Doug.Tolbert@unisys.com Cc: cwm-rtf@omg.org Subject: issue 4401 Doug, I am responsible for resolving this issue. Thank you for raising it. Regarding your suggestion on moving the TypeMapping package into the Transformation package, the CWM RTF can discuss this in Toronto. Doing so means that anyone who needs to use the TypeMapping package will have a dependency on the Transformation package. I am not sure this is desirable. As to the rest of the issue, since it is nonspecific, it cannot be addressed. If you have specific examples of people using the Transformation package to interchange metadata for data warehouse transformations but failed, please send them to me. Please note that: (1) The scope of the Transformation package is the data warehousing domain. (The AB has previously emphasized this point a number of times in relation to the BusinessInformation and BusinessNomenclature packages.) (2) The Transformation package has been successfully used in the OLAP package. (3) The Transformation package has been successfully used in the Warehouse Process package. (4) IBM has successfully implemented the Transformation package in DB2 Data Warehouse Center and used it to interchange metadata for data warehouse transformations. (5) SAS and IBM have successfully demonstrated interchanging warehouse process metadata in the CWM Enablement Showcase, which includes transformation metadata using the Transformation package. (6) All constructs in the Transformation package have been validated and used with the exception of TransformationTree. Regards, Dan e-business Data Technology and Standard IBM Silicon Valley Laboratory Notes: Dan Chang/Santa Teresa/IBM@IBMUS Internet: dtchang@us.ibm.com VM: IBMUSM50(DTCHANG) Phone: (408)-463-2319 Juergen Boldt cc: Subject: issues 4400 - 4405 CWM RTF issues 07/24/01 02:26 PM This is issue # 4400 "Tolbert, Doug M" XML Schema package issue The planned XML Schema package proposed for inclusion in CWM 1.1 should be cognizant of and wherever possible, equivalent to, the XML Schema model planned for the inclusion in the XMI specification. Within reason, corresponding XML Schema-specific class in the two specifications show share the same names, attributes, and relationships to other classes. ----------------------------- This is issue # 4401 "Tolbert, Doug M" package may fail to permit definition of transformations Usage experience with the CWM 1.0 Transformation package has uncovered several situations in which the package may fail to permit definition of transformations that fully capture the intent of implementors. Such problems have appeared in several unrelated modeling venues and have led some implementors to seek alternative means for describing transformations. The existing transformation package should be reviewed by the RTF and changed as needed to improve its ability to represent the breadth of transformation semantics found in practical usage scenarios. As part of this effort, the RTF should consider incorporating the existing TypeMapping package into an evolved Transformation package -- TypeMappings are, after all, really just lightweight transformations. ------------------------------- This is issue # 4402 "Tolbert, Doug M" consider changing DeployedComponent from being subclass of Core::Package In the SoftwareDeployment package, consider changing DeployedComponent from being a subclass of Core::Package to being as subclasss of Core::Subsystem. This change preserves the package nature of DeployedComponents and, at the same time, adds the ability of DeployedComponents to have features (because Core::Subsystem is a subclass of Core::Classifier, as well as Core::Package). -------------------------- This is issue # 4403 "Tolbert, Doug M" Identify precise CWM definition to which interchange doc. conforms Provide in the body of a CWM interchange document, a means for identifying the precise CWM definition to which the interchange document conforms. Something similar to the way the XML documents identify the URI of the XML definition they conform to would do nicely. Such a mechanism in effect creates a name space within which the contents of the CWM interchange document can be evaluated. Useful side effects of having such a namespace include: (1) the definition of CWM extension packages without the present need that they be accompanied by the CWM definition itself, (2) a framework in which Universally Unique Identifiers (UUIDs) can be defined for each CWM object. Several requests for CWM UUIDs have already been received informally. ----------------------------- This is issue # 4404 "Tolbert, Doug M" Review the semantics of existing attribute types that are also CWM classes The precise semantics of the use of the CWM Expression class (and its subclasses) as the type of attributes of CWM classes is not clearly delineated (as discussed at the 7/12/01 CWM RTF meeting in Danvers, MA). Review the semantics of existing attribute types that are also CWM classes and correct them as needed. ---------------------------- This is issue # 4405 "Tolbert, Doug M" diagram named "CWM Package Dependencies" shows wrong dependency arrow In the CWM .mdl file, the diagram named "CWM Package Dependencies" contains a dependency arrow showing that the Relational package depends on the SoftwareDeployment package. This dependency arrow is erroneous and should be removed (the dependency does not appear in the definitional CWM XMI file). ================================================================ Juergen Boldt Senior Member of Technical Staff Object Management Group Tel. +1-781 444 0404 ext. 132 250 First Avenue, Suite 201 Fax: +1-781 444 0320 Needham, MA 02494, USA Email: juergen@omg.org URL: www.omg.org ================================================================