I agree with Tom. That makes sense from a data and functional design perspective too.

It is best if OVMS remain uncoupled as much as possible and pushes out updates to OCM for opted-in users through an external system update layer. That layer could be independent of the main OVMS system and could have stubs for each data interface that OVMS wishes to interact with. That would make the design, development and maintenance of this functionality modular, isolated and easier to develop.

tbh, I would feel uncomfortable with OCM pulling changes in from OVMS. The update originate from within OVMS and so OVMS should initiate the action IMO. So, I would prefer to OVMS charging location capture to be generic and not tied to OCM or to OCM functionality. Of course, OCM and its requirements will impact on the OVMS design but OVMS should remain, wherever possible, external system/database agnostic.