Issue 765:  Map/SortedMap (zz-collection)
Source:  (, )
Nature:  Revision
Severity:  Significant
Summary: Summary: There is a confusing/conflicting situation in 2 parts of the document. Page 17-12 Map/SortedMap states that you can insert an object with 2 different keys (nicknames). The first note on page 17-122 states that if both key and element equality are defined, element and equality must imply key equality.

Resolution: 
Revised Text: 
Actions taken:
September 29, 1997: received issue
Discussion: 

End of Annotations:=====
Return-Path: <geoff>
Date: Mon, 29 Sep 1997 10:04:55 -0400
From: Geoffrey Speare <geoff@omg.org>
To: issues
CC: Ringo.DeSmet@advalvas.be
Subject: [Ringo.DeSmet@advalvas.be: Object Collection Service: docs.]


Ringo,

I'm forwarding your message to issues@omg.org; from there, your
comments and
questions will be logged and forwarded to the group responsible for
updating
the Collection Service specification. 

Thanks for pointing these out!

Geoff Speare
OMG
geoff@omg.org

------- Start of forwarded message -------

And now for the hard part: the questions!

  1. I have found a rather confusing (conflicting?) situation in two
     parts of the docs. On page 17-12, I read the example related to
     the Map/SortedMap. It is stated that you can insert an object
     (personal data) with 2 different keys (the nicknames). The
     semantics of equal is in my case 2 objects which have the same
     personal data. Now I take the first note on page 17-122. I can
     read there that if both key and element equality are defined,
     that for a consistent definition, element equality must imply key
     equality. But I have inserted 2 equal objects with a different
     key in my Map. Conflicting situation, no?