MOF24 — Issue for MOF 2 spec (ptc/04-10-15)

There are some shortcomings in the discussion of the isSet() and unset() operations of the Element class. In particular, there is no mention of optional properties in the Semantics section of the Element description.

Is is intended that optional properties be covered by the semantics inSingle-valued properties? If so, how, if at all, does the fact that a property is optional interact with the default for the property? For example, I assume that notwithstanding the spec language:

If a single-valued property has a default:
• It is set to that default value when the element is created. isSet=false

that an optional property will NOT, in fact, be set, and that isSet would be false.

Disposition: See issue 8269 for disposition