I have a lot of faith in Mark Nottingham. If I was going to put my money on anyone, it would be him. (Look up his contributions to WebArch in general. Also, he co-authored the Atom spec, for example.) I think it would be worth a punt. (Easy to say as the person who wont be coding it.) And I agree, that if we ship an alpha compat for this, we might help snowball adoption.
On Sun, Sep 9, 2012 at 11:33 PM, Paul Davis <[email protected]>wrote: > Yeah, its originally from the guy that wrote Persvr. I would say its > not terrible but its severely underspecified which worries me a bit. > It might be interesting to see what an implementation in Erlang looks > like but I'd still be quite hesitant to including it in trunk as I > haven't seen a lot of adoption of the standard (although if we started > pushing it we might be able to change that). > > > On Sun, Sep 9, 2012 at 8:16 AM, Noah Slater <[email protected]> wrote: > > Paul, > > > > Sorry to bring up an old thread. > > > > Did you see this, very recent, work by Mark Nottingham: > > > > http://tools.ietf.org/html/draft-ietf-appsawg-json-patch-03 > > > > Thanks, > > > > On Mon, Jul 30, 2012 at 6:21 PM, Paul Davis <[email protected] > >wrote: > > > >> On Mon, Jul 30, 2012 at 10:36 AM, Dirkjan Ochtman <[email protected]> > >> wrote: > >> > On Mon, Jul 30, 2012 at 5:28 PM, Dave Cottlehuber <[email protected]> > >> wrote: > >> >> Any other corner cases? > >> > > >> > I don't think CouchDB should invent it's own JSON patching scheme. I > >> > guess it would be best to implement, say, > >> > http://tools.ietf.org/html/draft-pbryan-json-patch-04 (but make sure > >> > to track the ID until it becomes a standard). > >> > > >> > Cheers, > >> > > >> > Dirkjan > >> > >> We've discussed this a number of times before and have always ended up > >> with exactly what Dirkjan describes. There's no accepted JSON patch > >> scheme that is widely adopted. There have been a few attempts but I've > >> not seen anything gather significant adoption to warrant picking sides > >> in that fight. > >> > > > > > > > > -- > > NS > -- NS
