efucile
commented
1 year ago Decision
The adoption of packaging is responsibility of the domain, not the WIS2 governance. This will not be offered in the guide. The only option that can be offered is to include the payload in the data message.
In the transition guide we need to clarify that there isn't any more requirement to build collectives before sharing data.
Suggested to implement in wis2box sharing data as payload when they are less than 4kB. To make the payload propagate to the GCs we need to clarify that a GC should not change the notification message and this includes when there is a payload.
6a6d74
WIS2 employs a one message one file policy. However we want to open the discussion if WIS2 should also allow the creation of packages.
One thing to consider is, that one message one file leads to a lot of connections from a single source each downloading one observation. This might trigger Denial of Service Prevention Systems or other cyber security technologies.
What i would like to propose is to allow for observations (or other items) to be stored in archives and these archives could then be ingested into WIS2 using for example ZIP or gzip as data format.
The WIS2 Guide would then need to be updated to specify the allowed packaging methods (given that ZIP and gzip are also widely accepted standards).