Should we refactor `getThingDescription` to a JS getter?

[relu91]

Currently, we are using a method but we could use a simple getter interface. There was some discussion on this point that we might dig up.

[relu91]

Call 02/10:

• @JKRhb Nowadays we have getters in JS, and I think this method is better if designed as such
• @zolkis prefers the method so that we can clearly convey the fact that additional steps might be done to create the ThingDescription in response. WebIDL supports getters and there are APIs that use them.
• @relu91 seconds that the method is better to convey to the API users that the call can cause some computation and it is not zero cost. We should look to other APIs too.

[danielpeintner]

I also think a methods makes more sense since

• computation might happen
• it is not required that the internal structure of a thing object matches the TD structure (it is the case in node-wot but there is no need/requirement for that)

[relu91]

Call 08/10

• @zolkis getter would be more "webish" (see https://www.w3.org/TR/design-principles/)
• @relu91 review the prose about the method and see the actual implications.