Issue 19659: Missing TracePackage (qvt-rtf)
Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk)
Nature: Clarification
Severity: Minor
Summary: The example transformation creates numerous orphan trace classes.


Surely these should be contained by a trace Package?


This could be produced by a top level RelationalTransformationToTracePackage relation. RelationToTraceClass should then not be top level.

Generation of trace is separate from core, so surely there should be a trace direction for the trace output? The core direction should use the trace direction.
Resolution: 
Revised Text: 
Actions taken:
November 21, 2014: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 21 Nov 2014 02:34:18 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Ed Willink
Employer:        
mailFrom:        ed@willink.me.uk
Terms_Agreement: 
Specification:   QVT
Section:         10
FormalNumber:    QVT 1.2
Version:         1.2
Doc_Year:        Year
Doc_Month:       Month
Doc_Day:         Day
Page:            n/a
Title:           Missing TracePackage
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue
Remote Name:     host81-155-171-149.range81-155.btcentralplus.com
Remote User:     
HTTP User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0
Time:            02:34 AM


Description:


The example transformation creates numerous orphan trace classes.


Surely these should be contained by a trace Package?


This could be produced by a top level RelationalTransformationToTracePackage relation. RelationToTraceClass should then not be top level.

Generation of trace is separate from core, so surely there should be a trace direction for the trace output? The core direction should use the trace direction.