[OASIS Issue Tracker] (OCPP-29) Provide input for explaining the arguments for potentially dropping SOAP.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OCPP-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64289#comment-64289 ] 

Lonneke Driessen commented on OCPP-29:
--------------------------------------

How is this as an explanation:

The OASIS Technical Committee would like to obtain feedback from the on continuing support for SOAP in OCPP 2.0. 
OASIS Technical Committee is discussing whether to continue the support for SOAP in OCPP 2.0 or not. JSON over websocket will continue to be supported and the OCPP Technical Committee will also continue to review additional IOT friendly messaging protocols. The discussion to phase out SOAP is based on the the fact that the SOAP protocol requires XML which is very verbose.  The protocol does not lend itself to constrained computing resources that many EVSEs operate under. The verbosity of the protocol also leads to slower performance and a need for larger bandwidth that leads to higher cellular costs in many cases. 
The Technical Committee would specifically want to hear reasons in favor of keeping the support for SOAP in OCPP 2.0.


> Provide input for explaining the arguments for potentially dropping SOAP.	
> --------------------------------------------------------------------------
>
>                 Key: OCPP-29
>                 URL: https://issues.oasis-open.org/browse/OCPP-29
>             Project: OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC
>          Issue Type: Task
>         Environment: Generic
>            Reporter: Jonel Timbergen
>            Assignee: Lonneke Driessen
>            Priority: Trivial
>
> Provide input for explaining the arguments for potentially dropping SOAP.	



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)