Replace the figure of the Building Blocks about wot-architecture

[mlagally]

@mryuichi many thanks for your work.
Can you please create a PR with this proposal that shows how the existing text is replaced by the new proposal? This will allow easier handling of the proposal in tomorrow's call.

[mryuichi]

OK. I have done.
The description of the building blocks is inserted in the beginning of section 6.

[mkovatsc]

In other pictures the application sits outside the runtime, controlling the latter through an API such as the WoT Scripting API. I would recommend to remove the "(application)" and put it as "Application" in a box on top of the runtime system.

Either "WoT Runtime" or correct "Runtime System" -- just "runtime" is not a proper term. I would recommend "Runtime System" to avoid the unnecessary special definition of WoT Runtime (see #35 )

I am a but confused about the emphasis on the "WoT Servient Life Cycle Management". Every runtime system needs a form of life cycle management for what it instantiates (in our case the Thing software objects). Furthermore, it is not the Servient Life Cycle. The Servient contains the runtime system.

Device interface adapter is too specific. Originally we had "System API" to also enable local hardware or abstract services such as a database (through a Database Thing with corresponding affordances).

[mlagally]

Will revisit this issue once we have a consolidated spec that integrates the changes discussed on 14.3.

[mmccool]

So, I've been working on a new set of figures to resolve issues around whether or not the scripting API is a mandatory part of the WoT Runtime or not. However, my new figures don't include the ExposedThing or ConsumedThing objects, and probably they should to align with the one above and the text...

[mlagally]

@mmccool I'm not clear about your comment. Do you want to update your figure to reflect the text or does the text have to be aligned?

[mlagally]

call on 21.3.
Consider https://github.com/w3c/wot-architecture/blob/master/images/wot-building-blocks-abstract.png to satisfy this issue.