>>>>> Michael Ströder <michael...> writes:
>> It seems that the cases when the same real world object is described
>> by several DIT entries are not uncommon.
>> The only thing that comes to my mind is a separate multi-value
>> attribute holding the DNs of all the DIT entries known to describe
>> the same real-world object, like:
>> ( ... NAME 'knownOtherObjectName'
>> EQUALITY distinguishedNameMatch
>> SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
> There is already an attribute type defined like that in section
> 2.30. of RFC 4519. Not sure whether that is the right approach for
> your particular application though.
I'm not quite sure that this attribute is appropriate.
From its description below it's clear that this attribute is to
hold references to the entries corresponding to the real-world
objects that are (somehow) related to the given real-world
object. The attribute I had in mind is either more specific or
(if ``related'' is specifically prohibited from carrying the
meaning ``being the same'') completely different.
Therefore, using `seeAlso' in such a way would, at least,
confuse potential users of the data.
--cut: http://www.rfc-editor.org/rfc/rfc4519.txt --
2.30. 'seeAlso'
The 'seeAlso' attribute type contains the distinguished names of
objects that are related to the subject object. Each related object
name is one value of this multi-valued attribute.
(Source: X.520 [X.520])
( 2.5.4.34 NAME 'seeAlso'
SUP distinguishedName )
...
Example: The person object "cn=James Brown,ou=employee,o=Widget\,
Inc." is related to the role objects "cn=Football Team
Captain,ou=sponsored activities,o=Widget\, Inc." and
"cn=Chess Team,ou=sponsored activities,o=Widget\, Inc.".
Since the role objects are related to the person object, the
'seeAlso' attribute will contain the distinguished name of
each role object as separate values.
--cut: http://www.rfc-editor.org/rfc/rfc4519.txt --
--
FSF associate member #7257
