Home The News
The latest News
OpenV2G 0.9.3 release is available PDF Print
Wednesday, 25 February 2015 00:00

This version reflects the ISO/IEC 15118-2 FDIS status and is interoperable with OpenV2G 0.8 and OpenV2G 0.9 and OpenV2G 0.9.1/2 (ISO track) and also interoperable with OpenV2G 0.7 (DIN track), meaning that one can generate streams with one and decode with the other or vice-versa.

Further, this version resolves XML signature interoperability issues.
Note: To make use of xmldsig the following defines have to be set:

in "xmldsigEXIDatatypes.h"

#define DEPLOY_XMLDSIG_CODEC SUPPORT_YES
#define DEPLOY_XMLDSIG_CODEC_FRAGMENT SUPPORT_YES

and in "v2gEXIDatatypes.h"

#define DEPLOY_ISO_CODEC_FRAGMENT SUPPORT_YES

Otherwise the code is turned off.

 
ISO15118 XML signature Interoperability Issue PDF Print
Tuesday, 16 December 2014 00:00

In the recent weeks an ambiguity in the ISO 15118 spec w.r.t. XML Signature has been detected due to the incompatibility between OpenV2G and another implementation.

As it is likely that the XML Signature feature is not yet widely used it should be resolved as soon as possible. To evaluate the most pragmatic way to resolve this issue we would like to know until 31st of January 2015 if you are using the XML Signature feature of OpenV2G so far. If yes we would like to ask you to contact us personally so we can discuss the options to resolve this issue.

The questionable part in the core spec is which schema needs to be used to encode the SignedInfo element (Requirement [V2G2-119]). OpenV2G uses the full V2G schema set while at least one other implementation uses XMLdsig schema only.

Even though the specification is not clear what schema to use for this purpose, the informative annex J states the intent as follows "XML signatures only signs the SignedInfo element. Therefore this element needs to be EXI encoded using the schema-informed fragment grammar based on the XMLdsig schema (Canonicalization)." The proposal is now to follow this line which would require to change the OpenV2G implementation with respect to the schema used. A compromise to resolve this issue is to behave as stated in the annex and implement a fix in the core spec.

As stated before the OpenV2G team is implementing this fix we would like to know "who" is using this OpenV2G feature already and for "whom" this change might cause issues. So please contact us before the 31st of January if you are already using XML Signature of the OpenV2G implementation and are concerned about the proposed fix.

see http://sourceforge.net/p/openv2g/discussion/1226276/thread/429a7e5c/

 

 
OpenV2G 0.9.2 release is available PDF Print
Friday, 12 September 2014 00:00

This version reflects the ISO/IEC 15118-2 FDIS status and is interoperable with OpenV2G 0.8 and OpenV2G 0.9 and OpenV2G 0.9.1 (ISO track) and also interoperable with OpenV2G 0.7 (DIN track), meaning that one can generate streams with one and decode with the other or vice-versa.

Changelog

  • resolves bug with name clashes w.r.t. iso and din track
  • fixes issue with test code for init handshake
  • Note: OpenV2G 0.9.2 is essentially just a bug fixed version of OpenV2G 0.9.1
 
OpenV2G 0.9.1 release is available PDF Print
Thursday, 28 August 2014 00:00

This version reflects the ISO/IEC 15118-2 FDIS status and is interoperable with OpenV2G 0.8 and OpenV2G 0.9 (ISO track) and also interoperable with OpenV2G 0.7 (DIN track), meaning that one can generate streams with one and decode with the other or vice-versa.

Changelog

  • includes also support for DIN and hence interoperability with OpenV2G 0.7
    (needs to be switched on though by #define DEPLOY_DIN_CODEC)
  • fixes bugs and warnings for Visual Studio
  • Note: OpenV2G 0.9.1 is a superset of previous versions
    v2g...c/h files support ISO track
    din...c/h files support DIN track
 
Page 1 of 5
 

Initiated by

 

Co-Initiated by

 

Supported by