[m2m-iwg] M2M4ME

[Cornie Malan <ctmalan@xxxxxxxxx>]

M2M for me consists of the following if you look from bottom up, written top-down:

- application layer: using my m2m data;

- security layer:  who owns this data, who can have access and who decides who can have access;

- database layer: rules of how the input/outputs from the atomic devices are stored;

- transport layer: MQTT;

- in between layer: set up the reporting rules (always on, deadband, delta, wait for delivery;)

- at the bottom: atomic devices (din, dout, ain, aout, sin, sout.)

My m2m4me layers might not conform to the 4all model, but maybe I can shuffle stuff around?

Maybe my in between layer can move around?

I am a bit worried who will look and abuse my m2m data, m2m4me to m2m4all conversion in the security layer.

There might be some advantage to let people see my data if they do not know it is mine...

Any help in formalising this into, (or out of) technospeak might help.

C-: