Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B29ABF609 for ; Tue, 1 Oct 2013 14:32:29 +0000 (UTC) Received: (qmail 97722 invoked by uid 500); 1 Oct 2013 14:32:29 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 97422 invoked by uid 500); 1 Oct 2013 14:32:28 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 97415 invoked by uid 99); 1 Oct 2013 14:32:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 14:32:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of julian.reschke@gmx.de designates 212.227.15.15 as permitted sender) Received: from [212.227.15.15] (HELO mout.gmx.net) (212.227.15.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 14:32:21 +0000 Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Ma1Mt-1V7xk71z1b-00LpRG for ; Tue, 01 Oct 2013 16:32:00 +0200 Message-ID: <524ADCDB.3080708@gmx.de> Date: Tue, 01 Oct 2013 16:31:55 +0200 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: dev@jackrabbit.apache.org Subject: Re: node naming References: <524AD6EA.60000@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:0wmuvu4kiAbIlWBwnsYhDkQhV6H/Q9Zu+aUp2CLKZBLW+wOpgQJ oIbttfai8gOUuoodpkNvmkI8fggmfVPEOxaHwsFHj2jGmfNsHL+g1KwpXhW520RTsSuHbHJ lHI+khY9zWzhbxyF0UL6KFKJLGza4R9W6Pf/tOPMMvXbTiI0SPxgCKAe1+/T/nj+AhnD/Vd vLSvZJr09BwbcBW9vqPaQ== X-Virus-Checked: Checked by ClamAV on apache.org On 2013-10-01 16:17, Jukka Zitting wrote: > Hi, > > On Tue, Oct 1, 2013 at 10:06 AM, Julian Reschke wrote: >> What are our expections with respect to certain normalizations of node names >> a repository *might* do, such as: > >>From the implementation perspective: I think such concerns should be > taken care of on a level above the repository. At best I'd see the > repository enforcing a particular naming policy by refusing to create > content with un-normalized names. > >>From the client perspective: I guess a client should be prepared for a > repository that actively does normalize names, as I don't think the > spec rules something like that out and as the spec was written in a > way that would allow it to be implemented on top of existing backends > that already may do such normalization. In practice that would > probably mean that a Node returned from getNode() or addNode() might > not have the exact same name as the one given as the argument. > ... Well, the call could either fail (in which case the client would have a hard time to figure out how to proceed), or it can pass (and the returned node would "know" its name). I think I'd prefer the latter. Questions: 1) Is this something the spec needs to say? 2) Is this something we want to do in Jackrabbit? 3) Or in Oak? Best regards, Julian