oneM2M TS-0032Release Notes diff from v5.0.2 to v5.0.2oneM2M TS-0032Release Notes diff from v5.0.2 to v5.0.2This clause corresponds to the specification in clause 7 and 8 of oneM2M TS-0004 [3].
Both MAF and MEF Interface request primitive formats conform to clause 7.2.1.1[3], constrained to the CRUD operations, with request parameters listed in table 5.1.2‑1 and table 5.2.2‑1, respectively.
Both MAF and MEF Interface response primitive formats conform to clause 7.2.1.2[3], constrained to the CRUD operations, with response parameters listed in table 5.1.2‑2 and table 5.2.2‑2, respectively.
The MAF Interface generic resource request procedure for originators and receivers conforms to clauses7.2.2.1 and 7.2.2.2 of oneM2M TS-0004 [3], with the following clarification:
The originator actions, receiver actions and Hosting CSE actions conform to clause 7.3 of [3], with clause 7.3.3.15 of [3] replaced by the authorization processes described in the MAF Interface resource-type specific procedures in clause 8.
The management common operations in clause 7.3.4 of [3] do not apply to the MAF Interface.
The resource-type-specification conventions apply to the specification in clause 8, but the remainder of clause 7.4 of [3] does not apply to the MAF Interface.
Clause 7.5.1 of [3] (regarding Notification) does not apply to the MAF Interface. Elements contained in the Content primitive parameter conform to clause 7.5.2 of [3].
The representation of MAF Interface primitives in data transfer conforms to clause 8. Clause 9 contains additional short names specific to both the MAF and MEF Interfaces.
The MEF Interface generic resource request procedure for originators and receivers conforms to clauses7.2.2.1 and 7.2.2.2 of oneM2M TS-0004 [3] with the following clarification:
The originator actions, receiver actions and Hosting CSE actions conform to clause 7.3 of [3], with clause 7.3.3.15 of [3] replaced by the authorization processes described in the MEF Interface resource-type specific procedures in clause 8.
The management common operations in clause 7.3.4 of [3] do not apply to the MEF Interface.
The resource-type-specification conventions apply to the specification in clause 8, but the remainder of clause 7.4 of [3] does not apply to the MEF Interface.
Clause 7.5.1 of [3] (regarding Notification) does not apply to the MEF Interface. Elements contained in the Content primitive parameter conform to clause 7.5.2 of [3].
The representation of MEF Interface primitives in data transfer conforms to clause 8. Clause 9 contains additional short names specific to the both the MAF and MEF Interfaces.