-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toolchain requirements #1975
Toolchain requirements #1975
Conversation
@relu91 please have a final look. We want to agree on this set of requirements next week. The concrete change to another toolchain will come afterwards. |
Looks fine, maybe an additional (optional) requirement could be "lightweightness". Lightweight tools are easier to install and usually are easier to understand. But of course, we should not compromise functionality and therefore might be just a nice to have or a criteria that help use to choose between two solutions. |
BTW reading the requirements I remember the validation folder. Do we want to tackle that in this discussion or is rather something orthogonal? |
In the TD Call:
|
Before starting the work on better tooling, I want to document what we currently generate and should keep on generating. Everything with a black output arrow in https://github.com/w3c/wot-thing-description/blob/main/toolchain/wot-toolchain-bpmn.png is also here but there is more.
This is not fixing #1958.