Issue 8525: add assetVersion attribute to RelatedAsset (ras-ftf) Source: International Business Machines (Mr. Grant Larsen, gjlarsen(at)us.ibm.com) Nature: Uncategorized Issue Severity: Summary: Currently the RelatedAsset class/element only contains the id of the related asset. This is fine if the related asset relationship type is aggregation because the related asset has a reference to the actual artifact that represents the asset. We need to support loosely coupled asset relationships where you don't have a direct reference to the related asset but instead some rules of where to search for it. In this scenario, we need more information to uniquely identify the asset. Specifically...we need the version of the related asset. We'd like to add an assetVersion attribute to the RelatedAsset element to match the assetId attribute that already exists. We think this provide us the information we would need for this loose coupling. Resolution: Revised Text: Resolution: Add to section 7.4.12 RelatedAsset the image below showing the assetVersion attribute. Add the following text at the end of the attributes already described in this section: The assetVersion attribute contains the version of the related asset. Actions taken: March 9, 2005: received issue August 1, 2005: closed issue Discussion: End of Annotations:===== ubject: RAS FTF: add assetVersion attribute to RelatedAsset X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Grant J Larsen Date: Tue, 8 Mar 2005 23:04:19 -0700 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Build V70_M4_01112005 Beta 3|January 11, 2005) at 03/08/2005 23:04:20, Serialize complete at 03/08/2005 23:04:20 Currently the RelatedAsset class/element only contains the id of the related asset. This is fine if the related asset relationship type is aggregation because the related asset has a reference to the actual artifact that represents the asset. We need to support loosely coupled asset relationships where you don't have a direct reference to the related asset but instead some rules of where to search for it. In this scenario, we need more information to uniquely identify the asset. Specifically...we need the version of the related asset. We'd like to add an assetVersion attribute to the RelatedAsset element to match the assetId attribute that already exists. We think this provide us the information we would need for this loose coupling. Thanks, Grant ----------------------------------------------------------- Grant Larsen STSM IBM Rational software Voice: (303) 932-7368 Mobile: (303) 601-1257 Fax: (303) 932-6963 Notes: Grant J Larsen/Denver/IBM E-mail: gjlarsen@us.ibm.com