Re: I-D ACTION:draft-ietf-ldapext-ldapv3-dupent-00.txt

[Jim Sermersheim <JIMSE@novell.com>]

>>> Erik Skovgaard <eskovgaard@geotrain.com> 11/25/98 2:57:21 PM >>>

>One major beef I have with your document is the rather casual use of
>directory terminology.  What you are trying to address is the multi-valued
>attributes, not multiple entries.  An Entry in the Directory is the
>instantiation of an Object Class complete with all the attributes that
>describe the instantiated object.

Well, I'm trying to say that you can use this control to represent (re-present) an entry (as you describe it above) as multiple (duplicate) entries depending on the number of values in a specified attribute.  Is there some specific text in the document that seems to be talking about multiple entries in the directory?

>I would suggest calling the paper: "LDAP Control for Handling Attributes
>with Multiple Values Returned in Search Results".  Or perhaps just: "LDAP
>Control for Handling Attributes with Multiple Values".

What I meant to say by "LDAP Control for a Duplicate Entry Representation of Search Results" is what I said above and could be re-stated as "LDAP Control for Representing Search Result Entries as Multiple Duplicate Entries Based on Multivalued Attributes".  Your suggestions shorten this quite a bit but make the objective a bit more ambiguous (for Handling as opposed to Duplicate Entry Representation).  You're right, the title is a little foul, I think adding "Multiple Valued Attributes" helps, but do you think using "for Handling" is too loose a term for what is being done?

I'll try to think about an ideal title.  What about the body?  Is there confusing language there as well?

Thanks. Jim