Hi, Already done that, right as the first thing. Best, Philipp Am 11.12.2014 um 21:15 schrieb Juanjo Hierro: > Dear Philipp, > > Please program the slot from 10:30 to 11:30 so that Fermin (in copy) > can attend. The slot about KIARA would be afterwards (from 11:30 to 12:30) > > It would be nice if you invite some of the finnish partners. > > Cheers, > > -- Juanjo > > P.S.: Please note that my email address has changed > __________________________________________________________________ > > FIWARE Coordinator and Chief Architect > CTO of IoT and Smart Cities platform at Telefónica > > email: juanjose.hierro at telefonica.com > twitter: twitter.com/JuanjoHierro > > You can follow FIWARE at: > website: http://www.fiware.org > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 11/12/14 12:27, Philipp Slusallek wrote: >> Hi, >> >> Am 11.12.2014 um 08:30 schrieb Juanjo Hierro: >>> Count on you then to run a discussion about POIs ... >> I can present the current state of the POI work and also include the >> ongoing discussions about how to go forward. It is probably good to get >> everyone up to speed on this, start a wider discussion, and get input >> and requirements from other chapters. >> >> >> Best, >> >> Philipp >> >> >>> Cheers, >>> >>> -- Juanjo >>> >>> P.S.: Please note that my email address has changed >>> __________________________________________________________________ >>> >>> FIWARE Coordinator and Chief Architect >>> CTO of IoT and Smart Cities platform at Telefónica >>> >>> email: juanjose.hierro at telefonica.com >>> twitter: twitter.com/JuanjoHierro >>> >>> You can follow FIWARE at: >>> website: http://www.fiware.org >>> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >>> twitter: http://twitter.com/FIware >>> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >>> >>> On 10/12/14 13:45, Thomas Michael Bohnert wrote: >>>> Hi Juanjo, >>>> >>>> Sorry for replying a bit later and thanks to my colleagues that >>>> already replied on my behalf. >>>> >>>> I'd like to confirm the following: >>>> - Jaime will present KIARA >>>> - Philipp will present a discussion on POIs >>>> >>>> Robotics will be skipped for the moment. We first need to finally sort >>>> out a few architectural aspects. >>>> >>>> Best - Thomas >>>> >>>> On 12/10/2014 06:43 AM, Philipp Slusallek wrote: >>>>> Hi, >>>>> >>>>> I suggest that Jaime does the technical presentation on the new KIARA >>>>> design (in contrast to the existing one) and I would be happy to support >>>>> any time. >>>>> >>>>> I could also talk about the current state of POI but would then need to >>>>> know as soon as possible, so I can prepare slides. >>>>> >>>>> >>>>> Best, >>>>> >>>>> Philipp >>>>> >>>>> >>>>> Am 10.12.2014 um 05:43 schrieb Juanjo Hierro: >>>>>> Dear Thomas, Philipp, Jaime, >>>>>> >>>>>> I would like to devote enough time to review the status of KIARA >>>>>> (technical point of view) in the next weekly architects follow-up >>>>>> confcall, scheduled on Monday 15th from 10:30 to 12:30. >>>>>> >>>>>> The goal would be to go deeper into KIARA. During the last >>>>>> sprint-demo day, you explained that you have closed a final >>>>>> specification of the KIARA IDL and that you have a first implementation >>>>>> of the tools and core middleware (in Java?). I would like to tackle >>>>>> the following points during the slot: >>>>>> >>>>>> * Overview of KIARA IDL and how it will finally compare with OMG IDL >>>>>> (e.g., does it support objects by value? does it support the "any" >>>>>> type? what basic and structured data types it supports, how >>>>>> exceptions are described? etc) >>>>>> * Example about how a simple HelloWorld program may look like >>>>>> (please >>>>>> define some interface example that comprises a couple of simple >>>>>> operations that comprise input arguments and generate some output >>>>>> arguments or result) >>>>>> o What sort of stub and skeleton files will be generated by >>>>>> compiling the OMG IDL >>>>>> o How the skeleton of the server side would be programmed >>>>>> o How programming of calls to interface operations would look >>>>>> like >>>>>> on the client side >>>>>> + using static stubs generated from the OMG IDL specs >>>>>> + using some sort of dynamic API, if KIARA will support such >>>>>> sort of API >>>>>> >>>>>> >>>>>> Please confirm whether it will be feasible to allocate the slot (it >>>>>> would be one hour, but you should allow interaction, so I wouldn't plan >>>>>> more than 30 mins for the presentation). >>>>>> >>>>>> @Thomas: In addition to the slot of KIARA, I would like to review >>>>>> any >>>>>> progress regarding the robotics architecture. Could we also prepare >>>>>> something? I guess there should be a sketch of architecture already >>>>>> available. >>>>>> >>>>>> @Philipp: If we couldn't plan the slot on robotics, I wonder whether >>>>>> we could plan a discussion on POIs. Then you should invite some of >>>>>> the >>>>>> Finnish guys (@Thomas: this will depend very much on whether the >>>>>> slot on >>>>>> robotics is taken, please let us know tomorrow so that Philipp can >>>>>> eventually plan the discusson on POIs) >>>>>> >>>>>> Regarding preparation of all the slots: please note that the >>>>>> audience >>>>>> is technical (FIWARE architects) but they may not know all the details >>>>>> about the topic being coverd (e.g., they may not be experts in >>>>>> Thrift/CORBA or ROS). Please generate slides that are >>>>>> "didactic/educational" enough. >>>>>> >>>>>> Best regards, >>>>>> >>>>>> -- Juanjo >>>>>> >>>>>> -- >>>>>> P.S.: Please note that my email address has changed >>>>>> __________________________________________________________________ >>>>>> >>>>>> FIWARE Coordinator and Chief Architect >>>>>> CTO of IoT and Smart Cities platform at Telefónica >>>>>> >>>>>> email: juanjose.hierro at telefonica.com >>>>>> twitter: twitter.com/JuanjoHierro >>>>>> >>>>>> You can follow FIWARE at: >>>>>> website: http://www.fiware.org >>>>>> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >>>>>> twitter: http://twitter.com/FIware >>>>>> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>>>> destinatario, >>>>>> puede contener información privilegiada o confidencial y es para uso >>>>>> exclusivo de la persona o entidad de destino. Si no es usted. el >>>>>> destinatario indicado, queda notificado de que la lectura, utilización, >>>>>> divulgación y/o copia sin autorización puede estar prohibida en virtud >>>>>> de la legislación vigente. Si ha recibido este mensaje por error, le >>>>>> rogamos que nos lo comunique inmediatamente por esta misma vía y >>>>>> proceda >>>>>> a su destrucción. >>>>>> >>>>>> The information contained in this transmission is privileged and >>>>>> confidential information intended only for the use of the individual or >>>>>> entity named above. If the reader of this message is not the intended >>>>>> recipient, you are hereby notified that any dissemination, distribution >>>>>> or copying of this communication is strictly prohibited. If you have >>>>>> received this transmission in error, do not read it. Please immediately >>>>>> reply to the sender that you have received this communication in error >>>>>> and then delete it. >>>>>> >>>>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>>>> destinatário, pode conter informação privilegiada ou confidencial e é >>>>>> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa >>>>>> senhoria o destinatário indicado, fica notificado de que a leitura, >>>>>> utilização, divulgação e/ou cópia sem autorização pode estar >>>>>> proibida em >>>>>> virtude da legislação vigente. Se recebeu esta mensagem por erro, >>>>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>>>> proceda a sua destruição >>>>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, >>> puede contener información privilegiada o confidencial y es para uso >>> exclusivo de la persona o entidad de destino. Si no es usted. el >>> destinatario indicado, queda notificado de que la lectura, utilización, >>> divulgación y/o copia sin autorización puede estar prohibida en virtud >>> de la legislación vigente. Si ha recibido este mensaje por error, le >>> rogamos que nos lo comunique inmediatamente por esta misma vía y proceda >>> a su destrucción. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual or >>> entity named above. If the reader of this message is not the intended >>> recipient, you are hereby notified that any dissemination, distribution >>> or copying of this communication is strictly prohibited. If you have >>> received this transmission in error, do not read it. Please immediately >>> reply to the sender that you have received this communication in error >>> and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinatário, pode conter informação privilegiada ou confidencial e é >>> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa >>> senhoria o destinatário indicado, fica notificado de que a leitura, >>> utilização, divulgação e/ou cópia sem autorização pode estar proibida em >>> virtude da legislação vigente. Se recebeu esta mensagem por erro, >>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>> proceda a sua destruição >> > > > ------------------------------------------------------------------------ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud > de la legislación vigente. Si ha recibido este mensaje por error, le > rogamos que nos lo comunique inmediatamente por esta misma vía y proceda > a su destrucción. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution > or copying of this communication is strictly prohibited. If you have > received this transmission in error, do not read it. Please immediately > reply to the sender that you have received this communication in error > and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinatário, pode conter informação privilegiada ou confidencial e é > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa > senhoria o destinatário indicado, fica notificado de que a leitura, > utilização, divulgação e/ou cópia sem autorização pode estar proibida em > virtude da legislação vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição -- ------------------------------------------------------------------------- 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: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20141212/6903b682/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy