@@ -1747,11 +1747,181 @@ The corresponding Redfish® API roots are specified below:
<mark>Editor's Note: This sub-clause will add sequence diagrams of operations supported over this service interface.</mark>
# 11.5 Resources
<mark>Editor's Note: This sub-clause will add API resources of the service interface.</mark>
## 11.5 Resources
# 11.6 Data model
<mark>Editor's Note: This sub-clause will add data model of the service interface.</mark>
### 11.5.1 Introduction
The present clause specifies API resources (endpoints) of the physical resource log management service interface.
### 11.5.2 Resource: LoggingJobs
This API resource represents the logging jobs (LoggingJobs) created for collecting logs related to physical resources managed by the PIM. The API resource can be used to retrieve a collection of available LoggingJobs as well as to create an individual LoggingJob resource.
Table 11.5.2-1 specifies the supported HTTP methods for this API 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 11.5.2-1: LoggingJobs resource methods mapped against PIM service interface requirements**
This API resource represents an individual LoggingJob created for collecting of logs related to physical resources managed by the PIM. The API resource can be used to query, update or delete an individual LoggingJob resource.
Table 11.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 <ahref="#_ref_1">[1]</a>.
The URI query parameters, request and response bodies, and response codes of the individual resource methods shall follow the provisions specified in Redfish® specification <ahref="#_ref_2">[2]</a>.
**Table 11.5.3-1: Individual LoggingJob resource methods mapped against PIM service interface requirements**
This API resource represents logs collected by the PIM based on the LoggingJobs related to log collection of physical resources. The API resource can be used to retrieve multiple log entries that have been generated by the PIM.
Table 11.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 11.5.4-1: Logs resource methods mapped against PIM service interface requirements**
This API resource represents an individual log entry generated by the PIM against a LoggingJob created for collection of logs related to physical resources managed by the PIM. The API resource can be used to retrieve an individual log entry.
Table 11.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 11.5.5-1: Individual Log resource methods mapped against PIM service interface requirements**
This resource represents subscriptions related to log 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 to receive a notification once the Redfish service has successfully collected logs (diagnostics data) in the respectiv message registry.
Table 11.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 11.5.6-1: Subscriptions resource methods mapped against PIM service interface requirements**
This resource represents an individual subscription related to log management of physical resources managed by the PIM, and can be used to query, update or delete the individual subscription resource.
Table 11.5.7-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 11.5.7-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 11.5.8-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 11.5.8-1: Individual Task Monitor resource methods mapped against PIM service interface requirements**
The request and response data structures of the physical resource log management service interface are defined in the Redfish® data model specification [\[3\]](#_ref_3).
