d398a6ced2
- CitrineOS core extracted (CSMS OCPP 2.0.1) - OpenOCPP extracted (firmware OCPP 1.6J/2.0.1) - ShapeShifter library installed (pip install -e) - ShapeShifter specification extracted - EVerest extracted TODO updated with progress
22 lines
1.4 KiB
Markdown
22 lines
1.4 KiB
Markdown
<!--
|
||
SPDX-FileCopyrightText: 2020-2023 Contributors to the Shapeshifter project
|
||
|
||
SPDX-License-Identifier: Apache-2.0
|
||
-->
|
||
|
||
# Scope
|
||
|
||
USEF defines the content of XML messages between role processes, as required for implementation of USEF’s MCM.
|
||
Each message has a unique recipient, identified by the Internet domain and USEF role of the participant.
|
||
The message transfer mechanism is responsible for sending and receiving these messages.
|
||
|
||
<figure markdown>
|
||
{ width=1000px }
|
||
<figcaption>Relationship between the normative USEF XML messages (yellow pane) and the best-practice message transfer mechanism (light-blue pane).</figcaption>
|
||
</figure>
|
||
|
||
When selecting a message transfer mechanism, local market conditions should be considered and the USEF privacy and security guidelines should be followed [^B5].
|
||
Further recommendations about the message transport mechanism are given in [Message transport mechanism](../appendix/message-transport-mechanism.md).
|
||
|
||
[^B5]: USEF Foundation, "USEF: The Privacy and Security Guideline," USEF Foundation, Arnhem, 2015. Available: [https://www.usef.energy/app/uploads/2016/12/USEF_PrivacySecurityGuideline_3nov15.pdf](https://www.usef.energy/app/uploads/2016/12/USEF_PrivacySecurityGuideline_3nov15.pdf)
|