Could you, please, clarify where the oem action should be added if there is no Action property in the DMTF resource schema - like Thermal resource.
If there is an Action property in the resource, it is clear that oem action should be in Actions->Oem. But if there is no Action property in the resource there are following possibilities:
We were supposed to define the "Actions" property in all (or at least most) of the Redfish schemas to allow for OEM's to add their own Actions, and keep them collected up in one, easily discovered location.
Looks like we missed 'Thermal', I've marked that as a high priority bug, we'll revise the schema and get it released in the next bundle (which should come in March).
#1 is the correct method. As of last summer, we've provisioned all of our resources to support an Actions property, so OEM actions belong inside of "Oem" within the Actions property. We have an example of this in our mockups for a ComputerSystem.