RE: WG last call on "duplicate entries"

[Dave Watts <DJW@dataconnection.com>]

Kurt, Jim,

"Both" is a fine answer, but I'm not sure Kurt's suggested minor editorial
change clarifies things explicitly enough. We could add something like the
following to 4.1.1 (or made into a 4th example in section 5).

...

For the purposes of determining multi-valuedness, values of subtypes are
treated as if they were values of the supplied attribute.  eg 'cn;lang-en'
is a subtype of 'cn' is a subtype of 'name', so an entry with
  cn: Johann
  cn;lang-en: John
is considered to have two values of 'name'.

....

This makes things completely explicit, but you might consider it
over-the-top. Your call.

Cheers,

David




-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: 26 March 2001 15:57
To: Dave Watts
Cc: 'jimse@novell.com'; 'roland@catalogix.se'; ietf-ldapext@netscape.com
Subject: RE: WG last call on "duplicate entries"


At 09:33 AM 3/26/01 +0100, Dave Watts wrote:
>I have a minor query about draft-ietf-ldapext-ldapv3-dupent-06.txt.
>
>Section 4.1.1 contains the following paragraph.
>
>   <snip>
>
>   While processing a search request, a server implementation examines
>   this list.  If a specified attribute or attribute subtype exists in
>   an entry to be returned by search, and that attribute holds multiple
>   values, the server treats the entry as if it were multiple,
>   duplicate entries -- the specified attributes each holding a single,
>   unique value from the original set of values of that attribute.
>
>   <snip>

I would suggest a minor editorial change.
s/attribute or attribute subtype/attribute or its subtype/

>When you talk about attribute subtypes, are you thinking of:
>- subtyping via attribute options (eg 'cn;lang-en' is a subtype of 'cn')
>- subtyping via attribute hierarchy (eg 'cn' is a subtype of 'name')
>- both?

I believe this sentence is the result of prior list discussion.  The
answer is both.  This is consistent with how requested attributes in
search operations are handled in LDAP/X.500.