-
Key: IPMFSSF-9
-
Legacy Issue Number: 19560
-
Status: closed
-
Source: THALES ( Olivier Constant)
-
Summary:
On behalf of Olivier Constant, Thales Group:
p.11. Figure 5, a note states "Element must own Property". This implies that the Element be a MOF::Class/DataType/Association/Extension. What is really meant, according to my understanding, is "Metaclass of Element must own Property". A similar issue arises in section 10.11 in the description of PropertyToRole::from.
-
Reported: IPMSS 1.0b1 — Thu, 31 Jul 2014 04:00 GMT
-
Disposition: Resolved — IPMSS 1.0
-
Disposition Summary:
MOF hierarchy false implication needs to be clarified. The intent was not that a MOF::Element contain a MOF::Property, as that limits the relationship to a certain subset of MOF classes. Instead, a metaclass was intended. The text in Figure 5, Sections 10.11 and 10.2 needs to be changed to reflect this.
-
Updated: Wed, 8 Jul 2015 12:06 GMT
-
Attachments:
- IPMSS1.0Figure5.pdf 35 kB (application/pdf)
- IPMSS1.0Figure5.png 125 kB (image/png)
IPMFSSF — Clarification needed on 'Element' ownership of Property, or 'metaclass of Element' ownership of Property
- Key: IPMFSSF-9
- OMG Task Force: Implementation Pattern Metamodel For Software Systems 1.0 FTF