Those are lots of buzzwords but none of this happens or makes sense in practice as we see it today (for consumer, not industrial, IoT).
- decentralization is fine; no one is complaining that a thermometer doesn't store temperature log (though it could have some benefits) - it's fine to store it on a server, but people are complaining that they can't store that data on their own servers, they have to use insert-random-toilet-paper-startup's servers. Especially that those third parties do not provide any value (even though they could, in principle), they just farm you for data.
- collecting a lot of data doesn't mean learning a lot of useful things; quite often it's the opposite. What really matters is what you do with this data. If your Hardware-as-a-Service smart thermostat records temperature twice a second and the only thing you do with this data is logging it and looking at pretty graphs, it could collect readings twice an hour for more-less the same value given to you.
- spatial join - could you elaborate on that? From cursory Googling, it seems to be a term from GIS that mixes some data with information about its underlying database implementation...
- decentralization is fine; no one is complaining that a thermometer doesn't store temperature log (though it could have some benefits) - it's fine to store it on a server, but people are complaining that they can't store that data on their own servers, they have to use insert-random-toilet-paper-startup's servers. Especially that those third parties do not provide any value (even though they could, in principle), they just farm you for data.
- collecting a lot of data doesn't mean learning a lot of useful things; quite often it's the opposite. What really matters is what you do with this data. If your Hardware-as-a-Service smart thermostat records temperature twice a second and the only thing you do with this data is logging it and looking at pretty graphs, it could collect readings twice an hour for more-less the same value given to you.
- spatial join - could you elaborate on that? From cursory Googling, it seems to be a term from GIS that mixes some data with information about its underlying database implementation...