Documenting the Benefits of using WoT

[egekorkan]

Even though we have different places explaining WoT, we don't have a place documenting the benefits of adoption. These can be given to different personas and have different goals. Here are some:

• Business: Reducing the integration cost
• Developers: No need to read excel or pdf files, standardized information exchange
• Technical Managers/Architects: Using well-standardized approaches
• HR: Easier to find people and train people when they already know a technology.

Some testimonials would be good here too, e.g. thanks to WoT we have 60% less development effort.

[RobWin]

I really think that the Developer documentation on https://thingweb.io/docs/Introduction needs some refinement.
For me Eclipse ThingWeb is like the open source reference implementation for WoT.

A very brief/simple introduction into WoT is needed. Simple images. Simple examples.
I don't think that we can expect that developers who find Eclipse ThingWeb on the internet already know what WoT is

[egekorkan]

Some more ideas from today's call:

• Ecosystem effect:
  1. Your solution is more applicable, it has a bigger addressable market
  2. Benefit from other's output: You can use tools that get contributions from others, reducing developments costs and risks of depending on a specific product (e.g. swap to another OSS tool)
• Maintenance Guarantees: The standards from W3C have very long maintenance guarantees
• Reducing the skill requirements to approach different protocols (possibly less-known protocols for junior sw devs)