a textual notation to locate fields within atproto records (draft spec)
microcosm.tngl.io/RecordPath/
fix callout?
+1
-1
+1
-1
spec.md
+1
-1
spec.md
···
116
116
117
117
RecordPath makes a pragmatic choice to treat all arrays as unordered sets. Index position is not encoded in the path, and selecting a RecordPath that traverses an array always matches zero-or-more items ("vector" matches), instead of the zero-or-one behaviour of object-only paths ("scalar" matches).
118
118
119
-
> ![INFO]
119
+
> [!NOTE]
120
120
> It's a compromise and bit unfortunate, but in practice it works well. Even for a data format like geoJSON, if you want only `longitude`s from its `[longitude, latitude]` pair format: you can RecordPath the array-pair itself and index into it at the application level.
121
121
122
122
Arrays are descended into with `[]`: