@@ -952,10 +952,135 @@ The replacement of an individual inventory object, as illustrated in Figure 7.4.
**Error handling:** In case of failure, appropriate error information is provided in the response.
**Error handling:** In case of failure, appropriate error information is provided in the response.
## 7.5 Resources
## 7.5 Resources
<mark>Editor's Note: This sub-clause will add API resources of the service interface.</mark>
### 7.5.1 Introduction
The present clause specifies API resources (endpoints) of the physical resource inventory management service interface.
### 7.5.2 Resource: InventoryObjectCollection
This resource represents a collection of physical resource inventory objects of the same kind, e.g., a chassis collection, systems collection, cables collection, software inventory collection, etc. The API resource can be used to retrieve a collection of physical resource inventory objects that are managed by the PIM.
Table 7.5.2-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).
The URI query parameters, request and response bodies, and response codes of the individual resource methods shall follow the provisions specified in Redfish® specification [\[2\]](#_ref_2).
**Table 7.5.2-1: InventoryObjectCollection resource methods mapped against PIM service interface requirements**
This resource represents an individual physical resource inventory object managed by the PIM, and can be used to query or update the individual object.
Table 7.5.3-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).
The URI query parameters, request and response bodies, and response codes of the individual resource methods shall follow the provisions specified in Redfish® specification [\[2\]](#_ref_2).
**Table 7.5.3-1: IndividualInventoryObject resource methods mapped against PIM service interface requirements**
This resource represents subscriptions related to inventory management of physical resources and can be used to retrieve a collection of already created subscription resources as well as to create a new individual subscription resource. This resource can be used to create a subscription for receiving notifications about any changes in the inventory information of physical resources.
Table 7.5.4-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).
The URI query parameters, request and response bodies, and response codes of the individual resource methods shall follow the provisions specified in Redfish® specification [\[2\]](#_ref_2).
**Table 7.5.4-1: Subscriptions resource methods mapped against PIM service interface requirements**
This resource represents an individual subscription related to inventory management of physical resources managed by the PIM, and can be used to query, update or delete the individual subscription resource.
Table 7.5.5-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).
The URI query parameters, request and response bodies, and response codes of the individual resource methods shall follow the provisions specified in Redfish® specification [\[2\]](#_ref_2).
**Table 7.5.5-1: Individual Subscription resource methods mapped against PIM service interface requirements**
This resource represents an individual task monitor for an asynchronous operation being performed by the PIM and can be used by the API consumer to monitor the progress of an asynchronous operation as well as receive the result of the requested operation once the corresponding task has been completed.
Table 7.5.6-1 specifies the supported HTTP methods for this resource and maps them against the PIM service interface requirements as specified in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1).
The URI query parameters, request and response bodies, and response codes of the individual resource methods shall follow the provisions specified in Redfish® specification [\[2\]](#_ref_2).
**Table 7.5.6-1: Individual Task Monitor resource methods mapped against PIM service interface requirements**
<mark>Editor's Note: This sub-clause will add data model of the service interface.</mark>
The request and response data structures of the physical resource inventory management service interface are defined in the Redfish® data model specification [\[3\]](#_ref_3).
# 8 Physical resource topology management service interface
# 8 Physical resource topology management service interface