Modbus Dataproperty terms changed to align with best practices

[mahdanoura]

fixes #335

[netlify]

✅ Deploy Preview for wot-binding-templates ready!

Name	Link
🔨 Latest commit	3778413
🔍 Latest deploy log	https://app.netlify.com/sites/wot-binding-templates/deploys/656f789b2c28600008615b64
😎 Deploy Preview	https://deploy-preview-336--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]

Are the changes to remove those terms intentional?

[mahdanoura]

I didn't remove any term, just updated the names to not include the "has", but maybe the tool does additional magic

[relu91]

I'm ok with changing (even though funny enough I thought that convention was to use always a verb, but maybe it is just for ObjectProperties?). Just remember that the context.json should be updated.

[sebastiankb]

my expectation would be that hasAddress, hasCodeNumber, etc are correct. In other WoT ontologies, we use the same pattern (e.g., https://www.w3.org/2019/wot/hypermedia#hasTarget).

The context file is the place, which should do the mapping from address to hasAddress, code to hasCode, etc and vice versa.

[mahdanoura]

I'm ok with changing (even though funny enough I thought that convention was to use always a verb, but maybe it is just for ObjectProperties?). Just remember that the context.json should be updated.

It is definitly not incorrect to have them, we can still stay with the current convention. As @sebastiankb also pointed they are used in the other WoT ontologies in a similar manner. However, when constructing RDF statements they should be also understandable in the meaning and form sentences. The object properties normally have the Verbs, and the Dataproperty can also have verb but when it makes meaning, e.g., [resource] John Doe has a [property] address which is [value] X.

[egekorkan]

TD Call 13.12:

• We are inconsistent in general so we should do this in one go for all ontologies. This should be a guideline for ontology editors
• Since this change impacts the URLs (e.g. https://www.w3.org/2019/wot/modbus#hasAddress becoming https://www.w3.org/2019/wot/modbus#address), implementations that use the ontology will be affected. We will get more input for this from known users, such as from @sebastiankb .
• We should think of a way to assign an "alias" but this will not be an automatic "redirect".
• For TD specs, we should keep the "bad practice" way but for TD 2.0 we should analyze where the inconsistencies are concerning implementations and use cases.
  • A first analysis by @mahdanoura shows that td.ttl is fine but sub-ontologies have more these problems (e.g. hctl.ttl, wotsec.ttl etc).