[Fiware-miwi] Text for TF-Proposal

[Philipp Slusallek]

Hi all,

Here is the text we talked about, in the call right now. It was sent to 
Juanjo and the TF core group:

----

-- Testing? Live Demos?
=======================
Here I can suggest that together with the team from Oulu and interested 
others we could organize such a task (e.g. as part of WP13). We have the 
UI components to make this very appealing to the public (industry, 
media, and politics) and there is already a strong interest in real 
applications within this team (so these would not just be mockups but 
prototypes). This is further supported by our close links to the very 
popular FI-Content UC (e.g. with Disney and other great partners) as 
well as FITMAN. I think strengthening such interactions with UCs on a 
technical and practical side would be an important strong point for the 
TF proposal. I would be willing to organize this quickly if there is 
enough support in the team.

Essentially, the goal would be to coordinate one or more larger 
demonstrators that would also involve the UC projects and their SEs. I 
believe this could be a great step forward in getting the UCs and 
Phase-III projects closer together and show what functionality we really 
have on offer.

Thematically, this should probably be based on the notion of 
"Dual/Simulated Reality" scenario where represent and interact with the 
real world out there via the computer/mobile. We would be using IoT to 
gather data from large numbers of sensors and actuators (e.g. home, 
city, production line) this data is preprocessed with help from the Data 
chapter and then visualized (2D, VR, AR in the Web) via WP13, which 
would also allows the user to interact with the real scene via its 
virtual representation. I2ND, Cloud, and Security are supporting this 
all very nicely.

If there is interest, I can provide a draft of such a task this weekend. 
It would be important to know who would want to contribute/support such 
activity in what way.


-- Robotics:
A robot cannot really be understood without its 3D environment. This is 
true for its sensing capabilities but even more so for its actuators. 
They are all placed on articulated structures, such that their 3D 
position, orientation, and motion has to be taken into account for many 
aspects. This cannot really be done in a pure IoT context where we 
essentially have a simply a collection of sensors and actuators but no 
real relationship between them or framework for interpreting or working 
with those relationships.

This is the main reason why I had previously suggested that robotics 
would fit well into WP13, where we have exactly these frameworks for 
representing, computing and simulating the robot as well as its 
environment. We can then (semantically) link the many sensors and 
actuators to such a 3D structure and do things like move the actuator to 
a specific position, which in turn involves animating many joint angles 
correctly (via Inverse Kinematics for example). I do not see any way of 
even representing such data/services in a IoT chapter.

We at least need to make this connection clear, independent of which WP 
the robotics task end up in. I actually do think that

As I have mentioned to some of you before: The big robotics department 
of DFKI has been involved in the ROS development and if there is still 
expertize needed, I could easily set up the connection and also act as 
their representative (since I no FI-PPP better). They would be happy to 
be engaged, so please let me know if I should contact them.

----


Best,

	Philipp
-- 

-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschäftsführung:
   Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
   Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
   Prof. Dr. h.c. Hans A. Aukes

Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973, Steuernummer:  19/673/0060/3
---------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slusallek.vcf
Type: text/x-vcard
Size: 441 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131127/87332fa1/attachment.vcf>