6.15 <reasoningJobInstance> Operations

6.15.1 Introduction

A Reasoning Initiator (RI), such as an AE or CSE, may trigger two types of reasoning operations. One type is a "one-time" reasoning operation. This is applicable to the case where a reasoning operation can be executed over a Fact Set (FS) and a Rule Set (RS) that may not change over time. In comparison, the other type is a "continuous" reasoning operation. The second type is applicable to the cases where the input FS and RS for reasoning may change over time, and accordingly the previously inferred knowledge may not be valid anymore. Therefore, new reasoning is executed over the latest version of FS and RS in order to generate up-to-date inferred knowledge.

A <reasoningJobInstance> resource represents a specific reasoning job instance for enabling the two types of reasoning operations. A RI initiates a desired reasoning operation by creating a <reasoningJobInstance> resource as a child resource of a <semanticRuleRepository> resource.

6.15.2 Create <reasoningJobInstance>

This procedure is used for creating a <reasoningJobInstance> resource as described in Table 6.15.2-1.

Table 6.15.2-1: <reasoningJobInstance> CREATE

<reasoningJobInstance> CREATE
Associated Reference Point	Mca, Mcc and Mcc'
Information in Request message	All parameters defined in [1] table 8.1.2-3 apply with the specific details for: Content: The resource content provides the information as defined in the resource definition of <reasoningJobInstance> resource.
Processing at Originator before sending Request	According to clause 10.1.2 in oneM2M TS-0001 in [1].
Processing at Receiver	The Receiver follows the basic procedure according to clause 10.1.4 in oneM2M TS-0001 [1], with the following specific details: The receiver first retrieves the facts from the resources referred to by the _factSet_ attribute. For example,     - If a referred resource is a type of _<semanticDescriptor>_ resource, the RDF triples included in the _descriptor_ attribute will be collected.     - If a referred resource is a type of _<ontology>_ resource, the data included in the _ontologyContent_ attribute will be collected. The receiver retrieves all the related reasoning rules for the resources referred to by the _ruleSet_ attribute. For example,     - If a referred resource is a _<reasoningRules>_ resource, the rules included in the _ruleRepresentation_ attribute will be collected. The receiver includes the retrieved facts and rules from the previous steps, as well as optional facts/rules based on local policies, as inputs for the semantic reasoning operation. The receiver performs semantic reasoning processing using these inputs and produces the reasoning result and stores it in the _resultRepresentation_ attribute of the created _<reasoningJobInstance>_ resource. If the created _<reasoningJobInstance>_ resource represents a continuous reasoning operation (i.e., the _reasoningType_ attribute is set to "continuous"), subsequent reasoning processing will be automatically triggered and performed according to the values of _reasoningMode_ and _reasoningPeriod_ attributes and the _resultRepresentation_ attribute will be overwritten with the latest reasoning result.
Information in Response message	All parameters defined in table 8.1.3-1 in [1] apply with the specific details for: Content : Address of the created <reasoningJobInstance> resource, according to clause 10.1.2 in [1].
Processing at Originator after receiving Response	According to clause 10.1.2 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.2 in oneM2M TS-0001 in [1].

6.15.3 Retrieve <reasoningJobInstance>

This procedure is used for retrieving the attributes of a <reasoningJobInstance> resource as described in Table 6.15.3-1.

Table 6.15.3-1: <reasoningJobInstance> RETRIEVE

<reasoningJobInstance> RETRIEVE
Associated Reference Point	Mca, Mcc and Mcc'.
Information in Request message	All parameters defined in table 8.1.2-3 in [1] apply.
Processing at Originator before sending Request	According to clause 10.1.3 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.3 in oneM2M TS-0001 in [1].
Information in Response message	All parameters defined in table 8.1.3-1 in [i.3] apply with the specific details for: Content: Attributes of the <reasoningJobInstance> resource.
Processing at Originator after receiving Response	According to clause 10.1.3 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.3 in oneM2M TS-0001 in [1].

6.15.4 Update <reasoningJobInstance>

This procedure is used for updating the attributes of a <reasoningJobInstance> resource as described in Table 6.15.4-1.

Table 6.15.4-1: <reasoningJobInstance> UPDATE

<reasoningJobInstance> UPDATE
Associated Reference Point	Mca, Mcc and Mcc'
Information in Request message	All parameters defined in table 8.1.2-3 in [1] apply with the specific details for: Content : Attributes of the <reasoningJobInstance> to be updated.
Processing at Originator before sending Request	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Information in Response message	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Processing at Originator after receiving Response	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.4 in oneM2M TS-0001 in [1].

6.15.5 Delete <reasoningJobInstance>

This procedure is used for deleting a <reasoningJobInstance> resource as described in Table 6.15.5-1.

Table 6.15.5-1: <reasoningJobInstance> DELETE

<reasoningJobInstance> DELETE
Associated Reference Point	Mca, Mcc and Mcc'
Exceptions	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Information in Request message	All parameters defined in table 8.1.2-3 in [1] apply.
Information in Response message	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Processing at Originator after receiving Response	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Processing at Originator before sending Request	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.5 in oneM2M TS-0001 in [1].