Merge branch 'NFVSOL(26)000088_SOL026_Review_Contribution_Update_to_latest_DMTF_protocol_specification' into 'main'
NFVSOL(26)000088_SOL026_Review_Contribution_Update_to_latest_DMTF_protocol_specification
See merge request !23
<spanid="_ref_3"></span><aname="_ref_3">[3]</a> [DMTF® DSP0268](DMTF® DSP0268): \"Redfish Data Model Specification\", v2025.1.
<spanid="_ref_3"></span><aname="_ref_3">[3]</a> [DMTF® DSP0268](DMTF® DSP0268): \"Redfish Data Model Specification\", v2025.1.
@@ -399,8 +399,6 @@ The corresponding Redfish® API roots are specified below:
- /redfish/v1/EventService/Subscriptions
- /redfish/v1/EventService/Subscriptions
- /redfish/v1/TaskService/TaskMonitors
- /redfish/v1/TaskService/TaskMonitors
<mark>Editor's Note: Creation of composed physical system via composition service needs further study. Appropriate endpoints for creating a composed system via composition service URI can be added later if required. Although, clause 15 of Redfish interface specification [\[2\]](#_ref_2) suggests that the same /redfish/v1/Systems endpoint may be used even for creating composed systems. The CompositionService is used for creating a composed system. Once composed that system would appears in the same Systems collection resource.</mark>
## 6.3 Resource structure and HTTP methods
## 6.3 Resource structure and HTTP methods
Figures 6.3-1, 6.3-2 and 6.3-3 show resource structures of the Redfish® API [\[2\]](#_ref_2) resources that are applicable for the physical resource provisioning and lifecycle management service interface.
Figures 6.3-1, 6.3-2 and 6.3-3 show resource structures of the Redfish® API [\[2\]](#_ref_2) resources that are applicable for the physical resource provisioning and lifecycle management service interface.