-
Notifications
You must be signed in to change notification settings - Fork 172
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
Rework Ecosystem section #611
Conversation
Some linter problems (trailing blanks, return at end of file) |
I would like the following VISS related updates:
|
|
||
![Signal tree](/vehicle_signal_specification/images/multi_target.png)<br> | ||
*Fig 1. Generating documents from specification* | ||
*Fig 1. Generating various output formats from a VSS specification* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have time, modernizing/recreating this picture would be great. We do not have a markdown generator, and the names of the *.vspec files shown does not match "real files". Maybe better to make it more general, like showing one box for "Standard catalog" and one or more boxes for overlays.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will look into it
40a258e
to
a52bfb8
Compare
Done |
… content Signed-off-by: Sebastian Schildt <sebastian.schildt@de.bosch.com>
a52bfb8
to
a82d8dd
Compare
Meeting notes:
|
The Ecosystem section in the official documentation was largely outdated, i.e. it mentions the dormant IoT Event Analytics, it contained a bit outdated information on KUKSA, and probably worse, a lot of things using VSS nowadays not even been mentioned.
While the texts could likely be better as well (please comment), the main thing this PR does, is suggesting a slightly different structure:
Screenshots for convenience: