12th video pptx added for review

[idilsezgin]

12th video Building Blocks pptx added for review.

• visuals, text, and animations to be reviewed.

[netlify[bot]]

❌ Deploy Preview for whatiswot failed.

Name	Link
🔨 Latest commit	17628b18dbbe67351b96308e806b1e3d16aeae8c
🔍 Latest deploy log	https://app.netlify.com/sites/whatiswot/deploys/652d972161e3fe0008c5a6a0

[egekorkan]

• [ ] Slide 1: we should not say "generic", maybe "in the third section of introduction to WoT". If this is repeated elsewhere, we should fix them too.
• [ ] Slide 6: a serialization to JSON-LD -> All TDs can be represented in JSON-LD and can be processed just as a normal JSON.
• [ ] Slide 15: What is relation metadata?
• [ ] Slide 17 can be removed, see below.
• [ ] Slide 19: In order to do that a programmer reads the TD and program it -> Typically, a programmer can read the robot's TD and program the controller accordingly to automate processes.
• [ ] Slide 19-21: The programmer programs the controller code by reading the TD of the robot.
• [ ] Slide 23: Controller controls the robot bu sending requests
• [ ] 27: WoT Thing Descriptions
• [ ] 37: It is a database with a REST API to access TDs
• [ ] 43: Instead of Philips Hue, we should write commercial products and the audio should say "such as Philips Hue"
• [ ] 45: Profile should be WoT Profile
• [ ] 66: And it turns from run time scripts to protocols. -> It turns abstract run time scripts into concrete protocol messages.
• [ ] 66: httpThing. reads temperature and increases temperature if needed
• [ ] 67: modbusThing. same code. application logic does not change
• [ ] 69: Choosing a protocol is not shown to the developers, the runtime chooses it itself based on the TD. We should think of a better design to convey that the script does not change based on the protocol. Maybe some morph transition?
• [ ] ending: protocol in TD: HTTP. protocol in TD: modbus. -> same application logic.

[egekorkan]

The changes are addressing my concerns, merging :)