Yeah, “iotp” isn’t very clear/helpful. I’ve often used “wiotp” when referring
to “Watson IoT Platform”.
FWIW, wiotp's API’s base package name is com.ibm.iotf (IoT Framework) and
Edgent’s connector was originally named “iotf”. Then renamed when they changed
the name, but not package name, to “I
Hi,
Well on our company in-house conference last Thursday to Sunday I had one
session on "implementing IoT Platform adapters for Apache Edgent" and I got
some people together and we started to work on an AWS IoT Connector. Seems that
the concepts of the iot module can be implemented 1-to-1 with
+1 , I think we also could support to EdgexFoundry in the future.
2018-03-11 20:00 GMT+08:00 Christofer Dutz :
> Hi all,
>
> I am currently thinking of adding modules to support other IoT Platforms:
>
> * Google IoT
> * AWS IoT
> * Siemens MindSphere
>
> For that the “iotp” sort of do
Hi all,
I am currently thinking of adding modules to support other IoT Platforms:
* Google IoT
* AWS IoT
* Siemens MindSphere
For that the “iotp” sort of doesn’t quite fit as it’s not just “one” IoT
platform.
So would you be ok with renaming that to something like: “iot-ibm” or simi
