Fix #280 and 281: add emitPropertyChange(), remove ConsumedThing inheritance

[zolkis]

add explicit emitPropertyChange() and remove ConsumedThing inheritance from ExposedThing

Signed-off-by: Zoltan Kis zoltan.kis@intel.com

---

Preview | Diff

[relu91]

Approve. Minor comments:

• Could we link the first editor's note also in the other algorithms? it might be handy when the document is read not linearly.
• Could we use camel case for ExposedThing internal slot extd. It might be confused with a shortened version of extend whereas it should be ExposedThingDescription. So it might be more intuitive to call it exTD or exTd.

[zolkis]

Could we use camel case for ExposedThing internal slot extd. It might be confused with a shortened version of extend whereas it should be ExposedThingDescription. So it might be more intuitive to call it exTD or exTd.

Makes sense, done.

Could we link the first editor's note also in the other algorithms? it might be handy when the document is read not linearly.

The algorithms say "selected by the implementation", which should be clear enough even without the ednote. Repeating the ednote everywhere would be too much clutter, given that it just repeats the last sentence. Perhaps we could remove even the first one?

[danielpeintner]

Could we use camel case for ExposedThing internal slot extd. It might be confused with a shortened version of extend whereas it should be ExposedThingDescription. So it might be more intuitive to call it exTD or exTd.

Makes sense, done.

Nit: I am always in favor of spelling out "what" it is since exTD sounds like example TD to me. Why not name it along the lines what it is: exposedTD.
Since it is internal only I don't mind much.

[danielpeintner]

I am generally fine with the PR.

I added some comments that seem beneficial to me.