[Fiware-miwi] miwi GE infos (Fwd: [Fiware] QUITE IMPORTANT AND URGENT: RE: GEs to discuss in the review meeting)

Christof Marti mach at zhaw.ch
Mon Dec 16 18:05:26 CET 2013


Dear WP13 GE owners and partners

Sorry for coming back to you so late.
It was not exactly clear how the questions will be addressed at the review meeting on Wednesday.
I joined now the rehearsal meeting in Brussels (after an traveling for 7h because of delayed and missed flights), where we prepare the content for the review. 
After todays discussion, the structure is more clear now.

I will present the status of WP13 and all its GEs in a very short slot (max 5 min.)
Therefore I would like to have 1 slide with a short overview per GE, in table-form with the following fields:
(these should only relate to the FI-WARE GEis features / not commercial additions)
GE-Name: generic name of the GE
GEI-Name: name of the specific implementation
Partner(s) involved:
Terms&Conditions: (Exact type of license for the GEi: commercial xxx, …, Apache 2, MIT, GPLv2,.…)
Status (Open API): now (not avail yet, early draft, draft, preliminary, final), reason why and why available.
Current status: What is available at this moment
What’s available in M33 (R3.2): 2-3 major features (or full functionality)
What’s available in M36 (R3.3): additional features (or full functionality)
Planned to be available in FI-LAB? yes/no (how: blue-print, vm image, global instance, demo app)
Demo-Links
To add this I prepared a Google Spreadsheet. Please complete it for your GE.
https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdEhYRnVwN3lzcHF1dFU3elh0R2ZTd1E#gid=0
(I will then see, if I can compact and reduce the amount of data, columns, … for the slide)

I will add a summary slide of the WP13 status at all:
Common points, OpenSpecification, Manuals, deliverables, …
(I also have a Word version of the OpenSpecification with me)

Then I would like to prepare 1 slide per partner where he can elaborate on
Examination plans
Dissemination activities (executed, planned)
Other comments (planned usage of UC-projects, reasons why something might get delayed, …)
Not sure if it will be used, but in case there are questions I can select the slide and show it.
Please use the attached template for your slide.

I saw some of you sent already some content. It’s fastest if you add it to 

Deadline for all of the above is: Tomorrow Tuesday noon (12:00)
(the earlier the better, because I also have to put it together to a nice presentation)

Thanks for your support.

Best regards
Christof
----
InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch
Institut of Applied Information Technology - InIT
Zurich University of Applied Sciences - ZHAW
School of Engineering 
Phone: +41 58 934 70 63
Skype: christof-marti

Am 15.12.2013 um 14:48 schrieb Philipp Slusallek <Philipp.Slusallek at dfki.de>:

