scope:

This document defines in general the different concepts, entities and roles involved in implementing and delivering ExVe web services. In addition, it also gives an overview of necessary activities that should be executed by the different roles involved and a logical order for thoseThe ExVe web services are in general a road vehicle combined with the telematics backend system of the Vehicle Manufacturer (the "Offering Party"). This enables for a 3rd party (the "Accessing Party") to access offered Resources via the internet. It also defines the concept of identifiers (direct and correlated) and resource categories (e.g. personal, vehicle related, pseudonymized and anonymized resources) as well as defining what a Resource and Resource groups are.An optional concept of Containers is also introduced that allow an accessing party to specify in detail what Resources to access. Containers are suggested to be used as a means to handle the issue of data economy and data privacy. Finally, this document states requirements on representation languages to be used like JSON and XML and illustrates how to use those languages to represent a Resource and in summary this standard defines a "framework" which uses adaptions of the following technology stack: Table 1 - List of used information technologies Transport Protocol HTTP 1.1 over TLS 1.2 Service Design RESTful Data format JSON XML Key-Value Authorization An OAuth 2.0 compatible framework End User Authentication An OpenID Connect 1.0 compatible framework