|
|
Post by michaeldu on Jun 1, 2020 10:02:12 GMT
The OEM actions is defined like BaseURI/Actions/Oem/Contoso.xxxx in the redfish spec. But if I want to define an action for a resource without actions property, what is the preferred behavior?
1. Oem/Actions/Contoso.xxxx or
2. Oem/Contoso/Actions/Contoso.xxxx
From the definition for OEM properties, seems it should be #2, what's your idea?
|
|
|
|
Post by mraineri on Jun 1, 2020 14:20:04 GMT
It's not possible to define OEM actions on a resource that does not already contain an "Actions" property. However, all standard resources we publish do contain an "Actions" property to ensure implementations are able to create OEM actions as needed.
|
|
|
|
Post by michaeldu on Jun 2, 2020 1:10:32 GMT
Thanks for the quick response. That makes sense. For the OEM actions, is it compliant if I define it as Actions/Oem/Contoso/Contoso.xxxx? Does the URI matter given I try to make the structure clear for multiple vendors?
|
|
|
|
Post by mraineri on Jun 2, 2020 15:18:18 GMT
Due to the structure of actions, the namespace of the action definition is already included in the URI. So, the Redfish rules for this URI are "Actions/Oem/Namespace.ActionName", where our guidance is the namespace should include the company identifier.
|
|
|
|
Post by michaeldu on Jun 3, 2020 10:51:04 GMT
Got it, thanks.
|
|
