Best practice for href in "thing" Modbus binding

[Kaz040]

I have a question please and it is related to the modbus href.

For thing description forms, it seems href is mandatory. My issue is with a thing that talks modbus.

I have my device entry point defined at the base level (base : modbus+tcp://127.0.0.1->IP:502->port/1-> unitID)

then for each form of property or action or event affordances, i have my modbus:address defined as modbus:address : address.

do I still need the href in the form definition? or I should put it and leave it blank or I should put the datapoint's address in the href and omit the modbus:address.

which is the best practice for the modbus client application of nodewot.

Thank you.
Kazeem.

[danielpeintner]

I think ideally best practices should be mentiond in the actual binding document and not in an implementation like node-wot.
see https://w3c.github.io/wot-binding-templates/bindings/protocols/modbus/index.html

Note: there have been some recent PRs like #916 that aligned node-wot with the binding document.

@relu91 @egekorkan
what do you think?

[relu91]

In theory, it should be already possible to use the base field of a thing description as a common configuration point, as you can see in the example. However, I am not sure if node-wot supports it.

[Kaz040]

In theory, it should be already possible to use the base field of a thing description as a common configuration point, as you can see in the example. However, I am not sure if node-wot supports it.

Thank you very much @relu91 and @danielpeintner for the clarification and assistance. I read the document earlier and saw the different examples. I will test the modbus binding in coming days to see what node-wot support or if it supports all examples stated in the document. I will report my findings.