Dear All, I have been looking at the IDS architecture. At the time being it seems that most of the concerns are at the logic level and at the “trust” between actors (and hence data provision and consumption services). This aspect is quite unrelated with the work done in MasterMind, in the sense that this concerns should be tackled first at the level of enablers, before they can be “managed” within an orchestration environment. In particular, all the part of “trusted” and “verified” communication between consumers and producers via trusted certificates requires a similar concept in the NGSI data chain, which in my understanding is lacking today. Beyond that, it looks a bus-based architecture, so it reflect the concept of having a context broker “federation” that exchange data among different peers and data are lifted at level of the context broker using “connectors” (which could be IoT Agents or any other NGSI adapters) in FIWARE picture. I.e. yes from the conceptual architecture, given the fact that FIWARE can be mapped to IDS (but this apply basically to any EBS like architecture), MasterMind is aligned as well. Still, if we want to promote FIWARE Data Management chain as a way to implement IDS, Data Management chapter should look in the way to implement trust management between data consumers and data producers. Best, Federico Dr. Federico Michele Facca Head of Martel Lab Martel Innovate Dorfstrasse 73 - 3073 Gümligen (Switzerland) 0041 78 807 58 38 0041 31 994 25 25 martel-innovate.com <http://martel-innovate.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170619/48bf71ea/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy