Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of julian.reschke@gmx.de
 designates 213.165.64.23 as permitted sender)
Message-ID: <4EE1EAC8.1000301@gmx.de>
Date: Fri, 09 Dec 2011 12:02:32 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dev@jackrabbit.apache.org
CC: =?UTF-8?B?TWljaGFlbCBEw7xyaWc=?= <mduerig@apache.org>
Subject: Re: [Jackrabbit Wiki] Update of "Jsop" by ThomasMueller
References: <20111209090645.25904.25876@eos.apache.org>
 <4EE1DE57.3030700@apache.org>
In-Reply-To: <4EE1DE57.3030700@apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 2011-12-09 11:09, Michael Dürig wrote:
>
>
> On 9.12.11 9:06, Apache Wiki wrote:
>> Comment:
>> Preserve order of child nodes
>>
>> '''addNodeDiff:'''
>> * + pathString: object
>>
>> + The added node may contain child nodes. The order of child node is
>> preserved, that means, when requesting the object, the child nodes
>> will appear in the same order as they appear when the node was added.
>> This only applies to child nodes however; it does not apply to the
>> order of properties. For example, an implementation may sort the
>> properties by name.
>> +
>> '''addPropertyDiff:'''
>> * + pathString: propertyValue
>
> I wouldn't specify this here since this since this would effectively
> break compatibility with the IETF JSON Patch [1]. Currently our compact
> syntax seems to nicely map to the JSON Patch syntax (when augmented with
> support for metadata and a reorder op) and vice versa. For the

In the meantime, JSON Patch has a move operation: 
<https://tools.ietf.org/html/draft-pbryan-json-patch-04#section-4.4>

 > ...

Best regards, Julian