Hi Juanjo, To be clear: While I work on weekend regularly I prefer projects not to require this from me (including this conversation to clarify thing for the Monday meeting)! There was plenty of time to discuss this last week. Or simply accept the shift by a week as suggested if it did not work out to answer my email during that week (which can happen). Obviously, the topic is not really time critical in that case. Am 23.11.2014 um 10:30 schrieb Juanjo Hierro: > On 23/11/14 08:36, Philipp Slusallek wrote: >> Dear Juanjo, > It is expected that architects book this slot and attend regularly. > Yes, being architect in FIWARE will be a bit demanding, but otherwise > this endeveur will never fly :-) This slot has been reserved in my calendar for months now but I took the freedom to reuse it since no meetings ever took place (and typically without it being canceled first!). I expect projects to make good use of my limited time! I am more than willing to again lock that slot for these events but please allow for a transition time (for me exactly one event on this coming Monday). > I had the opportunity to see that this integration has already been > achieved by people of the Web-based UI team. Indeed, they presented > some demos about how it is working at the Smart City Expo World > Congress. Therefore, it could be mostly a matter of describing what > has been done in a couple of slides, to make sure it is in the proper > manner (for this, people from the data chapter are expected to attend) > and let rest of the architects be aware of that. It shouldn't be so > that difficult. Well it is more difficult than that as there are several things ongoing and if we are going to present this we should do a joint presentation that puts the entire work in perspective for the rest of FIWARE. Since most of the chapter was busy with the Barcelona and other activities last week we had no joint meeting in which to prepare anything either. > We had activated 188 K€ for a demo that has to be finalized by end of > this year which should show how Web-based UI GEs can be used in an > end-to-end scenario, involving actual sensors and a flow of information > from sensors to the UI through the Context Broker. Therefore, we have to > make progress. As you apparently already saw at the event there has been quite some progress. I consider it better to give a well prepared presentation in a week from now than just show some pieces. I see no reason why this cannot wait one week! > Let's program the slot so that we can at least see where we are (a > couple of slides and some demo would be enough), then identify and > prepare specific points to be discussed in more detail next week (i.e., > monday December 1st) We can certainly talk about thing a bit but I am not sure if it is that helpful without other having seen the whole story first. Therefore, I would still prefer the full presentation one week later. >> Also: Do we even know yet which infrastructure we will use for these >> presentations, how to present, and how to call in? I might have missed >> it but I don't think I saw a decisions on that yet. > > Dial-in details (powwownow) have been always there in the main body > of the invitation of the call ... Didn't you get this info? > > We may use join.me for sharing the screen although I will make a try > to see if we can use Lync because join.me may have some limitations. Well, you yourself suggested the use of join.me in your first email. I responded but never got any feedback on this. So consider me confused. While we use powwownow normally, I at least have not seen us use it for more than audio conversations. I just tried to find out if and how powwownow works with Linux for non-audio stuff, however, it requires downloading a piece of software and one can do so only with an account (and probably for money). Do we have such an account to be used for FI-Core? Does it work for Linux (I could not find much on the Internet in that regard)? Just to be clear, to show demos we need to run interactive stuff in the Web browser and transmit this to everyone on the call. We would also show some slides. Even trying this out and checking it all works on a service we have not used before requires some time for preparation (preferably not on weekends!). >> Also is it correct that you want the morning call to take place now be >> from 10:30to 12:30h? The official invitation I have in my calender (from >> you) still reads 11-12:30h. It might be good to update that for all >> (including whatever call mechanism we plan to use). > > I updated it some time ago to be 2 hours yes (1 hour per topic). You > should have received an update of the invitation in your email time ago. What I got from you is -- The initial weekly meeting from 11-12.30 (this is still active in my calendar) -- a invite for this Monday (24th only, 10:30-12:30h, apparently via Google) -- A new invite today also only for tomorrow (10:30-12:30, apparently through Outlook or such) At least I have no weekly invite for 10:30-12:30. I might have missed something though. In that case please send that (change of) invite again. Best, Philipp > > Best regards, > > -- Juanjo > >> >> >> Best, >> >> Philipp >> >> >> Am 22.11.2014 um 17:36 schrieb Juanjo Hierro: >>> A friendly reminder ... >>> >>> @Philipp: I expect that someone form the Advanced Web-based UI >>> chapter >>> will come to elaborate on progress and explain us how they have >>> integrated with the Context Broker. I had the opportunity to see what >>> was achieved during the Smart City Expo World Congress and I believe we >>> are in the right track. >>> >>> @Sergio, @Javier: I expect that you will present work regarding >>> extensions to CKAN and the current state of the art regarding >>> monetization/access-control of APIs/datasets published through CKAN as >>> well as the publication of Context Broker endpoints-datasets through >>> CKAN. >>> >>> Could all of you confirm? >>> >>> Best regards, >>> >>> -- Juanjo >>> >>> __________________________________________________________________ >>> >>> 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 16/11/14 17:13, Juanjo Hierro wrote: >>>> Dear FIWARE architects, >>>> >>>> As announced when we started the FI-Core project, we will carry out >>>> periodic confcalls to carry out technical discussion on focused >>>> topics, also to follow-up technical progress. Besides, these >>>> meetings will help each FIWARE architect to understand what's going on >>>> in another chapters and identify potential areas to develop further >>>> integration between chapters. Attendance of FIWARE chapter >>>> architects is mandatory while attendance of FIWARE chapter leaders of >>>> FIWARE WG leaders is optional. >>>> >>>> Each of these confcalls will run from 10:30 to 12:30. We should be >>>> able to cover two specific technical topics during each of these >>>> confcall (devoting 1 hour to each). >>>> >>>> The confcall of the monday after the last friday of a given month >>>> will be devoted to demos of the results of the last development >>>> sprints from each of the chapters. Manuel will assist in >>>> coordinating the agenda of those sprint demo confcalls. >>>> >>>> The first of these periodic concalls will take place next November >>>> 24th. I would like to cover two topics: >>>> >>>> * Description of Web-based UI chapter and integration with Context >>>> Broker GE (responsible, Philipp) >>>> * CKAN extensions: publication of Context Broker API datasets and >>>> integration with Store for management of datasets access rights >>>> (responsible, Javier & Sergio) >>>> >>>> >>>> Please invite people from your chapters that you believe can >>>> contribute to the discussion or you believe it is important that get >>>> aware about the topics being discussed. >>>> >>>> We will need to use some tool to share screens (this will be >>>> essential to share presentations and/or demos). I would suggest >>>> using join.me, but if someone else have some other idea in mind, don't >>>> hesitate to make a proposal. >>>> >>>> Best regards, >>>> -- Juanjo >>>> __________________________________________________________________ >>>> >>>> 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 >>> >>> >>> _______________________________________________ >>> Fiware-chapter-architects mailing list >>> Fiware-chapter-architects at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-chapter-architects >>> >> > > > ________________________________ > > 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-leaders/attachments/20141123/8d4f6430/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy