search

w3c / wot-binding-templates

Web of Things (WoT) Binding Templates
http://w3c.github.io/wot-binding-templates/
Other
22 stars 25 forks source link

Introduce `contentType` byte order #118

Open relu91 opened 3 years ago

relu91 commented 3 years ago

Currently, we discussed byteOrder term usage in a Modbus form, but we did not describe it in the document it self. We can either add an example or properly introduce a section dedicated to usual content types for a particular protocol binding.

relu91 commented 3 years ago

On this topic, I wonder if content-type parameters or features description should be actually moved to the main binding document. It is more a cross-cutting concept and it can be re-used in different binding implementations.

sebastiankb commented 3 years ago

contentType is generic and it would make sense to have it at the generic place. However, some bindings have some specific parameters like byteSeq, this should be then specified in the corresponding binding.

egekorkan commented 3 years ago

I think it's good to think whether there's a cross-cutting concept for these terms. In HTTP, client decides these parameters on its own: https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST

There is blockwise transfers in coap (https://datatracker.ietf.org/doc/html/rfc7959) but this doesn't have to described in the TD I think.

I'd also say that we do not abstract this for now since I'm not aware of other cases where this needs to be known in advance.

egekorkan commented 9 months ago

In the Modbus specific case, we have this solved. The decision is to wait for use cases from other protocols and see how it can be made more generic.