←back to thread

JSON Patch

(zuplo.com)
299 points DataOverload | 1 comments | 17 Oct 24 17:46 UTC | HN request time: 0.203s | 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 #
bityard ◴[18 Oct 24 17:29 UTC] No.41881605[source]▶
Maybe we're talking about different things, but resources in REST are identified by their URL and URLs use '/' to separate elements in the path.
replies(2): >>41881871 #>>41887373 #
1. ddgflorida ◴[19 Oct 24 12:14 UTC] No.41887373[source]▶
When convertcsv.com converts JSON to CSV, it uses the / separator to store the structure in the column headings. Probably could use an option for . too.