following the discussion of registry redfishforum.com/thread/222/base-registry-extra-properties-addition It is need to clarify if we can modify the Redfish_1.0.X_PrivilegeRegistry.json and provide it as PrivilegeRegistry to client for there is no clear conclusion that we can or can not add our own custom message properties to Base or others registry.
If we can not modify PrivilegeRegistry provide from redfish.dmtf.org/registries/v1/, is it possible to define privilege of entities not in Redfish_1.0.X_PrivilegeRegistry.json and override with syntax defined in spec (like ResourceURI Override syntax) or OEMPrivilege defined by ourself?
I would not expect end clients to be able to modify a privilege registry on a service, but implementations can certainly construct their own privilege registry (as long as you follow the rules of the registry structure). The one published by the DMTF is a recommendation and does not necessarily fit everyone's needs.
... implementations can certainly construct their own privilege registry (as long as you follow the rules of the registry structure).
It means that we can add missing entities in Redfish_1.0.X_PrivilegeRegistry.json (i.e. NetworkPort/Certificate ... ) and OEMPrivilege to our privilege registry with following the rules defined in spec?
It would probably be good to change the name of the file and identification information since it's no longer the same as the DMTF copy, but you can certainly use the DMTF copy as a starting point and add in other resources, OEM privileges, etc.