Issue 16235: Use of the word meta (ocl2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: I want to signal that the use of the word "meta" is confusing. Here is an example on page 47. *TypeExp* A TypeExp is an expression used to refer to an existing meta type within an expression. According to Merriam-Webster, "meta" is usually a prefix that could be added at the beginning of a word. This particle should be merged to the main word (like in metabasis) or attached using an hyphen (like meta-analysis). In consequence, we should read "metatype" which seems to hold the correct meaning. It is coherent with metaclass, for example. By the way, "metatype" is used at many places in the document. In some contexts and in the familiar language, you can use "meta" as a diminutive for something when its meaning is obvious. For example, "the meta is broken" when you mean the metacarpus. In a specification document and in a context where we have to differentiate many metaconcepts, it doesn't have its place. It is seen at many places in this document and may be other. In this one, we see "meta model" and "meta-model", while the word "metamodel" should be and is effectively used. Resolution: yes Revised Text: In 8.3.1 TypeExp Replace two occurrences of meta type by type to give A TypeExp is an expression used to refer to an existing type within an expression. It is used in particular to pass the reference of the type when invoking the operations oclIsKindOf, oclIsTypeOf, and oclAsType. Excluding the Bibliography, replace all (5) occurrences of meta-model..., meta model by metamodel... Actions taken: May 13, 2011: received issue December 23, 2013: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 13 May 2011 14:09:43 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Dominic Roy Employer: CumuloCogitus Inc. mailFrom: roy.dominic@sympatico.ca Terms_Agreement: I agree Specification: Object Constraint Language (OCL) Section: 8.3.1 FormalNumber: ptc/2010-11-42 Version: 2.3 Doc_Year: 2010 Doc_Month: December Doc_Day: 01 Page: 47 Title: Use of the word meta Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Description: I want to signal that the use of the word "meta" is confusing. Here is an example on page 47. *TypeExp* A TypeExp is an expression used to refer to an existing meta type within an expression. According to Merriam-Webster, "meta" is usually a prefix that could be added at the beginning of a word. This particle should be merged to the main word (like in metabasis) or attached using an hyphen (like meta-analysis). In consequence, we should read "metatype" which seems to hold the correct meaning. It is coherent with metaclass, for example. By the way, "metatype" is used at many places in the document. In some contexts and in the familiar language, you can use "meta" as a diminutive for something when its meaning is obvious. For example, "the meta is broken" when you mean the metacarpus. In a specification document and in a context where we have to differentiate many metaconcepts, it doesn't have its place. It is seen at many places in this document and may be other. In this one, we see "meta model" and "meta-model", while the word "metamodel" should be and is effectively used.