Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of robert.newson@gmail.com
 designates 72.14.220.153 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=VCii8NR+YqEJzv5G+FGdcaFNw3r1HCw9yRbqO+cfiaOUiL/9s0BofzUh/WnM8DnznY
         PS6HSIOxy5rr9ngrWoQQ2v4jb9Sd9gKWrlaYbAxEeEjHlBl2S/mbd1uSeVBtRZ3ZFnvy
         WAd2V1YGBhc278I6UY4yPc/I8Y4YWBsVW8tUg=
MIME-Version: 1.0
In-Reply-To: <64a10fff0903100540y4cffade2r8516cb5d4a7114ec@mail.gmail.com>
References: <20090310095437.GA726@tumbolia.org>
	 <e2111bbb0903100443h3be03390j3c694a3ee8f973e8@mail.gmail.com>
	 <20090310115033.GF1876@tumbolia.org>
	 <64a10fff0903100459u2aebf66cj3bfd0044528f3082@mail.gmail.com>
	 <e2111bbb0903100507t69b31c43sf48be22937daea4a@mail.gmail.com>
	 <3376B25D-50D8-4FBD-86C5-8501F77446CE@apache.org>
	 <64a10fff0903100523m49817317w9dfa567faa40ac97@mail.gmail.com>
	 <57BA1F75-FE37-4F99-BFCD-76454C0122BB@gmx.de>
	 <64a10fff0903100540y4cffade2r8516cb5d4a7114ec@mail.gmail.com>
Date: Tue, 10 Mar 2009 12:46:51 +0000
Message-ID: <46aeb24f0903100546m7589a667g37f7c5b56c25d98f@mail.gmail.com>
Subject: Re: JSONQuery
From: Robert Newson <robert.newson@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

fwiw: it might make a more natural query language into couchdb-lucene
than Lucene's default query syntax. Not all of it applies, but there's
some decent overlap.

B.

On Tue, Mar 10, 2009 at 12:40 PM, Dean Landolt <dean@deanlandolt.com> wrote:
> On Tue, Mar 10, 2009 at 7:34 AM, Christopher Lenz <cmlenz@gmx.de> wrote:
>
>> On 10.03.2009, at 13:23, Dean Landolt wrote:
>>
>>> As an example of what I mean, JSONSchema already has an implementation in
>>> another language (in this case, python again[1]). And JSONQuery even less
>>> javascript-idiomatic. If you'd like, I'd be happy to try my hand at
>>> implementing it in erlang -- but I was thinking it would be most helpful
>>> for
>>> view ops (thus, in js). It would be pretty convenient if there were
>>> agreed-upon path semantics -- specifically for things like searching.
>>>
>>
>> Everyone in this thread seems to know where/how JSONPath would fit into
>> CouchDB, but I have no idea :)
>>
>> What would this be useful for?
>
>
> One way -- retrieving doc fragments. Another -- for json-based configuration
> of fti, rather than having to interpret js functions via rhino or
> python-spidermonkey (no offense Paul -- that's still a kickass project ;).
> There are probably quite a few others that will shake out -- but having an
> agreed-upon way to reference portions of a doc (or a view) should prove
> useful.
>