ocpi 0.3.5

Unofficial, in progress, OCPI implementation
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

use super::{CiString, TokenType};

#[derive(Clone, Debug, PartialEq, Eq, serde::Serialize, serde::Deserialize)]
pub struct CdrToken {
    /// Unique ID by which this Token can be identified.
    /// This is the field used by the CPO’s system (RFID reader on the Charge Point) to
    /// identify this token.
    /// Currently, in most cases: type=RFID, this is the RFID hidden ID as read by the
    /// RFID reader, but that is not a requirement.
    /// If this is a type=APP_USER Token, it will be a unique, by the eMSP, generated
    /// ID.
    pub uid: CiString<36>,

    /// Type of the token
    pub typ: TokenType,

    /// Uniquely identifies the EV driver contract token within the eMSP’s platform (and
    /// suboperator platforms). Recommended to follow the specification for eMA ID
    /// from "eMI3 standard version V1.0" (http://emi3group.com/documents-links/)
    /// "Part 2: business objects."
    pub contract_id: CiString<36>,
}