6.7 _<ontologyRepository>_ Operations
6.7.1 Introduction
The <ontologyRepository> represents an ontology repository which may contain any number of managed ontologies represented as <ontology> child resources (see clause 6.8). The ontology repository may further provide semantic validation function by the <semanticValidation> virtual child resource (see clause 6.9).
6.7.2 Create <ontologyRepository>
This procedure shall be used for creating a <ontologyRepository> resource.
Table 6.7.2-1: <ontologyRepository> CREATE
<ontologyRepository> CREATE | <ontologyRepository> CREATE |
---|---|
Associated Reference Point | Mca, Mcc and Mcc' |
Information in Request message | All parameters defined in table 8.1.2-2 in oneM2M TS-0001 [1] apply with the specific details for: Content: The resource content shall provide the information as defined in the clause 9.6.50 in oneM2M TS-0001 [1]. |
Processing at Originator before sending Request | According to clause 10.1.2 in oneM2M TS-0001 [1]. |
Processing at Receiver | According to clause 10.1.2 in oneM2M TS-0001 [1]. The hosting CSE shall also create the <semanticValidation> virtual child-resource if the addressed <ontologyRepository> resource is successfully created. |
Information in Response message | According to clause 10.1.2 in oneM2M TS-0001 [1]. |
Processing at Originator after receiving Response | According to clause 10.1.2 in oneM2M TS-0001 [1]. |
Exceptions | According to clause 10.1.2 in oneM2M TS-0001 [1]. |
6.7.3 Retrieve <ontologyRepository>
This procedure shall be used for retrieving <ontologyRepository> resource.
Table 6.7.3-1: <ontologyRepository> RETRIEVE
<ontologyRepository> RETRIEVE | <ontologyRepository> RETRIEVE |
---|---|
Associated Reference Point | Mca, Mcc and Mcc'. |
Information in Request message | All parameters defined in table 8.1.2-2 in oneM2M TS-0001 [1]. |
Processing at Originator before sending Request | According to clause 10.1.3 in oneM2M TS-0001 [1]. |
Processing at Receiver | According to clause 10.1.3 in oneM2M TS-0001 [1]. |
Information in Response message | All parameters defined in table 8.1.3-1 in oneM2M TS-0001 [1] apply. |
Processing at Originator after receiving Response | According to clause 10.1.3 in oneM2M TS-0001 [1]. |
Exceptions | According to clause 10.1.3 in oneM2M TS-0001 [1]. |
6.7.4 Update <ontologyRepository>
This procedure shall be used for updating an existing <ontologyRepository> resource.
Table 6.7.4-1: <ontologyRepository> UPDATE
<ontologyRepository> UPDATE | <ontologyRepository> UPDATE |
---|---|
Associated Reference Point | Mca, Mcc and Mcc'. |
Information in Request message | All parameters defined in table 8.1.2-2 in oneM2M TS-0001 [1]. |
Processing at Originator before sending Request | According to clause 10.1.4 in oneM2M TS-0001 [1]. |
Processing at Receiver | According to clause 10.1.4 in oneM2M TS-0001 [1]. |
Information in Response message | According to clause 10.1.4 in oneM2M TS-0001 [1]. |
Processing at Originator after receiving Response | According to clause 10.1.4 in oneM2M TS-0001 [1]. |
Exceptions | According to clause 10.1.4 in oneM2M TS-0001 [1]. |
6.7.5 Delete <ontologyRepository>
This procedure shall be used for deleting an existing <ontologyRepository> resource.
Table 6.7.5-1: <ontologyRepository> DELETE
<ontologyRepository> DELETE | <ontologyRepository> DELETE |
---|---|
Associated Reference Point | Mca, Mcc and Mcc' |
Information in Request message | All parameters defined in table 8.1.2-2 apply in oneM2M TS-0001 [1]. |
Processing at Originator before sending Request | According to clause 10.1.5 in oneM2M TS-0001 [1]. |
Processing at Receiver | According to clause 10.1.5 in oneM2M TS-0001 [1]. The hosting CSE shall also delete the <semanticValidation> virtual child-resource if the addressed <ontologyRepository> resource is successfully created. |
Information in Response message | According to clause 10.1.5 in oneM2M TS-0001 [1]. |
Processing at Originator after receiving Response | According to clause 10.1.5 in oneM2M TS-0001 [1]. |
Exceptions | According to clause 10.1.5 in oneM2M TS-0001 [1]. |