1791Re: JSON Patch Internet-Draft 04
- Dec 5, 2011
> The first draft of JSON Patch actually used JSON Path. Since JSON PathI think JSONPath is kind of a de facto standard. It was chosen by ebay to create its new SQL variant ( http://ql.io/examples )
> was not standardized, I had to choose to try to standardize JSON Path or
> do something else. For other reasons, we also needed a syntax that would
> be very easy to express in a URI fragment identifier. JSON Schema
> developed a simple syntax, which was very straightforward to implementâ"
> much simpler even if you only kept dot and bracket notation and dumped
> the rest. This was spun-off into the JSON Pointer specification.
I like JSON Schema but I'm not fan of this JSON Pointer draft. The JSON Path or Pointer reference something inside the representation (HTTP Body). So yes, it could be inserted with benefits in the fragment part of the URL as it is proposed for plain text (RFC 5147) or W3C Media fragments.
> Not sure what you mean by cross-typed operations. Can you replace aI meant something like a "add" of a number to a string
> number with a string or object? Yes.
- << Previous post in topic Next post in topic >>