[DG-IDoT] question about a project idea

j stollman stollman.j at gmail.com
Tue Aug 30 11:11:06 CDT 2016


Ingo,

I would suggest that the idea is a good start.  But what you really want in
you "Google for IoT" is to be able to ask a question and get the answer,
not just the data.

For example,

1)      A tourist asks for “weather in Berlin” then he can get a report
with a drill down option to view the sources of data and, potentially,
select a subset to get a more refined forecast.  (An intermediate service
(e.g., weather.com) tracks the weather stations around the globe to be able
to provide this service.)

2)      I’m on vacation and I use “Google for IoT” to bring up a management
consoled to control my sensors (heating, lightning, etc.) Only I can see
and modify them.

3)      I’m in a sports team and we want to exchange our fitness data. So I
search for the fitness summaries of my team members. Only team member can
see the search results

4)      A service engineer wants to check status of his machines (e.g.
energy wind mill) he types in “wind mill xyz area” and gets a management
console that reports the status of all endpoints he is allowed to see.

5)      A car can ask for traffic information and get a mashup of data from
other cars in the area, as well as traffic webcams, and other road sensors.

Because several of the above scenarios include access control, I suspect
that some organization is needed to manage access control.  This
organization may as well customize results for its clientele and provide
the mashup to answer consumer questions, rather than just providing sources
of data and forcing the client to perform his/her own analysis.  This is
commonly done today by weather sites and mapping sites that also provide
traffic information.  So it isn't really anything new.

Jeff


---------------------------------
Jeff Stollman
stollman.j at gmail.com
+1 202.683.8699
<stollman.j at gmail.com>

Truth never triumphs — its opponents just die out.
Science advances one funeral at a time.
                                    Max Planck

On Tue, Aug 30, 2016 at 11:23 AM, <afesta at alfweb.com> wrote:

> hi all,
>  usually I'm only a "viewer/listener" in this amazing group but I find the
> idea realyl usefull. My points:
> 1) this search engine should be a sort of "white pages" of my own sensors,
> as Ingo correctly states: "Of course not everybody wants to publish a
> link to his data to everyone in the Interne" but doesn't mean one could
> not want exactly the opposite. We do need anyway to setup some basic
> filters/rules like: visibility, certificate status (the sensor is still
> available?if it is not a person but a company how do I certify it comes
> from it?)
> 2) usability, this search engine may be a first example of what I call "my
> IDoT" that is a way to expose the relationship between my sensors with
> other creating a taxonomy of what I have, what I use,what I accept to
> connect with/to
> 3) how ppl may use it? Let say I founded a good sensor to use, how do I
> connect to? Do the site expose a standard way to define the connection?
>
> How do I collaborate? :)
>
>
> Il Martedì 30 Agosto 2016 17:04, "Ingo.Friese at telekom.de" <
> Ingo.Friese at telekom.de> ha scritto:
>
>
>
> Dear group,
>
> I’d like to ask you for your opinion on a project idea called “A new
> ‘Google’ for IoT.
> Like in a classic search engine you can find millions of public available
> sensors (weather stations, wind mills, web-cams, traffic sensors etc.
> But a user can also publish own sensors as well. This could be sensors of
> fitness wristbands of own weather stations, sensors in a car etc.   Of
> course not everybody wants to publish a link to his data to everyone in the
> Internet.  That’s why every user can set a “visibility”-option to his
> entry. The user is in control of who can see the entries and what’s in the
> entries.
> You can run a very basic demo under https://rethink.tlabscloud.
> com/discovery/ (it’s a result of a EU-project I used it to simulate a
> “Google” for IoT”)
>
> 5 small Examples:
> 1)      A tourist looks for “weather stations in Berlin” then he can find
> detailed information about rain, temperature etc. (this is something you
> can try with the demo just type in “weather”)
> 2)      I’m on vacation and I use “Google for IoT” to get very fast to
> the URL of my sensors (heating, lightning, etc.) Only I can see the results.
> 3)      I’m in a sports team and we want to exchange our fitness data. So
> I search for the endpoints of my team members. Only team member can see the
> search results
> 4)      A service engineer wants to check status of his machines (e.g.
> energy wind mill) he types in “wind mill xyz area” and gets all endpoints
> he is allowed to see (test with the demo by typing “wind”)
> 5)      A car can search in the back ground for other cars and ask for
> traffic information
> Is such a service useful especially for users or a company? Do you see
> issues, advantages?
> Do you have ideas where this could be useful?
> Any comment or idea is welcome!
>
> Thank you in advance!
>
> Ingo
>
>
> Mit freundlichen Grüßen / Viele Grüße / Best Regards
> Ingo Friese
>
>
> *DEUTSCHE TELEKOM AG*
> T-Labs (Research & Innovation)
> Dipl.-Ing. Ingo Friese
> Winterfeldtstr. 21, 10781 Berlin
> +4930835358148 (Tel.)
> +4930835358408 (Fax)
> E-Mail: ingo.friese at telekom.de
> www.telekom.com
>
> *Erleben, was verbindet.*
>
> Die gesetzlichen Pflichtangaben finden Sie unter:
> www.telekom.com/pflichtangaben
>
> *Grosse Veränderungen fangen klein an **–** Ressourcen schonen und nicht
> jede E-Mail drucken.*
>
>
>
> _______________________________________________
> DG-IDoT mailing list
> DG-IDoT at kantarainitiative.org
> http://kantarainitiative.org/mailman/listinfo/dg-idot
>
>
>
> _______________________________________________
> DG-IDoT mailing list
> DG-IDoT at kantarainitiative.org
> http://kantarainitiative.org/mailman/listinfo/dg-idot
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kantarainitiative.org/pipermail/dg-idot/attachments/20160830/ed0eb2ae/attachment.html>


More information about the DG-IDoT mailing list