Use OData path syntax & semantic to implement proper string-based Khepri paths?

[dumbbell]

Our current implementation of string-based path in Khepri is very limited and only supports basic paths. For instance, conditions can't be represented in string-based paths.

At some point, I would like to provide an HTTP API on top of Khepri (as a separate library to keep Khepri focused on the database itself). I thought about OData for several reasons, and their path syntax could be nice to support string-based paths as first class citizen.

This is just an idea and I didn't explore it deeply yet.