Odata URL Standards vs Redfish URL standard

David
Guest

Odata URL Standards vs Redfish URL standard Nov 17, 2017 9:35:31 GMT

Quote

Post by David on Nov 17, 2017 9:35:31 GMT

Hi

I have one basic question. Redfish suggests to have Rest URL in the below format

http://localhost/redfish/v1/Systems/{ID}/SimpleStorage/

But if we see the odata V4 url conventions it will not support pathvariable like below and it handles the requests in the below format

http://localhost/redfish/v1/Systems('ID')/SimpleStorage/

So, we should explicitly convert the Redfish URL to Standard OData URL convention in our code ? Or i would like to know if OData Implementation api supports Pathvariables ?

Regards,
Sagar

jack Minnow Posts: 5	Odata URL Standards vs Redfish URL standard Nov 20, 2017 11:48:12 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by jack on Nov 20, 2017 11:48:12 GMT I'm also concerned about this issue, no conventions of URI definition available for Redfish resource currently.

mraineri
Administrator

Posts: 1,050

Member is Online

Odata URL Standards vs Redfish URL standard Nov 28, 2017 19:02:24 GMT

Quote

Post by mraineri on Nov 28, 2017 19:02:24 GMT

In the Redfish spec, we're purposefully silent on any "recommended format" (although all of our mockups do use that first format). The reason being is we want to give implementations the flexibility in terms of their URI scheme. Some implementations may need to be used in a more OData-centric environment and should call for the second format. However, there are other standards to consider (such as OpenAPI/Swagger) where the first format may better suit and implementation.

Post by David on Nov 17, 2017 9:35:31 GMT

Post by jack on Nov 20, 2017 11:48:12 GMT

Post by mraineri on Nov 28, 2017 19:02:24 GMT