Issue 15924: Gap in KDM Platform Package (kdm-rtf) Source: Benchmark Consulting (Mr. Alain Picard, apicard(at)benchmarkconsulting.com) Nature: Uncategorized Issue Severity: Summary: In the platform package we don't seem to have any direct way to express relations between AbstractPlatformElement and InventoryElement. A good example is how to describe the file in the inventory model that represents a certain deployed component. AbstractPlatformElement has a source relation to a SourceRef but here we're not dealing with a Source inventory element (not sure how often PlatformElement would really need this relation). The Build package uses the implementation relation which points to KDM entity to describe relations to inventory elements. Again here in the platform package this points to AbstractCodeElement only. I hate to have to use stereotypes to build such a basic relation. Resolution: Revised Text: Actions taken: January 10, 2011: received issue Discussion: End of Annotations:===== te: Mon, 10 Jan 2011 20:23:42 -0500 Subject: Gap in KDM Platform Package From: Alain Picard To: nick@kdmanalytics.com, kdm-rtf@omg.org Nik, In the platform package we don't seem to have any direct way to express relations between AbstractPlatformElement and InventoryElement. A good example is how to describe the file in the inventory model that represents a certain deployed component. AbstractPlatformElement has a source relation to a SourceRef but here we're not dealing with a Source inventory element (not sure how often PlatformElement would really need this relation). The Build package uses the implementation relation which points to KDM entity to describe relations to inventory elements. Again here in the platform package this points to AbstractCodeElement only. I hate to have to use stereotypes to build such a basic relation. Cheers, Alain -- Alain Picard Chief Strategy Officer Benchmark Consulting 813-787-3424 apicard@benchmarkconsulting.com www.benchmarkconsulting.com Subject: Re: Gap in KDM Platform Package From: Nikolai Mansourov Date: Tue, 11 Jan 2011 15:10:26 -0500 Cc: kdm-rtf@omg.org To: Alain Picard X-Mailer: Apple Mail (2.1082) X-Authenticated: nickmansurov - ottawa-hs-64-26-169-119.s-ip.magma.ca ([192.168.0.188]) [64.26.169.119] Alain, I appreciate your reports! I suggest we start the discussion regarding the KDM 1.4 where we can do a substantial cleanup of the metamodel. I was thinking, there are several issues that require changes to the XMI format, but are not big enough to be KDM 2.0. We should have a discussion to what will be acceptable at this point. Cheers, Nick On 2011-01-10, at 8:23 PM, Alain Picard wrote: Nik, In the platform package we don't seem to have any direct way to express relations between AbstractPlatformElement and InventoryElement. A good example is how to describe the file in the inventory model that represents a certain deployed component. AbstractPlatformElement has a source relation to a SourceRef but here we're not dealing with a Source inventory element (not sure how often PlatformElement would really need this relation). The Build package uses the implementation relation which points to KDM entity to describe relations to inventory elements. Again here in the platform package this points to AbstractCodeElement only. I hate to have to use stereotypes to build such a basic relation. Cheers, Alain -- Alain Picard Chief Strategy Officer Benchmark Consulting 813-787-3424 apicard@benchmarkconsulting.com www.benchmarkconsulting.com