> Hi all,
> 
> Am 15.12.2013 12:01, schrieb Jarkko Vatjus-Anttila:
>> Please correct me now if I am wrong, but all the requested information
>> is already available!
> 
> Yes and No. Here is my view again in some more detail:
> 
> -- The Open Specification are in the private Wiki, but not in the public 
> one, which means that the commission could in principle see them, but 
> likely will not find them (unless we tell them, which we should do :-). 
> Putting your report on a (public Wiki) may be a good starting point for 
> this.
> 
> -- Outside of FI-WARE or the commission (e.g. use-case projects, general 
> public) the Open Spec will not be seen at all. We need to move it to the 
> Public Wiki. At the AB meeting on Fri I specifically asked Juanjo to 
> speed up this process, as our stuff has been ready for many weeks now 
> and people keep asking for it.
> 
> -- At the end the commission and the public will be mainly looking at 
> the FI-WARE catalog. Our stuff only gets in there if it fulfills certain 
> quality criteria. The most important ones are the quality of all the 
> other documentation we are preparing right now, including software and 
> examples to test things out, T&C, etc.
> 
> -- For the FI-LAB catalog we also need the Blueprints for automatic 
> installation. This is mandatory for server-based components but I 
> suggest that we also provide them for client-based software by 
> requesting a Web-server blueprint (probably available already) and 
> deploying the SW and examples to it.
> 
> Christof, feel free to correct me or add things I missed.
> 
> 
> Thanks,
> 
> 	Philipp
> 
>> You all know what is in the Open Specification. Up to this date, they
>> are as ready as they can be. We are having tracker, and feature sets,
>> and we have scheduled the development. From the schedule it can be seen
>> that everything what we plan is going to be ready in January, with minor
>> issues being patched after it. There are also installation and user
>> guides. At least on behalf of Cyber and CIE, those are up to date and
>> collectively already describe everything required. To emphasize: those
>> guides already make a number of references to github source code
>> repositories (which is allowed) and we already have a number of demos
>> online and they are collectively described in one place. This place is
>> now in the "interim payment" document, which contains demo links from
>> Cyber and Playsign. Other parties did not deliver anything for it.
>> 
>> So, given this, in my opinion the only thing we might be lacking is the
>> collective list of demo links in Wiki. Obviously the interim report is
>> not enough (since it is not public), and hence it should be published
>> somewhere in the Wiki.
>> 
>> Other thing we are missing still is the FI-LAB components. Those will
>> come together with January release, in one form or another.
>> 
>> Am I missing something? :) Maybe the other thing we need to be
>> collectively doing, is a summarizing report of the progress, of which
>> naturally contains a summary of the current Wiki status.
>> 
>> - jarkko
>> 
>> 
>> 
>> On Sun, Dec 15, 2013 at 8:43 AM, Philipp Slusallek
>> <Philipp.Slusallek at dfki.de <mailto:Philipp.Slusallek at dfki.de>> wrote:
>> 
>>    Hi Toni, all,
>> 
>>    I and Juanjo were at the Architecture Board meeting in Madrid
>>    Thu/Fri when that message arrived and did briefly talk about it.
>> 
>>    Here is my perspective based on the discussion with Juanjo: It is
>>    not a major issue. The point is listed last and we assume that Arian
>>    is just wondering when the GEs will become available as there is
>>    little information on this available yet (as discussed before).
>> 
>> 
>>    However, there are a few things that we should do:
>> 
>>    -- Put together a list of our GEs that will be ready for the January
>>    release. Please all respond as quickly as possible by email, maybe
>>    we can set up a document somewhere where we can collect the information.
>> 
>>    -- For GEs that will not be ready for January we should have a good
>>    explanation.
>> 
>>    -- This list should be sent to Juanjo on Monday (before their review
>>    on Tuesday) !!
>> 
>>    -- As agreed with Christof we need to push for information being
>>    made publicly available on FI-WARE Wiki and need to put them in the
>>    FI-WARE Catalog as well.
>> 
>>    -- GEs should also be available on FI-LAB. There they will only be
>>    accepted on FI-LAB when their quality is high enough. We need to
>>    make sure it is. This also requires setting up blueprints (at least
>>    for SEs that need to be installed on a server, which can also mean
>>    Web server + JS libraries).
>> 
>> 
>>    Best,
>> 
>>             Philipp
>> 
>>    Am 14.12.2013 14:54, schrieb Toni Alatalo:
>> 
>>        Was just wondering about this — is this simply due to WP13 GEs not
>>        having been part of any official fi-ware release yet?
>> 
>>        Or is something missing about the status of our GEs? Many of
>>        them are
>>        already available in work-in-progress pre-release mode, on
>>        github. Just
>>        wanted to mention Christof that if you need help in gathering
>>        MIWI GE
>>        status, links to the source codes and info about commercial
>>        exploitation
>>        etc. we can quite easily do that. And demo links ofc.
>> 
>>        For example, CIEs POI backend:
>>        GE is available from
>>        https://github.com/Chiru/WeX/__tree/master/poi
>>        <https://github.com/Chiru/WeX/tree/master/poi>
>>        and live demo at
>>        http://chiru.cie.fi/FI-WARE/__demos/POI/map_demo/
>>        <http://chiru.cie.fi/FI-WARE/demos/POI/map_demo/>
>> 
>>        etc. for almost all MIWI GEs. But right now I’m afraid that info
>>        is not
>>        gathered anywhere (that demo link for what the guys showed at
>>        the F2F I
>>        asked and got by private email) — would be good to have in the
>>        wiki in
>>        any case I figure.
>> 
>>        Cheers,
>>        ~Toni
>> 
>>        Begin forwarded message:
>> 
>>            *From: *Juanjo Hierro <jhierro at tid.es
>>            <mailto:jhierro at tid.es> <mailto:jhierro at tid.es
>>            <mailto:jhierro at tid.es>>>
>>            *Subject: **[Fiware] QUITE IMPORTANT AND URGENT: RE: GEs to
>>            discuss in
>>            the review meeting*
>>            *Date: *13 Dec 2013 22:49:49 GMT+2
>>            *To: *"fiware at lists.fi-ware.eu
>>            <mailto:fiware at lists.fi-ware.eu>
>>            <mailto:fiware at lists.fi-ware.__eu
>>            <mailto:fiware at lists.fi-ware.eu>>"
>>            <fiware at lists.fi-ware.eu <mailto:fiware at lists.fi-ware.eu>
>>            <mailto:fiware at lists.fi-ware.__eu
>>            <mailto:fiware at lists.fi-ware.eu>>>
>> 
>> 
>>            Dear FI-WARE GEi owners,
>> 
>>               We have got a very clear response from our PO, Arian
>>            Zweger, about
>>            what are the concrete GEis which are going to be particularly
>>            questioned during the month 30 project review next week.
>> 
>>               Please react accordingly so that:
>> 
>>               * you provide your WPL the necessary information that
>>            will allow him
>> 
>>                 to answer any potential question at the review; or
>>               * let us know INMEDIATELY whether you will attend the meeting
>> 
>>                 personally, as to be able to respond any questions directly
>> 
>>               Note that, regarding the first set of GEis, Arian
>>            mentions that the
>>            EC and reviewers wish to explore whether it is worthwhile to
>>            continue
>>            funding development.
>> 
>>               Some questions that I wouldn't be surprised if the
>>            PO/reviewers make:
>> 
>>               * What are your commercial plans around the GEis beyond
>>            the FI-PPP ?
>>               * (for those cases were the GEi is not being offered as open
>> 
>>                 source): what are the FRAND terms under which you plan
>>            to deliver
>>                 your GEi beyond the FI-PPP ?
>>               * If you are not involved in any proposal focused on
>>            continuation of
>> 
>>                 the Technology Foundation (FI-WARE) ... how do you plan
>>            to provide
>>                 lab support of your GEi to SMEs in phase 3 or even UC
>>            projects in
>>                 phase 2 trials ?    How doy you plan to provide level 1
>>            and 2
>>                 support of you GEi if deployed on FI-Lab ?
>> 
>>               Besides this, there are a number of questions regarding
>>            GEis in
>>            several chapters that WPLs/WPAs should prepare a response for.
>> 
>>               For those who didn't follow the details about the next
>>            month 30
>>            project review, these are the logistics:
>> 
>>                 Reharsal: Rehearsal: 16-17/Dec. Telefónica’s office
>>            (Avenue des
>>                 Arts, 20).The meeting will start at 11:15-12:00 on Monday.
>>                 Review: 18^th December 2013, avenue de Beaulieu BU25 0/S2
>> 
>>                 agenda of the
>> 
>>            review:https://docs.google.__com/spreadsheet/ccc?key=__0AmxBgS-__lWT4vdDB6NXJzMHVubDg1Zko5VG5Bb__zAzSnc#gid=0
>>            <https://docs.google.com/spreadsheet/ccc?key=0AmxBgS-lWT4vdDB6NXJzMHVubDg1Zko5VG5BbzAzSnc#gid=0>
>> 
>>               Best regards,
>> 
>>            -- Juanjo Hierro
>> 
>>            P.D.: A note about the list below ... apartently, the DCA
>>            GEi was in
>>            the list because of an inconsistent message in the catalogue
>>            (it was
>>            mentioned that the product was going to be licensed as open
>>            source
>>            while at the same time it was stated that it could be used under
>>            certain terms and conditions).   This has already been fixed.
>> 
>>            -------------
>>            Product Development and Innovation (PDI) - Telefonica Digital
>>            website:www.tid.es <http://www.tid.es>
>>            email:jhierro at tid.es <mailto:email%3Ajhierro at tid.es>
>>            twitter:twitter.com/__JuanjoHierro
>>            <http://twitter.com/JuanjoHierro>
>>              <http://twitter.com/__JuanjoHierro
>>            <http://twitter.com/JuanjoHierro>>
>> 
>> 
>>            FI-WARE (European Future Internet Core Platform) Coordinator
>>            and Chief Architect
>> 
>>            FI-PPP Architecture Board chairman
>> 
>>            You can follow FI-WARE at:
>>                website:http://www.fi-ware.eu
>> 
>>              facebook:http://www.facebook.__com/pages/FI-WARE/__251366491587242 <http://www.facebook.com/pages/FI-WARE/251366491587242>
>>                twitter:http://twitter.com/__FIware
>>            <http://twitter.com/FIware>
>>                linkedIn:http://www.linkedin.__com/groups/FIWARE-4239932
>>            <http://www.linkedin.com/groups/FIWARE-4239932>
>> 
>> 
>>            -------- Original Message --------
>>            Subject:        RE: GEs to discuss in the review meeting
>>            Date:   Fri, 13 Dec 2013 14:33:44 +0000
>>            From:   <Arian.ZWEGERS at ec.europa.eu
>>            <mailto:Arian.ZWEGERS at ec.europa.eu>>
>>            To:     <mcp at tid.es <mailto:mcp at tid.es>>
>>            CC:     <jhierro at tid.es
>>            <mailto:jhierro at tid.es>>,<CNECT-ICT-__285248 at ec.europa.eu
>>            <mailto:CNECT-ICT-285248 at ec.europa.eu>>
>> 
>> 
>> 
>>            Dear Miguel,
>> 
>>            As requested, please find a list below.
>> 
>>            The question for the first group is*whether it is worthwhile to
>>            continue funding development of:*
>> 
>>            - Data Chapter
>>                             - Compressed Domain Video Analysis, Codoan
>>            / Siemens
>>                             - Metadata Preprocessing, MetadataProcessor
>>            / Siemens
>>                             - Media-enhanced Query Broker, QueryBroker
>>            / Siemens
>>            - Apps Chapter
>>                             - (Service Composition, Ericsson
>>            Composition Editor
>>            (ECE) / Ericsson)
>>                             - Service Mashup, Mashup Factory / DT
>>                             - Mediator, Mediator_TI / Telecom Italia
>>            - IoT Chapter
>>                             - (Backend) Configuration Management, IoT
>>            Discovery - UNIS
>>                             - (Backend) IoT Broker, IoT Broker - NEC
>>                             - (Backend) Device Management, IDAS DCA - TID
>>                             - (Gateway) Protocol Adapter, ZPA / Telecom
>>            Italia /
>>            EPCGE / Orange
>>            - Security Chapter
>>                             - Security Monitoring / Android Vulnerability
>>            Assessment, Ovaldroid / Inria
>>                             - Identity Management, GCP / DT
>>                             - Identity Management, One-IDM / NSN
>>                             - Identity Management, DigitalSelf / NSN
>>                             - Malware Detection Service (Opt), Morphus
>>            / Inria
>>            - I2ND Chapter
>>                             - Cloud Proxy
>>                             - (I2ND) Network Information and Control
>>            (NetIC-VNP),
>>            Altoclient/ALU-D
>>                             - (I2ND) Network Information and Control
>>            (NetIC-OFNIC), VNP/NSN
>>                             - (I2ND) Network Information and Control
>>            (NetIC-altoclient), VNEIC/ALU-I
>>                             - (I2ND) Service Connectivity Capability
>>            and Control
>>            (S3C), S3C / DT
>>            - Tools
>>                             - Trace Analyzer, IBM Israel
>> 
>>            Then there are*specific questions*for the second group:
>> 
>>            - Cloud Chapter
>>                             - Why having a DCRM by IBM and one by
>>            Intel? Differences?
>>                             - Object Storage GEi by IBM:?? Status?
>>                             - Edgelets Manager by Thales: not in the
>>            Catalogue?
>>            - Data Chapter
>>                             - UDA – unstructured data analysis by
>>            ATOS?? Status?
>>            - Apps Chapter
>>                             - Relation Mediator_TI by Telecom Italia
>>            and SETHA2 by
>>            Thales?
>>            - IoT Chapter
>>                             - (Gateway) Device Management, Gateway Device
>>            Management / Franhoufer: not in the Catalogue?
>>                             - Test and evaluation server environment
>>            for NGSI by
>>            SAP?? Status?
>>                             - Template Handler by SAP?? Status?
>>            - Security Chapter
>>                             - KeyRock by UPM?? Status?
>>                             - Access Proxy by UPM?? Status?
>>            - MiWi Chapter
>>                             - Where are Advanced Middleware, 2D-UI, 3D-UI,
>>            Synchronization, Cloud Rendering, Display as a Service, GIS Data
>>            Provider, POI Data Provider, 2D-3D-Capture, Augmented Reality,
>>            Real-Virtual Interaction, Virtual Character, Interface
>>            Designer? Status?
>> 
>>            Best regards,
>>            Arian
>> 
>> 
>> 
>>            ------------------------------__------------------------------__------------
>> 
>> 
>>            Este mensaje se dirige exclusivamente a su destinatario. Puede
>>            consultar nuestra política de envío y recepción de correo
>>            electrónico
>>            en el enlace situado más abajo.
>>            This message is intended exclusively for its addressee. We
>>            only send
>>            and receive email on the basis of the terms set out at:
>>            http://www.tid.es/ES/PAGINAS/__disclaimer.aspx
>>            <http://www.tid.es/ES/PAGINAS/disclaimer.aspx>
>>            _________________________________________________
>>            Fiware mailing list
>>            Fiware at lists.fi-ware.eu <mailto:Fiware at lists.fi-ware.eu>
>>            <mailto:Fiware at lists.fi-ware.__eu
>>            <mailto:Fiware at lists.fi-ware.eu>>
>>            https://lists.fi-ware.eu/__listinfo/fiware
>>            <https://lists.fi-ware.eu/listinfo/fiware>
>> 
>> 
>> 
>> 
>>        _________________________________________________
>>        Fiware-miwi mailing list
>>        Fiware-miwi at lists.fi-ware.eu <mailto:Fiware-miwi at lists.fi-ware.eu>
>>        https://lists.fi-ware.eu/__listinfo/fiware-miwi
>>        <https://lists.fi-ware.eu/listinfo/fiware-miwi>
>> 
>> 
>> 
>>    --
>> 
>>    ------------------------------__------------------------------__-------------
>>    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-miwi mailing list
>>    Fiware-miwi at lists.fi-ware.eu <mailto:Fiware-miwi at lists.fi-ware.eu>
>>    https://lists.fi-ware.eu/listinfo/fiware-miwi
>> 
>> 
>> 
>> 
>> --
>> Jarkko Vatjus-Anttila
>> VP, Technology
>> Cyberlightning Ltd.
>> 
>> mobile. +358 405245142
>> email. jarkko at cyberlightning.com <mailto:jarkko at cyberlightning.com>
>> 
>> Go to www.cybersli.de <http://www.cybersli.de/> and enrich your
>> presentations!
>> 
>> www.cyberlightning.com <http://www.cyberlightning.com/>
> 
> 
> -- 
> 
> -------------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------------
> <slusallek.vcf>_______________________________________________
> Fiware-miwi mailing list
> Fiware-miwi at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-miwi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131216/dab1bb41/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FI-WARE_M30_Review_WP13_partnername.pptx
Type: application/vnd.openxmlformats-officedocument.presentationml.presentation
Size: 168943 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131216/dab1bb41/attachment.pptx>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131216/dab1bb41/attachment-0001.html>


More information about the Fiware-miwi mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy