OCPI 2.3.0

[andacata]

New specification on the horizon with minor changes from 2.2.1

ocpi/ocpi#505

Summary:
With the OCPI Development Working Group we have decided to create a new release in the OCPI 2.x family. The impetus for this new 2.x release comes from compliance issues that parties using OCPI 2.2.1 will face in the year 2025.

We will fix those compliance issues and some other things while we're at it. The list of changes to make is:

• Make OCPI Extensible: possible to add modules, fields, enum values for certain enums
• Vehicle types
• Information for people with disabilities
• Support for North American taxes
• Take straightforward enum values from the OCPI 3.0 draft, including 15118 compat
• Add new field in credentials to give hub party ID + make hub clients be reported as normal credentials roles

[lilgallon]

Interesting, I think we still have time to finish the 2.2.1 version.

Migrating to 2.3.0 will take some time for everyone (even if the changes are minimal), the issue is that if a partner wants to update, its connected partners need to update as well, and it often takes a lot of time (at least with historic partners)

Once 2.2.1 will be completely done, we will be able to copy/paste 2.2.1 module to 2.3.0 and make changes specific to 2.3.0, if that sounds good to you

[andacata]

Yes, I created the task just to keep it in mind.

In fact, the specification is still a work in progress.