Hi, Sorry to respond so late. I suggest we pick up this topic again on Wednesday. We need to soon open the discussion with the rest of FIWARE (as promised) and should have a good position that. I fully agree with you analysis and potential questions here. I suggest that we put together a list of challenges with suggestions of how to proceed, each one could have a set of possible answers with pros/cons attached to them. I suggest we use Stefan's stuff to start with (but might have to reorganize it as just suggested). Maybe someone can already start putting something together for our call on Wed? On Wed we will have to do the Sprint planning as well. It would be good if everyone had created the Tickets for the next sprint already by Wed and assigned the planned tickets to the next sprint. We can then simply click through the http://backlog.fiware.org/enabler/overview pages to get a good overview of what each GE plans to be doing and discuss then briefly. If things are well prepared this should not take more than a few minutes per GE. Thanks, Philipp Am 22.01.2015 um 09:02 schrieb Toni Alatalo: > Thanks - was thinking about this now after the demo & talks yesterday, > just a note: > > In earlier talks Juanjo has asked why a separate e.g. POI server is > needed when / if the data could just be in CB. Your doc seems to > address that: > > * NGSI capabilities for discovering relevant POIs (querying, > filtering) have some weaknesses and are not very convenient > > * In contrast, discovery is a strength of the common POI API > > I bet one question from Juanjo & CB folks may be whether they(/we) > could improve the CB/NGSI interfaces -- as also their idea is exactly > to support good geospatial queries AFAIK (I only know the surface of > CB though, I guess it doesn't use anything like the geoserver with > postgresqls's spatial queries or so underneath). > > Anyhow, I suppose that's one of the main points when discussing on the > wider POI forum -- like we should (I'm not sure if i'm on that list > yet but can join if not). > > About the integration with sync server & use of websockets (or webrtc) > etc. it would be also nice to have some drafts docs / specs. There we > may even encounter the same question as with CB, whether it even > should have sync/websocket support (one person at ECFI suggested that > after learned that our scene sync in avatar demos didn't use CB to > sync the av positions :) > > About the data components etc -- that AFAIK e.g. Juanjo found clear > already to begin with, the data component specs .. he was just asking > why not just put the data to CB. He and Philipp discussed this again > in that one telco where I was mostly lurking before christmas (Philipp > asking why everything should be put to CB or so). > > I guess all that is worth thinking: CB, POI, I guess RVI and Sync GE > all are some kind of entity-attribute systems where clients want > updates about info and make spatial queries etc. Perhaps good if we > don't have 4 separate mechanisms for that in parallel? > > ~Toni > > On Wed, Jan 21, 2015 at 8:11 PM, Stefan Lemme <stefan.lemme at dfki.de> wrote: >> >> Dear all, >> >> as promised in today's WebUI call, I'll share the mock-up demo for the >> RVI-POI integration. >> Please refer to http://130.206.80.175/rvi-poi-concept/ as demonstrated this >> morning. >> >> These demos illustrate a usecase according to scenario 2 as described at >> http://goo.gl/mahI6x#heading=h.e6sunace1wr7 with a (mocked) instance of the >> POI-DP as well as a (mocked) instance of the RVI. >> The repository is available at https://github.com/stlemme/rvi-poi-concept >> >> Best regards, >> Stefan >> >> >> >> >> On 21.01.2015 08:35, Torsten Spieldenner wrote: >> >> Good morning! >> >> I have created the minutes for today's call here : >> https://docs.google.com/document/d/1ARzZntB78ZNMbTDqZaRgUZxK1HCDUHBty5oSd-iT1F4/edit# >> >> In addition to POI and Roadmap discussion, I have added a short point about >> the complete procedure of bundle deployment after having had some helpful >> discussion with Manuel, Henar and Davide via email at the end of last week. >> >> I will send the Hangout-Link shortly before the meeting starts. >> >> See you there! >> >> Torsten >> >> Am 21.01.15 um 7:09 AM schrieb Philipp Slusallek: >> >> Hi, >> >> Since I will have to attend a meeting at the University that could not >> be moved, Torsten will run the meeting today. The main topics should be >> to continue the discussion on POI (we need to define our position and >> open this to the rest of FIWARE soon) and the other topics in the table >> from Tiina. >> >> Also we should close the current sprint and define the topics for the next. >> >> >> Thanks, >> >> Philipp >> >> >> >> _______________________________________________ >> Fiware-webui mailing list >> Fiware-webui at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-webui >> >> >> -- >> Torsten Spieldenner, M.Sc. >> >> Tel.: +49 6 81 / 8 57 75 - 77 48 >> Fax.: +49 6 81 / 8 57 75 - 22 35 >> >> Internet: http://www.dfki.de/web/forschung/asr/ >> >> ------------------------------------------------------------- >> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany >> >> Geschaeftsfuehrung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> >> Amtsgericht Kaiserslautern, HRB 2313 >> ------------------------------------------------------------- >> >> >> -- >> ******************************************************** >> Stefan Lemme >> >> DFKI GmbH >> Agenten und Simulierte Realität >> Campus, Geb. D 3 4, Raum 0.75 >> 66123 Saarbrücken >> >> Tel.: +49 (0) 681 / 85775 – 5391 >> Fax: +49 (0) 681 / 85775 – 2235 >> http://www.dfki.de/web >> ******************************************************** >> Deutsches Forschungszentrum für Künstliche Intelligenz GmbH >> Trippstadter Straße 122 >> D-67663 Kaiserslautern, Germany >> >> Geschaeftsfü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/ >> ******************************************************** >> >> >> >> >> >> ******************************************************** >> Stefan Lemme >> >> DFKI GmbH >> Agents and Simulated Reality >> Campus, Build. D 3 4, room 0.75 >> D-66123 Saarbruecken >> Germany >> >> Phone: +49 (0) 681 / 85775 – 5391 >> Fax: +49 (0) 681 / 85775 – 2235 >> http://www.dfki.de/web >> ******************************************************** >> German Research Center for Artificial Intelligence >> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany >> >> Management Board: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Chairman) >> Dr. Walter Olthoff >> >> Chairman of the Supervisory Board: >> Prof. Dr. h.c. Hans A. Aukes >> >> Amtsgericht Kaiserslautern, HRB 2313 >> ******************************************************** >> >> >> _______________________________________________ >> Fiware-webui mailing list >> Fiware-webui at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-webui >> > _______________________________________________ > Fiware-webui mailing list > Fiware-webui at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-webui > -- ------------------------------------------------------------------------- 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-webui/attachments/20150202/ae3f55f4/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy