Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4EE8BFE3.7050000@apache.org>
Date: Wed, 14 Dec 2011 15:25:23 +0000
From: =?ISO-8859-1?Q?Michael_D=FCrig?= <mduerig@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: <dev@jackrabbit.apache.org>
Subject: Re: [Jackrabbit Wiki] Update of "Jsop" by stefan
References: <CB0E6933.2146C%mueller@adobe.com> <4EE8B052.9000306@gmx.de>
 <4EE8B8A4.1080009@apache.org>
 <CAFYk8NkSwQvHLwCkHXiv-7Jekseqh7_3Ps81TQ6v6yr56ksXAA@mail.gmail.com>
In-Reply-To: 
 <CAFYk8NkSwQvHLwCkHXiv-7Jekseqh7_3Ps81TQ6v6yr56ksXAA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit


On 14.12.11 15:02, Stefan Guggisberg wrote:
> On Wed, Dec 14, 2011 at 3:54 PM, Michael D�rig<mduerig@apache.org>  wrote:
>> On 14.12.11 14:18, Julian Reschke wrote:
>>>>
>>>> The use case is that the client should have a way to detect the JCR data
>>>> type for unstructured data (JSON doesn't have a 'date' data type). For
>>>> the
>>>> MicroKernel, we currently use a different convention: we encode the data
>>>> type in the value.
>>>
>>>
>>> <insert-anti-JSON-pro-XML-rant-here/>
>>>
>>> Maybe sometimes simple is too simple :-)
>>>
>>
>> When we started using 'JSOP' and JSON for the jr3 Microkernel based
>> implementation, we didn't have a clear picture on how to map things to JCR.
>> The conception then was 'decorate it on top somehow'. As it is apparent from
>> this discussion, this isn't as easy as it seems without resorting to ad-hoc
>> extensions.
>
> WRT 'copy': not simple? ad-hoc extension? to what? a non-existing specification?

Ad-hoc since it is specifically targeted to the Microkernel's 
requirements and we don't seem to care too much about existing 
implementations nor about other, similar efforts. That's alright but 
then let's not call it JSOP.

Michael

>>
>> This discussion just touched two of the paint points: copy and data types.
>> Others are: observation, locking, name spaces and remapping, access control,
>> ordering, properties and nodes with the same name, same name siblings...
>>
>> Michael
>>
>>