Remove obsolete sensor/actuator properties #485
Conversation
|
Meeting discussion:
|
erikbosch
force-pushed
the
erikbosch/erik_opt
branch
from
2654700 to
ddfde0a
Compare
|
Updated the files based on the discussion on last meeting |
| In short this means that VSS introduces: | ||
|
|
||
| * A syntax for defining vehicle signals in a structured manner | ||
| * A catalogue of signals related to vehicles. |
There was a problem hiding this comment.
punctuation inconsistent
| @@ -19,14 +24,14 @@ vehicle implementation details. | |||
|
|
|||
| The representation of vehicle data specifications is vendor independent. | |||
| Vendor-specific extensions can be specified in a dedicated and uncontrolled | |||
There was a problem hiding this comment.
Remove "a" if it is "branch_es"
Not a big fan of the orignial text anyway, Maybe it is already to specific here and "uncontrolled" sounds not so good
Maybe something like
"While the data in the VSS standard catalogue aims to be vendor-independent, vendor specific extensions and adaptations complying with the VSS syntax rules can an be specified (see Overlays)
There was a problem hiding this comment.
The current documentation is quite academic, talking about taxonomies, domains and rule sets. We could discuss if we want to refactor it to make it more "practical"
There was a problem hiding this comment.
Changing to your proposal
|
|
||
| ## VSS usage for other domains | ||
|
|
||
| The VSS catalogue focus on signals related to vehicles. |
docs-gen/content/rule_set/basics.md
Outdated
|
|
||
| The YAML list is a single file, called a *vspec* file. | ||
| The Vehicle Signal Specification domain specification consist of *vspec* files. | ||
| *vspec* files are YAML lists following the rule set defined for VSS. |
There was a problem hiding this comment.
I think we are not "lists" anymore. "vspec files are YAML files" or "vspec files contain YAML defintions following..."
They have never been used and are not supported in tools. Better to reintroduce them if/when we in VSS specifies recommended additional properties for e.g. security purposes or protocol adoptions. Also improving documentation based on PR review. Fixes COVESA#302 Signed-off-by: Erik Jaegervall <erik.jaegervall@se.bosch.com>
erikbosch
force-pushed
the
erikbosch/erik_opt
branch
from
ddfde0a to
ddd49ef
Compare
They have never been used and are not supported in tools.
Better to reintroduce them if/when we in VSS specifies recommended
additional properties for e.g. security purposes or protocol adoptions.
Fixes #302
Signed-off-by: Erik Jaegervall erik.jaegervall@se.bosch.com