Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.132.247 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=SIcKgR8m1XhF3WnI091CISm6/j7VVY/k5cOxy+P2txv+rUSGP5n4Y5UZezZ4Hv3qPtLR+wg3sfhwCn8OVKeWucfYEyrx3Cqpb4zHvSj4OFW02rlnoW3IsU/tXwpvS93ydQeEw4gJdqEllgpqK2E7WgY+FfIlIdCViZOezsGYOr0=
Message-ID: <510143ac0707100125m172ec5f7n172f453da4e2dc7@mail.gmail.com>
Date: Tue, 10 Jul 2007 11:25:39 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: DM Rule #4: Beware of Same Name Siblings.
In-Reply-To: <8641fd7c0707100109y59f3965m7668553b09bf691@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <eb7e2190707070416l58e0636crf9829d4e6014c57d@mail.gmail.com>
	 <003401c7c0a6$d1238aa0$736a9fe0$@co.uk>
	 <eb7e2190707090528u7ceec6aal136ec2425696076e@mail.gmail.com>
	 <140176f0707090614y4620a324idd2f8cb0f0e509bf@mail.gmail.com>
	 <76a6ebd00707091316q776df0b9k950a82df44841ebc@mail.gmail.com>
	 <eb7e2190707092348x27a818a7hecda01b0de8b8be8@mail.gmail.com>
	 <510143ac0707100056k5b419b49r449dee28993927ac@mail.gmail.com>
	 <8641fd7c0707100109y59f3965m7668553b09bf691@mail.gmail.com>

Hi,

On 7/10/07, Tako Schotanus <quintesse@gmail.com> wrote:
> I understand the recommendation, I just would like to add that
> sometimes finding a good identifier is pretty difficult. The example
> of using a person's email address is just not stable enough, there are
> lots of people who are changing email addresses continuously and many
> of the addresses don't contain any clue as to the person they belong
> to.

Note that names don't really need to be globally unique or stable. A
name doesn't even need to reflect any specific attribute (real name,
etc.) of the node.

> And since the 1.5 years that I live in Spain now I'm still amazed at
> the number of people that have EXACTLY the same name! Even taking into
> account that they have 2 last names (from both parents) and normally
> several first names as well! (Probably due to the fact that it was
> customary to name children after grandparents)

This is where the recommendation to avoid huge flat collections comes
to help. A repository that models the population of Spain could (and
should!) use some hierarchy.

A geographic hierarchy would divide people based on the area, city,
street, block, etc. where they live in.

A geneologic hierarchy could use either maternal or paternal lines and
have the repository hierarchy reflect the actual parent/child
relations in real world.

BR,

Jukka Zitting