Issue 11685: Section: 7.11.3 (qvt-rtf)
Source:  (, )
Nature: Clarification
Severity: Minor
Summary: It is not clear when and how you choose a top-level and not-top-level relation. Primitive domains, the reason for them and the use of them, are not explained although they are used in the Relation language example A1.1.1

Resolution: 'top' is explained clearly in Section 7.2.2 Top-level Relations.
'primitive' is a bit of a secret
Revised Text: Add 7.2.4 Primitive Domains
Simple data such as configuration information or constants may be passed as parameters to a relation using
primitive domains. A primitive domain is identified by primitive keyword and no domain name. A primitive
domain is neither checkable nor enforceable.
relation Outer {
checkonly domain source s:Source {};
enforce domain target t:Target {};
where {
Inner(s,t,'target');
}
relation Inner {
checkonly domain source s:Source {name=pn};
enforce domain target t:Target {name=separator + pn};
primitive domain separator:String;
}
Actions taken:
November 26, 2007: received issue
July 15, 2014: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 26 Nov 2007 09:25:38 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Siegfried Nolte
Company: Siegfried Nolte
mailFrom: siegfried@siegfried-nolte.de
Notification: Yes
Specification: MOF QVT
Section: 7.11.3
FormalNumber: ptc/07-07-07
Version: FTF
RevisionDate: 07/07/07
Page: 14/34
Nature: Clarification
Severity: Minor
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; InfoPath.1)
Description
It is not clear when and how you choose a top-level and not-top-level relation. Primitive domains, the reason for them and the use of them, are not explained although they are used in the Relation language example A1.1.1