Issue 18323: Trace data for an 'accessed' transformation (qvt-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: The spec should clarify the interaction of 1.) explicit instantiation + execution of 'accessed' transformations, and 2.) trace records / resolving. The following questions are of interest: How does the initial trace for an 'accessed' transformation look like? Does it reuse the records previously created by the 'accessing' transformation, or does an 'accessed' transformation always start on an empty trace? How does an 'accessed' transformation affect the trace? Are the trace records post-visible that were created during execution of the 'accessed' transformation, or is the trace of the 'accessing' transformation unchanged? Both issues heavily affect the results of resolve-operations. Resolving object references after executing an 'accessed' transformation would be very practical. Resolution: Trace data for an 'accessed' transformation The spec should clarify the interaction of 1.) explicit instantiation + execution of 'accessed' transformations, and 2.) trace records / resolving. The following questions are of interest: How does the initial trace for an 'accessed' transformation look like? Does it reuse the records previously created by the 'accessing' transformation, or does an 'accessed' transformation always start on an empty trace? How does an 'accessed' transformation affect the trace? Are the trace records post-visible that were created during execution of the 'accessed' transformation, or is the trace of the 'accessing' transformation unchanged? Both issues heavily affect the results of resolve-operations. Resolving object references after executing an 'accessed' transformation would be very practical. Discussion The resolution of [1]QVT13-23 makes clear that the trace data contains a trace record for every mapping. ---------------------------------------------------------------------------------------- [1] http://issues.omg.org/browse/QVT13-23 Revised Text: Actions taken: December 27, 2012: received issue December 22, 2015: Duplicate or Merged March 29, 2016: closed issue Discussion: Help wanted. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 27 Dec 2012 07:25:42 -0500 To: Subject: Issue/Bug Report X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== ******************************************************************************* Name: Christopher Gerking Employer: mailFrom: cgerking@campus.upb.de Terms_Agreement: I agree Specification: Meta Object Facility (MOF) 2.0 Query/View/ Transformation Specification Section: 8.2.1.4 ModuleImport FormalNumber: formal/2011-01-01 Version: 1.1 Doc_Year: 2011 Doc_Month: January Doc_Day: 01 Page: 83 Title: Trace data for an 'accessed' transformation Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Description: The spec should clarify the interaction of 1.) explicit instantiation + execution of 'accessed' transformations, and 2.) trace records / resolving. The following questions are of interest: How does the initial trace for an 'accessed' transformation look like? Does it reuse the records previously created by the 'accessing' transformation, or does an 'accessed' transformation always start on an empty trace? How does an 'accessed' transformation affect the trace? Are the trace records post-visible that were created during execution of the 'accessed' transformation, or is the trace of the 'accessing' transformation unchanged? Both issues heavily affect the results of resolve-operations. Resolving object references after executing an 'accessed' transformation would be very practical.