https://github.com/covesa/vehicle-information-service-specification
https://github.com/covesa/vehicle-information-service-specification
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/covesa/vehicle-information-service-specification
- Owner: COVESA
- License: mpl-2.0
- Created: 2024-02-27T18:13:00.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-02-04T10:30:03.000Z (4 months ago)
- Last Synced: 2025-02-04T11:24:27.439Z (4 months ago)
- Language: HTML
- Size: 1.07 MB
- Stars: 4
- Watchers: 6
- Forks: 4
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# vehicle-information-service-specification
[](https://opensource.org/licenses/MPL-2.0)
### Maintainers
Ulf Björkengren - Ford Motor Company
Ted Guild - Geotab Inc.
Peter Winzell - Volvo Cars
Wonsuk Lee - ETRI
### Lead editors
Ulf Björkengren - Ford Motor Company
### Working group meetings
The VISS working group meets every other Monday at 16.00 CET.
The schedule and link to meeting can be found [here](https://wiki.covesa.global/display/WIK4/COVESA+Common+Meeting+Schedule).
Minutes of meetings is found [here](https://wiki.covesa.global/display/WIK4/VISS+Meeting+Topics+and+Meeting+Notes).
## Overview
>Vehicle Information Service Specification (VISS) is an API for accessing the COVESA Vehicle Signal Specification (VSS) data. The work started at [The World Wide Web Consortium (W3C)](https://www.w3.org) in collaboration with GENIVI and its successor COVESA. The W3C Automotive Working Group closed in February of 2024 and the work is continuing at COVESA.
To see the most recent HTML rendered version of the specifications from this repository can be found at the following:
- [COVESA VISS version 3.0 - Core](https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv3.0_Core.html)
- [COVESA VISS version 3.0-Payload Encoding](https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv3.0_PayloadEncoding.html)
- [COVESA VISS version 3.0-Transport](https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv3.0_Transport.html)
The [VISS explainer](./VISS-explainer.md) gives some background and rationale to this interface.
## Latest version
[VISS version 2.0](https://github.com/COVESA/vehicle-information-service-specification/releases/tag/v2.0)
## Previous versions
[VISS version 1](https://www.w3.org/TR/vehicle-information-service/)
## Reference Implementation
[http://github.com/COVESA/vissr](http://github.com/COVESA/vissr)
## Specification references
The Adaptive AUTOSAR R24-11 official publication.
[AUTOSAR](https://www.autosar.org/) released the [Adaptive AUTOSAR R24-11](https://www.autosar.org/search?tx_solr%5Bfilter%5D%5B1%5D=platform%3AAP&tx_solr%5Bfilter%5D%5B2%5D=category%3AR24-11&tx_solr%5Bq%5D=) including Automotive API Gateway specification at the end of December 2024. Automotive API Gateway specification is developed based on the [COVESA VISS v2-Core](https://github.com/COVESA/vehicle-information-service-specification/releases/tag/v2.0) and [COVESA VISS v2-Transport](https://github.com/COVESA/vehicle-information-service-specification/releases/tag/v2.0) specifications. The related standards and technical documents are as follows:
- [Explanation of Automotive API](https://www.autosar.org/fileadmin/standards/R24-11/AP/AUTOSAR_AP_EXP_AutomotiveAPI.pdf)
- [Requirements on Automotive API Gateway](https://www.autosar.org/fileadmin/standards/R24-11/AP/AUTOSAR_AP_RS_AutomotiveAPIGateway.pdf)
- [Specification of Automotive API Gateway](https://www.autosar.org/fileadmin/standards/R24-11/AP/AUTOSAR_AP_SWS_AutomotiveAPIGateway.pdf)
- [Technical Report on VSS Representation](https://www.autosar.org/fileadmin/standards/R24-11/AP/AUTOSAR_AP_TR_VSSRepresentation.pdf)
- [Adaptive Platform Release Overview](https://www.autosar.org/fileadmin/standards/R24-11/AP/AUTOSAR_AP_TR_ReleaseOverview.pdf)
## Tools
- [ReSpec](https://www.w3.org/respec/) has been used to style the specifications allowing the editors to focus on functionality and ensure consistency and referential integrity
- The [API Design Cookbook](http://www.w3.org/TR/api-design/) has been used as a guide for the use of WebIDL
## Style Guidelines
### JavaScript Style Guidelines
JavaScript should be written using the [JSCS](http://jscs.info/) rule set defined by [Echidna](https://github.com/w3c/echidna/blob/master/.jscs.json).