Issue 2400:  Clarify the areEquivelent interface of the CurrencyBook                                                                                                                                                (currency-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: areEquivalent() “determines whether the two passed-in Currency objects
 contain the same elements”. Again, what needs to be fully detailed are
 those Currency elements which must be to determine uniqueness. e.g.
 mnemonic, numeric code, etc.
 

Resolution: closed, resolved by Currency 2 RTF
Revised Text: Resolution: Update the spec to be clear that is all elements of the currency object, not just the key fields, as was intended from the original spec.
Revised Text: 
In section 2.3.10 add the following sentence to the sentence "The areEquivalent interface determines whether the two passed-in currency objects contain the same elements":
All elements of the currency value types are checked, not just the elements that make them unique.

Actions taken:
January 11, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <Robert_Mickley@CYBORG.COM>
From: Robert_Mickley@CYBORG.COM
X-Lotus-FromDomain: CYBORG@CYBORG_NET
To: issues@omg.org
cc: Robert_Mickley@CYBORG.COM, Amy_Griffis@CYBORG.COM
Date: Mon, 11 Jan 1999 21:28:52 -0700
Subject: Currency RTF Issues
Content-Disposition: inline



Today is the deadline for comments for the Currency RTF.  Below is an
itemized list of additions to that list.

Issue Title:  Clarify the areEquivelent interface of the CurrencyBook
Issue Type: Text Revision
Issue Description:
areEquivalent() contain the same elemenst. Again, what needs to be
fully detailed are
those Currency elements which must be to determine uniqueness. e.g.
mnemonic, numeric code, etc.