←back to thread

JSON Patch

(zuplo.com)
299 points DataOverload | 2 comments | 17 Oct 24 17:46 UTC | HN request time: 0s | source
Show context
bsimpson ◴[18 Oct 24 17:02 UTC] No.41881312[source]▶
`/` is a weird choice of delimiter for JSON.

Since JSON is a subset of JS, I would have expected `.` to be the delimiter. That jives with how people think of JSON structures in code. (Python does require bracket syntax for traversing JSON, but even pandas uses dots when you generate a dataframe from JSON.)

When I see `/`, I think:

- "This spec must have been written by backend people," and

- "I wonder if there's some relative/absolute path ambiguity they're trying to solve by making all the paths URLs."

replies(9): >>41881377 #>>41881605 #>>41881615 #>>41882491 #>>41883303 #>>41883342 #>>41885101 #>>41885337 #>>41888089 #
1. svckr ◴[18 Oct 24 20:46 UTC] No.41883342[source]▶
You're not the only one who thinks that!

JSON Patch uses JSON Pointer (RFC 6901) to address elements, but another method from (very) roughly same time is JSON Path [0] (RFC 9535) and here's one of my favorite mnemonics:

- JSON Path uses "points" between elements

- JSON Pointer uses "path separators" between elements

[0] https://en.wikipedia.org/wiki/JSONPath

replies(1): >>41885595 #
2. tyre ◴[19 Oct 24 04:16 UTC] No.41885595[source]▶
and json path is supported in Postgres as a way to query json documents. It’s surprisingly full featured!