BS ISO 20078-1:2019 pdf free.Road vehicles一Extended vehicle (ExVe) web services.
3.2.6 Access delegated right to an Accessing Party to access a Resource Owner’s Resources 3.2.7 Authorization Policy set of rules that define Access control to protected Resources
3.2.8 Token sequence of characters representing a verified identity and/or Access Note 1 to entry: The issuer of the token is responsible for the interpretation and the integrity of the token; e. g. the Authorization Provider of the Offering Party or in a second example an intermediate body for the Authorization Provider of the Offering Party. Note 2 to entry: The Token is used for securely transmitting verifiable identity and/or authorization information between involved parties like Resource Owner, Accessing Party and/or Offering Party. 3.2.9 Fleet group of Connected Vehicles associated to a specific Resource Owner  Figure 4 describes roles and their relationship to entities required for granting an Accessing Party Access to a Resource Owner’s Resources. NOTE 1 Each role could be implemented by the VM or other parties (e.g. IT Web developers, contractor agencies, or third-party software developers). NOTE 2
When the implementation is performed by other parties, the VM can remain responsible for data, data management, and data processing, subject to different national data protection legislations. 7 Identifiers 7.1 General Identifiers are used to uniquely identify a specific Resource or a party and are typically allocated by the Offering Party. Some identifiers are publicly known whereas some are only shared between two parties. Figure 6 is an example of the relation between Containers and Resources. Resources consist of data (e.g. Odometer, Fuel level, or in-vehicle temperature), aggregated information (e.g. Position, Vehicle Status, or Diagnostic Trouble Codes), and functionality (e.g. unlock Vehicle, set value of pre-Heater, dtcReadouts).
The three Containers defined by the Accessing Party (A, B, and C) each have an individual purpose (A, B, and C) and an individual relation to Resources. Container A is defined to include the odometer. Container B relates to Resources like Position, Vehicle Status, and functionalities to unlock Vehicle and set the value for Pre-Heater. Container C only includes the functionality to read out a list of Diagnostic Trouble Codes. Such Containers can be defined by the Accessing Party for allowing (data) minimalism while processing Resource. By that possibility the (data) privacy by design principle is fulfilled. 10 Representation 10.1 General When transferring Resources between the Offering Party and the Accessing Party, a well-defined structure is needed. It is recommended to use JSON, but the Offering Party may choose to use XML or key-value pairs. The Offering Party selects and defines the representation of Resources and describes each Resource for the Accessing Party.BS ISO 20078-1 pdf download.