[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[sparkplug-dev] Request for comments on Sparkplug 'A'
|
TL;DR: Is there anyone concerned with the 'Sparkplug A' version of the
protobuf payload being removed from the original version of the
specification?
History: The original concept behind payloads for Sparkplug was that
there could/would be more than one. As a result, we created a 'first
topic token' to define what the form of the payload would be. A well
known example of this is 'spBv1.0'. The idea here was:
sp = Sparkplug
B = The form of the payload (i.e. the 'B' Google Protobuf definition)
v1.0 = The version of the payload form (i.e. version 1.0 - and there
could be future versions)
So, there could be completely different forms of a payload (i.e. JSON,
XML, some yet to be defined structure, etc). Then there could also be
versions of the payload forms. Using this first token, an Edge Node is
declaring what decoder to use at a Host Application.
As we thought could occur, there were a number of problems with
Sparkplug A. We tracked a lot of these issues and pretty quickly after
the original Sparkplug A release came up with the 'B' version. However,
at this point I know of nobody using the 'A' form except for Cirrus
Link. With the evolution of the specification the current thinking of
the spec team is to note the history and long term vision of payload
structures, but not include the technical details of 'A' as there
doesn't seem to be a good reason to do so. I would always encourage any
new implementor to go the route of B.
So my question is - Is there anyone that strongly disagrees with this
before it gets removed?