Fix #215: make the API entry point a namespace.

[zolkis]

Also, apply Web IDL namespace rules.

Signed-off-by: Zoltan Kis [email protected]

[relu91]

It seems right, even if I liked more WOT as namespace than WebOfThings. However, I understand that WebOfThings is more evocative and less obscure. What about simply Things?

Also, this commit actually does not fix #215 because the issue was related to typescript definition file. So even after merging this we still need to fix typescript typings.

[zolkis]

I thought this issue was to draw attention to namespaces because of the node-wot issue.
From the other hand, IIRC we have got that feedback to use a namespace also from elsewhere.

I am fine with the WOT name, this PR was a bit provocative with this (better readable) name.
I thought spelling it out plays better with Web IDL guidance on namespace naming, and be more clear in the same time. IMHO it makes things more clear/explicit when you import/use WebOfThings vs WOT. But no hard take on that.

[zolkis]

https://heycam.github.io/webidl/#idl-namespaces

[danielpeintner]

It seems right, even if I liked more WOT as namespace than WebOfThings. However, I understand that WebOfThings is more evocative and less obscure. What about simply Things?

I agree with @relu91
I don't think changing "WOT" to "WebOfThings" is a good idea. It conflicts with a product too.

And in general I think this is a TypeScript issue.. but it may also relate to IDL namespaces...

[zolkis]

Changed the name back to WOT.