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 <juanjose.hierro at telefonica.com> 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 <juanjose.hierro at telefonica.com> > An: fiware-chapter-architects at lists.fi-ware.org > <fiware-chapter-architects at lists.fi-ware.org>, > fiware-chapter-leaders 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 >
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy