Issue 10937: 9.18: Realized (qvt-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Uncategorized Issue Severity: Summary: The concrete syntax defines 'realized', but section 10 consistently uses 'realize'. Suggest: 'realize' The concrete syntax defines 'realized' for a single element of a comma-separated list. Section 10 appears to expect that 'realized' is a prefix to a comma-separated list. Suggest: 'realize' is a comma-separated list prefix. (semi-colon separation is available for distinct realize/not-realize.) Resolution: Use 'realize' as a keyword in the concrete syntax. Use 'realized' as an adjective in editorial text, model names; e.g. RealizedVariable Revised Text: In 9.18 Concrete Syntax change RealizedVariable := “realized” VariableName “:” TypeDeclaration to RealizedVariable := “realize” VariableName “:” TypeDeclaration Actions taken: March 25, 2007: received issue July 15, 2014: closed issue Discussion: End of Annotations:===== s is issue # 10937 From: "Ed Willink" The concrete syntax defines 'realized', but section 10 consistently uses 'realize'. Suggest: 'realize' The concrete syntax defines 'realized' for a single element of a comma-separated list. Section 10 appears to expect that 'realized' is a prefix to a comma-separated list. Suggest: 'realize' is a comma-separated list prefix. (semi-colon separation is available for distinct realize/not-realize.) Date: Wed, 10 Dec 2008 06:41:39 +0000 From: Ed Willink User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) To: issues@omg.org Subject: Re:MOF-QVT Issue 10937: 9.18: Realized (qvt-rtf) X-Plusnet-Relay: 963d6eee0679a35e5e9b040eebad8dcc Hi Partial retraction. Issue 10937 has two sub-issues: The inconsistent spelling of 'realize' and 'realized' needs resolving. My statement 'Section 10 appears to expect that 'realized' is a prefix to a comma-separated list.' is wrong. Section 10 is semantically consistent with the grammar; 'realize/realized' should remain a per-variable prefix. Structuring text to avoid reader confusion is a style issue. Regards Ed Willink