Dear Clara, Thanks very much for your proposal. I answer also in english, copying the whole TSC because it would be great to hear others' feedback. For me the question or "challenge" to solve is how to design a training course (Developers' Primer) which a) lasts two days, b) content-wise is complete enough to justify that we give away some sort of "FIWARE programmers primer" certificate (and obtaining such certificate is meaningful) and c) the course doesn't become a long and tedious course plenty of "theory" and just slides, one after the other. One potential approach would be that of designing an agenda of sessions where we introduce small "pills" of "show me te code" or "learn by example" presentations along the agenda. Thus, for instance, in our traditional agenda we have: 1. FIWARE Overview - 30 min 2. FIWARE Orion Context Broker / FIWARE NGSI - 60 mins But we can do something more dynamic if we do the following: 1. Perform the first part of the FIWARE Overview where we elaborate on the intrisic nature of "Powered by FIWARE" (e.g., explain the vision about what a Powered by FIWARE app means relying on the very notion of context information management) - 15 mins 2. We stop and we showcase a very simple example application where main components of FIWARE have been used and give a "flavour" about how a "Powered by FIWARE" solution may look like - 15 mins 3. We continue with the presentation and finish the overview - 15 mins 4. We come with another hands-on session where we explain how to deploy and configure your first context broker - 15 mins 5. We start explaining FIWARE NGSI and elaborate on basic query and update functionality - 20 mins 6. We come with some example application relying on some Orion Context Broker instance and encourage attendees to perform their first queries on the Orion Context Broker instance - 15 mins 7. We continue explaining FIWARE NGSI elaborating on advanced query (e.g, geo query) functionalities - 20 mins 8. We make a presentation accompanied by a demo of an application developed by a startup/SME that makes a rather nice use of the Orion Context Broker, particularly usage of geo-queries and shows some code - 15 min 9. We end explaining FIWARE NGSI, elaborating on advanced notification features and roadmap - 20 mins 10. We run a session where some startup/SME explains how they incorporated notifications in their application and shows some code - 15 min I hope you see my point. The idea is not doing any 20 mins of the theory without stopping and running some demo, ideally showing some bits of code, or doing some easy exercise. We may run longer, but the contents will be much more dynamic, less tedious. The kind of demos you are proposing can be used for this purpose. We just need to go with a complete agenda where we perform this jumps from theory to practice. At the time of designing the agenda, we may use as format a table, where in the first column we elaborate on the learning "object" we wanna cover and in the second column we list the "show me the code" or "learn by example" speeches that will accompany that learning object. slot duration item who duration item who 09:00 - 10:00 30 mins FIWARE Overview Juanjo Hierro 15 mins Showcase of CityGo application Clara Pezuela 15 mins Installing the Orion Context Broker Joaquin Salvachúa 10:00 - 11:45 60 mins Orion FIWARE Context Broker / FIWARE NGSI José Manuel Cantera 15 mins Performing your first queries on an Orion Context Broker whoever 15 mins Find the buses in your city (demo on geo-queries) startup/SME A 15 mins Notify me when it happens (demo on notification features) startup/SME B Hope it helps. Cheers, Juanjo On 10/07/2017 17:00, Pezuela, Clara wrote: > Hola, > Te lo pongo todo en inglés por si luego hay que reutilizar contenido J > Saludos > For the Developers Track: > > * After some of the training about FIWARE core components, some > practical applications can be shown. As summit is hosted in > Málaga, we propose couple of tools based on Málaga open data and > infrastructure that provide services to Málaga citizens and > companies. A front-end aggregating and centralizing city services > will be shown, and then one of the services provided through this > front-end for monitoring the transportation of citizens across the > city. A mobile app for citizens to calculate best routes will be > also demonstrated (this can be also used by summit attendees for > their mobility in the city). This will be the storyline, and for > each, FIWARE components that have been used will be shown, > teaching the attendees how the integration and development were > done and telling lessons learned from the process. They could then > ask questions about the experience or doubts about the explained > architectures and demonstrations. We would like also to propose a > kind of questionnaire (online most sure) to collect feedback from > attendees (mainly developers) about how they feel after looking at > the practical session (technically speaking of course J) > > (FYI, la app de movilidad (CityGO) se inició en las showcases de > Fi-core, y ahora se está evolucionando como parte de un proyecto con > el CDTI, e integrada con el trabajo que se está haciendo en CEDUS para > integrar en un front-end común todos los verticales para Málaga, entre > ellos el CityGO). > For the FIWARE Challenge: > > * Here, if I understood correctly, the idea is to launch a challenge > beforehand the event, when it was launched and then leave until > the event for resolving it and during the event making the > selection and awarding the winner, no? In this case, maybe we > could propose a challenge to provide some service by taking the > open data published by Malaga in their portal, by using at least 2 > GEs from FIWARE and integrate it in the city front-end above > mentioned. We could show the challenges after the practical show > and announce the winner. Of course we will provide the > specifications for that. If you refer to another type of > Challenge, please let me know. > > What do you think? > Clara Pezuela > Head of IT Market > Research and Innovation Group > _ARI booklet_ > <https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf> > Atos Spain SA > _Clara.pezuela at atos.net_ <mailto:Clara.pezuela at atos.net> > +34 675 62 9974 > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy > it. > As its integrity cannot be secured on the Internet, the Atos group > liability cannot be triggered for the message content. Although the > sender endeavors to maintain a computer virus-free network, the sender > does not warrant that this transmission is virus-free and will not be > liable for any damages resulting from any virus transmitted. > > Este mensaje y los ficheros adjuntos pueden contener información > confidencial destinada solamente a la(s) persona(s) mencionadas > anteriormente y pueden estar protegidos por secreto profesional. > Si usted recibe este correo electrónico por error, gracias por > informar inmediatamente al remitente y destruir el mensaje. > Al no estar asegurada la integridad de este mensaje sobre la red, Atos > no se hace responsable por su contenido. Su contenido no constituye > ningún compromiso para el grupo Atos, salvo ratificación escrita por > ambas partes. > Aunque se esfuerza al máximo por mantener su red libre de virus, el > emisor no puede garantizar nada al respecto y no será responsable de > cualesquiera daños que puedan resultar de una transmisión de virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170711/91cafca6/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4410 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170711/91cafca6/attachment-0001.jpe>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy