Discard controlledBy for TD 2.0?

[sebastiankb]

After having a discussion with @hadjian we are wondering if controlledBy as link relation is still contemporary in the TD.

controlledBy was born with the idea of having a practical way to create a reference to another Thing with its Thing Description via a link reference. This was also a practical approach for which no specific RDF knowledge was required.

However, the question arise how this very specific relation type value is used in practical implementations. RDF with specific ontologies are more expressive and offer more possibilities to describe relations. So, it would be desirable to be able to specify such relationships in RDF style only, in order to be able to query RDF stores and do reasoning the relationships.

The question is, if we should discontinue controlledBy and introduce, e.g., a subsection in chapter 7 to express relations based on existing ontologies (e.g., https://ontology.brickschema.org/).

[egekorkan]

While I do understand that we should have a better way, I see it in submitted TDs for testing.

• @relu91 has https://github.com/w3c/wot-testing/blob/037c8d686ad8c145dd4fe01c2123ad26eca0e185/events/2021.06.Online/TD/TDs/Unibo/imu_sensor.td.jsonld#L32
• An old Siemens submission that is probably just for testing: https://github.com/w3c/wot-testing/blob/037c8d686ad8c145dd4fe01c2123ad26eca0e185/events/testfest/2019-02-princeton/OLD/TDs/Siemens/fullInteractionsTest-siemens.json#L7

Given that @relu91 case looks more realistic, what are your opinions?