SignedMeteringValue specification is far too short... for some EMPs at least ;)

[ahzf]

The SignedMeteringValue is defined as max 3000 characters in https://github.com/hubject/oicp/blob/master/OICP-2.3/OICP%202.3%20CPO/03_CPO_Data_Types.asciidoc

Some EMPs start to cry when they receive a SignedMeteringValue larger than this via Hubject and demand changes at the CPO.

Yet, the CPO is also just forwarding this information from the charging station/energy meter, just like Hubject does. And the fact that Hubject forwards this information even when it is larger than 3000 characters means, that even Hubject understands this demand.

Please change this field within the sepcification to a very large or better an unknown size, as there are also HPC charging stations sending a large blob of signed meter values every 2 minutes at the end of the charging session... so it might even be several kByte of data in this field.