3. Why OData? Following common OData conventions for describing schema, url conventions, and naming and structure of common properties in a JSON payload, not only encapsulate best practices for RESTful APIs but further enables Redfish services to be consumed by a growing ecosystem of generic OData client libraries, applications, and tools. So with Redfish, we get the best of both worlds - a direct API accessible by JSON developers as well as the growing number of OData clients.
The only OData clients that I found are Excel and LINQpad, but neither of those are working with my Dell iDRAC's Redfish service.
Are there other, preferentially ones that work with Linux or are web-based, OData tools that someone can recommend?
The only Chrome store app I found wants me to pay them in 30 days.
While OData looked promising early on in Redfish, the reality is the tooling around OData itself has shown to be very limiting. From a Redfish specification perspective, the amount of OData requirements have been incredibly minimal. I have not actually seen any examples of OData clients interacting with Redfish to date.