Meta Object Facility Avatar
  1. OMG Specification

Meta Object Facility — Closed Issues

  • Acronym: MOF
  • Issues Count: 4
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

Container and owningProperty

  • Key: MOF24-20
  • Legacy Issue Number: 9147
  • Status: closed  
  • Source: Honeywell ( David Oglesby)
  • Summary:

    On an Object, container() is defined as
    result = self.get(self.owningProperty())
    where owningProperty() is defined as
    result = self.allProperties->select(op| op.isComposite and self.get(op)
    <> null)

    If I read this correctly, the container of an object is the value of a
    property on that object such that isComposite on the property is true
    and the value of the property on the object is not null.

    How is that not backwards? The value of an object's composite properties
    are the objects it contains. Don't we want (op|
    op.opposite.isComposite and self.get(op) <> null)?

  • Reported: MOF 1.4 — Thu, 10 Nov 2005 05:00 GMT
  • Disposition: Resolved — MOF 2.4
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

FormalNumber: formal/02-04-03 section 3.6.2

  • Key: MOF24-24
  • Legacy Issue Number: 11157
  • Status: closed  
  • Source: VBA ( Tomasz Biegacz)
  • Summary:

    In the specification [The “lower” bound of a MultiplicityType to be “Unbounded.” [C-54]] [The “upper” bound of a MultiplicityType cannot be less than 1. [C-56]] and it should be [The “upper” bound of a MultiplicityType to be “Unbounded.” [C-54]] [The “lower” bound of a MultiplicityType cannot be less than 1. [C-56]]

  • Reported: MOF 1.4 — Wed, 18 Jul 2007 04:00 GMT
  • Disposition: Resolved — MOF 2.4
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

MOF 2.0 Core: Inconsistency about use of defaults

  • Key: MOF24-19
  • Legacy Issue Number: 8269
  • Status: closed  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    In ptc/04-10-05, section 9.1, the documentation for isSet() states that it "returns true if the value of the Property is different than the default value of that property. "
    However later on in the section under Semantics, it states:

    If a single-valued property has a default:

    ....

    • If the value of that property is later explicitly set, even to the default value, isSet=true,

    Thus there is an inconsistency as to the value if isSet() in the case where the property has been explicitly set to a value that happens to be the same as its default.

  • Reported: MOF 1.4 — Fri, 11 Feb 2005 05:00 GMT
  • Disposition: Resolved — MOF 2.4
  • Disposition Summary:

    It’s important to note that Property::default is used only for initial assignment on element creation, not as the value returned in absence of an explicit value.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

MOF 2 Core: undefined behavior of convertToString

  • Key: MOF24-18
  • Legacy Issue Number: 8267
  • Status: closed  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    Section 9.1 of ptc/04-10-15 defines operation convertToString that takes an Object parameter and converts to a string representation for a supplied DataType.
    However no exception is defined for when the supplied Object is an instance of a ModelElement and not a DataType.

  • Reported: MOF 1.4 — Fri, 11 Feb 2005 05:00 GMT
  • Disposition: Resolved — MOF 2.4
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT