Moving td-tools to separate repository

[egekorkan]

Given that the td-tools package can be used without the other node-wot components, it makes sort of sense to move it out to its own repository since people are confused and think that it is part of node-wot. With the new GitHub organization, this should be easy and can be easily kept governed in a similar way. Even if everyone is ok with it, we should decide on:

• Name of the repository and project.
• Whether each kind of tool is a separate package (TM tools one, AID another)
• Relationship to playground "td tools" which are packages that manipulate TDs in different ways such as OpenAPI generation, inserting defaults etc.
• Versioning of those packages in relationship to node-wot

[danielpeintner]

Very good idea of extracting functionality.

I think/hope from the users point of view it should not be a big hurdle since already now the https://www.npmjs.com/package/@node-wot/td-tools is a dedicated NPM package. Anyhow, the name of the package might change...

Versioning between the different solutions we offer might become a bit more complex.

W.r.t. to splitting "td-tools" even further into TM, AID parts etc
I don't think I would like to see that happening 🙃
I am more in favor of combining the "td tools" from playground and node-wot.

[egekorkan]

Currently, each conversion in the playground is its own package. Combining them would not be a technical issue but an end user would be installing tools that are not needed (which is currently the case with td-tools).