Modbus fixes

[egekorkan]

This PR fixes a couple of small but important aspects:

• Types: We have noticed that type information like https://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/#unsignedByte are not aligned with the binding template at even though our ontology was correct (https://w3c.github.io/wot-binding-templates/bindings/protocols/modbus/ontology.html#payloaddatatype). This is due to lowercasing in the template.sparql file . I had to fix the schema manually.
• Editor was missing in the ontology
• Schema was using wrong operation names where an s was missing. This is the perfect example of needing toolchain since this was an oversight from our side for a long time.

[netlify[bot]]

✅ Deploy Preview for wot-binding-templates ready!

Name	Link
🔨 Latest commit	bdf9ec0032031e8d36f9db6545eb9afc9cbcca41
🔍 Latest deploy log	https://app.netlify.com/sites/wot-binding-templates/deploys/66150d61dff6440008b67cae
😎 Deploy Preview	https://deploy-preview-359--wot-binding-templates.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[egekorkan]

Call of 11.04:

• @relu91 We have noticed that the function names need a second look since the name, label and descriptions sometimes have a mismatch. We should see the modbus spec as well (e.g. is it read coil or read coilS)
• In any case, we should make sure to review the table content much better since the table content is what is used in schemas or code, thus used by software that is very strict i.e. the presence of an s or capitalization means a totally different word.

[egekorkan]

The labels and descriptions are fine for now and the values are copy-pasted into implementations anyways so no need to change with this PR. Merging as agreed upon