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.250 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=miiMrD2l2JmLCTw3W6846RodaIEYhsqBoEeg72ae7Br11un/KlvhwCXr7eBts+1wXibTD9bXWiaYZIRojem12kCdoE2mFA1wGWmqPNKrJ5FoK/z15DjJb1sw/L0dLX8MfgzaqQhhifmZ+chNujB8tFqYJwjnIfQD+v4NdZTSl7s=
Message-ID: <510143ac0707100136t20b1d1b0ybb60f66cf381f64d@mail.gmail.com>
Date: Tue, 10 Jul 2007 11:36:02 +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: <f767f0600707100118v67d64789mdda6dd30d607a628@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>
	 <f767f0600707100118v67d64789mdda6dd30d607a628@mail.gmail.com>

Hi,

On 7/10/07, Bertrand Delacretaz <bdelacretaz@apache.org> wrote:
> Still (and I'm being slightly paranoid here, for the purpose of
> discussion), some of these meaningful path elements might change at
> some point.

I don't really see this as a problem.

> mark@gmail might get a new email...what happens? Worst case, his old
> email is made available after some time, and someone else grabs it
> (remember, I'm in paranoid mode ;-)

We can just rename the node, or if we don't care we can leave it as
is. In any case I think it makes sense *not* to use the node name as
the email address in an aplication. It's much better to put such
semantic information in a property and keep the name as just a local
identifier.

> "Nelly Furtado" usually stays forever...though she might get married
> and change her name (not to mention the Wendy/Walter Carlos case
> [1]...or The Artist Formerly Known As Prince).
>
> New records will be released under her new name, but somehow a
> connection must be made to the old name, which would be easier with an
> abstract identifier.

Again, in this model each record should probably have a string
property that contains the name of the artist.

> What I'm getting at: meaningful paths are great, but when using them
> one must be prepared to handle edge cases where meaningful path
> elements change in the world that you're modeling.

I guess we need to make a difference between meaningful paths in the
sense of "locally unique and readable" and the sense of "semantically
valid" where someone would want to use the name itself as a specific
attribute like name or email address. I much prefer treating names in
the former sense.

BR,

Jukka Zitting