Em sexta-feira, 21 de abril de 2017, ?s 01:26:52 PDT, Dwarkaprasad Dayama escreveu: > Hi Thiago, > > Very much appreciated for your detailed feedback. > > Sure we can consider Cloud to be hybrid the way you expressed. > > Please find my answers in same order below - > > > > [Thiago] 1) can you provide a little more detail on the projects? What > activities and subsystems do you expect to be inside each? The distinction > between Device Framework and Device Platform escapes me. > > Each project here is software functionality layer of product. IMHO > activities and subsystems per layer will be as below - > > Bridge : Translators or Plugins & Bridge Security implementation. > > Cloud / Fog : Cloud/Fog interface, User/Device Management, Data Analytics, > Cloud/Fog Security implementation.
These are ok for me. > Device : Connectivity, Protocol & Device Security implementation. > > Device framework here means IoTivity or IoTivity constrained. Which is > actually just library to be used on top preferred operating system. What's the difference between Device and Device Framework? And where would you put extra service functionality, such as proxies, resource directory, etc.? > Device platform here means a Kernel. There can be solutions which come > packaged (Kernel + Framework) to be used for Chipset vendors at ease and > quickly. This code may or may not be hosted in IoTivity git. But if there is > a relation with IoTivity (aka OCF), there can be collateral information in > IoTivity website. I think this needs some more discussion. My initial reaction is that doing the kernel itself is not IoTivity's business. However, doing "everything but the kernel" makes sense and was indeed part of what I had initially proposed, last year. That is, everything that sits on top of the base system and libraries that come with that system, integrated so that they will work well together and provide a nice service functionality. This eventually can lead to device management APIs, like the ability to install updates. But it cannot be exclusive. IoTivity needs to work on other systems too. And we need to be careful on what is IoTivity and what is just an external open source project we reuse. Anyway, more discussion needed. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
