would it be better to graphql style api for selector?

[conanchen]

Question as topic:-

Selector
A string which is the conjunction of an path expression identifying a set of paths and some optional parts allowing to refine the set of paths and associated values.
Structure of a selector:

/s1/s2/.../sn?x>1&y<2&...&z=4(p1=v1;p2=v2;...;pn=vn)#a;b;x;y;...;z
|           | |             | |                   |  |           |
|-- expr ---| |--- filter --| |---- properties ---|  |--fragment-|

[OlivierHecart]

What we are trying to ensure is that the same zenoh resources can be retrieved using the same queries and selectors from our language bindings (rust, c, python, ...) as well as from our REST API. That's why the selector follows the URI scheme.

But nothing prevents us to optionally allow to query data with another format like graphql. Is this something you need? We may add this in our roadmap.

[conanchen]

yeah. cool to add this to the roadmap.