[Fiware-webui] Fwd: Re: [Fiware-technical-committee] NGSI-v2 in WebUI

[Philipp Slusallek]

[Not sure this got send before, so to be sure, I send it again]

HI all,

See the email below for Juanjos suggestions for the POI GE regarding the
POI GE.

I have added the topic to the agenda as well.

Best,

    Philipp


-------- Weitergeleitete Nachricht --------
Betreff: 	Re: [Fiware-technical-committee] NGSI-v2 in WebUI
Datum: 	Tue, 8 Mar 2016 07:54:00 +0100
Von: 	Juanjo Hierro <juanjose.hierro at telefonica.com>
An: 	fiware-technical-committee at lists.fiware.org



Dear Philipp,

  Very nice indeed!  Note that discussion about the incorporation of the
ability to use JSON-LD in NGSI v2 is evolving in a promising way.    I
don't know to what extend support to JSON-LD will end being part of the
final NGSI v2 specifications or if we will end up generating NGSI v3
(I'm more in favor of keeping NGSI v2 in draft and close it with the
support to JSON-LD if we manage to solve of the issues regarding support
of JSON-LD during March-April) but certainly it will be there in NGSI specs.

  As always mentioned, I believe that the right roadmap of the POI
server would be that of making it be a FIWARE NGSI context provider.  
Furthermore, I believe that we should specify that POI servers in the
Web UI chapter Reference Architecture are just that.   Wouldn't it make
things more easy to the architects we want to convince about using
FIWARE overall and a way to push for the closer integration of the
chapter with the rest of the FIWARE Architecture?  I think so.

  A separate but relevant discussion is the one about the open source
reference implementation of the POI server.   There I believe we have to
question ourselves if it is worth keeping a concrete open source
reference implementation of the POI server (again, I insist, working as
FIWARE NGSI context provider) or, since we would be specifying that POI
servers are FIWARE NGSI Context Providers within the Web UI architecture
specs, just propose the Orion Context Broker as an open source reference
implementation for it.   Having a specific open source reference
implementation of the POI server would only make sense IMHO if we
determine that, for whatever reason, the way it could be implemented is
definitively more efficient/scalable than the way it would be
implemented with Orion (because, for instance, it is fine to use another
very specific database/storage technology for POI information).   This,
I don't know and I would like to hear Philipp's/Torsten's opinions.  
Maybe this together with the discussion about the architecture specs
should be a topic for the next FIWARE TC?

  But again, let's not mix the discussion between architecture specs and
open source reference implementation of the POI server.

  If it were a matter of control (i.e., DFKI or anyone else wishes to
keep control of this component and be able to be self-sustainable in
terms of support, which is something I rather understand) I believe that
joining the Orion development team makes more sense in the longer
term.   After all ... this is open source!   In the ideal situation, the
Orion Context Broker would be an component many organizations share
ownership about and have knowledge regarding support.  That woud allow
that DFKI be part of the dev team behind Orion and can act as first
evangelist/first-contact regarding NGSI and Orion at W3C, OGC, for example.

  Cheers,

-- 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 08/03/16 07:22, Philipp Slusallek wrote:
> Hi Juanjo,
>
> You yesterday asked about the status of NGSIv2 within WebUI. I am happy
> to report that the planned connection between our Sync GE implementation
> (FiVES) and ContextBroker is actually already using NGSIv2 as Torsten
> reports:
>
>> I am actually implementing the NGSI-v2 specification, as also listed here:
>> <http://telefonicaid.github.io/fiware-orion/api/v2/cookbook/>http://telefonicaid.github.io/fiware-orion/api/v2/cookbook/
>>
>> In the first step, until end of the Release 5.2, I will focus on the
>> client side, i.e. wrapping the interactions described in the cookbook
>> such that FiVES can send requests to an NGSIv2 endpoint (e.g. Context
>> Broker), and handle the response. I plan to extend this in a future step
>> to have FiVES also handle external requests, and send the response to
>> these requests in the format as specified in the cookbook.
>>
>> I am testing the current implementation against a Context Broker
>> instance that I have launched in Lab, and that indeed supports NGSIv2 in
>> the version that is specified in above cookbook.
> We will discuss the next steps regarding the POI GE in our call tomorrow.
>
> We are also analysing the JSON-LD aspects right now, discuss how this
> relates to what we are doing in our ARVIDA project, and how we could
> contribute from our work there. This work, however, will take still a
> bit longer.
>
>
> Best,
>
> 	Philipp
> --
>
> -------------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------------
>
>
>
>
> _______________________________________________
> Fiware-technical-committee mailing list
> Fiware-technical-committee at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-technical-committee


------------------------------------------------------------------------

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 --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-webui/attachments/20160313/29c93e17/attachment.html>
-------------- next part --------------
_______________________________________________
Fiware-technical-committee mailing list
Fiware-technical-committee at lists.fiware.org
https://lists.fiware.org/listinfo/fiware-technical-committee


-------------- 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/20160313/29c93e17/attachment.vcf>