Files
cariflex/tools/shapeshifter-specification-main/docs/message-descriptions/scope.md
Eric F d398a6ced2 Add extracted tools: CitrineOS, OpenOCPP, ShapeShifter
- 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
2026-06-08 00:38:27 -04:00

1.4 KiB
Raw Blame History

Scope

USEF defines the content of XML messages between role processes, as required for implementation of USEFs 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.

![Relationship between the normative USEF XML messages (yellow pane) and the best-practice message transfer mechanism (light-blue pane).](../assets/images/image18.emf.odg.svg.png){ width=1000px }
Relationship between the normative USEF XML messages (yellow pane) and the best-practice message transfer mechanism (light-blue pane).

When selecting a message transfer mechanism, local market conditions should be considered and the USEF privacy and security guidelines should be followed 1 . Further recommendations about the message transport mechanism are given in Message transport mechanism.


  1. 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 ↩︎