Hello, *

I have a question regarding the mapping of request and response primitives in JSON. When consulting TS 0010, sec. 6.5, I see something like this (linebreaks inserted for the sake of legibility):

{
  "op": 1,
  "to": "//xxxxx/2345",
  "fr": "//xxxxx/99",
  "rqi": "A1234", 
  "ty": 18,
  "pc": {
    "m2m:sch": {
      "rn": "schedule1",
      "se": " * 0-5 2,6,10 * * * * "
    }
  },
  "ot": "20150910T062032"
}

This also happens to be consistent with TS 0004, sec. 8.4 (or my reading thereof), and in particular the example illustrated in 8.4.3, which is almost identical to the one quoted above.

However, from what I see "in the wild," a request would rather look as follows:

{
  "m2m:rqp": {
    "op": 1,
    "to": "//xxxxx/2345",
    "fr": "//xxxxx/99",
    "rqi": "A1234", 
    "ty": 18,
    "pc": {
      "m2m:sch": {
        "rn": "schedule1",
        "se": " * 0-5 2,6,10 * * * * "
      }
    },
    "ot": "20150910T062032"
  }
}

One implementation (but as far as I can tell not the only one) practicing this is OM2M as seen on <https://wiki.eclipse.org/OM2M/one/MQTT_Binding>.

If somebody could shed some light on this and tell me which one is correct, it were greatly appreciated.

Best regards,
  Stephan Hohmann
  Fraunhofer FOKUS

########################################################################

To unsubscribe from the oneM2M_TechQuestions list, click the following link:
http://list.etsi.org/scripts/wa.exe?SUBED1=oneM2M_TechQuestions&A=1