Re: [core] SenML and link-format in RDF (was: Re: Designs to resolve streaming issues in SenML)

[Michael Koster <[e-mail]>]

Picking up the original thread again, I  am building a reference implementation [1]  of collections that uses the representation format below [2].

It turns out that rather than simply extending the existing senml or link-format content formats, the better approach may be to define a new content-format to represent the collection that resues the identifiers from senml and link-format. In this way, I can provide a map format for the collection that is optimized for collection processing by the tools, while supplying standard link-format and senml content formats for hypertext applications.

To this end, I would propose to define a new content-format for a "hypermedia sensor markup language" which enables representation of a hypermedia construction that includes both senml and link-format resources. Resources that support application/hsml ( +json, cbor, xml, exi) should also be able to return representations of application/senml and application/link-format for use by general hypermedia applications. The representation of the Hypermedia Collection would be defined this way in the CoRE Interfaces draft.

This will decouple changes in senml from the collection model and content format but keep the identifier mapping to the common link and data formats so tools can easily construct correct representations in multiple formats, indluding senml optimized for efficient processing.

Does this sound like a good course of action?

Best regards,

Michael

[1] https://github.com/connectIOT/HypermediaDemo <https://github.com/connectIOT/HypermediaDemo>

[2]
[
  {
    "bn": "/light/colorHS/currentcolorh/",
    "e": [
      {
        "n": "",
        "v": 0
      }
    ],
    "l": [
      {
        "href": "",
        "rel": [
          "self",
          "item"
        ],
        "rt": [
          "property",
          "currentcolorh"
        ]
      }
    ]
  }
]