Comments (4)
I proposed this in the W3C automotive WG, with the following discussion found below under “Gen2 ideas”.
https://lists.w3.org/Archives/Public/public-automotive/2019May/
I think the correct link is this one: https://lists.w3.org/Archives/Public/public-automotive/2019May/0009.html
I think VSS should stick to the scope of a schema and metadata definition for signals/sensors/attributes but you propose multiple ideas:
there must be aq way of tagging the nodes with the appropriate level of access restriction
I agree. But this should not be in the YAML spec but rather something you specify in your implementation of VSS, at the same time as when you map VSS to your hardware.
that informs whether access to the node require an authorization verification before access is allowed
A good practice would be to "force" the usage of an "access" implementation-specific property. If you do not require an access, this should be epxlicitely mentioned there.
In order not to have to tag all nodes of the tree, a mechanism of inheritance from ancestor nodes could be applied (“if no explicit tag, a child inherits from parent”).
+1
This relates to the general discussion about schema and conceptual signal metadata (unit, format, description) vs implementation metadata (access, accuracy). See #105 and #109 also
from vehicle_signal_specification.
But this should not be in the YAML spec but rather something you specify in your implementation of VSS, at the same time as when you map VSS to your hardware.
I fully agree.
from vehicle_signal_specification.
I think it is now a good timing to define a solution to the access restriction tagging, as the W3C automotive spec referring to VSS is defining a comprehensive access restriction solution. I agree with @klotzbenjamin that this tagging should not be done in the YAML spec, but introduced at a later stage, but I also think the details of this later stage should be defined as part of the VSS specification.
from vehicle_signal_specification.
I am doing some cleanup closing all issues created 2021 or earlier where there have been no activity 2023 or later. If you still consider this issue relevant feel free to reopen it add and add a comment on how you would like to see progress on this one.
from vehicle_signal_specification.
Related Issues (20)
- Type Limitations? HOT 9
- VSS or HIM? HOT 5
- Types and datatypes HOT 3
- Release Planning 5.0 and 4.X HOT 6
- Support of multiple measurement units in VSS signals HOT 14
- In-Vehicle Notification signal for Infotainment HOT 2
- Enforce "style" for VSS standard catalog HOT 6
- Need for release-branches? HOT 11
- Ranges for Float and Double HOT 1
- Supported encoding for string values HOT 1
- Need for release tar-ball HOT 4
- Hydrofoil signals HOT 1
- Vehicle Error Codes HOT 2
- Representing signals in VSS tree HOT 2
- Inconsistent terminology - attributes, members, elements, meta data HOT 3
- typo in vspec v3.0 makes vss-tools 4.x fail HOT 2
- vehicle signal specification generated fidl is not recognized by commonapi. HOT 1
- Overlay childrens are not merged causing extensions_attributes missing HOT 3
- Mathematical Operation in Vspec HOT 5
- Signal references inside structs? HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vehicle_signal_specification.