Confused about whether to chose JSON or XML in SPINE layer

[xsjqqq123]

In <EEBus_SHIP_TS_Specification_v1.1.0.pdf>, it clearly show "11 Message Representation Using JSON Text Format".
But in <EEBus_SPINE_TS_ProtocolSpecification.pdf>, it has lots of example using XML,

eebus-go seems using JSON as well in SPINE layer, it's correct? I'm new to eebus, thank for help me. We now want connect to FNN Control Box.

[sthelen-enqs]

Hi, that's a historical disconnect in the documentation.
SPINE is "technically" encoding agnostic (meaning it could be encoded as JSON or XML or ASN.1 or whatever). The actual encoding format is negotiated in the SHIP handshake in the SME Protocol Handshake which currently specifies JSON-UTF8 and JSON-UTF16 as possible options of which JSON-UTF8 is mandatory, und UTF16 is optional.
ship-go should just handle this for you though (we only support JSON-UTF8)