From philipp.slusallek at dfki.de Fri Jun 5 14:15:59 2015 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Fri, 05 Jun 2015 14:15:59 +0200 Subject: [Fiware-pois] Fwd: [Fiware-chapter-leaders] Next FIWARE Architects meetings In-Reply-To: <555EF4D5.7040500@telefonica.com> References: <555EF4D5.7040500@telefonica.com> Message-ID: <557192FF.6090909@dfki.de> Hi, This is a reminder that next Monday we wanted to continue the discussion on POIs and collaboration with the ContextBroker. I hope this is still valid after the recent move of meetings. Are we actually starting at 9:30h? (usually the architecture call is 10:30-12:30, no?). Both is fine with me next week, BTW. As you know, we have set up a document for comparing the current and proposed approach with NGSI: https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit# We got valuable input from the WebUI chapter as well as from FIcontent -- but apparently nothing from the CB side, as far as I can tell. There is still some time to read the proposals and add you comments until Monday morning. BTW, we have also added a section of possible future direction as wel las linked the documents about the possible evolution of POIs to this document. Best, Philipp -------- Weitergeleitete Nachricht -------- Betreff: [Fiware-chapter-leaders] Next FIWARE Architects meetings Datum: Fri, 22 May 2015 11:20:21 +0200 Von: Juanjo Hierro An: fiware-chapter-architects at lists.fi-ware.org , fiware-chapter-leaders at lists.fi-ware.org Dear FIWARE architects, This is to summarize the topics that will be covered in our next FIWARE Architecs calls (monday mornings, from 09:30am to 11:00am CET): * Monday May 25th: revision of architecture to support federated user account management on the FIWARE Lab * Monday June 1st: support of dockers in FIWARE Architecture * Monday June 8th: 2nd meeting about POIs Feel free to invite anyone you believe can add value to the discussions. FIWARE chapter leaders are of course welcome to join. Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telef??nica email: juanjose.hierro at telefonica.com twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 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 -- ------------------------------------------------------------------------- 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: From fermin.galanmarquez at telefonica.com Fri Jun 5 14:20:22 2015 From: fermin.galanmarquez at telefonica.com (=?windows-1252?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Fri, 5 Jun 2015 14:20:22 +0200 Subject: [Fiware-pois] Fwd: [Fiware-chapter-leaders] Next FIWARE Architects meetings In-Reply-To: <557192FF.6090909@dfki.de> References: <555EF4D5.7040500@telefonica.com> <557192FF.6090909@dfki.de> Message-ID: <55719406.10902@telefonica.com> Dear Philipp, Unfortunately, I'm not available for this meeting on Monday morning. Regarding CB, we have a first draft of contributions, but we are now discussing internally before to include it in the google doc. Best regards, ------ Ferm?n El 05/06/2015 a las 14:15, Philipp Slusallek escribi?: Hi, This is a reminder that next Monday we wanted to continue the discussion on POIs and collaboration with the ContextBroker. I hope this is still valid after the recent move of meetings. Are we actually starting at 9:30h? (usually the architecture call is 10:30-12:30, no?). Both is fine with me next week, BTW. As you know, we have set up a document for comparing the current and proposed approach with NGSI: https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit# We got valuable input from the WebUI chapter as well as from FIcontent -- but apparently nothing from the CB side, as far as I can tell. There is still some time to read the proposals and add you comments until Monday morning. BTW, we have also added a section of possible future direction as wel las linked the documents about the possible evolution of POIs to this document. Best, Philipp -------- Weitergeleitete Nachricht -------- Betreff: [Fiware-chapter-leaders] Next FIWARE Architects meetings Datum: Fri, 22 May 2015 11:20:21 +0200 Von: Juanjo Hierro An: fiware-chapter-architects at lists.fi-ware.org , fiware-chapter-leaders at lists.fi-ware.org Dear FIWARE architects, This is to summarize the topics that will be covered in our next FIWARE Architecs calls (monday mornings, from 09:30am to 11:00am CET): * Monday May 25th: revision of architecture to support federated user account management on the FIWARE Lab * Monday June 1st: support of dockers in FIWARE Architecture * Monday June 8th: 2nd meeting about POIs Feel free to invite anyone you believe can add value to the discussions. FIWARE chapter leaders are of course welcome to join. Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telef??nica email: juanjose.hierro at telefonica.com twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 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-pois mailing list Fiware-pois at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-pois ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From philipp.slusallek at dfki.de Fri Jun 5 14:40:07 2015 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Fri, 05 Jun 2015 14:40:07 +0200 Subject: [Fiware-pois] Fwd: [Fiware-chapter-leaders] Next FIWARE Architects meetings In-Reply-To: <55719406.10902@telefonica.com> References: <555EF4D5.7040500@telefonica.com> <557192FF.6090909@dfki.de> <55719406.10902@telefonica.com> Message-ID: <557198A7.4030909@dfki.de> Hi, Too bad, I hope someone else from the CB team will still be able to attend? Would it be possible to get your contributions before Monday's meeting, so we can base our discussion on top of that and thus be more efficient? Thanks, Philipp Am 05.06.2015 um 14:20 schrieb Ferm?n Gal?n M?rquez: > Dear Philipp, > > Unfortunately, I'm not available for this meeting on Monday morning. > > Regarding CB, we have a first draft of contributions, but we are now > discussing internally before to include it in the google doc. > > Best regards, > > ------ > Ferm?n > > El 05/06/2015 a las 14:15, Philipp Slusallek escribi?: >> Hi, >> >> This is a reminder that next Monday we wanted to continue the discussion >> on POIs and collaboration with the ContextBroker. >> >> I hope this is still valid after the recent move of meetings. Are we >> actually starting at 9:30h? (usually the architecture call is >> 10:30-12:30, no?). Both is fine with me next week, BTW. >> >> As you know, we have set up a document for comparing the current and >> proposed approach with NGSI: >> https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit# >> >> We got valuable input from the WebUI chapter as well as from FIcontent >> -- but apparently nothing from the CB side, as far as I can tell. There >> is still some time to read the proposals and add you comments until >> Monday morning. >> >> BTW, we have also added a section of possible future direction as wel >> las linked the documents about the possible evolution of POIs to this >> document. >> >> >> Best, >> >> Philipp >> >> >> >> -------- Weitergeleitete Nachricht -------- >> Betreff: [Fiware-chapter-leaders] Next FIWARE Architects meetings >> Datum: Fri, 22 May 2015 11:20:21 +0200 >> Von: Juanjo Hierro >> An: fiware-chapter-architects at lists.fi-ware.org >> , >> fiware-chapter-leaders at lists.fi-ware.org >> >> >> >> >> Dear FIWARE architects, >> >> This is to summarize the topics that will be covered in our next >> FIWARE Architecs calls (monday mornings, from 09:30am to 11:00am CET): >> >> * Monday May 25th: revision of architecture to support federated user >> account management on the FIWARE Lab >> * Monday June 1st: support of dockers in FIWARE Architecture >> * Monday June 8th: 2nd meeting about POIs >> >> Feel free to invite anyone you believe can add value to the >> discussions. FIWARE chapter leaders are of course welcome to join. >> >> Best regards, >> >> -- Juanjo >> >> ______________________________________________________ >> >> Coordinator and Chief Architect, FIWARE platform >> CTO Industrial IoT, Telef??nica >> >> email: juanjose.hierro at telefonica.com >> twitter: @JuanjoHierro >> >> You can follow FIWARE at: >> website: http://www.fiware.org >> twitter: @FIWARE >> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 >> 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-pois mailing list >> Fiware-pois at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-pois > > > ------------------------------------------------------------------------ > > 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: From juanjose.hierro at telefonica.com Mon Jun 8 08:52:24 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 8 Jun 2015 08:52:24 +0200 Subject: [Fiware-pois] [Fiware-chapter-architects] Fwd: [Fiware-chapter-leaders] Next FIWARE Architects meetings In-Reply-To: <557198A7.4030909@dfki.de> References: <555EF4D5.7040500@telefonica.com> <557192FF.6090909@dfki.de> <55719406.10902@telefonica.com> <557198A7.4030909@dfki.de> Message-ID: <55753BA8.1060308@telefonica.com> An HTML attachment was scrubbed... URL: From toni at playsign.net Mon Jun 8 09:35:24 2015 From: toni at playsign.net (Toni Alatalo) Date: Mon, 8 Jun 2015 10:35:24 +0300 Subject: [Fiware-pois] [Fiware-chapter-architects] Fwd: [Fiware-chapter-leaders] Next FIWARE Architects meetings In-Reply-To: <55753BA8.1060308@telefonica.com> References: <555EF4D5.7040500@telefonica.com> <557192FF.6090909@dfki.de> <55719406.10902@telefonica.com> <557198A7.4030909@dfki.de> <55753BA8.1060308@telefonica.com> Message-ID: Hi - there seems to be an 'x' in the document for Fermin now, perhaps that is old information though if he can't come now? I'm in a seminar (ubicomp, open data & 3d web for smart cities) and need to give a presentation in 20mins .. will check after the talk etc. if have a chance. Timo Mukari seems to be here too, I figure someone from CIE is joining at least. (he, Ari or both I guess). In case I can't join, wanted to note here: >From the comments and discussion in the doc, it seems that there is good progress on the NGSI/CB side in V2 for simple HTTP queries which start to look very similar to the POI queries. Whether that means that it would make actually sense to use CB (or that API otherwise) for POIs, I don't know -- looking forward to learning more based on how the discussions go by folks more involved in this. One question, possibly due to my ignorance: I think Fermin noted in the previous call how the POI with the schema is like a vocabulary, for a certain application area. Whereas CB at the base is a generic entity-attribute system. So is there some mechanism / practice you have with NGSI to introduce schemas or some vocabularies otherwise? To define data types, 'attribute bags' kind of -- is it ever needed? I'm not sure how the POI folks see their usages, IIRC someone mentioned validation in the prev call? In the 3DUI & Scene synchronization side, where we also have a generic entity-attribute system, there are many pre-defined so-called components (a group of attributes for a particular purpose, basically). The POI component architecture was designed following that. One usage for those in the 3D apps there is autogenerated GUIs (in the 'interface designer' GE). So for example when an entity has position (in the placeable component), the GUI editor for configing entities shows the correct type of editor for changing the position automatically (using attribute metadata actually). Other point here is that NGSI/CB is also not really a generic entity-attribute pubsub (like I've perhaps mistakingly thought of it earlier) as it also embeds some kind of knowledge about geopositions, spatial queries and such -- which makes of course a lot of sense for IoT. I think that's something for me to study more: how are places and spaces conceptualized in NGSI/CB .. and see if we're already compatible enough there for example with the synchronization GE (where we already have optimized websocket protocol for subscriptions and many things for dealing with spatiality). ~Toni ~Toni On Mon, Jun 8, 2015 at 9:52 AM, Juanjo Hierro wrote: > Fermin, > > Aren't you going to attend the FIWARE Architects meeting? Who is going > to replace you at the confcall? > > Input to the document gathering pros and cons of using the FIWARE NGSI API > as POI server API were incorporated as far as I see: > > https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit?usp=sharing > > > ... but we need to carry out the discussion with involvement of someone > representing the position regarding adoption of FIWARE NGSI API as POI > server API. > > As a reminder for the rest, the confcall was scheduled from 10:30am to > 12:30pm CET. > > I have produced a shared google doc to be used as minutes for the meeting > in case it gets confirmed (pending of confirmation of attendance from > someone representing the position pushing for adoption of FIWARE NGSI as POI > server API): > > https://docs.google.com/document/d/1egdqwlXtICfmDOXyBNTMxHBW03REP752PmtxvzDtHk8/edit?usp=sharing > > > Can people attending the previous meeting on POI discussion add their > names to the list of attendees listed in the minutes? It would be useful. > A reminder about where they were: > > https://docs.google.com/document/d/1TmiF1skp5zZib0gacZ4pNzx8XAIQVcoku-th947rHrA/edit?usp=sharing > > > Best regards, > > -- Juanjo > > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telef?nica > > email: juanjose.hierro at telefonica.com > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: http://www.fiware.org > twitter: @FIWARE > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > On 05/06/15 14:40, Philipp Slusallek wrote: > > Hi, > > Too bad, I hope someone else from the CB team will still be able to attend? > > Would it be possible to get your contributions before Monday's meeting, > so we can base our discussion on top of that and thus be more efficient? > > Thanks, > > Philipp > > Am 05.06.2015 um 14:20 schrieb Ferm?n Gal?n M?rquez: > > Dear Philipp, > > Unfortunately, I'm not available for this meeting on Monday morning. > > Regarding CB, we have a first draft of contributions, but we are now > discussing internally before to include it in the google doc. > > Best regards, > > ------ > Ferm?n > > El 05/06/2015 a las 14:15, Philipp Slusallek escribi?: > > Hi, > > This is a reminder that next Monday we wanted to continue the discussion > on POIs and collaboration with the ContextBroker. > > I hope this is still valid after the recent move of meetings. Are we > actually starting at 9:30h? (usually the architecture call is > 10:30-12:30, no?). Both is fine with me next week, BTW. > > As you know, we have set up a document for comparing the current and > proposed approach with NGSI: > https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit# > > We got valuable input from the WebUI chapter as well as from FIcontent > -- but apparently nothing from the CB side, as far as I can tell. There > is still some time to read the proposals and add you comments until > Monday morning. > > BTW, we have also added a section of possible future direction as wel > las linked the documents about the possible evolution of POIs to this > document. > > > Best, > > Philipp > > > > -------- Weitergeleitete Nachricht -------- > Betreff: [Fiware-chapter-leaders] Next FIWARE Architects meetings > Datum: Fri, 22 May 2015 11:20:21 +0200 > Von: Juanjo Hierro > An: fiware-chapter-architects at lists.fi-ware.org > , > fiware-chapter-leaders at lists.fi-ware.org > > > > > Dear FIWARE architects, > > This is to summarize the topics that will be covered in our next > FIWARE Architecs calls (monday mornings, from 09:30am to 11:00am CET): > > * Monday May 25th: revision of architecture to support federated user > account management on the FIWARE Lab > * Monday June 1st: support of dockers in FIWARE Architecture > * Monday June 8th: 2nd meeting about POIs > > Feel free to invite anyone you believe can add value to the > discussions. FIWARE chapter leaders are of course welcome to join. > > Best regards, > > -- Juanjo > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telef??nica > > email: juanjose.hierro at telefonica.com > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: http://www.fiware.org > twitter: @FIWARE > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > 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-pois mailing list > Fiware-pois at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-pois > > ------------------------------------------------------------------------ > > 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 > > _______________________________________________ > Fiware-pois mailing list > Fiware-pois at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-pois > From fermin.galanmarquez at telefonica.com Mon Jun 8 10:11:47 2015 From: fermin.galanmarquez at telefonica.com (=?windows-1252?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Mon, 8 Jun 2015 10:11:47 +0200 Subject: [Fiware-pois] [Fiware-chapter-architects] Fwd: [Fiware-chapter-leaders] Next FIWARE Architects meetings In-Reply-To: <55753BA8.1060308@telefonica.com> References: <555EF4D5.7040500@telefonica.com> <557192FF.6090909@dfki.de> <55719406.10902@telefonica.com> <557198A7.4030909@dfki.de> <55753BA8.1060308@telefonica.com> Message-ID: <55754E43.20307@telefonica.com> Hi, I can try to join at 10:30am but at some point of the morning around 11:00am I could need to leave the audio during an undefined time (I could try to make this time as shorter as possible, but I cannot know it advance how much it could take). Best regarrds, ------ Ferm?n El 08/06/2015 a las 8:52, Juanjo Hierro escribi?: Fermin, Aren't you going to attend the FIWARE Architects meeting? Who is going to replace you at the confcall? Input to the document gathering pros and cons of using the FIWARE NGSI API as POI server API were incorporated as far as I see: * https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit?usp=sharing ... but we need to carry out the discussion with involvement of someone representing the position regarding adoption of FIWARE NGSI API as POI server API. As a reminder for the rest, the confcall was scheduled from 10:30am to 12:30pm CET. I have produced a shared google doc to be used as minutes for the meeting in case it gets confirmed (pending of confirmation of attendance from someone representing the position pushing for adoption of FIWARE NGSI as POI server API): * https://docs.google.com/document/d/1egdqwlXtICfmDOXyBNTMxHBW03REP752PmtxvzDtHk8/edit?usp=sharing Can people attending the previous meeting on POI discussion add their names to the list of attendees listed in the minutes? It would be useful. A reminder about where they were: * https://docs.google.com/document/d/1TmiF1skp5zZib0gacZ4pNzx8XAIQVcoku-th947rHrA/edit?usp=sharing Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telef?nica email: juanjose.hierro at telefonica.com twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 05/06/15 14:40, Philipp Slusallek wrote: Hi, Too bad, I hope someone else from the CB team will still be able to attend? Would it be possible to get your contributions before Monday's meeting, so we can base our discussion on top of that and thus be more efficient? Thanks, Philipp Am 05.06.2015 um 14:20 schrieb Ferm?n Gal?n M?rquez: Dear Philipp, Unfortunately, I'm not available for this meeting on Monday morning. Regarding CB, we have a first draft of contributions, but we are now discussing internally before to include it in the google doc. Best regards, ------ Ferm?n El 05/06/2015 a las 14:15, Philipp Slusallek escribi?: Hi, This is a reminder that next Monday we wanted to continue the discussion on POIs and collaboration with the ContextBroker. I hope this is still valid after the recent move of meetings. Are we actually starting at 9:30h? (usually the architecture call is 10:30-12:30, no?). Both is fine with me next week, BTW. As you know, we have set up a document for comparing the current and proposed approach with NGSI: https://docs.google.com/document/d/1771CUAemUvfuX1_oqK6eKkzRdDn5cW7LSsbE1JB2WZ0/edit# We got valuable input from the WebUI chapter as well as from FIcontent -- but apparently nothing from the CB side, as far as I can tell. There is still some time to read the proposals and add you comments until Monday morning. BTW, we have also added a section of possible future direction as wel las linked the documents about the possible evolution of POIs to this document. Best, Philipp -------- Weitergeleitete Nachricht -------- Betreff: [Fiware-chapter-leaders] Next FIWARE Architects meetings Datum: Fri, 22 May 2015 11:20:21 +0200 Von: Juanjo Hierro An: fiware-chapter-architects at lists.fi-ware.org , fiware-chapter-leaders at lists.fi-ware.org Dear FIWARE architects, This is to summarize the topics that will be covered in our next FIWARE Architecs calls (monday mornings, from 09:30am to 11:00am CET): * Monday May 25th: revision of architecture to support federated user account management on the FIWARE Lab * Monday June 1st: support of dockers in FIWARE Architecture * Monday June 8th: 2nd meeting about POIs Feel free to invite anyone you believe can add value to the discussions. FIWARE chapter leaders are of course welcome to join. Best regards, -- Juanjo ______________________________________________________ Coordinator and Chief Architect, FIWARE platform CTO Industrial IoT, Telef??nica email: juanjose.hierro at telefonica.com twitter: @JuanjoHierro You can follow FIWARE at: website: http://www.fiware.org twitter: @FIWARE facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 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-pois mailing list Fiware-pois at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-pois ------------------------------------------------------------------------ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin.galanmarquez at telefonica.com Wed Jun 10 11:30:21 2015 From: fermin.galanmarquez at telefonica.com (=?windows-1252?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Wed, 10 Jun 2015 11:30:21 +0200 Subject: [Fiware-pois] NGSIv2 specification Message-ID: <557803AD.2070602@telefonica.com> Hi, Please, find the draft of the NGSI v2 specification we are preparing in the following URL: http://docs.fiwarengsiv2.apiary.io Apart from the Apiary documentation, some of the operations have a textual specification with more detail, published as github.com issues (the index for reaching the textual specification from the operation type is at https://docs.google.com/spreadsheets/d/1f4m624nmO3jRjNalGE11lFLQixnfCENMV6dc54wUCCg/edit#gid=50130961 tab "NGSI API v2 operations"). At the end, this textual specification would be probably merged into Apiary to have all the information in the same place. I would like to stress that it is a draft. That means, that although the "skeleton" of the operations is defined, not all the details are closed and both Apiary and textual specification are evolving regularly (even in a daily basics). Probably in a couple of weeks the draft would be more "stable" and complete. You can monitor what operations have finished the ongoing review looking into the aforementioned https://docs.google.com/spreadsheets/d/1f4m624nmO3jRjNalGE11lFLQixnfCENMV6dc54wUCCg/edit#gid=50130961 tab "NGSI API v2 operations". This covers the "AP on Fermin to provide link to V2 draft specifications" (https://docs.google.com/document/d/1egdqwlXtICfmDOXyBNTMxHBW03REP752PmtxvzDtHk8/edit#). For completing the other " AP on CB team to match requirements to NGSI v2 capabilities" on my side I'd need first the set of requirements. Is that information already published, please? Any feedback is welcome. Thanks! Best regards, ------ Ferm?n ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From philipp.slusallek at dfki.de Wed Jun 10 21:33:53 2015 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Wed, 10 Jun 2015 21:33:53 +0200 Subject: [Fiware-pois] NGSIv2 specification In-Reply-To: <557803AD.2070602@telefonica.com> References: <557803AD.2070602@telefonica.com> Message-ID: <55789121.40901@dfki.de> Hi, Thanks alot. Will have a look in the next days. Best, Philipp Am 10.06.2015 um 11:30 schrieb Ferm?n Gal?n M?rquez: > Hi, > > Please, find the draft of the NGSI v2 specification we are preparing in > the following URL: > > http://docs.fiwarengsiv2.apiary.io > > Apart from the Apiary documentation, some of the operations have a > textual specification with more detail, published as github.com issues > (the index for reaching the textual specification from the operation > type is at > https://docs.google.com/spreadsheets/d/1f4m624nmO3jRjNalGE11lFLQixnfCENMV6dc54wUCCg/edit#gid=50130961 > tab "NGSI API v2 operations"). At the end, this textual specification > would be probably merged into Apiary to have all the information in the > same place. > > I would like to stress that it is a draft. That means, that although the > "skeleton" of the operations is defined, not all the details are closed > and both Apiary and textual specification are evolving regularly (even > in a daily basics). Probably in a couple of weeks the draft would be > more "stable" and complete. You can monitor what operations have > finished the ongoing review looking into the aforementioned > https://docs.google.com/spreadsheets/d/1f4m624nmO3jRjNalGE11lFLQixnfCENMV6dc54wUCCg/edit#gid=50130961 > tab "NGSI API v2 operations". > > This covers the "AP on Fermin to provide link to V2 draft > specifications" > (https://docs.google.com/document/d/1egdqwlXtICfmDOXyBNTMxHBW03REP752PmtxvzDtHk8/edit#). > For completing the other " AP on CB team to match requirements to NGSI > v2 capabilities" on my side I'd need first the set of requirements. Is > that information already published, please? > > Any feedback is welcome. Thanks! > > Best regards, > > ------ > Ferm?n > > ------------------------------------------------------------------------ > > 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-pois mailing list > Fiware-pois at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-pois > -- ------------------------------------------------------------------------- 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: From fermin.galanmarquez at telefonica.com Thu Jun 11 13:15:19 2015 From: fermin.galanmarquez at telefonica.com (=?windows-1252?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 11 Jun 2015 13:15:19 +0200 Subject: [Fiware-pois] NGSIv2 specification In-Reply-To: <557803AD.2070602@telefonica.com> References: <557803AD.2070602@telefonica.com> Message-ID: <55796DC7.2090107@telefonica.com> Hi, Just to tell you that we have moved the apiary specification "closer" to the Orion Context Broker repository, thus now it is available at: http://telefonicaid.github.io/fiware-orion/api/v2/ Best regards, ------ Ferm?n El 10/06/2015 a las 11:30, Ferm?n Gal?n M?rquez escribi?: Hi, Please, find the draft of the NGSI v2 specification we are preparing in the following URL: http://docs.fiwarengsiv2.apiary.io Apart from the Apiary documentation, some of the operations have a textual specification with more detail, published as github.com issues (the index for reaching the textual specification from the operation type is at https://docs.google.com/spreadsheets/d/1f4m624nmO3jRjNalGE11lFLQixnfCENMV6dc54wUCCg/edit#gid=50130961 tab "NGSI API v2 operations"). At the end, this textual specification would be probably merged into Apiary to have all the information in the same place. I would like to stress that it is a draft. That means, that although the "skeleton" of the operations is defined, not all the details are closed and both Apiary and textual specification are evolving regularly (even in a daily basics). Probably in a couple of weeks the draft would be more "stable" and complete. You can monitor what operations have finished the ongoing review looking into the aforementioned https://docs.google.com/spreadsheets/d/1f4m624nmO3jRjNalGE11lFLQixnfCENMV6dc54wUCCg/edit#gid=50130961 tab "NGSI API v2 operations". This covers the "AP on Fermin to provide link to V2 draft specifications" (https://docs.google.com/document/d/1egdqwlXtICfmDOXyBNTMxHBW03REP752PmtxvzDtHk8/edit#). For completing the other " AP on CB team to match requirements to NGSI v2 capabilities" on my side I'd need first the set of requirements. Is that information already published, please? Any feedback is welcome. Thanks! Best regards, ------ Ferm?n ________________________________ 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-pois mailing list Fiware-pois at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-pois ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.lemme at dfki.de Tue Jun 16 12:50:11 2015 From: stefan.lemme at dfki.de (Stefan Lemme) Date: Tue, 16 Jun 2015 12:50:11 +0200 Subject: [Fiware-pois] Requirements to POI API and Format Message-ID: <557FFF63.2000509@dfki.de> Dear all, we started to collect "Requirements to POI API and Format" in a Google Doc at https://goo.gl/OmHRoK I made a first pass and revisited the current 34 requirements. All POI group members are invited to * AP1 - add further requirements at https://goo.gl/OmHRoK#heading=h.kpno8vym0krr and * AP2 - review the current requirements as well as add further information, such as priority and description. Please feel free to add comments too. Philipp is invited to * AP3 - review the assignment of requirements to the three "aspects": API, data model/format, query interface/capabilities Technology providers are invited to * AP4 - explain how each requirement is met/not met by their proposal. The main course of collecting requirements will be closed on June 21st 2015. Please ensure to perform *AP[1..3] until end of this week*. The next call on the POI topic is scheduled on June 29th 2015. Hence, please ensure *AP4 *is performed *before June 26th*. In case of questions, don't hesitate to post to list. Best regards, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From fermin.galanmarquez at telefonica.com Thu Jun 18 12:32:26 2015 From: fermin.galanmarquez at telefonica.com (=?windows-1252?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 18 Jun 2015 12:32:26 +0200 Subject: [Fiware-pois] Requirements to POI API and Format In-Reply-To: <557FFF63.2000509@dfki.de> References: <557FFF63.2000509@dfki.de> Message-ID: <55829E3A.5000901@telefonica.com> Hi, I have done a first part in the document, adding information regarding how the requirements can be addressed using NGSIv2. A second pass will be done once AP[1..3] gets completed (in some cases a detailed description is needed to understand what is the requirement about). Thanks! Best regards, ------ Ferm?n El 16/06/2015 a las 12:50, Stefan Lemme escribi?: Dear all, we started to collect "Requirements to POI API and Format" in a Google Doc at https://goo.gl/OmHRoK I made a first pass and revisited the current 34 requirements. All POI group members are invited to * AP1 - add further requirements at https://goo.gl/OmHRoK#heading=h.kpno8vym0krr and * AP2 - review the current requirements as well as add further information, such as priority and description. Please feel free to add comments too. Philipp is invited to * AP3 - review the assignment of requirements to the three "aspects": API, data model/format, query interface/capabilities Technology providers are invited to * AP4 - explain how each requirement is met/not met by their proposal. The main course of collecting requirements will be closed on June 21st 2015. Please ensure to perform AP[1..3] until end of this week. The next call on the POI topic is scheduled on June 29th 2015. Hence, please ensure AP4 is performed before June 26th. In case of questions, don't hesitate to post to list. Best regards, Stefan _______________________________________________ Fiware-pois mailing list Fiware-pois at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-pois ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.lemme at dfki.de Wed Jun 24 09:01:02 2015 From: stefan.lemme at dfki.de (Stefan Lemme) Date: Wed, 24 Jun 2015 09:01:02 +0200 Subject: [Fiware-pois] Requirements to POI API and Format In-Reply-To: <557FFF63.2000509@dfki.de> References: <557FFF63.2000509@dfki.de> Message-ID: <558A55AE.8080006@dfki.de> Dear all, this is a reminder to *all POI group members* to contribute to *AP1, AP2, AP3*. Please address those issues as soon as possible. Best regards, Stefan On 6/16/2015 12:50 PM, Stefan Lemme wrote: > > Dear all, > > we started to collect "Requirements to POI API and Format" in a Google > Doc at https://goo.gl/OmHRoK > I made a first pass and revisited the current 34 requirements. > > All POI group members are invited to > > * AP1 - add further requirements at > https://goo.gl/OmHRoK#heading=h.kpno8vym0krr and > * AP2 - review the current requirements as well as add further > information, such as priority and description. > > Please feel free to add comments too. > > Philipp is invited to > > * AP3 - review the assignment of requirements to the three > "aspects": API, data model/format, query interface/capabilities > > Technology providers are invited to > > * AP4 - explain how each requirement is met/not met by their proposal. > > The main course of collecting requirements will be closed on June 21st > 2015. > Please ensure to perform *AP[1..3] until end of this week*. > > The next call on the POI topic is scheduled on June 29th 2015. > Hence, please ensure *AP4 *is performed *before June 26th*. > > In case of questions, don't hesitate to post to list. > > Best regards, > Stefan > > > > > _______________________________________________ > Fiware-pois mailing list > Fiware-pois at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-pois -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.lemme at dfki.de Mon Jun 29 16:46:58 2015 From: stefan.lemme at dfki.de (Stefan Lemme) Date: Mon, 29 Jun 2015 16:46:58 +0200 Subject: [Fiware-pois] Requirements to POI API and Format In-Reply-To: <558A55AE.8080006@dfki.de> References: <557FFF63.2000509@dfki.de> <558A55AE.8080006@dfki.de> Message-ID: <55915A62.8020500@dfki.de> Dear all, I made a pass over the requirements document at https://goo.gl/OmHRoK to address in particular AP1 and AP2. You are invited to perform any follow-up actions along those lines. Best regards, Stefan On 6/24/2015 9:01 AM, Stefan Lemme wrote: > > Dear all, > > this is a reminder to *all POI group members* to contribute to *AP1, > AP2, AP3*. > Please address those issues as soon as possible. > > Best regards, > Stefan > > > > On 6/16/2015 12:50 PM, Stefan Lemme wrote: >> >> Dear all, >> >> we started to collect "Requirements to POI API and Format" in a >> Google Doc at https://goo.gl/OmHRoK >> I made a first pass and revisited the current 34 requirements. >> >> All POI group members are invited to >> >> * AP1 - add further requirements at >> https://goo.gl/OmHRoK#heading=h.kpno8vym0krr and >> * AP2 - review the current requirements as well as add further >> information, such as priority and description. >> >> Please feel free to add comments too. >> >> Philipp is invited to >> >> * AP3 - review the assignment of requirements to the three >> "aspects": API, data model/format, query interface/capabilities >> >> Technology providers are invited to >> >> * AP4 - explain how each requirement is met/not met by their proposal. >> >> The main course of collecting requirements will be closed on June >> 21st 2015. >> Please ensure to perform *AP[1..3] until end of this week*. >> >> The next call on the POI topic is scheduled on June 29th 2015. >> Hence, please ensure *AP4 *is performed *before June 26th*. >> >> In case of questions, don't hesitate to post to list. >> >> Best regards, >> Stefan >> >> >> >> >> _______________________________________________ >> Fiware-pois mailing list >> Fiware-pois at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-pois > > > > _______________________________________________ > Fiware-pois mailing list > Fiware-pois at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-pois -------------- next part -------------- An HTML attachment was scrubbed... URL: