From mach at zhaw.ch Wed Apr 2 08:32:53 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 2 Apr 2014 06:32:53 +0000 Subject: [Fiware-miwi] Agenda/Minutes of todays meeting Message-ID: Hi I prepared the Agenda/Minutes for today: https://docs.google.com/document/d/1ngF8bHSD-7utHj1ZWVYCtB8_QePIm9LLV2I8ThyDwJg/edit Hangout is available here: https://plus.google.com/hangouts/_/7acpis4b5lu92k84hb76r0sri8?hl=de Best regards Christof ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From Philipp.Slusallek at dfki.de Wed Apr 2 09:56:41 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 02 Apr 2014 09:56:41 +0200 Subject: [Fiware-miwi] Agenda/Minutes of todays meeting In-Reply-To: References: Message-ID: <533BC2B9.7070903@dfki.de> Hi, I am at the ECFI Future Internet conference today and there was too much other stuff, so I could not join. Sorry, Philipp Am 02.04.2014 08:32, schrieb Marti Christof (mach): > Hi > > I prepared the Agenda/Minutes for today: > https://docs.google.com/document/d/1ngF8bHSD-7utHj1ZWVYCtB8_QePIm9LLV2I8ThyDwJg/edit > > Hangout is available here: > https://plus.google.com/hangouts/_/7acpis4b5lu92k84hb76r0sri8?hl=de > > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/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 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From lasse.oorni at ludocraft.com Wed Apr 2 15:11:55 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Wed, 2 Apr 2014 16:11:55 +0300 Subject: [Fiware-miwi] Synchronization & Virtual Characters documents up for review Message-ID: Hi, the Synchronization & Virtual Characters documents have been updated for R3.3 and are ready for internal review. You can find the links from the dashboard: https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=24 Note that releases are not yet uploaded so the links to packages are missing. The upload will likely happen in the beginning of next week. -- Lasse ??rni Game Programmer LudoCraft Ltd. From jarkko at cyberlightning.com Wed Apr 2 18:13:09 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Wed, 2 Apr 2014 19:13:09 +0300 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> Message-ID: As discussed today, I modified the existing State of the art document to include also those references. Here you go: - j On Fri, Mar 21, 2014 at 1:45 PM, Jarkko Vatjus-Anttila < jarkko at cyberlightning.com> wrote: > All, > > Here are all the missing references. I did not edit them directly to the > document since I at the moment do not have an access to Microsoft Word. > Libreoffice would have just screwed the document. > > Anyway, all missing references are here as formatted list, so if you can > copy-paste the list to the end of document, it would be very nice. > > - Vergauwem 06: Vergauwen M. and Van Gool, L. (2006) "Web-based 3D > reconstruction service". Machine Vision and Applications (2006) 17. pp. > 411-426 > - Milgram 94: Milgram P., Takemura H., Utsumi A. and Kishino F. (1994) > "Augmented Reality: A class of displays on the reality-virtuality > continuum". > - Azuma 01: Azuma R., Baillot Y., Behringer R., Feiner S. and Julier S. > (2001) "Recent Advances in Augmented Reality". IEEE Computer Graphics and > Applications table of contents archive.Volume 21 Issue 6. pp. 34-47. ISSN > 0272-1716 > Blair MacIntyre > - Lowe 04: Lowe D. G. (2004) "Distinctive Image Features from > Scale-Invariant Keypoints". International Journal of Computer Vision table > of contents archive Volume 60 Issue 2. pp. 91-110. ISSN 0920-5691 > - Bay 08: Bay H., Ess, A., Tuytelaars T. and Van Gool, L. (2008) > "Speeded-up robust features (SURF)". Journal Computer Vision and Image > Understanding archive Volume 110 Issue 3, June, 2008 pp. 346-359 > - Forssen 07: Forssen P. and Lowe D. G. (2007) "Shape Descriptors for > Maximally Stable Extremal Regions". Computer Vision, 2007. ICCV 2007. IEEE > 11th International Conference on. pp. 1 - 8. ISSN : 1550-5499 > - Engels 06: Engels C., Stew?nius H. and Nist? D. (2006) "Bundle > Adjustment Rules" *Photogrammetric Computer Vision (PCV).* > - Holmes 07: Holmes, S., Sibley. G., Klein, G. and Murray, D. W. (2007) "A > Relative Frame Representation for Fixed-Time Bundle Adjustment in SFM". > CRA'09 Proceedings of the 2009 IEEE international conference on Robotics > and Automation. pp 2631-2636 > - Vilhjalmsson 07: Vilhjalmsson, H., Cantelmo, N., Cassell, J., Chafai, N. > E., Kipp, M., Kopp, S., Manxini, M., Marsella, S., Marshall, A. N., > Pelachaud, C., Ruttkay, Z., Thorinsson, K. R., Welbergen, H and Werf, R J. > (2007) "The behavior markup language: Recent developments and challenges". > Intelligent Virtual Agents Lecture Notes in Computer Science Volume 4722, > 2007, pp 99-111. ISSN 0302-9743 > > > > On Wed, Mar 19, 2014 at 3:13 PM, Cvetan Stefanovski > wrote: > >> Hello, >> >> Here's Adminotech part of the internal review for SotA >> >> >> On Mon, Mar 17, 2014 at 6:14 PM, Christof Marti wrote: >> >>> Hi Philipp >>> >>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to >>> you? >>> >>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>> Deliverable >>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>> feedback >>> for Miguel, to get the release-review process going again. >>> >>> Important: In todays WPL/WPA call it was pointed out, that we also have >>> to >>> provide a management summary (~ 1 page), containing only the newest >>> developments. >>> (For the other chapters this are the changes since last release of the >>> deliverable) >>> (For us this could be a compilation from the last part of all the GEs >>> sota) >>> >>> Best regards >>> Christof >>> >>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek < >>> Philipp.Slusallek at dfki.de>: >>> >>> > Hi, >>> > >>> > I did go through the text and fixed quite a few missing references and >>> > marked some others that are still missing (please can some of the >>> people >>> > involved in those GEs fix them). >>> > >>> > In general, there is a lack of references to previous work in quite a >>> > few of the GE descriptions. Please follow the model we have done in the >>> > middleware section and add some more references to previous work and >>> > then position your work in FI-WARE in relation to that. >>> > >>> > >>> > Best, >>> > >>> > Philipp >>> > >>> > >>> > Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>> >> Hello, >>> >> >>> >> I read through the paper in my behalf, and the text seems to be pretty >>> >> much collected from the text that has been formulated already >>> earlier. I >>> >> my opinion, it gives an overview of the state of the art and as such I >>> >> would guess it works as a deliverable for this purpose. However, >>> having >>> >> said that, I may not know all exact requirements what this deliverable >>> >> is expected to fulfill. >>> >> >>> >> I made minor changes here and there, mainly fixing misspellings and >>> word >>> >> ordering. The modified document is attached here, with track changes >>> >> enabled. >>> >> >>> >> - jarkko >>> >> >>> >> >>> >> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >> >> > wrote: >>> >> >>> >> Hi Philipp, dear WP13 GE Owners >>> >> >>> >> Also due in M36 is an updated version (D.2.6.3) of the "State of >>> the >>> >> art analysis - emerging technologies" deliverable. The previous >>> >> release can be found here: >>> >> >>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>> >> < >>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+%E2%80%93+Emerging+Technologies.pdf >>> > >>> >> >>> >> Idea for all existing WPs is to provide a management summary and do >>> >> only required updates on the existing chapters. >>> >> Because there is no Web User Interfaces chapter in the last >>> >> deliverable I took the content from the FI-Core proposal and tried >>> >> to put together a WP13 contribution for this deliverable. >>> >> It was more work than expected, because the writing style in a >>> >> proposal is a little bit different than for this deliverable. So I >>> >> would like to ask Philipp (and the respective GE owner for their >>> >> part) to review the attached document (in change tracking mode), >>> add >>> >> missing content and in particular also add missing entries in the >>> >> "Reference" section. >>> >> >>> >> Deadline for delivering updates to the coordinator for review >>> is/was >>> >> today (March 14th). Because of this additional internal review >>> >> roundtrip, this will not be feasible. >>> >> If each GE owner can review its 20 to 30 lines and Philipp keeps am >>> >> eye on the overarching context until Monday noon, the delay would >>> be >>> >> minimal. >>> >> >>> >> Thanks for your contributions. >>> >> >>> >> @Miguel, Juanjo: I do not want to release this without the OK of >>> >> Philipp and the domain experts. >>> >> >>> >> Best regards >>> >> Christof >>> >> ---- >>> >> InIT Cloud Computing Lab - ICCLab >>> >> Institut of Applied Information Technology - InIT >>> >> Zurich University of Applied Sciences - ZHAW >>> >> School of Engineering >>> >> Phone: +41 58 934 70 63 >>> >> Skype: christof-marti >>> >> >>> >> _______________________________________________ >>> >> Fiware-miwi mailing list >>> >> 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 >>> >> >>> >> Go to www.cybersli.de and enrich your >>> >> presentations! >>> >> >>> >> 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 >>> > >>> --------------------------------------------------------------------------- >>> > >> WP13-1-phs.docx> >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> 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 > > Go to www.cybersli.de and enrich your presentations! > > www.cyberlightning.com > -- Jarkko Vatjus-Anttila VP, Technology Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com Go to www.cybersli.de and enrich your presentations! www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.3 State of the Art Analysis - Emerging Technologies - WP13.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 419698 bytes Desc: not available URL: From toni at playsign.net Fri Apr 4 14:08:51 2014 From: toni at playsign.net (Toni Alatalo) Date: Fri, 4 Apr 2014 15:08:51 +0300 Subject: [Fiware-miwi] 3DUI-WebTundra docs & release for review Message-ID: Hi Jarkko, others - our docs are finally updated for current code: https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php?title=3D-UI_-_WebTundra_-_Installation_and_Administration_Guide(R3.3) https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php?title=3D-UI_-_WebTundra_-_User_and_Programmers_Guide(R3.3) https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php?title=3D-UI_-_WebTundra_-_Unit_Testing_Plan_and_Report(R3.3) code is in dev branch right now still, we upload zip and push to master now. ~Toni From jonne at adminotech.com Fri Apr 4 15:20:07 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Fri, 4 Apr 2014 16:20:07 +0300 Subject: [Fiware-miwi] Open sourcing the core of Meshmoon WebRocket Message-ID: As many have probably noticed, nowadays there is no shortcoming in the amount of web implementations that have been running side by side in the realXtend community :) We announced yesterday of open sourcing our web browser client core SDK (WebRocket) that you all have seen in the MIWI IRL demos. I don't want to rewrite all the details as I made a quite detailed blog post about it yesterday. please check it for the reasoning and timing of the open source release: http://blog.meshmoon.com/2014/04/03/open-sourcing-the-core-of-meshmoon-webrocket/ The main thing I want to signal to the FIWARE (MIWI in particular) community is that we aim to work with all the companies here, combining the best parts of all our open source codebases going forward. This pull requestwas specifically done to the rex FIWARE repository so that we can do this. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Philipp.Slusallek at dfki.de Sat Apr 5 11:12:33 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Sat, 05 Apr 2014 11:12:33 +0200 Subject: [Fiware-miwi] Fwd: [Fiware-ge-owners] Backlog content - Reviews - LAST CALL In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90BB31BB107@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90BB31BB107@EX10-MB2-MAD.hi.inet> Message-ID: <533FC901.2090401@dfki.de> Hi, It would be great if we could solve the remaining issues quickly. Please everyone check his entries if not done so yet. Best, Philipp -------- Original-Nachricht -------- Betreff: [Fiware-ge-owners] Backlog content - Reviews - LAST CALL Datum: Sat, 05 Apr 2014 09:05:12 +0000 Von: MANUEL ESCRICHE VICENTE An: fiware-ge-owners at lists.fi-ware.org Kopie (CC): fiware-wpl at lists.fi-ware.org , fiware-wpa at lists.fi-ware.org Dear Partners, Please have backlog review reports updated: No chapter has finished yet!! *I2ND* ? 27 (4%) ?still leads but loosed the opportunity to win the contest. *MIWI* ? 49 (14%) ? MiWi being at winning distance also loses the opportunity. *APP* ? 96 (12%) ? Amazing reaction!!! - Apps reaches the 3^rd position I2ND MIWI APPS *DATA* ? 130 (15%) *CLOUD* ? 161 (14%) *SECURITY* ? 222 (34%) *IOT* ? 294 (57%) On Monday 7^th at 18:00 I?ll take the snapshot whose review reports? statistics will be joined to the dashboard snapshot took on 31^st March to be delivered to the EC. https://forge.fi-ware.org/docman/view.php/27/3742/FIWARE.backlog.apps.review.20140405.xlsx https://forge.fi-ware.org/docman/view.php/27/3743/FIWARE.backlog.cloud.review.20140405.xlsx https://forge.fi-ware.org/docman/view.php/27/3746/FIWARE.backlog.iot.review.20140405.xlsx https://forge.fi-ware.org/docman/view.php/27/3744/FIWARE.backlog.data.review.20140405.xlsx https://forge.fi-ware.org/docman/view.php/27/3745/FIWARE.backlog.i2nd.review.20140405.xlsx https://forge.fi-ware.org/docman/view.php/27/3748/FIWARE.backlog.security.review.20140405.xlsx https://forge.fi-ware.org/docman/view.php/27/3747/FIWARE.backlog.miwi.review.20140405.xlsx Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WAREInitiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ------------------------------------------------------------------------ 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 -- ------------------------------------------------------------------------- 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 -------------- _______________________________________________ Fiware-ge-owners mailing list Fiware-ge-owners at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-ge-owners -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Sat Apr 5 13:42:00 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Sat, 05 Apr 2014 13:42:00 +0200 Subject: [Fiware-miwi] Fwd: Re: [TC-Discuss] Finding WMS, WFS, WCS services In-Reply-To: <6C34D1C3A653794D84FAE1CEEE8CFB1381C2097B@RED-INF-EXMB-P1.esri.com> References: <6C34D1C3A653794D84FAE1CEEE8CFB1381C2097B@RED-INF-EXMB-P1.esri.com> Message-ID: <533FEC08.8030905@dfki.de> Hi, Could be useful in the GIS context even though they seem not to have any 3D services available. Best, Philipp -------- Original-Nachricht -------- Betreff: Re: [TC-Discuss] Finding WMS, WFS, WCS services Datum: Thu, 3 Apr 2014 23:50:17 +0000 Von: Marten Hogeweg An: Mike Botts , "TC-Discuss at lists.opengeospatial.org" We have a Geoportal Server instance running that has 1300+ WMS http://gptogc.esri.com/geoportal/rest/find/document?searchText=WMS&start=1&max=10&f=searchpage and then some WFS, WCS, SOS, CSW, ? from here you can direct your searches to a number of other catalogs (not harvested, but federated), including Data.gov, ArcGIS Online, GEOSS Clearinghouse etc rather than this service type approach, you could also to start from ?in and area around Alabama? and ?about Alabama? http://gptogc.esri.com/geoportal/rest/find/document?searchText=alabama&start=1&max=10&spatialRel=esriSpatialRelWithin&bbox=-95.75%2C26.4583%2C-79.25%2C36.5417&expandResults=true&f=searchpage or be a bit more specific and also include a type filter (map services only), but also consider global items overlapping Alabama (in this case a spatial ranking is at play as well as a textual ranking): http://gptogc.esri.com/geoportal/rest/find/document?searchText=alabama&start=1&max=10&contentType=liveData&spatialRel=esriSpatialRelOverlaps&bbox=-95.396%2C27.5272%2C-80.2597%2C36.7772&expandResults=true&f=searchpage cheers, Marten *From:*TC-Discuss [mailto:tc-discuss-bounces+mhogeweg=esri.com at lists.opengeospatial.org] *On Behalf Of *Mike Botts *Sent:* Wednesday, April 02, 2014 3:24 PM *To:* TC-Discuss at lists.opengeospatial.org *Subject:* [TC-Discuss] Finding WMS, WFS, WCS services I should of course know this, but its been awhile since I was doing much with non-SWE services. How does one find existing WMS, WFS, WCS services these days? Are there one or more registries that are being used? This is of course fundamental question that I don?t know the answer for, so would appreciate help. We are working up a Pilot Project (not an OGC IP) as part of the GeoINT Huntsville initiative and are looking for OGC layers that might be relevant to the North Alabama area, including primarily standard GIS-type data and weather-related data. Thanks. Mike Botts ***************************************** Dr. Mike Botts Botts Innovative Research, Inc. http://www.botts-inc.com mike.botts at botts-inc.com 256-652-0165 ***************************************** -- ------------------------------------------------------------------------- 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 -------------- _______________________________________________ TC-Discuss mailing list TC-Discuss at lists.opengeospatial.org This is an auto-subscribe list. All OGC members are encouraged to maintain a subscription to this list. You may change your delivery options in the "Email Subscriptions" portion of "My Account" in the OGC Web Portal. https://portal.opengeospatial.org/?m=users&a=viewuser&tab=3 -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Sun Apr 6 08:19:28 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Sun, 06 Apr 2014 08:19:28 +0200 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> Message-ID: <5340F1F0.6040404@dfki.de> Hi, Sorry for the dealy but I was extremely busy the last few weeks. Here is (what I consider) the final version of the SotA for WP13. I did a final pass over the general text, adding some more references, and adding an extensive Executive Summary that gives and overview of the available technology, puts it in perspective, and sketches how the individual enabler are related to each other.. It would be good if someone did a quick pass over it to spot any typos and such but otherwise it should be ready to go. Hope you like it :-), Philipp Am 17.03.2014 17:14, schrieb Christof Marti: > Hi Philipp > > Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to you? > > I am very busy going through OpenSpecs v3 and create the D.13.1.3 Deliverable > and also checking all the Release 3 comments (Guides, UTP) and prepare feedback > for Miguel, to get the release-review process going again. > > Important: In todays WPL/WPA call it was pointed out, that we also have to > provide a management summary (~ 1 page), containing only the newest developments. > (For the other chapters this are the changes since last release of the deliverable) > (For us this could be a compilation from the last part of all the GEs sota) > > Best regards > Christof > > Am 16.03.2014 um 10:48 schrieb Philipp Slusallek : > >> Hi, >> >> I did go through the text and fixed quite a few missing references and >> marked some others that are still missing (please can some of the people >> involved in those GEs fix them). >> >> In general, there is a lack of references to previous work in quite a >> few of the GE descriptions. Please follow the model we have done in the >> middleware section and add some more references to previous work and >> then position your work in FI-WARE in relation to that. >> >> >> Best, >> >> Philipp >> >> >> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>> Hello, >>> >>> I read through the paper in my behalf, and the text seems to be pretty >>> much collected from the text that has been formulated already earlier. I >>> my opinion, it gives an overview of the state of the art and as such I >>> would guess it works as a deliverable for this purpose. However, having >>> said that, I may not know all exact requirements what this deliverable >>> is expected to fulfill. >>> >>> I made minor changes here and there, mainly fixing misspellings and word >>> ordering. The modified document is attached here, with track changes >>> enabled. >>> >>> - jarkko >>> >>> >>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >> > wrote: >>> >>> Hi Philipp, dear WP13 GE Owners >>> >>> Also due in M36 is an updated version (D.2.6.3) of the ?State of the >>> art analysis - emerging technologies? deliverable. The previous >>> release can be found here: >>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+?+Emerging+Technologies.pdf >>> >>> >>> Idea for all existing WPs is to provide a management summary and do >>> only required updates on the existing chapters. >>> Because there is no Web User Interfaces chapter in the last >>> deliverable I took the content from the FI-Core proposal and tried >>> to put together a WP13 contribution for this deliverable. >>> It was more work than expected, because the writing style in a >>> proposal is a little bit different than for this deliverable. So I >>> would like to ask Philipp (and the respective GE owner for their >>> part) to review the attached document (in change tracking mode), add >>> missing content and in particular also add missing entries in the >>> ?Reference" section. >>> >>> Deadline for delivering updates to the coordinator for review is/was >>> today (March 14th). Because of this additional internal review >>> roundtrip, this will not be feasible. >>> If each GE owner can review its 20 to 30 lines and Philipp keeps am >>> eye on the overarching context until Monday noon, the delay would be >>> minimal. >>> >>> Thanks for your contributions. >>> >>> @Miguel, Juanjo: I do not want to release this without the OK of >>> Philipp and the domain experts. >>> >>> Best regards >>> Christof >>> ---- >>> InIT Cloud Computing Lab - ICCLab >>> Institut of Applied Information Technology - InIT >>> Zurich University of Applied Sciences - ZHAW >>> School of Engineering >>> Phone: +41 58 934 70 63 >>> Skype: christof-marti >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> 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 >>> >>> Go to www.cybersli.de and enrich your >>> presentations! >>> >>> 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 >> --------------------------------------------------------------------------- >> > -- ------------------------------------------------------------------------- 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: D.2.6.3 State of the Art Analysis - Emerging Technologies - WP13-phs.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 440809 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From toni at playsign.net Sun Apr 6 09:34:54 2014 From: toni at playsign.net (Toni Alatalo) Date: Sun, 6 Apr 2014 10:34:54 +0300 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: <5340F1F0.6040404@dfki.de> References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> Message-ID: I've also found it OK when looked previously. Had a couple of things that wanted to add then but was traveling and didn't have access to Word (actually never normally do unfortunately) so didn't have a way to work on them safely. Still seems fine and is good to go if there's a hurry - a couple of notes here anyhow in case there's a chance to work on it still: a simple story -- how fi-ware has advanced the state of the art from realXtend's perspective: - starting point: ECA model proposed as a standard for extensible virtual worlds a few years back (Alatalo 2011). with a c++ implementation that has since matured and is in commercial use - progress beyond state of art: ECA implemented over web sockets with integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same proposed platform - improvements to the ECA model: * mapping between xml3d & reX ECA: allows much more human friendly declarative authoring than TXML. integrates nicely to Web when used inside HTML. * entity hierarchy (not flat like before fi-ware, proper parenting) (new in 3.3) * proper custom component support from Javascript (new in 3.3) * these last points also AFAIK enable complete representation of any xml, including html & xml3d in reX ECA -> the generic simple network protocol with AttributeChanged etc. messages works to sync those too In the current document I think a section based on that could be used to improve the "Web User Interface Server Core Technologies" - it doesn't really make sense to say: "Today, real-time synchronization of 3D scenes is limited to specialized applications such as SecondLife (secondlife.com) and games engines like Unreal and others. " when we already presented a *generic* protocol and platform already 3 years ago and have happily used it in business since. Basically what was missing before fi-ware was a web/html5 implementation of that. That 2011 article which introduced the model & platform is this BTW, perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html Here is a mistake (it's realxtend.org, not .com) and I'd consider the wording too: "FI-WARE technology is currently based on realXtend (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization layer (FIVES) has been designed that is based on the FI-WARE Advanced Middleware [Byelozyorov 13]" I'm not sure if 'more pure' is a good choice of words there, especially as AFAIK the FiVES implementation is basically identical with the realXtend model and implementations. realXtend is also completely pure in several ways: the ECA model doesn't specify any vocabulary itself (like XML doesn't) but applications or plugins can define whatever components they want (like xml3d and realXtend's set of basic components do). The networking works automatically for any component. reX ECA is independent of the transport layer: in current Tundra impls the messaging is handled by the Kristalli / kNet library, but any other transport could be used without the application layer seeing any changes I think. I know and sure acknowledge that KIARA is much more ambitious and advanced in how it can do the serialisation and automatically choose suitable transports etc. but I'm not aware how something on the FiVES level would be 'more pure' nor what that'd mean. If it refers to generality with regards to application data types etc. it's AFAIK the same. A more informative description of the differences in purity and networking might be useful there. At least for me to understand what the doc is trying to say :) Final point: some of these things are already done and being delivered, at least glTF and other optimized transfer format support (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration with the editor / Interface Designer and the basic 3D things - if this is to report how we're progressed we could change some of the future form 'wills' there to past tense: "FI-WARE technology is based on XML3D [Sons 10] and will in future extend the current state-of-the-art by (i) adding a much extended content pipeline for integrating 3D content, (ii) a 3D asset data base including versioning and different, Web-optimized 3D data formats (working with the glTF initiative at Khronos), (iii) improved resource management for adaptive, on-demand loading and unloading of scene content, (iv) improved developer tools for distributed and synchronized Web applications, and (v) significantly improving the access to hardware resources for computational expensive tasks like AR, animation, and others. The 3D-UI technologies will closely tie together with the Interface Designer technology that will provide all of the features mentioned above in an interactive context directly to users." Anyhow I think it's also fine already if must go forward. If there is still time and you find some of these would be good improvements I can give a shot at integrating them in some simple ways tomorrow (can get to a compu with ms word then if necessary). Cheers and thanks for work on the comprehensive doc! ~Toni On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek wrote: > Hi, > > Sorry for the dealy but I was extremely busy the last few weeks. > > Here is (what I consider) the final version of the SotA for WP13. I did a > final pass over the general text, adding some more references, and adding an > extensive Executive Summary that gives and overview of the available > technology, puts it in perspective, and sketches how the individual enabler > are related to each other.. > > It would be good if someone did a quick pass over it to spot any typos and > such but otherwise it should be ready to go. > > Hope you like it :-), > > > Philipp > > Am 17.03.2014 17:14, schrieb Christof Marti: > >> Hi Philipp >> >> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to >> you? >> >> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >> Deliverable >> and also checking all the Release 3 comments (Guides, UTP) and prepare >> feedback >> for Miguel, to get the release-review process going again. >> >> Important: In todays WPL/WPA call it was pointed out, that we also have to >> provide a management summary (~ 1 page), containing only the newest >> developments. >> (For the other chapters this are the changes since last release of the >> deliverable) >> (For us this could be a compilation from the last part of all the GEs >> sota) >> >> Best regards >> Christof >> >> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >> : >> >>> Hi, >>> >>> I did go through the text and fixed quite a few missing references and >>> marked some others that are still missing (please can some of the people >>> involved in those GEs fix them). >>> >>> In general, there is a lack of references to previous work in quite a >>> few of the GE descriptions. Please follow the model we have done in the >>> middleware section and add some more references to previous work and >>> then position your work in FI-WARE in relation to that. >>> >>> >>> Best, >>> >>> Philipp >>> >>> >>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>> >>>> Hello, >>>> >>>> I read through the paper in my behalf, and the text seems to be pretty >>>> much collected from the text that has been formulated already earlier. I >>>> my opinion, it gives an overview of the state of the art and as such I >>>> would guess it works as a deliverable for this purpose. However, having >>>> said that, I may not know all exact requirements what this deliverable >>>> is expected to fulfill. >>>> >>>> I made minor changes here and there, mainly fixing misspellings and word >>>> ordering. The modified document is attached here, with track changes >>>> enabled. >>>> >>>> - jarkko >>>> >>>> >>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>> > wrote: >>>> >>>> Hi Philipp, dear WP13 GE Owners >>>> >>>> Also due in M36 is an updated version (D.2.6.3) of the "State of the >>>> art analysis - emerging technologies" deliverable. The previous >>>> release can be found here: >>>> >>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>> >>>> >>>> >>>> Idea for all existing WPs is to provide a management summary and do >>>> only required updates on the existing chapters. >>>> Because there is no Web User Interfaces chapter in the last >>>> deliverable I took the content from the FI-Core proposal and tried >>>> to put together a WP13 contribution for this deliverable. >>>> It was more work than expected, because the writing style in a >>>> proposal is a little bit different than for this deliverable. So I >>>> would like to ask Philipp (and the respective GE owner for their >>>> part) to review the attached document (in change tracking mode), add >>>> missing content and in particular also add missing entries in the >>>> "Reference" section. >>>> >>>> Deadline for delivering updates to the coordinator for review is/was >>>> today (March 14th). Because of this additional internal review >>>> roundtrip, this will not be feasible. >>>> If each GE owner can review its 20 to 30 lines and Philipp keeps am >>>> eye on the overarching context until Monday noon, the delay would be >>>> minimal. >>>> >>>> Thanks for your contributions. >>>> >>>> @Miguel, Juanjo: I do not want to release this without the OK of >>>> Philipp and the domain experts. >>>> >>>> Best regards >>>> Christof >>>> ---- >>>> InIT Cloud Computing Lab - ICCLab >>>> Institut of Applied Information Technology - InIT >>>> Zurich University of Applied Sciences - ZHAW >>>> School of Engineering >>>> Phone: +41 58 934 70 63 >>>> Skype: christof-marti >>>> >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> 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 >>>> >>>> Go to www.cybersli.de and enrich your >>>> presentations! >>>> >>>> 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 >>> >>> --------------------------------------------------------------------------- >>> >> WP13-1-phs.docx> >> >> > > > -- > > ------------------------------------------------------------------------- > 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.org > https://lists.fi-ware.org/listinfo/fiware-miwi > From Philipp.Slusallek at dfki.de Sun Apr 6 10:39:10 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Sun, 06 Apr 2014 10:39:10 +0200 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> Message-ID: <534112AE.5000905@dfki.de> Hi, Feel free to add to it based on the text you wrote. I pass the token to you. I am not exactly sure when it is supposed to go to the commission -- but this is very soon. Regarding the sync section. On the one hand you are right that realXtend had a generic protocol embedded in it, but my understanding was that it was pretty much tied to realXtend and not really available outside of it (even though one could probably have extracted it with some effort). This is the point I find important in the sense of offering a generic tool for synchronization. With "pure", I meant "standalone" in the sense of the above. Wording should be fixed. Best, Philipp Am 06.04.2014 09:34, schrieb Toni Alatalo: > I've also found it OK when looked previously. Had a couple of things > that wanted to add then but was traveling and didn't have access to > Word (actually never normally do unfortunately) so didn't have a way > to work on them safely. Still seems fine and is good to go if there's > a hurry - a couple of notes here anyhow in case there's a chance to > work on it still: > > a simple story -- how fi-ware has advanced the state of the art from > realXtend's perspective: > > - starting point: ECA model proposed as a standard for extensible > virtual worlds a few years back (Alatalo 2011). with a c++ > implementation that has since matured and is in commercial use > > - progress beyond state of art: ECA implemented over web sockets with > integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same > proposed platform > - improvements to the ECA model: > * mapping between xml3d & reX ECA: allows much more human friendly > declarative authoring than TXML. integrates nicely to Web when used > inside HTML. > * entity hierarchy (not flat like before fi-ware, proper parenting) > (new in 3.3) > * proper custom component support from Javascript (new in 3.3) > * these last points also AFAIK enable complete representation of any > xml, including html & xml3d in reX ECA -> the generic simple network > protocol with AttributeChanged etc. messages works to sync those too > > In the current document I think a section based on that could be used > to improve the "Web User Interface Server Core Technologies" - it > doesn't really make sense to say: "Today, real-time synchronization of > 3D scenes is limited to specialized applications such as SecondLife > (secondlife.com) and games engines like Unreal and others. " when we > already presented a *generic* protocol and platform already 3 years > ago and have happily used it in business since. Basically what was > missing before fi-ware was a web/html5 implementation of that. > > That 2011 article which introduced the model & platform is this BTW, > perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model > for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. > 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 > http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html > > Here is a mistake (it's realxtend.org, not .com) and I'd consider the > wording too: "FI-WARE technology is currently based on realXtend > (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization > layer (FIVES) has been designed that is based on the FI-WARE Advanced > Middleware [Byelozyorov 13]" > > I'm not sure if 'more pure' is a good choice of words there, > especially as AFAIK the FiVES implementation is basically identical > with the realXtend model and implementations. realXtend is also > completely pure in several ways: the ECA model doesn't specify any > vocabulary itself (like XML doesn't) but applications or plugins can > define whatever components they want (like xml3d and realXtend's set > of basic components do). The networking works automatically for any > component. reX ECA is independent of the transport layer: in current > Tundra impls the messaging is handled by the Kristalli / kNet library, > but any other transport could be used without the application layer > seeing any changes I think. > > I know and sure acknowledge that KIARA is much more ambitious and > advanced in how it can do the serialisation and automatically choose > suitable transports etc. but I'm not aware how something on the FiVES > level would be 'more pure' nor what that'd mean. If it refers to > generality with regards to application data types etc. it's AFAIK the > same. > > A more informative description of the differences in purity and > networking might be useful there. At least for me to understand what > the doc is trying to say :) > > Final point: some of these things are already done and being > delivered, at least glTF and other optimized transfer format support > (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration > with the editor / Interface Designer and the basic 3D things - if this > is to report how we're progressed we could change some of the future > form 'wills' there to past tense: "FI-WARE technology is based on > XML3D [Sons 10] and will in future extend the current state-of-the-art > by (i) adding a much extended content pipeline for integrating 3D > content, (ii) a 3D asset data base including versioning and different, > Web-optimized 3D data formats (working with the glTF initiative at > Khronos), (iii) improved resource management for adaptive, on-demand > loading and unloading of scene content, (iv) improved developer tools > for distributed and synchronized Web applications, and (v) > significantly improving the access to hardware resources for > computational expensive tasks like AR, animation, and others. The > 3D-UI technologies will closely tie together with the Interface > Designer technology that will provide all of the features mentioned > above in an interactive context directly to users." > > Anyhow I think it's also fine already if must go forward. If there is > still time and you find some of these would be good improvements I can > give a shot at integrating them in some simple ways tomorrow (can get > to a compu with ms word then if necessary). > > Cheers and thanks for work on the comprehensive doc! > ~Toni > > > On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek > wrote: >> Hi, >> >> Sorry for the dealy but I was extremely busy the last few weeks. >> >> Here is (what I consider) the final version of the SotA for WP13. I did a >> final pass over the general text, adding some more references, and adding an >> extensive Executive Summary that gives and overview of the available >> technology, puts it in perspective, and sketches how the individual enabler >> are related to each other.. >> >> It would be good if someone did a quick pass over it to spot any typos and >> such but otherwise it should be ready to go. >> >> Hope you like it :-), >> >> >> Philipp >> >> Am 17.03.2014 17:14, schrieb Christof Marti: >> >>> Hi Philipp >>> >>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to >>> you? >>> >>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>> Deliverable >>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>> feedback >>> for Miguel, to get the release-review process going again. >>> >>> Important: In todays WPL/WPA call it was pointed out, that we also have to >>> provide a management summary (~ 1 page), containing only the newest >>> developments. >>> (For the other chapters this are the changes since last release of the >>> deliverable) >>> (For us this could be a compilation from the last part of all the GEs >>> sota) >>> >>> Best regards >>> Christof >>> >>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >>> : >>> >>>> Hi, >>>> >>>> I did go through the text and fixed quite a few missing references and >>>> marked some others that are still missing (please can some of the people >>>> involved in those GEs fix them). >>>> >>>> In general, there is a lack of references to previous work in quite a >>>> few of the GE descriptions. Please follow the model we have done in the >>>> middleware section and add some more references to previous work and >>>> then position your work in FI-WARE in relation to that. >>>> >>>> >>>> Best, >>>> >>>> Philipp >>>> >>>> >>>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>>> >>>>> Hello, >>>>> >>>>> I read through the paper in my behalf, and the text seems to be pretty >>>>> much collected from the text that has been formulated already earlier. I >>>>> my opinion, it gives an overview of the state of the art and as such I >>>>> would guess it works as a deliverable for this purpose. However, having >>>>> said that, I may not know all exact requirements what this deliverable >>>>> is expected to fulfill. >>>>> >>>>> I made minor changes here and there, mainly fixing misspellings and word >>>>> ordering. The modified document is attached here, with track changes >>>>> enabled. >>>>> >>>>> - jarkko >>>>> >>>>> >>>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>>> > wrote: >>>>> >>>>> Hi Philipp, dear WP13 GE Owners >>>>> >>>>> Also due in M36 is an updated version (D.2.6.3) of the "State of the >>>>> art analysis - emerging technologies" deliverable. The previous >>>>> release can be found here: >>>>> >>>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>>> >>>>> >>>>> >>>>> Idea for all existing WPs is to provide a management summary and do >>>>> only required updates on the existing chapters. >>>>> Because there is no Web User Interfaces chapter in the last >>>>> deliverable I took the content from the FI-Core proposal and tried >>>>> to put together a WP13 contribution for this deliverable. >>>>> It was more work than expected, because the writing style in a >>>>> proposal is a little bit different than for this deliverable. So I >>>>> would like to ask Philipp (and the respective GE owner for their >>>>> part) to review the attached document (in change tracking mode), add >>>>> missing content and in particular also add missing entries in the >>>>> "Reference" section. >>>>> >>>>> Deadline for delivering updates to the coordinator for review is/was >>>>> today (March 14th). Because of this additional internal review >>>>> roundtrip, this will not be feasible. >>>>> If each GE owner can review its 20 to 30 lines and Philipp keeps am >>>>> eye on the overarching context until Monday noon, the delay would be >>>>> minimal. >>>>> >>>>> Thanks for your contributions. >>>>> >>>>> @Miguel, Juanjo: I do not want to release this without the OK of >>>>> Philipp and the domain experts. >>>>> >>>>> Best regards >>>>> Christof >>>>> ---- >>>>> InIT Cloud Computing Lab - ICCLab >>>>> Institut of Applied Information Technology - InIT >>>>> Zurich University of Applied Sciences - ZHAW >>>>> School of Engineering >>>>> Phone: +41 58 934 70 63 >>>>> Skype: christof-marti >>>>> >>>>> _______________________________________________ >>>>> Fiware-miwi mailing list >>>>> 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 >>>>> >>>>> Go to www.cybersli.de and enrich your >>>>> presentations! >>>>> >>>>> 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 >>>> >>>> --------------------------------------------------------------------------- >>>> >>> WP13-1-phs.docx> >>> >>> >> >> >> -- >> >> ------------------------------------------------------------------------- >> 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.org >> https://lists.fi-ware.org/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 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From toni at playsign.net Sun Apr 6 12:46:37 2014 From: toni at playsign.net (Toni Alatalo) Date: Sun, 6 Apr 2014 13:46:37 +0300 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: <534112AE.5000905@dfki.de> References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> <534112AE.5000905@dfki.de> Message-ID: ok - I'll plan tomorrow so that can give a shot, thanks for info. and yes missing such a 'standalone' implementation is correct and makes sense -- the implementation of the ECA biz in C++ tundra's TundraProtocolModule etc. is pretty tied to the rest of the system, rendering with Ogre etc. only kNet is separate but that's just the low level networking and not related to the scene-entities. that's something where the standalone sync impl in WebTundra's networking module helps a little now, gives a small simple client lib for generic use (for example the case of sim servers discussed related to SceneAPI) but only for Javascript & WebSockets. Erno has tested it with Node.js recently btw. But Kiara with support for perhaps all relevant langs later and transports etc. is indeed still good to check for next steps and is sure great it already works for reX like things in FiVES. ~Toni On Sun, Apr 6, 2014 at 11:39 AM, Philipp Slusallek wrote: > Hi, > > Feel free to add to it based on the text you wrote. I pass the token to you. > I am not exactly sure when it is supposed to go to the commission -- but > this is very soon. > > Regarding the sync section. On the one hand you are right that realXtend had > a generic protocol embedded in it, but my understanding was that it was > pretty much tied to realXtend and not really available outside of it (even > though one could probably have extracted it with some effort). This is the > point I find important in the sense of offering a generic tool for > synchronization. > > With "pure", I meant "standalone" in the sense of the above. Wording should > be fixed. > > > Best, > > Philipp > > > Am 06.04.2014 09:34, schrieb Toni Alatalo: > >> I've also found it OK when looked previously. Had a couple of things >> that wanted to add then but was traveling and didn't have access to >> Word (actually never normally do unfortunately) so didn't have a way >> to work on them safely. Still seems fine and is good to go if there's >> a hurry - a couple of notes here anyhow in case there's a chance to >> work on it still: >> >> a simple story -- how fi-ware has advanced the state of the art from >> realXtend's perspective: >> >> - starting point: ECA model proposed as a standard for extensible >> virtual worlds a few years back (Alatalo 2011). with a c++ >> implementation that has since matured and is in commercial use >> >> - progress beyond state of art: ECA implemented over web sockets with >> integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same >> proposed platform >> - improvements to the ECA model: >> * mapping between xml3d & reX ECA: allows much more human friendly >> declarative authoring than TXML. integrates nicely to Web when used >> inside HTML. >> * entity hierarchy (not flat like before fi-ware, proper parenting) >> (new in 3.3) >> * proper custom component support from Javascript (new in 3.3) >> * these last points also AFAIK enable complete representation of any >> xml, including html & xml3d in reX ECA -> the generic simple network >> protocol with AttributeChanged etc. messages works to sync those too >> >> In the current document I think a section based on that could be used >> to improve the "Web User Interface Server Core Technologies" - it >> doesn't really make sense to say: "Today, real-time synchronization of >> 3D scenes is limited to specialized applications such as SecondLife >> (secondlife.com) and games engines like Unreal and others. " when we >> already presented a *generic* protocol and platform already 3 years >> ago and have happily used it in business since. Basically what was >> missing before fi-ware was a web/html5 implementation of that. >> >> That 2011 article which introduced the model & platform is this BTW, >> perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model >> for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. >> 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 >> http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html >> >> Here is a mistake (it's realxtend.org, not .com) and I'd consider the >> wording too: "FI-WARE technology is currently based on realXtend >> (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization >> layer (FIVES) has been designed that is based on the FI-WARE Advanced >> Middleware [Byelozyorov 13]" >> >> I'm not sure if 'more pure' is a good choice of words there, >> especially as AFAIK the FiVES implementation is basically identical >> with the realXtend model and implementations. realXtend is also >> completely pure in several ways: the ECA model doesn't specify any >> vocabulary itself (like XML doesn't) but applications or plugins can >> define whatever components they want (like xml3d and realXtend's set >> of basic components do). The networking works automatically for any >> component. reX ECA is independent of the transport layer: in current >> Tundra impls the messaging is handled by the Kristalli / kNet library, >> but any other transport could be used without the application layer >> seeing any changes I think. >> >> I know and sure acknowledge that KIARA is much more ambitious and >> advanced in how it can do the serialisation and automatically choose >> suitable transports etc. but I'm not aware how something on the FiVES >> level would be 'more pure' nor what that'd mean. If it refers to >> generality with regards to application data types etc. it's AFAIK the >> same. >> >> A more informative description of the differences in purity and >> networking might be useful there. At least for me to understand what >> the doc is trying to say :) >> >> Final point: some of these things are already done and being >> delivered, at least glTF and other optimized transfer format support >> (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration >> with the editor / Interface Designer and the basic 3D things - if this >> is to report how we're progressed we could change some of the future >> form 'wills' there to past tense: "FI-WARE technology is based on >> XML3D [Sons 10] and will in future extend the current state-of-the-art >> by (i) adding a much extended content pipeline for integrating 3D >> content, (ii) a 3D asset data base including versioning and different, >> Web-optimized 3D data formats (working with the glTF initiative at >> Khronos), (iii) improved resource management for adaptive, on-demand >> loading and unloading of scene content, (iv) improved developer tools >> for distributed and synchronized Web applications, and (v) >> significantly improving the access to hardware resources for >> computational expensive tasks like AR, animation, and others. The >> 3D-UI technologies will closely tie together with the Interface >> Designer technology that will provide all of the features mentioned >> above in an interactive context directly to users." >> >> Anyhow I think it's also fine already if must go forward. If there is >> still time and you find some of these would be good improvements I can >> give a shot at integrating them in some simple ways tomorrow (can get >> to a compu with ms word then if necessary). >> >> Cheers and thanks for work on the comprehensive doc! >> ~Toni >> >> >> On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek >> wrote: >>> >>> Hi, >>> >>> Sorry for the dealy but I was extremely busy the last few weeks. >>> >>> Here is (what I consider) the final version of the SotA for WP13. I did a >>> final pass over the general text, adding some more references, and adding >>> an >>> extensive Executive Summary that gives and overview of the available >>> technology, puts it in perspective, and sketches how the individual >>> enabler >>> are related to each other.. >>> >>> It would be good if someone did a quick pass over it to spot any typos >>> and >>> such but otherwise it should be ready to go. >>> >>> Hope you like it :-), >>> >>> >>> Philipp >>> >>> Am 17.03.2014 17:14, schrieb Christof Marti: >>> >>>> Hi Philipp >>>> >>>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to >>>> you? >>>> >>>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>>> Deliverable >>>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>>> feedback >>>> for Miguel, to get the release-review process going again. >>>> >>>> Important: In todays WPL/WPA call it was pointed out, that we also have >>>> to >>>> provide a management summary (~ 1 page), containing only the newest >>>> developments. >>>> (For the other chapters this are the changes since last release of the >>>> deliverable) >>>> (For us this could be a compilation from the last part of all the GEs >>>> sota) >>>> >>>> Best regards >>>> Christof >>>> >>>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >>>> : >>>> >>>>> Hi, >>>>> >>>>> I did go through the text and fixed quite a few missing references and >>>>> marked some others that are still missing (please can some of the >>>>> people >>>>> involved in those GEs fix them). >>>>> >>>>> In general, there is a lack of references to previous work in quite a >>>>> few of the GE descriptions. Please follow the model we have done in the >>>>> middleware section and add some more references to previous work and >>>>> then position your work in FI-WARE in relation to that. >>>>> >>>>> >>>>> Best, >>>>> >>>>> Philipp >>>>> >>>>> >>>>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>>>> >>>>>> >>>>>> Hello, >>>>>> >>>>>> I read through the paper in my behalf, and the text seems to be pretty >>>>>> much collected from the text that has been formulated already earlier. >>>>>> I >>>>>> my opinion, it gives an overview of the state of the art and as such I >>>>>> would guess it works as a deliverable for this purpose. However, >>>>>> having >>>>>> said that, I may not know all exact requirements what this deliverable >>>>>> is expected to fulfill. >>>>>> >>>>>> I made minor changes here and there, mainly fixing misspellings and >>>>>> word >>>>>> ordering. The modified document is attached here, with track changes >>>>>> enabled. >>>>>> >>>>>> - jarkko >>>>>> >>>>>> >>>>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>>>> > wrote: >>>>>> >>>>>> Hi Philipp, dear WP13 GE Owners >>>>>> >>>>>> Also due in M36 is an updated version (D.2.6.3) of the "State of >>>>>> the >>>>>> art analysis - emerging technologies" deliverable. The previous >>>>>> release can be found here: >>>>>> >>>>>> >>>>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Idea for all existing WPs is to provide a management summary and >>>>>> do >>>>>> only required updates on the existing chapters. >>>>>> Because there is no Web User Interfaces chapter in the last >>>>>> deliverable I took the content from the FI-Core proposal and >>>>>> tried >>>>>> to put together a WP13 contribution for this deliverable. >>>>>> It was more work than expected, because the writing style in a >>>>>> proposal is a little bit different than for this deliverable. So >>>>>> I >>>>>> would like to ask Philipp (and the respective GE owner for their >>>>>> part) to review the attached document (in change tracking mode), >>>>>> add >>>>>> missing content and in particular also add missing entries in the >>>>>> "Reference" section. >>>>>> >>>>>> Deadline for delivering updates to the coordinator for review >>>>>> is/was >>>>>> today (March 14th). Because of this additional internal review >>>>>> roundtrip, this will not be feasible. >>>>>> If each GE owner can review its 20 to 30 lines and Philipp keeps >>>>>> am >>>>>> eye on the overarching context until Monday noon, the delay would >>>>>> be >>>>>> minimal. >>>>>> >>>>>> Thanks for your contributions. >>>>>> >>>>>> @Miguel, Juanjo: I do not want to release this without the OK of >>>>>> Philipp and the domain experts. >>>>>> >>>>>> Best regards >>>>>> Christof >>>>>> ---- >>>>>> InIT Cloud Computing Lab - ICCLab >>>>>> Institut of Applied Information Technology - InIT >>>>>> Zurich University of Applied Sciences - ZHAW >>>>>> School of Engineering >>>>>> Phone: +41 58 934 70 63 >>>>>> Skype: christof-marti >>>>>> >>>>>> _______________________________________________ >>>>>> Fiware-miwi mailing list >>>>>> 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 >>>>>> >>>>>> Go to www.cybersli.de and enrich your >>>>>> presentations! >>>>>> >>>>>> 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 >>>>> >>>>> >>>>> --------------------------------------------------------------------------- >>>>> >>>> WP13-1-phs.docx> >>>> >>>> >>>> >>> >>> >>> -- >>> >>> ------------------------------------------------------------------------- >>> 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.org >>> https://lists.fi-ware.org/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 > --------------------------------------------------------------------------- From Philipp.Slusallek at dfki.de Sun Apr 6 13:29:22 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Sun, 06 Apr 2014 13:29:22 +0200 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> <534112AE.5000905@dfki.de> Message-ID: <53413A92.4060708@dfki.de> Hi, Great we agree here. BTW, Torsten has started to work on the KIARA implementation in JS and C# (beyond the stubs that we had so far) and we will sync (sic!) this to the initial C/C++ version from Dmitri we have now, so they can all talk to each other efficiently. Best, Philipp Am 06.04.2014 12:46, schrieb Toni Alatalo: > ok - I'll plan tomorrow so that can give a shot, thanks for info. > > and yes missing such a 'standalone' implementation is correct and > makes sense -- the implementation of the ECA biz in C++ tundra's > TundraProtocolModule etc. is pretty tied to the rest of the system, > rendering with Ogre etc. only kNet is separate but that's just the low > level networking and not related to the scene-entities. > > that's something where the standalone sync impl in WebTundra's > networking module helps a little now, gives a small simple client lib > for generic use (for example the case of sim servers discussed related > to SceneAPI) but only for Javascript & WebSockets. Erno has tested it > with Node.js recently btw. But Kiara with support for perhaps all > relevant langs later and transports etc. is indeed still good to check > for next steps and is sure great it already works for reX like things > in FiVES. > > ~Toni > > > On Sun, Apr 6, 2014 at 11:39 AM, Philipp Slusallek > wrote: >> Hi, >> >> Feel free to add to it based on the text you wrote. I pass the token to you. >> I am not exactly sure when it is supposed to go to the commission -- but >> this is very soon. >> >> Regarding the sync section. On the one hand you are right that realXtend had >> a generic protocol embedded in it, but my understanding was that it was >> pretty much tied to realXtend and not really available outside of it (even >> though one could probably have extracted it with some effort). This is the >> point I find important in the sense of offering a generic tool for >> synchronization. >> >> With "pure", I meant "standalone" in the sense of the above. Wording should >> be fixed. >> >> >> Best, >> >> Philipp >> >> >> Am 06.04.2014 09:34, schrieb Toni Alatalo: >> >>> I've also found it OK when looked previously. Had a couple of things >>> that wanted to add then but was traveling and didn't have access to >>> Word (actually never normally do unfortunately) so didn't have a way >>> to work on them safely. Still seems fine and is good to go if there's >>> a hurry - a couple of notes here anyhow in case there's a chance to >>> work on it still: >>> >>> a simple story -- how fi-ware has advanced the state of the art from >>> realXtend's perspective: >>> >>> - starting point: ECA model proposed as a standard for extensible >>> virtual worlds a few years back (Alatalo 2011). with a c++ >>> implementation that has since matured and is in commercial use >>> >>> - progress beyond state of art: ECA implemented over web sockets with >>> integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same >>> proposed platform >>> - improvements to the ECA model: >>> * mapping between xml3d & reX ECA: allows much more human friendly >>> declarative authoring than TXML. integrates nicely to Web when used >>> inside HTML. >>> * entity hierarchy (not flat like before fi-ware, proper parenting) >>> (new in 3.3) >>> * proper custom component support from Javascript (new in 3.3) >>> * these last points also AFAIK enable complete representation of any >>> xml, including html & xml3d in reX ECA -> the generic simple network >>> protocol with AttributeChanged etc. messages works to sync those too >>> >>> In the current document I think a section based on that could be used >>> to improve the "Web User Interface Server Core Technologies" - it >>> doesn't really make sense to say: "Today, real-time synchronization of >>> 3D scenes is limited to specialized applications such as SecondLife >>> (secondlife.com) and games engines like Unreal and others. " when we >>> already presented a *generic* protocol and platform already 3 years >>> ago and have happily used it in business since. Basically what was >>> missing before fi-ware was a web/html5 implementation of that. >>> >>> That 2011 article which introduced the model & platform is this BTW, >>> perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model >>> for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. >>> 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 >>> http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html >>> >>> Here is a mistake (it's realxtend.org, not .com) and I'd consider the >>> wording too: "FI-WARE technology is currently based on realXtend >>> (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization >>> layer (FIVES) has been designed that is based on the FI-WARE Advanced >>> Middleware [Byelozyorov 13]" >>> >>> I'm not sure if 'more pure' is a good choice of words there, >>> especially as AFAIK the FiVES implementation is basically identical >>> with the realXtend model and implementations. realXtend is also >>> completely pure in several ways: the ECA model doesn't specify any >>> vocabulary itself (like XML doesn't) but applications or plugins can >>> define whatever components they want (like xml3d and realXtend's set >>> of basic components do). The networking works automatically for any >>> component. reX ECA is independent of the transport layer: in current >>> Tundra impls the messaging is handled by the Kristalli / kNet library, >>> but any other transport could be used without the application layer >>> seeing any changes I think. >>> >>> I know and sure acknowledge that KIARA is much more ambitious and >>> advanced in how it can do the serialisation and automatically choose >>> suitable transports etc. but I'm not aware how something on the FiVES >>> level would be 'more pure' nor what that'd mean. If it refers to >>> generality with regards to application data types etc. it's AFAIK the >>> same. >>> >>> A more informative description of the differences in purity and >>> networking might be useful there. At least for me to understand what >>> the doc is trying to say :) >>> >>> Final point: some of these things are already done and being >>> delivered, at least glTF and other optimized transfer format support >>> (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration >>> with the editor / Interface Designer and the basic 3D things - if this >>> is to report how we're progressed we could change some of the future >>> form 'wills' there to past tense: "FI-WARE technology is based on >>> XML3D [Sons 10] and will in future extend the current state-of-the-art >>> by (i) adding a much extended content pipeline for integrating 3D >>> content, (ii) a 3D asset data base including versioning and different, >>> Web-optimized 3D data formats (working with the glTF initiative at >>> Khronos), (iii) improved resource management for adaptive, on-demand >>> loading and unloading of scene content, (iv) improved developer tools >>> for distributed and synchronized Web applications, and (v) >>> significantly improving the access to hardware resources for >>> computational expensive tasks like AR, animation, and others. The >>> 3D-UI technologies will closely tie together with the Interface >>> Designer technology that will provide all of the features mentioned >>> above in an interactive context directly to users." >>> >>> Anyhow I think it's also fine already if must go forward. If there is >>> still time and you find some of these would be good improvements I can >>> give a shot at integrating them in some simple ways tomorrow (can get >>> to a compu with ms word then if necessary). >>> >>> Cheers and thanks for work on the comprehensive doc! >>> ~Toni >>> >>> >>> On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek >>> wrote: >>>> >>>> Hi, >>>> >>>> Sorry for the dealy but I was extremely busy the last few weeks. >>>> >>>> Here is (what I consider) the final version of the SotA for WP13. I did a >>>> final pass over the general text, adding some more references, and adding >>>> an >>>> extensive Executive Summary that gives and overview of the available >>>> technology, puts it in perspective, and sketches how the individual >>>> enabler >>>> are related to each other.. >>>> >>>> It would be good if someone did a quick pass over it to spot any typos >>>> and >>>> such but otherwise it should be ready to go. >>>> >>>> Hope you like it :-), >>>> >>>> >>>> Philipp >>>> >>>> Am 17.03.2014 17:14, schrieb Christof Marti: >>>> >>>>> Hi Philipp >>>>> >>>>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to >>>>> you? >>>>> >>>>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>>>> Deliverable >>>>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>>>> feedback >>>>> for Miguel, to get the release-review process going again. >>>>> >>>>> Important: In todays WPL/WPA call it was pointed out, that we also have >>>>> to >>>>> provide a management summary (~ 1 page), containing only the newest >>>>> developments. >>>>> (For the other chapters this are the changes since last release of the >>>>> deliverable) >>>>> (For us this could be a compilation from the last part of all the GEs >>>>> sota) >>>>> >>>>> Best regards >>>>> Christof >>>>> >>>>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >>>>> : >>>>> >>>>>> Hi, >>>>>> >>>>>> I did go through the text and fixed quite a few missing references and >>>>>> marked some others that are still missing (please can some of the >>>>>> people >>>>>> involved in those GEs fix them). >>>>>> >>>>>> In general, there is a lack of references to previous work in quite a >>>>>> few of the GE descriptions. Please follow the model we have done in the >>>>>> middleware section and add some more references to previous work and >>>>>> then position your work in FI-WARE in relation to that. >>>>>> >>>>>> >>>>>> Best, >>>>>> >>>>>> Philipp >>>>>> >>>>>> >>>>>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>>>>> >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I read through the paper in my behalf, and the text seems to be pretty >>>>>>> much collected from the text that has been formulated already earlier. >>>>>>> I >>>>>>> my opinion, it gives an overview of the state of the art and as such I >>>>>>> would guess it works as a deliverable for this purpose. However, >>>>>>> having >>>>>>> said that, I may not know all exact requirements what this deliverable >>>>>>> is expected to fulfill. >>>>>>> >>>>>>> I made minor changes here and there, mainly fixing misspellings and >>>>>>> word >>>>>>> ordering. The modified document is attached here, with track changes >>>>>>> enabled. >>>>>>> >>>>>>> - jarkko >>>>>>> >>>>>>> >>>>>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>>>>> > wrote: >>>>>>> >>>>>>> Hi Philipp, dear WP13 GE Owners >>>>>>> >>>>>>> Also due in M36 is an updated version (D.2.6.3) of the "State of >>>>>>> the >>>>>>> art analysis - emerging technologies" deliverable. The previous >>>>>>> release can be found here: >>>>>>> >>>>>>> >>>>>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Idea for all existing WPs is to provide a management summary and >>>>>>> do >>>>>>> only required updates on the existing chapters. >>>>>>> Because there is no Web User Interfaces chapter in the last >>>>>>> deliverable I took the content from the FI-Core proposal and >>>>>>> tried >>>>>>> to put together a WP13 contribution for this deliverable. >>>>>>> It was more work than expected, because the writing style in a >>>>>>> proposal is a little bit different than for this deliverable. So >>>>>>> I >>>>>>> would like to ask Philipp (and the respective GE owner for their >>>>>>> part) to review the attached document (in change tracking mode), >>>>>>> add >>>>>>> missing content and in particular also add missing entries in the >>>>>>> "Reference" section. >>>>>>> >>>>>>> Deadline for delivering updates to the coordinator for review >>>>>>> is/was >>>>>>> today (March 14th). Because of this additional internal review >>>>>>> roundtrip, this will not be feasible. >>>>>>> If each GE owner can review its 20 to 30 lines and Philipp keeps >>>>>>> am >>>>>>> eye on the overarching context until Monday noon, the delay would >>>>>>> be >>>>>>> minimal. >>>>>>> >>>>>>> Thanks for your contributions. >>>>>>> >>>>>>> @Miguel, Juanjo: I do not want to release this without the OK of >>>>>>> Philipp and the domain experts. >>>>>>> >>>>>>> Best regards >>>>>>> Christof >>>>>>> ---- >>>>>>> InIT Cloud Computing Lab - ICCLab >>>>>>> Institut of Applied Information Technology - InIT >>>>>>> Zurich University of Applied Sciences - ZHAW >>>>>>> School of Engineering >>>>>>> Phone: +41 58 934 70 63 >>>>>>> Skype: christof-marti >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Fiware-miwi mailing list >>>>>>> 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 >>>>>>> >>>>>>> Go to www.cybersli.de and enrich your >>>>>>> presentations! >>>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------------- >>>>>> >>>>> WP13-1-phs.docx> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> ------------------------------------------------------------------------- >>>> 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.org >>>> https://lists.fi-ware.org/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 >> --------------------------------------------------------------------------- -- ------------------------------------------------------------------------- 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: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Mon Apr 7 08:14:41 2014 From: mach at zhaw.ch (Christof Marti) Date: Mon, 7 Apr 2014 08:14:41 +0200 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: <6cffefa5d6a3416cab7c63467f336f74@SRV-MAIL-001.zhaw.ch> References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> <534112AE.5000905@dfki.de> <6cffefa5d6a3416cab7c63467f336f74@SRV-MAIL-001.zhaw.ch> Message-ID: Hi Toni, hi Philipp Thanks for the work on your weekend. Toni, please let me know, when you are done. Miguel and Manuel are waiting for it and I would like to deliver it today, finally. Best Regards Christof Am 06.04.2014 um 12:46 schrieb Toni Alatalo : > ok - I'll plan tomorrow so that can give a shot, thanks for info. > > and yes missing such a 'standalone' implementation is correct and > makes sense -- the implementation of the ECA biz in C++ tundra's > TundraProtocolModule etc. is pretty tied to the rest of the system, > rendering with Ogre etc. only kNet is separate but that's just the low > level networking and not related to the scene-entities. > > that's something where the standalone sync impl in WebTundra's > networking module helps a little now, gives a small simple client lib > for generic use (for example the case of sim servers discussed related > to SceneAPI) but only for Javascript & WebSockets. Erno has tested it > with Node.js recently btw. But Kiara with support for perhaps all > relevant langs later and transports etc. is indeed still good to check > for next steps and is sure great it already works for reX like things > in FiVES. > > ~Toni > > > On Sun, Apr 6, 2014 at 11:39 AM, Philipp Slusallek > wrote: >> Hi, >> >> Feel free to add to it based on the text you wrote. I pass the token to you. >> I am not exactly sure when it is supposed to go to the commission -- but >> this is very soon. >> >> Regarding the sync section. On the one hand you are right that realXtend had >> a generic protocol embedded in it, but my understanding was that it was >> pretty much tied to realXtend and not really available outside of it (even >> though one could probably have extracted it with some effort). This is the >> point I find important in the sense of offering a generic tool for >> synchronization. >> >> With "pure", I meant "standalone" in the sense of the above. Wording should >> be fixed. >> >> >> Best, >> >> Philipp >> >> >> Am 06.04.2014 09:34, schrieb Toni Alatalo: >> >>> I've also found it OK when looked previously. Had a couple of things >>> that wanted to add then but was traveling and didn't have access to >>> Word (actually never normally do unfortunately) so didn't have a way >>> to work on them safely. Still seems fine and is good to go if there's >>> a hurry - a couple of notes here anyhow in case there's a chance to >>> work on it still: >>> >>> a simple story -- how fi-ware has advanced the state of the art from >>> realXtend's perspective: >>> >>> - starting point: ECA model proposed as a standard for extensible >>> virtual worlds a few years back (Alatalo 2011). with a c++ >>> implementation that has since matured and is in commercial use >>> >>> - progress beyond state of art: ECA implemented over web sockets with >>> integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same >>> proposed platform >>> - improvements to the ECA model: >>> * mapping between xml3d & reX ECA: allows much more human friendly >>> declarative authoring than TXML. integrates nicely to Web when used >>> inside HTML. >>> * entity hierarchy (not flat like before fi-ware, proper parenting) >>> (new in 3.3) >>> * proper custom component support from Javascript (new in 3.3) >>> * these last points also AFAIK enable complete representation of any >>> xml, including html & xml3d in reX ECA -> the generic simple network >>> protocol with AttributeChanged etc. messages works to sync those too >>> >>> In the current document I think a section based on that could be used >>> to improve the "Web User Interface Server Core Technologies" - it >>> doesn't really make sense to say: "Today, real-time synchronization of >>> 3D scenes is limited to specialized applications such as SecondLife >>> (secondlife.com) and games engines like Unreal and others. " when we >>> already presented a *generic* protocol and platform already 3 years >>> ago and have happily used it in business since. Basically what was >>> missing before fi-ware was a web/html5 implementation of that. >>> >>> That 2011 article which introduced the model & platform is this BTW, >>> perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model >>> for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. >>> 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 >>> http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html >>> >>> Here is a mistake (it's realxtend.org, not .com) and I'd consider the >>> wording too: "FI-WARE technology is currently based on realXtend >>> (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization >>> layer (FIVES) has been designed that is based on the FI-WARE Advanced >>> Middleware [Byelozyorov 13]" >>> >>> I'm not sure if 'more pure' is a good choice of words there, >>> especially as AFAIK the FiVES implementation is basically identical >>> with the realXtend model and implementations. realXtend is also >>> completely pure in several ways: the ECA model doesn't specify any >>> vocabulary itself (like XML doesn't) but applications or plugins can >>> define whatever components they want (like xml3d and realXtend's set >>> of basic components do). The networking works automatically for any >>> component. reX ECA is independent of the transport layer: in current >>> Tundra impls the messaging is handled by the Kristalli / kNet library, >>> but any other transport could be used without the application layer >>> seeing any changes I think. >>> >>> I know and sure acknowledge that KIARA is much more ambitious and >>> advanced in how it can do the serialisation and automatically choose >>> suitable transports etc. but I'm not aware how something on the FiVES >>> level would be 'more pure' nor what that'd mean. If it refers to >>> generality with regards to application data types etc. it's AFAIK the >>> same. >>> >>> A more informative description of the differences in purity and >>> networking might be useful there. At least for me to understand what >>> the doc is trying to say :) >>> >>> Final point: some of these things are already done and being >>> delivered, at least glTF and other optimized transfer format support >>> (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration >>> with the editor / Interface Designer and the basic 3D things - if this >>> is to report how we're progressed we could change some of the future >>> form 'wills' there to past tense: "FI-WARE technology is based on >>> XML3D [Sons 10] and will in future extend the current state-of-the-art >>> by (i) adding a much extended content pipeline for integrating 3D >>> content, (ii) a 3D asset data base including versioning and different, >>> Web-optimized 3D data formats (working with the glTF initiative at >>> Khronos), (iii) improved resource management for adaptive, on-demand >>> loading and unloading of scene content, (iv) improved developer tools >>> for distributed and synchronized Web applications, and (v) >>> significantly improving the access to hardware resources for >>> computational expensive tasks like AR, animation, and others. The >>> 3D-UI technologies will closely tie together with the Interface >>> Designer technology that will provide all of the features mentioned >>> above in an interactive context directly to users." >>> >>> Anyhow I think it's also fine already if must go forward. If there is >>> still time and you find some of these would be good improvements I can >>> give a shot at integrating them in some simple ways tomorrow (can get >>> to a compu with ms word then if necessary). >>> >>> Cheers and thanks for work on the comprehensive doc! >>> ~Toni >>> >>> >>> On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek >>> wrote: >>>> >>>> Hi, >>>> >>>> Sorry for the dealy but I was extremely busy the last few weeks. >>>> >>>> Here is (what I consider) the final version of the SotA for WP13. I did a >>>> final pass over the general text, adding some more references, and adding >>>> an >>>> extensive Executive Summary that gives and overview of the available >>>> technology, puts it in perspective, and sketches how the individual >>>> enabler >>>> are related to each other.. >>>> >>>> It would be good if someone did a quick pass over it to spot any typos >>>> and >>>> such but otherwise it should be ready to go. >>>> >>>> Hope you like it :-), >>>> >>>> >>>> Philipp >>>> >>>> Am 17.03.2014 17:14, schrieb Christof Marti: >>>> >>>>> Hi Philipp >>>>> >>>>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution to >>>>> you? >>>>> >>>>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>>>> Deliverable >>>>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>>>> feedback >>>>> for Miguel, to get the release-review process going again. >>>>> >>>>> Important: In todays WPL/WPA call it was pointed out, that we also have >>>>> to >>>>> provide a management summary (~ 1 page), containing only the newest >>>>> developments. >>>>> (For the other chapters this are the changes since last release of the >>>>> deliverable) >>>>> (For us this could be a compilation from the last part of all the GEs >>>>> sota) >>>>> >>>>> Best regards >>>>> Christof >>>>> >>>>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >>>>> : >>>>> >>>>>> Hi, >>>>>> >>>>>> I did go through the text and fixed quite a few missing references and >>>>>> marked some others that are still missing (please can some of the >>>>>> people >>>>>> involved in those GEs fix them). >>>>>> >>>>>> In general, there is a lack of references to previous work in quite a >>>>>> few of the GE descriptions. Please follow the model we have done in the >>>>>> middleware section and add some more references to previous work and >>>>>> then position your work in FI-WARE in relation to that. >>>>>> >>>>>> >>>>>> Best, >>>>>> >>>>>> Philipp >>>>>> >>>>>> >>>>>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>>>>> >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I read through the paper in my behalf, and the text seems to be pretty >>>>>>> much collected from the text that has been formulated already earlier. >>>>>>> I >>>>>>> my opinion, it gives an overview of the state of the art and as such I >>>>>>> would guess it works as a deliverable for this purpose. However, >>>>>>> having >>>>>>> said that, I may not know all exact requirements what this deliverable >>>>>>> is expected to fulfill. >>>>>>> >>>>>>> I made minor changes here and there, mainly fixing misspellings and >>>>>>> word >>>>>>> ordering. The modified document is attached here, with track changes >>>>>>> enabled. >>>>>>> >>>>>>> - jarkko >>>>>>> >>>>>>> >>>>>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>>>>> > wrote: >>>>>>> >>>>>>> Hi Philipp, dear WP13 GE Owners >>>>>>> >>>>>>> Also due in M36 is an updated version (D.2.6.3) of the "State of >>>>>>> the >>>>>>> art analysis - emerging technologies" deliverable. The previous >>>>>>> release can be found here: >>>>>>> >>>>>>> >>>>>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Idea for all existing WPs is to provide a management summary and >>>>>>> do >>>>>>> only required updates on the existing chapters. >>>>>>> Because there is no Web User Interfaces chapter in the last >>>>>>> deliverable I took the content from the FI-Core proposal and >>>>>>> tried >>>>>>> to put together a WP13 contribution for this deliverable. >>>>>>> It was more work than expected, because the writing style in a >>>>>>> proposal is a little bit different than for this deliverable. So >>>>>>> I >>>>>>> would like to ask Philipp (and the respective GE owner for their >>>>>>> part) to review the attached document (in change tracking mode), >>>>>>> add >>>>>>> missing content and in particular also add missing entries in the >>>>>>> "Reference" section. >>>>>>> >>>>>>> Deadline for delivering updates to the coordinator for review >>>>>>> is/was >>>>>>> today (March 14th). Because of this additional internal review >>>>>>> roundtrip, this will not be feasible. >>>>>>> If each GE owner can review its 20 to 30 lines and Philipp keeps >>>>>>> am >>>>>>> eye on the overarching context until Monday noon, the delay would >>>>>>> be >>>>>>> minimal. >>>>>>> >>>>>>> Thanks for your contributions. >>>>>>> >>>>>>> @Miguel, Juanjo: I do not want to release this without the OK of >>>>>>> Philipp and the domain experts. >>>>>>> >>>>>>> Best regards >>>>>>> Christof >>>>>>> ---- >>>>>>> InIT Cloud Computing Lab - ICCLab >>>>>>> Institut of Applied Information Technology - InIT >>>>>>> Zurich University of Applied Sciences - ZHAW >>>>>>> School of Engineering >>>>>>> Phone: +41 58 934 70 63 >>>>>>> Skype: christof-marti >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Fiware-miwi mailing list >>>>>>> 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 >>>>>>> >>>>>>> Go to www.cybersli.de and enrich your >>>>>>> presentations! >>>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------------- >>>>>> >>>>> WP13-1-phs.docx> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> ------------------------------------------------------------------------- >>>> 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.org >>>> https://lists.fi-ware.org/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 >> --------------------------------------------------------------------------- From toni at playsign.net Mon Apr 7 08:45:37 2014 From: toni at playsign.net (Toni Alatalo) Date: Mon, 7 Apr 2014 09:45:37 +0300 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: <53413A92.4060708@dfki.de> References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> <534112AE.5000905@dfki.de> <53413A92.4060708@dfki.de> Message-ID: I did some edits to the Sync section along the lines of the comments that posted yesterday, using MS Word 2010 with track changes on. Also added a ref that had gone missing to the refs list at the end (Dahl 13) Cheers, ~Toni On Sun, Apr 6, 2014 at 2:29 PM, Philipp Slusallek wrote: > Hi, > > Great we agree here. > > BTW, Torsten has started to work on the KIARA implementation in JS and C# > (beyond the stubs that we had so far) and we will sync (sic!) this to the > initial C/C++ version from Dmitri we have now, so they can all talk to each > other efficiently. > > > Best, > > Philipp > > Am 06.04.2014 12:46, schrieb Toni Alatalo: > >> ok - I'll plan tomorrow so that can give a shot, thanks for info. >> >> and yes missing such a 'standalone' implementation is correct and >> makes sense -- the implementation of the ECA biz in C++ tundra's >> TundraProtocolModule etc. is pretty tied to the rest of the system, >> rendering with Ogre etc. only kNet is separate but that's just the low >> level networking and not related to the scene-entities. >> >> that's something where the standalone sync impl in WebTundra's >> networking module helps a little now, gives a small simple client lib >> for generic use (for example the case of sim servers discussed related >> to SceneAPI) but only for Javascript & WebSockets. Erno has tested it >> with Node.js recently btw. But Kiara with support for perhaps all >> relevant langs later and transports etc. is indeed still good to check >> for next steps and is sure great it already works for reX like things >> in FiVES. >> >> ~Toni >> >> >> On Sun, Apr 6, 2014 at 11:39 AM, Philipp Slusallek >> wrote: >>> >>> Hi, >>> >>> Feel free to add to it based on the text you wrote. I pass the token to >>> you. >>> I am not exactly sure when it is supposed to go to the commission -- but >>> this is very soon. >>> >>> Regarding the sync section. On the one hand you are right that realXtend >>> had >>> a generic protocol embedded in it, but my understanding was that it was >>> pretty much tied to realXtend and not really available outside of it >>> (even >>> though one could probably have extracted it with some effort). This is >>> the >>> point I find important in the sense of offering a generic tool for >>> synchronization. >>> >>> With "pure", I meant "standalone" in the sense of the above. Wording >>> should >>> be fixed. >>> >>> >>> Best, >>> >>> Philipp >>> >>> >>> Am 06.04.2014 09:34, schrieb Toni Alatalo: >>> >>>> I've also found it OK when looked previously. Had a couple of things >>>> that wanted to add then but was traveling and didn't have access to >>>> Word (actually never normally do unfortunately) so didn't have a way >>>> to work on them safely. Still seems fine and is good to go if there's >>>> a hurry - a couple of notes here anyhow in case there's a chance to >>>> work on it still: >>>> >>>> a simple story -- how fi-ware has advanced the state of the art from >>>> realXtend's perspective: >>>> >>>> - starting point: ECA model proposed as a standard for extensible >>>> virtual worlds a few years back (Alatalo 2011). with a c++ >>>> implementation that has since matured and is in commercial use >>>> >>>> - progress beyond state of art: ECA implemented over web sockets with >>>> integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same >>>> proposed platform >>>> - improvements to the ECA model: >>>> * mapping between xml3d & reX ECA: allows much more human friendly >>>> declarative authoring than TXML. integrates nicely to Web when used >>>> inside HTML. >>>> * entity hierarchy (not flat like before fi-ware, proper parenting) >>>> (new in 3.3) >>>> * proper custom component support from Javascript (new in 3.3) >>>> * these last points also AFAIK enable complete representation of any >>>> xml, including html & xml3d in reX ECA -> the generic simple network >>>> protocol with AttributeChanged etc. messages works to sync those too >>>> >>>> In the current document I think a section based on that could be used >>>> to improve the "Web User Interface Server Core Technologies" - it >>>> doesn't really make sense to say: "Today, real-time synchronization of >>>> 3D scenes is limited to specialized applications such as SecondLife >>>> (secondlife.com) and games engines like Unreal and others. " when we >>>> already presented a *generic* protocol and platform already 3 years >>>> ago and have happily used it in business since. Basically what was >>>> missing before fi-ware was a web/html5 implementation of that. >>>> >>>> That 2011 article which introduced the model & platform is this BTW, >>>> perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model >>>> for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. >>>> 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 >>>> http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html >>>> >>>> Here is a mistake (it's realxtend.org, not .com) and I'd consider the >>>> wording too: "FI-WARE technology is currently based on realXtend >>>> (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization >>>> layer (FIVES) has been designed that is based on the FI-WARE Advanced >>>> Middleware [Byelozyorov 13]" >>>> >>>> I'm not sure if 'more pure' is a good choice of words there, >>>> especially as AFAIK the FiVES implementation is basically identical >>>> with the realXtend model and implementations. realXtend is also >>>> completely pure in several ways: the ECA model doesn't specify any >>>> vocabulary itself (like XML doesn't) but applications or plugins can >>>> define whatever components they want (like xml3d and realXtend's set >>>> of basic components do). The networking works automatically for any >>>> component. reX ECA is independent of the transport layer: in current >>>> Tundra impls the messaging is handled by the Kristalli / kNet library, >>>> but any other transport could be used without the application layer >>>> seeing any changes I think. >>>> >>>> I know and sure acknowledge that KIARA is much more ambitious and >>>> advanced in how it can do the serialisation and automatically choose >>>> suitable transports etc. but I'm not aware how something on the FiVES >>>> level would be 'more pure' nor what that'd mean. If it refers to >>>> generality with regards to application data types etc. it's AFAIK the >>>> same. >>>> >>>> A more informative description of the differences in purity and >>>> networking might be useful there. At least for me to understand what >>>> the doc is trying to say :) >>>> >>>> Final point: some of these things are already done and being >>>> delivered, at least glTF and other optimized transfer format support >>>> (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration >>>> with the editor / Interface Designer and the basic 3D things - if this >>>> is to report how we're progressed we could change some of the future >>>> form 'wills' there to past tense: "FI-WARE technology is based on >>>> XML3D [Sons 10] and will in future extend the current state-of-the-art >>>> by (i) adding a much extended content pipeline for integrating 3D >>>> content, (ii) a 3D asset data base including versioning and different, >>>> Web-optimized 3D data formats (working with the glTF initiative at >>>> Khronos), (iii) improved resource management for adaptive, on-demand >>>> loading and unloading of scene content, (iv) improved developer tools >>>> for distributed and synchronized Web applications, and (v) >>>> significantly improving the access to hardware resources for >>>> computational expensive tasks like AR, animation, and others. The >>>> 3D-UI technologies will closely tie together with the Interface >>>> Designer technology that will provide all of the features mentioned >>>> above in an interactive context directly to users." >>>> >>>> Anyhow I think it's also fine already if must go forward. If there is >>>> still time and you find some of these would be good improvements I can >>>> give a shot at integrating them in some simple ways tomorrow (can get >>>> to a compu with ms word then if necessary). >>>> >>>> Cheers and thanks for work on the comprehensive doc! >>>> ~Toni >>>> >>>> >>>> On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek >>>> wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> Sorry for the dealy but I was extremely busy the last few weeks. >>>>> >>>>> Here is (what I consider) the final version of the SotA for WP13. I did >>>>> a >>>>> final pass over the general text, adding some more references, and >>>>> adding >>>>> an >>>>> extensive Executive Summary that gives and overview of the available >>>>> technology, puts it in perspective, and sketches how the individual >>>>> enabler >>>>> are related to each other.. >>>>> >>>>> It would be good if someone did a quick pass over it to spot any typos >>>>> and >>>>> such but otherwise it should be ready to go. >>>>> >>>>> Hope you like it :-), >>>>> >>>>> >>>>> Philipp >>>>> >>>>> Am 17.03.2014 17:14, schrieb Christof Marti: >>>>> >>>>>> Hi Philipp >>>>>> >>>>>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution >>>>>> to >>>>>> you? >>>>>> >>>>>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>>>>> Deliverable >>>>>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>>>>> feedback >>>>>> for Miguel, to get the release-review process going again. >>>>>> >>>>>> Important: In todays WPL/WPA call it was pointed out, that we also >>>>>> have >>>>>> to >>>>>> provide a management summary (~ 1 page), containing only the newest >>>>>> developments. >>>>>> (For the other chapters this are the changes since last release of the >>>>>> deliverable) >>>>>> (For us this could be a compilation from the last part of all the GEs >>>>>> sota) >>>>>> >>>>>> Best regards >>>>>> Christof >>>>>> >>>>>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >>>>>> : >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I did go through the text and fixed quite a few missing references >>>>>>> and >>>>>>> marked some others that are still missing (please can some of the >>>>>>> people >>>>>>> involved in those GEs fix them). >>>>>>> >>>>>>> In general, there is a lack of references to previous work in quite a >>>>>>> few of the GE descriptions. Please follow the model we have done in >>>>>>> the >>>>>>> middleware section and add some more references to previous work and >>>>>>> then position your work in FI-WARE in relation to that. >>>>>>> >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Philipp >>>>>>> >>>>>>> >>>>>>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I read through the paper in my behalf, and the text seems to be >>>>>>>> pretty >>>>>>>> much collected from the text that has been formulated already >>>>>>>> earlier. >>>>>>>> I >>>>>>>> my opinion, it gives an overview of the state of the art and as such >>>>>>>> I >>>>>>>> would guess it works as a deliverable for this purpose. However, >>>>>>>> having >>>>>>>> said that, I may not know all exact requirements what this >>>>>>>> deliverable >>>>>>>> is expected to fulfill. >>>>>>>> >>>>>>>> I made minor changes here and there, mainly fixing misspellings and >>>>>>>> word >>>>>>>> ordering. The modified document is attached here, with track changes >>>>>>>> enabled. >>>>>>>> >>>>>>>> - jarkko >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>>>>>>> >>>>>>> > wrote: >>>>>>>> >>>>>>>> Hi Philipp, dear WP13 GE Owners >>>>>>>> >>>>>>>> Also due in M36 is an updated version (D.2.6.3) of the "State >>>>>>>> of >>>>>>>> the >>>>>>>> art analysis - emerging technologies" deliverable. The >>>>>>>> previous >>>>>>>> release can be found here: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Idea for all existing WPs is to provide a management summary >>>>>>>> and >>>>>>>> do >>>>>>>> only required updates on the existing chapters. >>>>>>>> Because there is no Web User Interfaces chapter in the last >>>>>>>> deliverable I took the content from the FI-Core proposal and >>>>>>>> tried >>>>>>>> to put together a WP13 contribution for this deliverable. >>>>>>>> It was more work than expected, because the writing style in a >>>>>>>> proposal is a little bit different than for this deliverable. >>>>>>>> So >>>>>>>> I >>>>>>>> would like to ask Philipp (and the respective GE owner for >>>>>>>> their >>>>>>>> part) to review the attached document (in change tracking >>>>>>>> mode), >>>>>>>> add >>>>>>>> missing content and in particular also add missing entries in >>>>>>>> the >>>>>>>> "Reference" section. >>>>>>>> >>>>>>>> Deadline for delivering updates to the coordinator for review >>>>>>>> is/was >>>>>>>> today (March 14th). Because of this additional internal review >>>>>>>> roundtrip, this will not be feasible. >>>>>>>> If each GE owner can review its 20 to 30 lines and Philipp >>>>>>>> keeps >>>>>>>> am >>>>>>>> eye on the overarching context until Monday noon, the delay >>>>>>>> would >>>>>>>> be >>>>>>>> minimal. >>>>>>>> >>>>>>>> Thanks for your contributions. >>>>>>>> >>>>>>>> @Miguel, Juanjo: I do not want to release this without the OK >>>>>>>> of >>>>>>>> Philipp and the domain experts. >>>>>>>> >>>>>>>> Best regards >>>>>>>> Christof >>>>>>>> ---- >>>>>>>> InIT Cloud Computing Lab - ICCLab >>>>>>>> Institut of Applied Information Technology - InIT >>>>>>>> Zurich University of Applied Sciences - ZHAW >>>>>>>> School of Engineering >>>>>>>> Phone: +41 58 934 70 63 >>>>>>>> Skype: christof-marti >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Fiware-miwi mailing list >>>>>>>> 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 >>>>>>>> >>>>>>>> Go to www.cybersli.de and enrich your >>>>>>>> presentations! >>>>>>>> >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------------- >>>>>>> >>>>>> WP13-1-phs.docx> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> 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.org >>>>> https://lists.fi-ware.org/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 >>> >>> --------------------------------------------------------------------------- > > > > -- > > ------------------------------------------------------------------------- > 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: D.2.6.3 State of the Art Analysis - Emerging Technologies - WP13-ta.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 444612 bytes Desc: not available URL: From toni at playsign.net Mon Apr 7 08:55:53 2014 From: toni at playsign.net (Toni Alatalo) Date: Mon, 7 Apr 2014 09:55:53 +0300 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution (internal review roundtrip) In-Reply-To: References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> <534112AE.5000905@dfki.de> <53413A92.4060708@dfki.de> Message-ID: oops sorry there was a editing mistake leading to a typo, fixed in here. -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.3 State of the Art Analysis - Emerging Technologies - WP13-ta2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 447534 bytes Desc: not available URL: From mach at zhaw.ch Mon Apr 7 10:24:31 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Mon, 7 Apr 2014 08:24:31 +0000 Subject: [Fiware-miwi] D.2.6.3 SotA Analysis - Emerging technologies WP13 contribution In-Reply-To: <43957df15cdf4b029e09c7af30dc6804@SRV-MAIL-001.zhaw.ch> References: <73EA1F59-A252-4548-9890-5D66EA566C55@zhaw.ch> <651885cad7d242269b82641bda628eb6@SRV-MAIL-001.zhaw.ch> <785BCA63-A4ED-4E3D-8CFE-A2A7CF3A573B@zhaw.ch> <5340F1F0.6040404@dfki.de> <534112AE.5000905@dfki.de> <53413A92.4060708@dfki.de> <43957df15cdf4b029e09c7af30dc6804@SRV-MAIL-001.zhaw.ch> Message-ID: <9F6586F0-344D-46A5-88A8-418670D94E08@zhaw.ch> Hi Miguel, hi Manuel Attached the WP13 contribution for D.2.6.3 SotA Analysis - Emerging technologies @Toni, @Philipp: I did a final check and fixed some References table entries (each reference in its own row) Best regards Christof Am 07.04.2014 um 08:45 schrieb Toni Alatalo : > I did some edits to the Sync section along the lines of the comments > that posted yesterday, using MS Word 2010 with track changes on. Also > added a ref that had gone missing to the refs list at the end (Dahl > 13) > > Cheers, > ~Toni > > On Sun, Apr 6, 2014 at 2:29 PM, Philipp Slusallek > wrote: >> Hi, >> >> Great we agree here. >> >> BTW, Torsten has started to work on the KIARA implementation in JS and C# >> (beyond the stubs that we had so far) and we will sync (sic!) this to the >> initial C/C++ version from Dmitri we have now, so they can all talk to each >> other efficiently. >> >> >> Best, >> >> Philipp >> >> Am 06.04.2014 12:46, schrieb Toni Alatalo: >> >>> ok - I'll plan tomorrow so that can give a shot, thanks for info. >>> >>> and yes missing such a 'standalone' implementation is correct and >>> makes sense -- the implementation of the ECA biz in C++ tundra's >>> TundraProtocolModule etc. is pretty tied to the rest of the system, >>> rendering with Ogre etc. only kNet is separate but that's just the low >>> level networking and not related to the scene-entities. >>> >>> that's something where the standalone sync impl in WebTundra's >>> networking module helps a little now, gives a small simple client lib >>> for generic use (for example the case of sim servers discussed related >>> to SceneAPI) but only for Javascript & WebSockets. Erno has tested it >>> with Node.js recently btw. But Kiara with support for perhaps all >>> relevant langs later and transports etc. is indeed still good to check >>> for next steps and is sure great it already works for reX like things >>> in FiVES. >>> >>> ~Toni >>> >>> >>> On Sun, Apr 6, 2014 at 11:39 AM, Philipp Slusallek >>> wrote: >>>> >>>> Hi, >>>> >>>> Feel free to add to it based on the text you wrote. I pass the token to >>>> you. >>>> I am not exactly sure when it is supposed to go to the commission -- but >>>> this is very soon. >>>> >>>> Regarding the sync section. On the one hand you are right that realXtend >>>> had >>>> a generic protocol embedded in it, but my understanding was that it was >>>> pretty much tied to realXtend and not really available outside of it >>>> (even >>>> though one could probably have extracted it with some effort). This is >>>> the >>>> point I find important in the sense of offering a generic tool for >>>> synchronization. >>>> >>>> With "pure", I meant "standalone" in the sense of the above. Wording >>>> should >>>> be fixed. >>>> >>>> >>>> Best, >>>> >>>> Philipp >>>> >>>> >>>> Am 06.04.2014 09:34, schrieb Toni Alatalo: >>>> >>>>> I've also found it OK when looked previously. Had a couple of things >>>>> that wanted to add then but was traveling and didn't have access to >>>>> Word (actually never normally do unfortunately) so didn't have a way >>>>> to work on them safely. Still seems fine and is good to go if there's >>>>> a hurry - a couple of notes here anyhow in case there's a chance to >>>>> work on it still: >>>>> >>>>> a simple story -- how fi-ware has advanced the state of the art from >>>>> realXtend's perspective: >>>>> >>>>> - starting point: ECA model proposed as a standard for extensible >>>>> virtual worlds a few years back (Alatalo 2011). with a c++ >>>>> implementation that has since matured and is in commercial use >>>>> >>>>> - progress beyond state of art: ECA implemented over web sockets with >>>>> integrated 3D-UI with WebGL -> Web / HTML5 implementation of the same >>>>> proposed platform >>>>> - improvements to the ECA model: >>>>> * mapping between xml3d & reX ECA: allows much more human friendly >>>>> declarative authoring than TXML. integrates nicely to Web when used >>>>> inside HTML. >>>>> * entity hierarchy (not flat like before fi-ware, proper parenting) >>>>> (new in 3.3) >>>>> * proper custom component support from Javascript (new in 3.3) >>>>> * these last points also AFAIK enable complete representation of any >>>>> xml, including html & xml3d in reX ECA -> the generic simple network >>>>> protocol with AttributeChanged etc. messages works to sync those too >>>>> >>>>> In the current document I think a section based on that could be used >>>>> to improve the "Web User Interface Server Core Technologies" - it >>>>> doesn't really make sense to say: "Today, real-time synchronization of >>>>> 3D scenes is limited to specialized applications such as SecondLife >>>>> (secondlife.com) and games engines like Unreal and others. " when we >>>>> already presented a *generic* protocol and platform already 3 years >>>>> ago and have happily used it in business since. Basically what was >>>>> missing before fi-ware was a web/html5 implementation of that. >>>>> >>>>> That 2011 article which introduced the model & platform is this BTW, >>>>> perhaps good to add to refs: Toni Alatalo, "An Entity-Component Model >>>>> for Extensible Virtual Worlds," IEEE Internet Computing, vol. 15, no. >>>>> 5, pp. 30-37, Sept.-Oct. 2011, doi:10.1109/MIC.2011.82 >>>>> http://www.computer.org/csdl/mags/ic/2011/05/mic2011050030-abs.html >>>>> >>>>> Here is a mistake (it's realxtend.org, not .com) and I'd consider the >>>>> wording too: "FI-WARE technology is currently based on realXtend >>>>> (realXtend.com) [Dahl 13]. Additionally, an more pure synchronization >>>>> layer (FIVES) has been designed that is based on the FI-WARE Advanced >>>>> Middleware [Byelozyorov 13]" >>>>> >>>>> I'm not sure if 'more pure' is a good choice of words there, >>>>> especially as AFAIK the FiVES implementation is basically identical >>>>> with the realXtend model and implementations. realXtend is also >>>>> completely pure in several ways: the ECA model doesn't specify any >>>>> vocabulary itself (like XML doesn't) but applications or plugins can >>>>> define whatever components they want (like xml3d and realXtend's set >>>>> of basic components do). The networking works automatically for any >>>>> component. reX ECA is independent of the transport layer: in current >>>>> Tundra impls the messaging is handled by the Kristalli / kNet library, >>>>> but any other transport could be used without the application layer >>>>> seeing any changes I think. >>>>> >>>>> I know and sure acknowledge that KIARA is much more ambitious and >>>>> advanced in how it can do the serialisation and automatically choose >>>>> suitable transports etc. but I'm not aware how something on the FiVES >>>>> level would be 'more pure' nor what that'd mean. If it refers to >>>>> generality with regards to application data types etc. it's AFAIK the >>>>> same. >>>>> >>>>> A more informative description of the differences in purity and >>>>> networking might be useful there. At least for me to understand what >>>>> the doc is trying to say :) >>>>> >>>>> Final point: some of these things are already done and being >>>>> delivered, at least glTF and other optimized transfer format support >>>>> (glTF demo in WebTundra demos, CTM also in xml3d.js) & integration >>>>> with the editor / Interface Designer and the basic 3D things - if this >>>>> is to report how we're progressed we could change some of the future >>>>> form 'wills' there to past tense: "FI-WARE technology is based on >>>>> XML3D [Sons 10] and will in future extend the current state-of-the-art >>>>> by (i) adding a much extended content pipeline for integrating 3D >>>>> content, (ii) a 3D asset data base including versioning and different, >>>>> Web-optimized 3D data formats (working with the glTF initiative at >>>>> Khronos), (iii) improved resource management for adaptive, on-demand >>>>> loading and unloading of scene content, (iv) improved developer tools >>>>> for distributed and synchronized Web applications, and (v) >>>>> significantly improving the access to hardware resources for >>>>> computational expensive tasks like AR, animation, and others. The >>>>> 3D-UI technologies will closely tie together with the Interface >>>>> Designer technology that will provide all of the features mentioned >>>>> above in an interactive context directly to users." >>>>> >>>>> Anyhow I think it's also fine already if must go forward. If there is >>>>> still time and you find some of these would be good improvements I can >>>>> give a shot at integrating them in some simple ways tomorrow (can get >>>>> to a compu with ms word then if necessary). >>>>> >>>>> Cheers and thanks for work on the comprehensive doc! >>>>> ~Toni >>>>> >>>>> >>>>> On Sun, Apr 6, 2014 at 9:19 AM, Philipp Slusallek >>>>> wrote: >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> Sorry for the dealy but I was extremely busy the last few weeks. >>>>>> >>>>>> Here is (what I consider) the final version of the SotA for WP13. I did >>>>>> a >>>>>> final pass over the general text, adding some more references, and >>>>>> adding >>>>>> an >>>>>> extensive Executive Summary that gives and overview of the available >>>>>> technology, puts it in perspective, and sketches how the individual >>>>>> enabler >>>>>> are related to each other.. >>>>>> >>>>>> It would be good if someone did a quick pass over it to spot any typos >>>>>> and >>>>>> such but otherwise it should be ready to go. >>>>>> >>>>>> Hope you like it :-), >>>>>> >>>>>> >>>>>> Philipp >>>>>> >>>>>> Am 17.03.2014 17:14, schrieb Christof Marti: >>>>>> >>>>>>> Hi Philipp >>>>>>> >>>>>>> Can I delegate the finalization of the D.2.6.3 WP13 SoTA contribution >>>>>>> to >>>>>>> you? >>>>>>> >>>>>>> I am very busy going through OpenSpecs v3 and create the D.13.1.3 >>>>>>> Deliverable >>>>>>> and also checking all the Release 3 comments (Guides, UTP) and prepare >>>>>>> feedback >>>>>>> for Miguel, to get the release-review process going again. >>>>>>> >>>>>>> Important: In todays WPL/WPA call it was pointed out, that we also >>>>>>> have >>>>>>> to >>>>>>> provide a management summary (~ 1 page), containing only the newest >>>>>>> developments. >>>>>>> (For the other chapters this are the changes since last release of the >>>>>>> deliverable) >>>>>>> (For us this could be a compilation from the last part of all the GEs >>>>>>> sota) >>>>>>> >>>>>>> Best regards >>>>>>> Christof >>>>>>> >>>>>>> Am 16.03.2014 um 10:48 schrieb Philipp Slusallek >>>>>>> : >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I did go through the text and fixed quite a few missing references >>>>>>>> and >>>>>>>> marked some others that are still missing (please can some of the >>>>>>>> people >>>>>>>> involved in those GEs fix them). >>>>>>>> >>>>>>>> In general, there is a lack of references to previous work in quite a >>>>>>>> few of the GE descriptions. Please follow the model we have done in >>>>>>>> the >>>>>>>> middleware section and add some more references to previous work and >>>>>>>> then position your work in FI-WARE in relation to that. >>>>>>>> >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Philipp >>>>>>>> >>>>>>>> >>>>>>>> Am 15.03.2014 08:13, schrieb Jarkko Vatjus-Anttila: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> I read through the paper in my behalf, and the text seems to be >>>>>>>>> pretty >>>>>>>>> much collected from the text that has been formulated already >>>>>>>>> earlier. >>>>>>>>> I >>>>>>>>> my opinion, it gives an overview of the state of the art and as such >>>>>>>>> I >>>>>>>>> would guess it works as a deliverable for this purpose. However, >>>>>>>>> having >>>>>>>>> said that, I may not know all exact requirements what this >>>>>>>>> deliverable >>>>>>>>> is expected to fulfill. >>>>>>>>> >>>>>>>>> I made minor changes here and there, mainly fixing misspellings and >>>>>>>>> word >>>>>>>>> ordering. The modified document is attached here, with track changes >>>>>>>>> enabled. >>>>>>>>> >>>>>>>>> - jarkko >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Mar 14, 2014 at 10:00 PM, Marti Christof (mach) >>>>>>>>> >>>>>>>> > wrote: >>>>>>>>> >>>>>>>>> Hi Philipp, dear WP13 GE Owners >>>>>>>>> >>>>>>>>> Also due in M36 is an updated version (D.2.6.3) of the "State >>>>>>>>> of >>>>>>>>> the >>>>>>>>> art analysis - emerging technologies" deliverable. The >>>>>>>>> previous >>>>>>>>> release can be found here: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> https://forge.fi-ware.org/docman/view.php/7/2667/D.2.6.2+State+of+the+Art+Analysis+-+Emerging+Technologies.pdf >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Idea for all existing WPs is to provide a management summary >>>>>>>>> and >>>>>>>>> do >>>>>>>>> only required updates on the existing chapters. >>>>>>>>> Because there is no Web User Interfaces chapter in the last >>>>>>>>> deliverable I took the content from the FI-Core proposal and >>>>>>>>> tried >>>>>>>>> to put together a WP13 contribution for this deliverable. >>>>>>>>> It was more work than expected, because the writing style in a >>>>>>>>> proposal is a little bit different than for this deliverable. >>>>>>>>> So >>>>>>>>> I >>>>>>>>> would like to ask Philipp (and the respective GE owner for >>>>>>>>> their >>>>>>>>> part) to review the attached document (in change tracking >>>>>>>>> mode), >>>>>>>>> add >>>>>>>>> missing content and in particular also add missing entries in >>>>>>>>> the >>>>>>>>> "Reference" section. >>>>>>>>> >>>>>>>>> Deadline for delivering updates to the coordinator for review >>>>>>>>> is/was >>>>>>>>> today (March 14th). Because of this additional internal review >>>>>>>>> roundtrip, this will not be feasible. >>>>>>>>> If each GE owner can review its 20 to 30 lines and Philipp >>>>>>>>> keeps >>>>>>>>> am >>>>>>>>> eye on the overarching context until Monday noon, the delay >>>>>>>>> would >>>>>>>>> be >>>>>>>>> minimal. >>>>>>>>> >>>>>>>>> Thanks for your contributions. >>>>>>>>> >>>>>>>>> @Miguel, Juanjo: I do not want to release this without the OK >>>>>>>>> of >>>>>>>>> Philipp and the domain experts. >>>>>>>>> >>>>>>>>> Best regards >>>>>>>>> Christof >>>>>>>>> ---- >>>>>>>>> InIT Cloud Computing Lab - ICCLab >>>>>>>>> Institut of Applied Information Technology - InIT >>>>>>>>> Zurich University of Applied Sciences - ZHAW >>>>>>>>> School of Engineering >>>>>>>>> Phone: +41 58 934 70 63 >>>>>>>>> Skype: christof-marti >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Fiware-miwi mailing list >>>>>>>>> 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 >>>>>>>>> >>>>>>>>> Go to www.cybersli.de and enrich your >>>>>>>>> presentations! >>>>>>>>> >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------------- >>>>>>>> >>>>>>> WP13-1-phs.docx> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------- >>>>>> 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.org >>>>>> https://lists.fi-ware.org/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 >>>> >>>> --------------------------------------------------------------------------- >> >> >> >> -- >> >> ------------------------------------------------------------------------- >> 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.org > https://lists.fi-ware.org/listinfo/fiware-miwi -------------- next part -------------- A non-text attachment was scrubbed... Name: D.2.6.3 State of the Art Analysis - Emerging Technologies - WP13.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 431280 bytes Desc: D.2.6.3 State of the Art Analysis - Emerging Technologies - WP13.docx URL: From mcp at tid.es Mon Apr 7 15:11:09 2014 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 07 Apr 2014 15:11:09 +0200 Subject: [Fiware-miwi] Launch of Release 3.3 (reminder) In-Reply-To: <5328184A.403@tid.es> References: <5328184A.403@tid.es> Message-ID: <5342A3ED.1030601@tid.es> Dear all, This is just to remind you the deadline on April,11 ( a)User & Prog., b)Unit Testing Plan, c)Install & Admin manual ) Best regards, Miguel El 18/03/2014 10:56, Miguel Carrillo escribi?: Dear all, This message is to inform you that we have created the links to edit the R3.3 manuals. If you follow the links, you will see that there are two blocks per WP (R3.2 & R3.3) in each one of the three manuals (User & Prog., Unit Testing Plan, Install & Admin). * https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR3 For the WPLs: * Please check that the manuals under R3.2 and R3.3 are the right ones and delete/add as needed. Do not trust the ones you see now. If there are any changes please inform me in private. * Of course, take into account those GEs that are stopped and delete them For each GE owner: * Please edit the R3.3 manuals. Deadline to have the manuals ready: April, 11. At this point we will provide a dedicated google doc for the R3.3 reviews. The reviews of R3.2 are not superseded and the review will continue in parallel. They continue and all changes from R3.2 should be synchronized in the R3.3 manuals. We will try to reactivate the reviews of R3.2 shortly. Best regards, Manuel & Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.org Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.org Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Tue Apr 8 07:23:00 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 8 Apr 2014 05:23:00 +0000 Subject: [Fiware-miwi] [Fiware-ge-owners] Backlog Content: Reviews for deliverable In-Reply-To: References: Message-ID: Hi Manuel In 3D-UI WebTundra review report we have two to ?issues?, which are not clear to me how to handle them. T-6576 & T-6578 are both WorkItems related to updating the Architecture and OpenSpecification Documentation, which is GE specific (not GE Implementation specific). So in the tracker they are not assigned to a specific implementation and shared between the two implementations. In the review the entry is now appearing as an issue at the WebTundra implementation, because it is assigned to the 3D-UI GE and NOT to a GEi. How should we solve this issue now and in future? Best regards Christof Am 07.04.2014 um 18:50 schrieb MANUEL ESCRICHE VICENTE >: Dear Partners, Thanks for cooperation!! There?s been great effort at some GEIs, whose issues were cleaned. There?s still no winner!! Impressive reaction at Security Chapter!! ? That left Cloud behind!! I2ND (22-3%) ? MiWi (30-9%) ? Apps (66-8%) Data (120-14%) ? Security (134-21%) ? Cloud (135-12%) ? IoT (294-43%) https://forge.fi-ware.org/docman/view.php/27/3750/FIWARE.backlog.apps.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3751/FIWARE.backlog.cloud.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3754/FIWARE.backlog.iot.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3752/FIWARE.backlog.data.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3753/FIWARE.backlog.i2nd.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3756/FIWARE.backlog.security.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3755/FIWARE.backlog.miwi.review.20140407.xlsx Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ 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 _______________________________________________ Fiware-ge-owners mailing list Fiware-ge-owners at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-ge-owners -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Tue Apr 8 08:55:59 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 8 Apr 2014 08:55:59 +0200 Subject: [Fiware-miwi] Fwd: [Fiware-ge-owners] Backlog Content: Reviews for deliverable References: Message-ID: <335D7423-20FA-4626-95EC-F0D0A4857098@zhaw.ch> Hi everybody There were great enhancements in the WP13 backlog review yesterday evening and I see the possibility to bring it down to zero today. I just fixed the remaining 7 feature description issues in KIARA myself. The 5 ?new? issues in POI are fixable with little effort As soon we know how to handle the ?shared? 3D-UI issues, it can be fixed also asap. To not add new review issues please keep the rules in mind (e.g. assigning correct status and timeframes; 3.4(.1) entries should be ?under execution? now.) Especially also the following rules, which require also some effort in the wiki: if you close (or ?Finished but not released?) a Feature, it has to be added to the materializing page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE if you create a new Feature (for Release 3.4/3.5) it also has to be added to the wiki and linked from the roadmap page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI (but NOT YET the materializing page!!) please also keep in mind the sizing rules for the feature wiki (summary: 10 words, description: 30 words, rational 20 words). Cheers, Christof Anfang der weitergeleiteten Nachricht: > Umgeleitet von: > Von: MANUEL ESCRICHE VICENTE > Betreff: [Fiware-ge-owners] Backlog Content: Reviews for deliverable > Datum: 7. April 2014 [15] 18:50:35 MESZ > An: "fiware-ge-owners at lists.fi-ware.org" > Kopie: "fiware-wpl at lists.fi-ware.org" , "fiware-wpa at lists.fi-ware.org" > > Dear Partners, > > Thanks for cooperation!! > There?s been great effort at some GEIs, whose issues were cleaned. > > There?s still no winner!! > Impressive reaction at Security Chapter!! ? That left Cloud behind!! > > I2ND (22-3%) ? MiWi (30-9%) ? Apps (66-8%) > Data (120-14%) ? Security (134-21%) ? Cloud (135-12%) ? IoT (294-43%) > > https://forge.fi-ware.org/docman/view.php/27/3750/FIWARE.backlog.apps.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3751/FIWARE.backlog.cloud.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3754/FIWARE.backlog.iot.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3752/FIWARE.backlog.data.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3753/FIWARE.backlog.i2nd.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3756/FIWARE.backlog.security.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3755/FIWARE.backlog.miwi.review.20140407.xlsx > > Kind regards, > Manuel > > > ---------------------------- > Manuel Escriche Vicente > Agile Project Manager/Leader > FI-WARE Initiative > Telef?nica Digital > Parque Tecnol?gico > C/ Abraham Zacuto, 10 > 47151 - Boecillo > Valladolid - Spain > Tfno: +34.91.312.99.72 > Fax: +34.983.36.75.64 > http://www.tid.es > > > > 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 > _______________________________________________ > Fiware-ge-owners mailing list > Fiware-ge-owners at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-ge-owners -------------- next part -------------- An HTML attachment was scrubbed... URL: From mev at tid.es Tue Apr 8 09:02:27 2014 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Tue, 08 Apr 2014 07:02:27 +0000 Subject: [Fiware-miwi] [Fiware-ge-owners] Backlog Content: Reviews for deliverable In-Reply-To: References: Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90BB31BBCEE@EX10-MB2-MAD.hi.inet> Hi Christof, Please, select GE-Common for GEI [cid:image001.png at 01CF5309.4229A3F0] Kind regards, Manuel From: Marti Christof (mach) [mailto:mach at zhaw.ch] Sent: martes, 08 de abril de 2014 7:23 To: MANUEL ESCRICHE VICENTE Cc: MiWi FI-WARE Subject: Re: [Fiware-ge-owners] Backlog Content: Reviews for deliverable Hi Manuel In 3D-UI WebTundra review report we have two to "issues", which are not clear to me how to handle them. T-6576 & T-6578 are both WorkItems related to updating the Architecture and OpenSpecification Documentation, which is GE specific (not GE Implementation specific). So in the tracker they are not assigned to a specific implementation and shared between the two implementations. In the review the entry is now appearing as an issue at the WebTundra implementation, because it is assigned to the 3D-UI GE and NOT to a GEi. How should we solve this issue now and in future? Best regards Christof Am 07.04.2014 um 18:50 schrieb MANUEL ESCRICHE VICENTE >: Dear Partners, Thanks for cooperation!! There's been great effort at some GEIs, whose issues were cleaned. There's still no winner!! Impressive reaction at Security Chapter!! - That left Cloud behind!! I2ND (22-3%) - MiWi (30-9%) - Apps (66-8%) Data (120-14%) - Security (134-21%) - Cloud (135-12%) - IoT (294-43%) https://forge.fi-ware.org/docman/view.php/27/3750/FIWARE.backlog.apps.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3751/FIWARE.backlog.cloud.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3754/FIWARE.backlog.iot.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3752/FIWARE.backlog.data.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3753/FIWARE.backlog.i2nd.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3756/FIWARE.backlog.security.review.20140407.xlsx https://forge.fi-ware.org/docman/view.php/27/3755/FIWARE.backlog.miwi.review.20140407.xlsx Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telef?nica Digital Parque Tecnol?gico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es ________________________________ 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 _______________________________________________ Fiware-ge-owners mailing list Fiware-ge-owners at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-ge-owners ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5629 bytes Desc: image001.png URL: From mach at zhaw.ch Tue Apr 8 09:09:21 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 8 Apr 2014 09:09:21 +0200 Subject: [Fiware-miwi] Fwd: FI-WARE: MiWi - longest backlog item descriptions -> please reduce References: <3f260bb8f760489ba1bb9a5bf7c9ed49@SRV-MAIL-001.zhaw.ch> Message-ID: <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> Hi Torsten, Toni & Philipp A strange topic, but we should also reduce the size of the description for the 3D-UI and DataflowProcessing Epic descriptions to less than 250 words. Can somebody of you take over and bring it to a more compact form? Thanks, Christof Anfang der weitergeleiteten Nachricht: > Umgeleitet von: > Von: MANUEL ESCRICHE VICENTE > Betreff: FI-WARE: MiWi - longest backlog item descriptions -> please reduce > Datum: 3. April 2014 [14] 18:24:32 MESZ > An: "Marti Christof (mach)" > > Hi Christof, > > I?d appreciate you would manage to whoever owns the items below to reduce those descriptions, if possible below 250 words. > > 560 http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.DataflowProcessing > 438 http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.3D-UI > > Thanks in advance! > Manuel > > ---------------------------- > Manuel Escriche Vicente > Agile Project Manager/Leader > FI-WARE Initiative > Telef?nica Digital > Parque Tecnol?gico > C/ Abraham Zacuto, 10 > 47151 - Boecillo > Valladolid - Spain > Tfno: +34.91.312.99.72 > Fax: +34.983.36.75.64 > http://www.tid.es > > > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Tue Apr 8 09:14:07 2014 From: mach at zhaw.ch (Christof Marti) Date: Tue, 8 Apr 2014 09:14:07 +0200 Subject: [Fiware-miwi] [Fiware-ge-owners] Backlog Content: Reviews for deliverable In-Reply-To: <453e8f608a7a43cea915b41035022534@SRV-MAIL-001.zhaw.ch> References: <453e8f608a7a43cea915b41035022534@SRV-MAIL-001.zhaw.ch> Message-ID: <37FCD2F0-C4B4-4512-A9DA-225D8DF25290@zhaw.ch> Thanks I fixed it for T-6576 & T-6578. Hope the issue disappears from the review. Best regards Christof Am 08.04.2014 um 09:02 schrieb MANUEL ESCRICHE VICENTE : > Hi Christof, > Please, select GE-Common for GEI > > > > Kind regards, > Manuel > > From: Marti Christof (mach) [mailto:mach at zhaw.ch] > Sent: martes, 08 de abril de 2014 7:23 > To: MANUEL ESCRICHE VICENTE > Cc: MiWi FI-WARE > Subject: Re: [Fiware-ge-owners] Backlog Content: Reviews for deliverable > > Hi Manuel > > In 3D-UI WebTundra review report we have two to ?issues?, which are not clear to me how to handle them. > T-6576 & T-6578 are both WorkItems related to updating the Architecture and OpenSpecification Documentation, which is GE specific (not GE Implementation specific). > So in the tracker they are not assigned to a specific implementation and shared between the two implementations. > > In the review the entry is now appearing as an issue at the WebTundra implementation, because it is assigned to the 3D-UI GE and NOT to a GEi. > > How should we solve this issue now and in future? > > Best regards > Christof > > Am 07.04.2014 um 18:50 schrieb MANUEL ESCRICHE VICENTE : > > > Dear Partners, > > Thanks for cooperation!! > There?s been great effort at some GEIs, whose issues were cleaned. > > There?s still no winner!! > Impressive reaction at Security Chapter!! ? That left Cloud behind!! > > I2ND (22-3%) ? MiWi (30-9%) ? Apps (66-8%) > Data (120-14%) ? Security (134-21%) ? Cloud (135-12%) ? IoT (294-43%) > > https://forge.fi-ware.org/docman/view.php/27/3750/FIWARE.backlog.apps.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3751/FIWARE.backlog.cloud.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3754/FIWARE.backlog.iot.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3752/FIWARE.backlog.data.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3753/FIWARE.backlog.i2nd.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3756/FIWARE.backlog.security.review.20140407.xlsx > https://forge.fi-ware.org/docman/view.php/27/3755/FIWARE.backlog.miwi.review.20140407.xlsx > > Kind regards, > Manuel > > > ---------------------------- > Manuel Escriche Vicente > Agile Project Manager/Leader > FI-WARE Initiative > Telef?nica Digital > Parque Tecnol?gico > C/ Abraham Zacuto, 10 > 47151 - Boecillo > Valladolid - Spain > Tfno: +34.91.312.99.72 > Fax: +34.983.36.75.64 > http://www.tid.es > > > > 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 > _______________________________________________ > Fiware-ge-owners mailing list > Fiware-ge-owners at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-ge-owners > > > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Tue Apr 8 09:34:04 2014 From: toni at playsign.net (Toni Alatalo) Date: Tue, 8 Apr 2014 10:34:04 +0300 Subject: [Fiware-miwi] FI-WARE: MiWi - longest backlog item descriptions -> please reduce In-Reply-To: <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> References: <3f260bb8f760489ba1bb9a5bf7c9ed49@SRV-MAIL-001.zhaw.ch> <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> Message-ID: Regarding 3D-UI, I don't feel like the best person for it as it is largely about the DFKI-originated declarative authoring & browser integration so I hope Philipp or Torsten can do it soon enough. However if you're busy I'm confident that can shorten the text fine, have read and comprehended it repeatedly during the project :) I'll reserve time for this in early afternoon (13:00 our time, 12:00 CET) in case. BTW I'm happy to report that we ported with Jonne yesterday the XML3D SceneParser from current WebTundra master to the dev2 branch where the WebRocket core with the plugin system etc is now contributed by Adminotech. So the same code that is used on meshmoon as the web client can in the new version read xml3d declarations too :) That branch is a candidate for eventual WebTundra 2.0 release, we plan the dev work more tomorrow (at CIE) but I think there's a fair chance we can package it also for fi-ware release by the 3.4 deadline at the end of June (there's also other funding and projects besides fi-ware putting dev efforts in) .. or at least by the later autumn releases (there's still some core feats like the new scene hierarchy and custom components biz, and movement interpolation, missing from the dev2 / web rocket base -- the master version which is the rex 1.0 / fi-ware 3.3 release is still the best version for new feats and some dev friendliness things) While developing that we also used the DomIntegration plugin in dev2 now, is similar to what I wrote for xml3dsview in other branch earlier but with TXML .. is indeed nice to see from the debugger document view how the scene structure & data looks like. (this is one of the things that 3D-UI epic text argues). ~Toni On Tue, Apr 8, 2014 at 10:09 AM, Marti Christof (mach) wrote: > Hi Torsten, Toni & Philipp > > A strange topic, but we should also reduce the size of the description for > the 3D-UI and DataflowProcessing Epic descriptions to less than 250 words. > > Can somebody of you take over and bring it to a more compact form? > > Thanks, > Christof > > > Anfang der weitergeleiteten Nachricht: > > Umgeleitet von: > Von: MANUEL ESCRICHE VICENTE > Betreff: FI-WARE: MiWi - longest backlog item descriptions -> please reduce > Datum: 3. April 2014 [14] 18:24:32 MESZ > An: "Marti Christof (mach)" > > Hi Christof, > > > > I'd appreciate you would manage to whoever owns the items below to reduce > those descriptions, if possible below 250 words. > > > > 560 > http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.DataflowProcessing > 438 > http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.3D-UI > > > > Thanks in advance! > Manuel > > > > ---------------------------- > Manuel Escriche Vicente > Agile Project Manager/Leader > FI-WARE Initiative > Telef?nica Digital > Parque Tecnol?gico > C/ Abraham Zacuto, 10 > 47151 - Boecillo > Valladolid - Spain > Tfno: +34.91.312.99.72 > Fax: +34.983.36.75.64 > http://www.tid.es > > > > > ________________________________ > > 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 > > From Philipp.Slusallek at dfki.de Tue Apr 8 09:49:53 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Tue, 08 Apr 2014 09:49:53 +0200 Subject: [Fiware-miwi] Fwd: FI-WARE: MiWi - longest backlog item descriptions -> please reduce In-Reply-To: <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> References: <3f260bb8f760489ba1bb9a5bf7c9ed49@SRV-MAIL-001.zhaw.ch> <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> Message-ID: <5343AA21.1060201@dfki.de> Hi, It does not make much sense to me either, but I can look into it. Best, Philipp Am 08.04.2014 09:09, schrieb Marti Christof (mach): > Hi Torsten, Toni & Philipp > > A strange topic, but we should also reduce the size of the description > for the 3D-UI and DataflowProcessing Epic descriptions to less than 250 > words. > > Can somebody of you take over and bring it to a more compact form? > > Thanks, > Christof > > > Anfang der weitergeleiteten Nachricht: > >> *Umgeleitet von: *> >> *Von: *MANUEL ESCRICHE VICENTE > >> *Betreff: **FI-WARE: MiWi - longest backlog item descriptions -> >> please reduce* >> *Datum: *3. April 2014 [14] 18:24:32 MESZ >> *An: *"Marti Christof (mach)" > >> >> Hi Christof, >> >> I?d appreciate you would manage to whoever owns the items below to >> reduce those descriptions, if possible below 250 words. >> >> 560 >> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.DataflowProcessing >> 438 >> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.3D-UI >> >> Thanks in advance! >> Manuel >> >> ---------------------------- >> Manuel Escriche Vicente >> Agile Project Manager/Leader >> FI-WAREInitiative >> Telef?nica Digital >> Parque Tecnol?gico >> C/ Abraham Zacuto, 10 >> 47151 - Boecillo >> Valladolid - Spain >> Tfno: +34.91.312.99.72 >> Fax: +34.983.36.75.64 >> http://www.tid.es >> >> >> ------------------------------------------------------------------------ >> >> 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 > -- ------------------------------------------------------------------------- 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: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Tue Apr 8 10:08:49 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Tue, 08 Apr 2014 10:08:49 +0200 Subject: [Fiware-miwi] Fwd: FI-WARE: MiWi - longest backlog item descriptions -> please reduce In-Reply-To: <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> References: <3f260bb8f760489ba1bb9a5bf7c9ed49@SRV-MAIL-001.zhaw.ch> <2ADDF483-E3AE-40AB-A5B4-0941D187BCAE@zhaw.ch> Message-ID: <5343AE91.6080306@dfki.de> Done! DataflowProcessing 242 3D-UI: 250 (!!) According to Unix wc(1). Best Philipp Am 08.04.2014 09:09, schrieb Marti Christof (mach): > Hi Torsten, Toni & Philipp > > A strange topic, but we should also reduce the size of the description > for the 3D-UI and DataflowProcessing Epic descriptions to less than 250 > words. > > Can somebody of you take over and bring it to a more compact form? > > Thanks, > Christof > > > Anfang der weitergeleiteten Nachricht: > >> *Umgeleitet von: *> >> *Von: *MANUEL ESCRICHE VICENTE > >> *Betreff: **FI-WARE: MiWi - longest backlog item descriptions -> >> please reduce* >> *Datum: *3. April 2014 [14] 18:24:32 MESZ >> *An: *"Marti Christof (mach)" > >> >> Hi Christof, >> >> I?d appreciate you would manage to whoever owns the items below to >> reduce those descriptions, if possible below 250 words. >> >> 560 >> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.DataflowProcessing >> 438 >> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.MiWi.AdvWebUI.3D-UI >> >> Thanks in advance! >> Manuel >> >> ---------------------------- >> Manuel Escriche Vicente >> Agile Project Manager/Leader >> FI-WAREInitiative >> Telef?nica Digital >> Parque Tecnol?gico >> C/ Abraham Zacuto, 10 >> 47151 - Boecillo >> Valladolid - Spain >> Tfno: +34.91.312.99.72 >> Fax: +34.983.36.75.64 >> http://www.tid.es >> >> >> ------------------------------------------------------------------------ >> >> 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 > -- ------------------------------------------------------------------------- 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: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From antti.kokko at adminotech.com Tue Apr 8 11:38:58 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Tue, 8 Apr 2014 12:38:58 +0300 Subject: [Fiware-miwi] 2D-UI to internal review Message-ID: Hello, 2D-UI is ready for internal review: https://docs.google.com/a/adminotech.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=24 Thanks, - Antti Kokko -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.spieldenner at dfki.de Tue Apr 8 16:01:48 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Tue, 08 Apr 2014 16:01:48 +0200 Subject: [Fiware-miwi] 2D-UI to internal review In-Reply-To: References: Message-ID: <5344014C.8030709@dfki.de> Hello, I have just finished the review. There are just a few very small fixes that I've suggested, and a seemingly broken link in the installation guide. Best, Torsten Am 08.04.2014 11:38, schrieb Antti Kokko: > Hello, > > 2D-UI is ready for internal review: > https://docs.google.com/a/adminotech.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=24 > > Thanks, > > - Antti Kokko From mach at zhaw.ch Tue Apr 8 18:59:43 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 8 Apr 2014 16:59:43 +0000 Subject: [Fiware-miwi] Review and fixes for Release 3.2 (January) Guides Message-ID: <4ED524D0-482A-4C80-B7B8-F2309E44D92C@zhaw.ch> Hi everybody Last week/weekend and today I finally found time to finish checking and verifying the R3.2 Software, User&Programmer Guides and Install&Admin Guides. I tried to fix as many issues I could myself. Sadly there are still some fixes/extensions from your side required. The updated status can be found here: https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=17 All entries marked ?Review OK? or ?Ready for 2nd review? are OK and need no enhancements. Those requiring fixes are yellow and I added some comments below. (Miguels and Manuels original review comments are also linked from the Dashboard) Software: * All Package naming issues fixed. * Still missing DaaS package (at least I can not find it) User & Programmer Guides: * Structure is OK for all GEis. * Content is updated/enhanced and most GEi are ready for 2nd review. * Cloud Renderer Guide is rejected and will be rejected again if not updated. I guess main reason is, that it is very difficult to understand how it has to be used without digging into the WebClient example source code. You mention the WebClient JavaScript library. What about a code example on how to use it? Installation & Admin Guides: Miguel stopped reviewing them, because the structure was not OK for most of them. I fixed quite a lot of structural issues. Here it is important, that the document structure has to follow exactly the template https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php/Template_GE_-_Installation_and_Administration_Guide You are not supposed to remove given sections or change the given section titles. You can add subsections to them. If a section is not applicable, you can write N/A (e.g. if you are not using a database). The template also gives some hints about the content of the sections. * TOC OK means the Structure was ok. Maybe I did some minor edits * TOC fixed means I fixed the structure and maybe moved some content. * TOC fix still needed means that it was not so simple for me to split the content into the required sections. Anyways, please check your Installation & Admin Guide by * checking if the content is still correct. (You can check my changes/diffs in the history tab). * Enhancing the content of HW/SW requirements (minimal, optimal and concrete minimal version numbers for OS/Software) * Enhancing the Sanity Check and Diagnosis Procedures (check content hints on template page) I am still working on the Unit Testing Plans and will send an update later this evening. Reminder: tomorrow April 9th EOB is the internal deadline for the updated R3.3 Guides and UTPs (dashboard) They should also be updated to include the fixes from R3.2. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Apr 9 08:34:54 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 9 Apr 2014 06:34:54 +0000 Subject: [Fiware-miwi] Agenda/minutes WP 13 weekly meeting Message-ID: Hi I created the agenda/minutes here: https://docs.google.com/document/d/1pUIHbx71Y00P9fB9owOsFU5ZO0MCoF24HuzYl-oxDTg/edit Hangout is here:https://plus.google.com/hangouts/_/72cpjrcdf587dvtlrf7p8eiaac?hl=de Best regards Christof ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From jarkko at cyberlightning.com Wed Apr 9 09:09:06 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Wed, 9 Apr 2014 10:09:06 +0300 Subject: [Fiware-miwi] 3DUI-WebTundra docs & release for review In-Reply-To: References: Message-ID: Hello all, I took a look at the papers and I am happy to say that they look good :) At least to me the instructions are clear, and I think it tells already something if I managed to install and run all the examples :) Review doc here with minor correction requests: < https://docs.google.com/document/d/1Q4bzSTQAcvdi3Aq2vGo47yYJln7Ph-bVRo5kvmO_w7Q/edit?usp=sharing > - jarkko On Fri, Apr 4, 2014 at 3:08 PM, Toni Alatalo wrote: > Hi Jarkko, others - our docs are finally updated for current code: > > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php?title=3D-UI_-_WebTundra_-_Installation_and_Administration_Guide(R3.3) > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php?title=3D-UI_-_WebTundra_-_User_and_Programmers_Guide(R3.3) > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php?title=3D-UI_-_WebTundra_-_Unit_Testing_Plan_and_Report(R3.3) > > code is in dev branch right now still, we upload zip and push to master > now. > > ~Toni > -- Jarkko Vatjus-Anttila VP, Technology Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com Go to www.cybersli.de and enrich your presentations! www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From antti.kokko at adminotech.com Wed Apr 9 10:03:58 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Wed, 9 Apr 2014 11:03:58 +0300 Subject: [Fiware-miwi] 2D-UI to internal review In-Reply-To: <5344014C.8030709@dfki.de> References: <5344014C.8030709@dfki.de> Message-ID: Hi, Thanks for the review! I have done corrections according to the suggested comments. Best, Antti On Tue, Apr 8, 2014 at 5:01 PM, Torsten Spieldenner < torsten.spieldenner at dfki.de> wrote: > Hello, > > I have just finished the review. There are just a few very small fixes > that I've suggested, and a seemingly broken link in the installation guide. > > Best, > Torsten > > Am 08.04.2014 11:38, schrieb Antti Kokko: > > Hello, >> >> 2D-UI is ready for internal review: >> https://docs.google.com/a/adminotech.com/spreadsheet/ccc?key=0Auieh_ >> fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=24 >> >> Thanks, >> >> - Antti Kokko >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Wed Apr 9 15:20:11 2014 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Wed, 09 Apr 2014 13:20:11 +0000 Subject: [Fiware-miwi] Dissemination Deliverables (WP12) - Contribs Request (Fast&Easy to complete!) - Deadline Apr 14th EoB In-Reply-To: <5342A3ED.1030601@tid.es> Message-ID: Dear colleagues, It is time to collect all information regarding dissemination, communication & collaboration actions you performed in the last WP12 reporting period (M30 = Oct 2013 to M36 = Apr 2014, all included). Please, bear in mind that the EC may reject one of your trips for these activities if they are not correctly reported in this new edition of D12.2 and D12.3 documents. This time, to make things easier for all of you I have prepared a Googledoc where you can place your contribs and then I may transfer them myself to the wiki: https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_73M/edit#heading=h.o4j1rtrg6tzx However, you may always contribute to the wiki directly as in previous times. The contribs have to be added here: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Dissemination_activities http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Communication_activities http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities Even when you add your contribs straight into the wiki, do not forget to add your partner name to the googledoc and add "(Wiki)" so I keep informed. As said in the googledoc the 6 possible sections you may contribute with entries (the googledoc includes examples) are: 1. Participation in Events (Presentations, round tables, keynotes...) 2. Scientific Papers and Panels 3. Book chapters 4. Training materials & Tutorials 5. Collaboration Meetings/Actions 6. Press Releases and other relevant Communication actions Normally, most partners will have contribs to 1 and 2 sections. Deadline for this is next monday April 14th EoB. Should you have any question/comment, please do contact me. Thanks in advance for your kind cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Apr 9 20:18:12 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 9 Apr 2014 18:18:12 +0000 Subject: [Fiware-miwi] [Fiware-administrative] VERY IMPORTANT: Final revision of FI-WARE Amendment 6 In-Reply-To: <00166267f3ba4a929e20a5f3f484bb63@SRV-MAIL-001.zhaw.ch> References: <00166267f3ba4a929e20a5f3f484bb63@SRV-MAIL-001.zhaw.ch> Message-ID: Hi Juanjo I was checking the new DoW regarding the WP13 specific content and found the following two points: * B.1.3.3 Work package list (p 126): WPA for WP13 is missing in the table (WPA partic. No = 29, WPA short name = DFKI) * B.1.3.6.13 WP13 Workpackage-Description (p. 236/237): There are still 2 old comments from Arian, which are identical to those in the accepted Amendment5 release. It is irritating, that they have the current date. To keep them might provoke additional updates of already accepted DoW parts. All the other WP13 related changes seem to be OK. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab 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 09.04.2014 um 07:40 schrieb Juanjo Hierro >: Dear all, The final draft of the FI-WARE Amendment 6 is ready to be sent to our Project Officer. You can download the final DoW, from the following links available on the docman system of the FI-WARE private project: * https://forge.fi-ware.org/docman/view.php/27/3770/FI-WARE-DoW-Amendment6-DRAFT-v6.7.docx * https://forge.fi-ware.org/docman/view.php/27/3772/FI-WARE+effort-budget-funding-Amendment6-v15.xlsx * https://forge.fi-ware.org/docman/view.php/27/3773/GPF+FI-WARE+%28285248%29+2014-04-08+%28DRAFT%29.pdf Note that these files will only be accessible using your username and password in the FI-WARE forge. Please contact Javier de Pedro Sanchez or Miguel Carrillo if you experience any problem retrieving the files. As you know, this amendment establishes the extension of the project until month 41 (i.e., end of September). However, some of the partners have decided to finalize their activities by end of month 36 (i.e., end of April). Provisions to handle this are given in B.13 - Annex X referred from section B.1.3.8. Please make sure that your organization is listed in the right category (partners finalizing their activities in M36 or not) within that annex. It is our intention to submit this draft to our PO this Friday April 11 at noon so a period for comments is open until Thursday April 10th (tomorrow) EOB. There have not been many changes since the last draft we distributed on February 14, and there are not so many changes overall compared to previous amendments, so its revision should be pretty straightforward in our opinion. Nevertheless, this will be a draft so our PO has to review it and may come back with some changes. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: 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 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ________________________________ 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 _______________________________________________ Fiware-administrative mailing list Fiware-administrative at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-administrative -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonne at adminotech.com Thu Apr 10 15:36:55 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Thu, 10 Apr 2014 16:36:55 +0300 Subject: [Fiware-miwi] Cloud Rendering review status Message-ID: The install and user guide pages are ready for review and we actually already communicated with Lasse on IRC and he checked them out http://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php/Cloud_Rendering_-_Installation_and_Administration_Guide(R3.3) http://forge.fi-ware.org/plugins/mediawiki/wiki/fi-ware-private/index.php/Cloud_Rendering_-_User_and_Programmers_Guide(R3.3) So those are ready for external review. I think they are now a lot better. There is a form of "hello world" now on the JavaScript library side. More code related things, more details on installation and usage. Unfortunately the unit test page is not yet complete. The guy who is making them is 90% done, just need to push the tests to the repo and update the wiki pages. We will do this during today and tomorrow, hopefully inside the deadline of 11.4. He had some unexpected traveling (I assume work related) that he had to do so making this stuff got on hold for a bit too long time. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonne at adminotech.com Thu Apr 10 16:11:34 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Thu, 10 Apr 2014 17:11:34 +0300 Subject: [Fiware-miwi] Synchronization internal review done Message-ID: https://docs.google.com/a/adminotech.com/document/d/1lbP17oyh8ieAi6UsJ0CP1Y7C_eBrVrymXcwS7Z4OZio Only found one little detail and Lasse already fixed it. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Fri Apr 11 14:10:57 2014 From: toni at playsign.net (Toni Alatalo) Date: Fri, 11 Apr 2014 15:10:57 +0300 Subject: [Fiware-miwi] Fwd: [ITEE] Guest talk 16th April: Cloud Architectures for Cost-Efficient Applications and Services Provisioning in Internet of Things In-Reply-To: References: <5347BA75.9050208@ee.oulu.fi> Message-ID: This guest lecture at the Oulu uni next Wed before noon seemed to match many keywords in FI-WARE - I might go, perhaps of interest to others as well. If the weekly is short doesn't overlap too much :) ~Toni ---------- Forwarded message ---------- From: Hannakaisa Aikio Subject: [ITEE] Guest talk 16th April: Cloud Architectures for Cost-Efficient Applications and Services Provisioning in Internet of Things Date: 11 Apr 2014 12:48:37 GMT+3 To: itee at lists.oulu.fi Welcome to hear Professor Roch H. Glitho (Associate Professor and Canada Research Chair, Concordia University, Montreal, Canada) on state-of-the-art and research directions of Cloud Architectures for Cost-Efficient Applications and Services Provisioning in Internet of Things Time: Wednesday 16th April, 10-12 am Venue: lecture room TS128, Tietotalo, entrance E Abstract: Internet of Things (IoT) aims at enabling interactions between devices ranging from wireless sensors/actuators to smart meters and robots, with little or no human intervention. Applications and services provisioning (e.g. development, deployment and management) in IoT remains rather cost inefficient. Applications and services are still usually embedded in IoT infrastructure at deployment time. This precludes re-use by new applications and services, and leads to redundant IoT infrastructure deployment. IoT Applications and services provisioning platforms do not enable cost efficiency because they do not offer application programming interfaces (APIs) suitable to users with different levels of technical skills. In addition they do not enable easy re-use of third party components. Cloud computing is an emerging paradigm with several facets (e.g. Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS)) and several inherent benefits (e.g. efficiency in resource usage, easy introduction of new applications and services, scalability, and flexibility in pricing). These benefits make it an ideal candidate for bringing cost efficiency to the realm of IoT applications and services provisioning. This invited speech focuses on cloud architectures for cost efficient applications and services provisioning in IoT. There actually two approaches to cloud architectures for cost efficient applications provisioning in IoT. The first approach leverages the storage and processing power in cloud fabrics while the second goes much further and applies true cloud computing concepts (e.g. virtualization) to IoT infrastructure. These two approaches are reviewed in this speech and research directions are identified. Instructor's biography: Roch H. Glitho [SM] (http://www.ece.concordia.ca/~glitho/) holds a Ph.D. (Tekn. Dr.) in tele-informatics (Royal Institute of Technology, Stockholm, Sweden). He also holds M.Sc. degrees in business economics (University of Grenoble, France), pure mathematics (University Geneva, Switzerland), computer science (University of Geneva). He is as an associate professor of networking and telecommunications at the Concordia Institute of Information Systems Engineering (CIISE), (Concordia University, Montreal) where he holds the Canada Research Chair in End-user Services Engineering for Communications Networks. In the past he has worked in industry for almost a quarter of a century and has held several senior technical positions at LM Ericsson in Sweden and Canada (e.g. expert, principal engineer, senior specialist). His industrial experience includes research, international standards setting (e.g. contributions to ITU-T, ETSI, TMF, ANSI, TIA, and 3GPP), product management, project management, systems engineering and software/firmware design. In the past he has served as IEEE Communications Society distinguished lecturer, Editor-In-Chief of IEEE Communications Magazine and Editor-In-Chief of IEEE Communications Surveys & Tutorials. His research areas include architectures for end-users applications, cloud computing, virtualization, Internet of Things, distributed systems, and ICT for development. _______________________________________________ Itee mailing list Itee at lists.oulu.fi http://lists.oulu.fi/mailman/listinfo/itee From mach at zhaw.ch Fri Apr 11 16:49:18 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Fri, 11 Apr 2014 14:49:18 +0000 Subject: [Fiware-miwi] Infos on VM installation on testbed. References: Message-ID: Hi everybody Seems to be a misunderstanding from my side. We do not have to install the VMs in http://testbed.fi-ware.org as I assumed. We have to install it in http://130.206.80.61 which is not the same instance and you need to get an account from Henar/Jose Ignacio. Please follow the instructions on https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Operation_Cockpit for access and installing the VMs. Contact for questions and requests are: Henar Mu?oz > (backup: Jose Ignacio Carretero Guarde >) Best regards Christof Anfang der weitergeleiteten Nachricht: Umgeleitet von: > Von: HENAR MU?OZ FRUTOS > Betreff: RE: VM descriptions in V3 implementation cockpit for MiWi Datum: 11. April 2014 [15] 12:22:23 MESZ An: "Marti Christof (mach)" > Kopie: stefano de panfilis >, MIGUEL CARRILLO PACHECO > Hi Sorry for not reply to you before. You should be able to access to the GE Cloud http://130.206.80.61/. In addition, some information you can use for using the cloud and deploying vms can be found in https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Operation_Cockpit Tell me if you have any problems. Regards, Henar -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Fri Apr 11 18:27:50 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Fri, 11 Apr 2014 16:27:50 +0000 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] URGENT: GEis installation and test References: Message-ID: <7994FDAF-5F38-4F07-B62E-343985C7D5A8@zhaw.ch> Hi everybody Sorry for contacting to you late Friday afternoon, but we have an additional exercise to do. One of the M30 review recommendations is to enhance the quality of the Installation Guides and usage tests. Idea is now, that each GEi installation and test is verified by a company not involved in its development (see email text below). So we have to declare for each GEi, which partner will execute the installation (local and in fi-lab, manually and with recipes) and document the results (Template attached) AP: ASAP (whenever possible today): Each partner (only 1 entry per company) fills in the following survey https://docs.google.com/forms/d/19-yM_MBlsXJY4O6yxa546GZbEJ0245caDqz8UzcObgE/viewform Please select all the GEi?s you are willing/able to test. Also give the max number of GEi?s you are able to verify. Rule of thumb is about as many as you are developing. NOW I need you commitment. The verifications have then to be performed until June 30th. AP: ASAP (whenever possible today): Please also check and confirm in the above survey, that the entries for your GEi?s in the in the following spreadsheet (https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0), are correct. (Correct release to be tested, is testable at all (open source, not as a service, ?), can it be tested in FI-LAB or only local/special hardware). Thanks for fast reaction. Cheers and have a nice weekend. Christof Marti ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Anfang der weitergeleiteten Nachricht: dear all, as discussed yesterday during our call and refined this morning in the wp10 call, here is the procedure to install and test the geis as requested in the scope of recommendation 18 of the review report 6 excerpt of which is ?Obviously, hardly any of the documentation can claim completeness in the remaining time, but should at least cover all known grounds. To this end, extensive and directed installation and usage tests should be performed ? not only through the Use Case projects, but also within the consortium. For example, partners not involved in the development of a specific Generic Enabler can verify it through installation and testing. The according results and findings should be incorporated in the forthcoming Release 3 and the validation reporting of deliverable D10.5.3.? the wpl migth already have received at this time an invitation from me to access a googledoc (here again the link for your convenience: https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0) this doc contains all the geis implemented at the moment or in the very near future. 1. each wpl must, within this friday (11 april 2014), fill, in agreement with their wp participants, the name of the organisation responsible for installing a testing a specific gei. in addition the wpl should declare which geis will be tested. the overal rules are: 1.1 no geis of wp4 for what concerns fi-lab installation and test 1.2 only the geis of wp7 which do not require special network environment 1.3 no geis for which do not exist an oss version 2. within 25 april 2014 all the installations and tests must be completed either by the organisations leaving the project at m36, and by those organisation if a test assigned to them involve a gei owned by an organisation leaving the project at m36. 3. all the remaining installations and tests must be fulfilled by 30 june 2014. the installation and tests must be documented using the form described in the attached document. please note that, as you can easily guess from point 1 above, there are two different kind of installations to be tested: 1. manual deplyoment, which involves all oss released geis 2. recipes supported deployment in the fi-ware testbed. this case the person making the test must create a vm, which should be removed immediately after the installation and test is completed (due to the obvious resource cosumption) it would be great if the persons who will make the installation and tests are completely outside the fi-ware environment. this procedure refines and superseeds what sent by thorsten, thank you for triggering the process, on last wednesday. for any clarification you migth need, please do not hesitate to contact me. ciao, stefano -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-068307-4295 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 skype: depa01 _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-wpa -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I10.2_Installation_and_Test_Template_v2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 220183 bytes Desc: I10.2_Installation_and_Test_Template_v2.docx URL: From jarkko at cyberlightning.com Fri Apr 11 18:32:29 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Fri, 11 Apr 2014 19:32:29 +0300 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] URGENT: GEis installation and test In-Reply-To: <7994FDAF-5F38-4F07-B62E-343985C7D5A8@zhaw.ch> References: <7994FDAF-5F38-4F07-B62E-343985C7D5A8@zhaw.ch> Message-ID: Christof and all, I am on the road and unable to comply personally before sunday evening. However i tested those three GE manuals which were assigned for me and those worked. This is just a quick note from me. Jarkko On Apr 11, 2014 7:28 PM, "Marti Christof (mach)" wrote: > Hi everybody > > Sorry for contacting to you late Friday afternoon, but we have an > additional exercise to do. > One of the M30 review recommendations is to enhance the quality of the > Installation Guides and usage tests. > Idea is now, that each *GEi installation and test is verified by a > company not involved in its development* (see email text below). > > So we have to declare for each GEi, which partner will execute the > installation (local and in fi-lab, manually and with recipes) and document > the results (Template attached) > > AP: ASAP (whenever possible today): Each partner (only 1 entry per > company) fills in the following survey > > https://docs.google.com/forms/d/19-yM_MBlsXJY4O6yxa546GZbEJ0245caDqz8UzcObgE/viewform > > Please select all the GEi's you are willing/able to test. Also give the > max number of GEi's you are able to verify. Rule of thumb is about as many > as you are developing. > *NOW I need you commitment. The verifications have then to be performed > until June 30th.* > > AP: ASAP (whenever possible today): Please also check and confirm in the > above survey, that the entries for your GEi's in the in the following > spreadsheet ( > https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 > ), are correct. > (Correct release to be tested, is testable at all (open source, not as a > service, ...), can it be tested in FI-LAB or only local/special hardware). > > Thanks for fast reaction. > > Cheers and have a nice weekend. > Christof Marti > ---- > InIT Cloud Computing Lab - ICCLab > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > > Anfang der weitergeleiteten Nachricht: > > > dear all, > > as discussed yesterday during our call and refined this morning in the > wp10 call, here is the procedure to install and test the geis as requested > in the scope of recommendation 18 of the review report 6 excerpt of which > is "*Obviously, hardly any of the documentation can claim completeness in > the remaining time, but should at least cover all known grounds. To this > end, extensive and directed installation and usage tests should be > performed - not only through the Use Case projects, but also within the > consortium. For example, partners not involved in the development of a > specific Generic Enabler can verify it through installation and testing. > The according results and findings should be incorporated in the > forthcoming Release 3 and the validation reporting of deliverable D10.5.3* > ." > > > the wpl migth already have received at this time an invitation from me > to access a googledoc (here again the link for your convenience: > https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 > ) > > this doc contains all the geis implemented at the moment or in the very > near future. > > 1. each wpl must, within this friday (11 april 2014), fill, in agreement > with their wp participants, the name of the organisation responsible for > installing a testing a specific gei. in addition the wpl should declare > which geis will be tested. the overal rules are: > 1.1 no geis of wp4 for what concerns fi-lab installation and test > 1.2 only the geis of wp7 which do not require special network environment > 1.3 no geis for which do not exist an oss version > > 2. within 25 april 2014 all the installations and tests must be > completed either by the organisations leaving the project at m36, and by > those organisation if a test assigned to them involve a gei owned by an > organisation leaving the project at m36. > > 3. all the remaining installations and tests must be fulfilled by 30 > june 2014. > > the installation and tests must be documented using the form described > in the attached document. > > please note that, as you can easily guess from point 1 above, there are > two different kind of installations to be tested: > 1. manual deplyoment, which involves all oss released geis > 2. recipes supported deployment in the fi-ware testbed. this case the > person making the test must create a vm, which should be removed > immediately after the installation and test is completed (due to the > obvious resource cosumption) > > it would be great if the persons who will make the installation and > tests are completely outside the fi-ware environment. > > this procedure refines and superseeds what sent by thorsten, thank you > for triggering the process, on last wednesday. > > for any clarification you migth need, please do not hesitate to contact > me. > > ciao, > stefano > > -- > Stefano De Panfilis > Chief Innovation Officer > Engineering Ingegneria Informatica S.p.A. > via Riccardo Morandi 32 > 00148 Roma > Italy > > tel (direct): +39-068307-4295 > tel (secr.): +39-068307-4513 > fax: +39-068307-4200 > cell: +39-335-7542-567 > skype: depa01 > > _______________________________________________ > Fiware-wpa mailing list > Fiware-wpa at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-wpa > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Mon Apr 14 10:06:28 2014 From: mach at zhaw.ch (Christof Marti) Date: Mon, 14 Apr 2014 10:06:28 +0200 Subject: [Fiware-miwi] URGENT: GEis installation and test In-Reply-To: References: Message-ID: Reminder. Please fill in the Survey until 11:00 if not yet done: - DFKI, - ADMINO The following GEi? are missing they need also installation tests: - All Middleware components - Augmented Reality See here for survey answers: https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFI3MGZQVGo3cnpHMk5nZE9XZWwwd2c&usp=docslist_api#gid=0 Best regards Christof Am 11.04.2014 um 18:27 schrieb Marti Christof (mach) : > Hi everybody > > Sorry for contacting to you late Friday afternoon, but we have an additional exercise to do. > One of the M30 review recommendations is to enhance the quality of the Installation Guides and usage tests. > Idea is now, that each GEi installation and test is verified by a company not involved in its development (see email text below). > > So we have to declare for each GEi, which partner will execute the installation (local and in fi-lab, manually and with recipes) and document the results (Template attached) > > AP: ASAP (whenever possible today): Each partner (only 1 entry per company) fills in the following survey > https://docs.google.com/forms/d/19-yM_MBlsXJY4O6yxa546GZbEJ0245caDqz8UzcObgE/viewform > > Please select all the GEi?s you are willing/able to test. Also give the max number of GEi?s you are able to verify. Rule of thumb is about as many as you are developing. > NOW I need you commitment. The verifications have then to be performed until June 30th. > > AP: ASAP (whenever possible today): Please also check and confirm in the above survey, that the entries for your GEi?s in the in the following spreadsheet (https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0), are correct. > (Correct release to be tested, is testable at all (open source, not as a service, ?), can it be tested in FI-LAB or only local/special hardware). > > Thanks for fast reaction. > > Cheers and have a nice weekend. > Christof Marti > ---- > InIT Cloud Computing Lab - ICCLab > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > > Anfang der weitergeleiteten Nachricht: > >> >> dear all, >> >> as discussed yesterday during our call and refined this morning in the wp10 call, here is the procedure to install and test the geis as requested in the scope of recommendation 18 of the review report 6 excerpt of which is ?Obviously, hardly any of the documentation can claim completeness in the remaining time, but should at least cover all known grounds. To this end, extensive and directed installation and usage tests should be performed ? not only through the Use Case projects, but also within the consortium. For example, partners not involved in the development of a specific Generic Enabler can verify it through installation and testing. The according results and findings should be incorporated in the forthcoming Release 3 and the validation reporting of deliverable D10.5.3.? >> >> >> the wpl migth already have received at this time an invitation from me to access a googledoc (here again the link for your convenience: https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0) >> >> this doc contains all the geis implemented at the moment or in the very near future. >> >> 1. each wpl must, within this friday (11 april 2014), fill, in agreement with their wp participants, the name of the organisation responsible for installing a testing a specific gei. in addition the wpl should declare which geis will be tested. the overal rules are: >> 1.1 no geis of wp4 for what concerns fi-lab installation and test >> 1.2 only the geis of wp7 which do not require special network environment >> 1.3 no geis for which do not exist an oss version >> >> 2. within 25 april 2014 all the installations and tests must be completed either by the organisations leaving the project at m36, and by those organisation if a test assigned to them involve a gei owned by an organisation leaving the project at m36. >> >> 3. all the remaining installations and tests must be fulfilled by 30 june 2014. >> >> the installation and tests must be documented using the form described in the attached document. >> >> please note that, as you can easily guess from point 1 above, there are two different kind of installations to be tested: >> 1. manual deplyoment, which involves all oss released geis >> 2. recipes supported deployment in the fi-ware testbed. this case the person making the test must create a vm, which should be removed immediately after the installation and test is completed (due to the obvious resource cosumption) >> >> it would be great if the persons who will make the installation and tests are completely outside the fi-ware environment. >> >> this procedure refines and superseeds what sent by thorsten, thank you for triggering the process, on last wednesday. >> >> for any clarification you migth need, please do not hesitate to contact me. >> >> ciao, >> stefano >> >> -- >> Stefano De Panfilis >> Chief Innovation Officer >> Engineering Ingegneria Informatica S.p.A. >> via Riccardo Morandi 32 >> 00148 Roma >> Italy >> >> tel (direct): +39-068307-4295 >> tel (secr.): +39-068307-4513 >> fax: +39-068307-4200 >> cell: +39-335-7542-567 >> skype: depa01 >> > >> _______________________________________________ >> Fiware-wpa mailing list >> Fiware-wpa at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-wpa > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Apr 16 08:33:38 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 16 Apr 2014 08:33:38 +0200 Subject: [Fiware-miwi] WP13 weekly meeting Message-ID: Link to Agenda/minutes: https://docs.google.com/document/d/1qecLMb6MwtYZcTZeUOrsy0MuVMDmUQRuLPnNJgsV_04/edit# Link to Hangout: https://plus.google.com/hangouts/_/76cpjpd6cfakb8lo9ddnrdgslk?hl=de Cheers Christof From mach at zhaw.ch Thu Apr 17 11:12:51 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 17 Apr 2014 09:12:51 +0000 Subject: [Fiware-miwi] Fwd: [PPP-TF-proposal] news on negotiation References: Message-ID: FYI Some infos about the current status of the FI-Core negotiations. Cheers Christof Anfang der weitergeleiteten Nachricht: Umgeleitet von: > Von: Juanjo Hierro > Betreff: Aw: [PPP-TF-proposal] news on negotiation Datum: 17. April 2014 [16] 11:07:50 MESZ An: Sander van der Waal >, Philippe Cousin > Kopie: Technology Foundation proposal > Dear all, It seems like the EC is very busy with the negotiations with the 16 acceleration projects which they haven't been able to close yet as far as I know. I have been told that we will receive comments to our proposal they will ask us to incorporate in the DoW along the week, most probably end of the week. I still assume that we will be able to close the negotiations as to be able to start the project by June 1st. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: 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 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 16/04/14 14:06, Sander van der Waal wrote: Dear Juanjo, Do you have any update on FI-CORE? I look forward to hearing more soon so we can start planning the resourcing. Kind Regards, Sander On 31 March 2014 14:58, Philippe Cousin > wrote: Juanjo, all What news on the negotiation and any changes for the DoW ? I notice big silence since brussels meetings Best regards Philippe _______________________________________________ Ppp-tf-proposal mailing list Ppp-tf-proposal at tid.es https://listas.tid.es/mailman/listinfo/ppp-tf-proposal -- Sander van der Waal Projects Director | @sandervdwaal The Open Knowledge Foundation Empowering through Open Knowledge http://okfn.org/ | @okfn | OKF on Facebook | Blog | Newsletter _______________________________________________ Ppp-tf-proposal mailing list Ppp-tf-proposal at tid.es https://listas.tid.es/mailman/listinfo/ppp-tf-proposal -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralli at tid.es Mon Apr 21 11:55:10 2014 From: ralli at tid.es (CARLOS RALLI UCENDO) Date: Mon, 21 Apr 2014 09:55:10 +0000 Subject: [Fiware-miwi] LAST CALL - Dissemination Deliverables (WP12) - Contribs Request (Fast&Easy to complete!) - Deadline Apr 14th EoB In-Reply-To: Message-ID: Dear Colleagues, So far I can only see the contributions from: iMinds, NEC, IBM-CH, ALU-D, Playsign, SAP(WP3), NSN-H, DT (sent to Carlos by e-mail) ATOS and Ogilvy have committed to send it tomorrow EoB. Please, let me extend the deadline until this wednesday at 12CET. However there will be no further extensions and all contribs not received will not be included in the document to be delivered this friday. As said before, the European Commission may reject the costs of dissemination trips within M30 and M36 not included in this document. Obviously, for partners leaving the project on M36 is extremely important if you want to get all funds related to dissemination of FI-WARE. The googledoc to contribute is still active here: https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_73M/edit#heading=h.kgxusv5ldjp Thanks for your understanding and contributions, Best regards. -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ De: Carlos Ralli Ucendo > Fecha: mi?rcoles, 9 de abril de 2014 15:20 Para: "fiware at lists.fi-ware.org" > CC: "fiware-cloud at lists.fi-ware.org" >, "fiware-iot at lists.fi-ware.org" >, "Fiware-data at lists.fi-ware.org" >, "FI-WARE, MiWi" >, "fiware-i2nd at lists.fi-ware.org" >, "fiware-apps at lists.fi-ware.eorg" >, "fiware-security at lists.fi-ware.org" > Asunto: Dissemination Deliverables (WP12) - Contribs Request (Fast&Easy to complete!) - Deadline Apr 14th EoB Dear colleagues, It is time to collect all information regarding dissemination, communication & collaboration actions you performed in the last WP12 reporting period (M30 = Oct 2013 to M36 = Apr 2014, all included). Please, bear in mind that the EC may reject one of your trips for these activities if they are not correctly reported in this new edition of D12.2 and D12.3 documents. This time, to make things easier for all of you I have prepared a Googledoc where you can place your contribs and then I may transfer them myself to the wiki: https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_73M/edit#heading=h.o4j1rtrg6tzx However, you may always contribute to the wiki directly as in previous times. The contribs have to be added here: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Dissemination_activities http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Communication_activities http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Collaboration_activities Even when you add your contribs straight into the wiki, do not forget to add your partner name to the googledoc and add "(Wiki)" so I keep informed. As said in the googledoc the 6 possible sections you may contribute with entries (the googledoc includes examples) are: 1. Participation in Events (Presentations, round tables, keynotes...) 2. Scientific Papers and Panels 3. Book chapters 4. Training materials & Tutorials 5. Collaboration Meetings/Actions 6. Press Releases and other relevant Communication actions Normally, most partners will have contribs to 1 and 2 sections. Deadline for this is next monday April 14th EoB. Should you have any question/comment, please do contact me. Thanks in advance for your kind cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From suraci at dis.uniroma1.it Mon Apr 21 19:41:06 2014 From: suraci at dis.uniroma1.it (Vincenzo Suraci) Date: Mon, 21 Apr 2014 19:41:06 +0200 Subject: [Fiware-miwi] R: [Fiware-i2nd] LAST CALL - Dissemination Deliverables (WP12) - Contribs Request (Fast&Easy to complete!) - Deadline Apr 14th EoB In-Reply-To: References: Message-ID: <005401cf5d88$e07d09a0$a1771ce0$@dis.uniroma1.it> Dear Carlos, find attached the UNIROMA1 contribution to WP12 periodic report. Best Regards, Vincenzo Suraci _____________________________________ Dr. Vincenzo Suraci "Sapienza" - Universit? di Roma Dipartimento di Ingegneria Informatica, Automatica e Gestionale (DIAG) Via Ariosto, 25 - 00185 Rome - Italy Phone +39 06 77274 037 Fax +39 06 77274 033 Mobile +39 340 156 2258 Mail suraci at dis.uniroma1.it Web Site http://www.dis.uniroma1.it/~suraci Da: fiware-i2nd-bounces at lists.fi-ware.org [mailto:fiware-i2nd-bounces at lists.fi-ware.org] Per conto di CARLOS RALLI UCENDO Inviato: luned? 21 aprile 2014 11:55 A: fiware at lists.fi-ware.org; fiware-cloud at lists.fi-ware.org; fiware-iot at lists.fi-ware.org; Fiware-data at lists.fi-ware.org; FI-WARE, MiWi; fiware-i2nd at lists.fi-ware.org; fiware-apps at lists.fi-ware.eorg; fiware-security at lists.fi-ware.org Oggetto: [Fiware-i2nd] LAST CALL - Dissemination Deliverables (WP12) - Contribs Request (Fast&Easy to complete!) - Deadline Apr 14th EoB Dear Colleagues, So far I can only see the contributions from: iMinds, NEC, IBM-CH, ALU-D, Playsign, SAP(WP3), NSN-H, DT (sent to Carlos by e-mail) ATOS and Ogilvy have committed to send it tomorrow EoB. Please, let me extend the deadline until this wednesday at 12CET. However there will be no further extensions and all contribs not received will not be included in the document to be delivered this friday. As said before, the European Commission may reject the costs of dissemination trips within M30 and M36 not included in this document. Obviously, for partners leaving the project on M36 is extremely important if you want to get all funds related to dissemination of FI-WARE. The googledoc to contribute is still active here: https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_ 73M/edit#heading=h.kgxusv5ldjp Thanks for your understanding and contributions, Best regards. -- ---------------------------------------------------------------------------- -------------------------------------------- Carlos Ralli Ucendo ( ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es Telef?nica I+D SAU Madrid, Spain ---------------------------------------------------------------------------- -------------------------------------------- Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------------- -------------------------------------------- De: Carlos Ralli Ucendo < ralli at tid.es> Fecha: mi?rcoles, 9 de abril de 2014 15:20 Para: " fiware at lists.fi-ware.org" < fiware at lists.fi-ware.org> CC: " fiware-cloud at lists.fi-ware.org" < fiware-cloud at lists.fi-ware.org>, " fiware-iot at lists.fi-ware.org" < fiware-iot at lists.fi-ware.org>, " Fiware-data at lists.fi-ware.org" < Fiware-data at lists.fi-ware.org>, "FI-WARE, MiWi" < fiware-miwi at lists.fi-ware.org>, " fiware-i2nd at lists.fi-ware.org" < fiware-i2nd at lists.fi-ware.org>, " fiware-apps at lists.fi-ware.eorg" < fiware-apps at lists.fi-ware.org>, " fiware-security at lists.fi-ware.org" < fiware-security at lists.fi-ware.org> Asunto: Dissemination Deliverables (WP12) - Contribs Request (Fast&Easy to complete!) - Deadline Apr 14th EoB Dear colleagues, It is time to collect all information regarding dissemination, communication & collaboration actions you performed in the last WP12 reporting period (M30 = Oct 2013 to M36 = Apr 2014, all included). Please, bear in mind that the EC may reject one of your trips for these activities if they are not correctly reported in this new edition of D12.2 and D12.3 documents. This time, to make things easier for all of you I have prepared a Googledoc where you can place your contribs and then I may transfer them myself to the wiki: https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_ 73M/edit#heading=h.o4j1rtrg6tzx However, you may always contribute to the wiki directly as in previous times. The contribs have to be added here: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Disseminati on_activities http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Communicati on_activities http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Collaborati on_activities Even when you add your contribs straight into the wiki, do not forget to add your partner name to the googledoc and add "(Wiki)" so I keep informed. As said in the googledoc the 6 possible sections you may contribute with entries (the googledoc includes examples) are: 1. Participation in Events (Presentations, round tables, keynotes...) 2. Scientific Papers and Panels 3. Book chapters 4. Training materials & Tutorials 5. Collaboration Meetings/Actions 6. Press Releases and other relevant Communication actions Normally, most partners will have contribs to 1 and 2 sections. Deadline for this is next monday April 14th EoB. Should you have any question/comment, please do contact me. Thanks in advance for your kind cooperation. Best regards, -- ---------------------------------------------------------------------------- -------------------------------------------- Carlos Ralli Ucendo ( ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Blog: http://the-internet6.blogspot.com.es Telef?nica I+D SAU Madrid, Spain ---------------------------------------------------------------------------- -------------------------------------------- Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------------- -------------------------------------------- _____ 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 --- Questa e-mail ? priva di virus e malware perch? ? attiva la protezione avast! Antivirus. http://www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1646 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D.1.2.6 - WP12 - M31-M36 - UNIROMA1_2014_04_10.doc Type: application/msword Size: 47104 bytes Desc: not available URL: From mach at zhaw.ch Wed Apr 23 07:37:24 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 23 Apr 2014 05:37:24 +0000 Subject: [Fiware-miwi] Weeky meeting (canceled) Message-ID: Hi folks While going through the last minutes I noticed that the state is unchanged. The APs are still the same, at least from my side. In favor working on working on the open action points, I would like to cancel todays call. Two infos/reminders which came in lately: - Deadline in WP12 to report all Dissemination activities in Period M30-M36 (Oct-Apr) is today 12CET: https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_73M/edit#heading=h.kgxusv5ldjp (see email from Carlos Rally from April 9th, Reminder April 21st) - Tracking of Reviews for R3.3 delivery is done in the following Dashboard: https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 Please also check your open APs in the last minutes: https://docs.google.com/document/d/1qecLMb6MwtYZcTZeUOrsy0MuVMDmUQRuLPnNJgsV_04/edit Best regards Christof ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From toni at playsign.net Wed Apr 23 08:09:34 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 23 Apr 2014 09:09:34 +0300 Subject: [Fiware-miwi] Weeky meeting (canceled) In-Reply-To: References: Message-ID: Ok - one question for the group, same as at the end of prev meeting: Is someone already running our software on some of the fi-ware systems? I mean has a VM that works etc. Am specifically interested in when we could get Tundra instances up somewhere. For example to test how the n-player Pong works with many players and over distances etc. The game has been ready for several months already waiting for a way to do such tests. IIRC we agreed back in January or so that can share (a) VM instance(s?) for Tundra servers + something with a web server for the client side html + code + 3d data files. Something with limited access is fine to begin with but a publicly available server so that anyone could play would be ideal. ~Toni On Wed, Apr 23, 2014 at 8:37 AM, Marti Christof (mach) wrote: > Hi folks > > While going through the last minutes I noticed that the state is unchanged. > The APs are still the same, at least from my side. > > In favor working on working on the open action points, I would like to cancel todays call. > > Two infos/reminders which came in lately: > - Deadline in WP12 to report all Dissemination activities in Period M30-M36 (Oct-Apr) is today 12CET: > https://docs.google.com/document/d/1yijmVTzawgTKayW6aNH_L5LSn7r26yVIpZGh-Wb_73M/edit#heading=h.kgxusv5ldjp > (see email from Carlos Rally from April 9th, Reminder April 21st) > > - Tracking of Reviews for R3.3 delivery is done in the following Dashboard: > https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 > > > Please also check your open APs in the last minutes: > https://docs.google.com/document/d/1qecLMb6MwtYZcTZeUOrsy0MuVMDmUQRuLPnNJgsV_04/edit > > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi From ari.okkonen at cie.fi Wed Apr 23 12:28:27 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Wed, 23 Apr 2014 13:28:27 +0300 Subject: [Fiware-miwi] Hands-on: POI Data Provider GE In-Reply-To: <53064A3A.5070503@dfki.de> References: <53064A3A.5070503@dfki.de> Message-ID: <535795CB.8030201@cie.fi> Hello, I try to address your point about below: On 20.2.2014 20:32, Stefan Lemme wrote: > > Hello, > > after our workshop last week a few questions about the POI Data > Provider raised and hopefully you can provide some insights. > > * [...] Which ontology is used for the category of a POI? How to > handle POIs referring to multiple categories? And what about tags? > (All with regard to multi-lingual content) > > [...] I think support for different category ontologies would be good for generality of this generic system. One possibility for better category is e.g.:*"category": [, ,...]* where is ":" or "" . The latter would be for the default ontology (to be defined). Multilingual presentations of categories is different problem. Translations could reside with ontology definitions or in application specific servers. The same applies for possible icons for categories. Could you tell more about tags. * What kind of tags would be useful here? * How tags would be used? * Who defines tags for a POI? * etc. -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Mon Apr 28 09:39:12 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Mon, 28 Apr 2014 07:39:12 +0000 Subject: [Fiware-miwi] Review of R3.3 UTP und SW availability Message-ID: <764168DC-8C94-4ED7-9233-1AB3D70149AD@zhaw.ch> Hi This weekend I finally hat time to review the Unit Testing Plans & SW. Regarding the large amount of date I could only check the basic structure and compared the tested features with the released according the roadmap. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#List_of_new_features_for_this_release In the R3.3 Dashboard I set the status of all GEi UTP to ?Coord Review? if I found no major topics. https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=24 Most of the UTP and SW are OK. Only the following need some clarifications/updates: - General: I renamed the SW-Releases to ?3.2.3? and ?3.3.3? for all the GEis to be conform with the other packages (removed GEi-Names from the release entry, because they are already in the package-name) - 3D-UI XML-3D SW: Moved the File ?DataFlowProcessing_R3.2.tar.gz? to ?3.2.3? and removed the separate release entry. (no action required) UTP: Missing, but features defined in Roadmap, so we need also an updated UTP, covering those features. - DaaS: SW: Still missing. UTP: Available for 3.2 release. In the roadmap the features are mentioned in the 3.3 release. We need to clarify this. Is it released in 3.2 or 3.3 and move all the content accordingly. - Real/Virtual Interaction There is no update in R3.3, but the roadmap contains features for R3.3. UTP R3.2: contains tests for 40 Features, roadmap contains 41 features (incl. R3.3). (?) - KIARA SW: R3.3.3 SW for RPC over DDS, RPC over REST & FastBuffers components missing. Is promised to be updated today. Integrated KIARA is OK. All the rest seems to be OK. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From jarkko at cyberlightning.com Mon Apr 28 10:59:56 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Mon, 28 Apr 2014 11:59:56 +0300 Subject: [Fiware-miwi] Review of R3.3 UTP und SW availability In-Reply-To: <764168DC-8C94-4ED7-9233-1AB3D70149AD@zhaw.ch> References: <764168DC-8C94-4ED7-9233-1AB3D70149AD@zhaw.ch> Message-ID: Christof, all, Regarding the real-virtual interaction there has been no document update since to us the documentation was actually sufficient for R3.3 and it covers the features also which are part of R3.3. In other words, those features did not directly reflect to the documentation. I take this is not a problem? And regarding to the one missing test case coverage, I will hunt that one down and update the document accordingly. Thank for noticing! - jarkko On Mon, Apr 28, 2014 at 10:39 AM, Marti Christof (mach) wrote: > Hi > > This weekend I finally hat time to review the Unit Testing Plans & SW. > Regarding the large amount of date I could only check the basic structure > and compared the tested features with the released according the roadmap. > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#List_of_new_features_for_this_release > > In the R3.3 Dashboard I set the status of all GEi UTP to ?Coord Review? if > I found no major topics. > > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=24 > > Most of the UTP and SW are OK. Only the following need some > clarifications/updates: > > - General: > I renamed the SW-Releases to ?3.2.3? and ?3.3.3? for all the GEis to be > conform with the other packages (removed GEi-Names from the release entry, > because they are already in the package-name) > > - 3D-UI XML-3D > SW: Moved the File ?DataFlowProcessing_R3.2.tar.gz? to ?3.2.3? and removed > the separate release entry. (no action required) > UTP: Missing, but features defined in Roadmap, so we need also an updated > UTP, covering those features. > > - DaaS: > SW: Still missing. > UTP: Available for 3.2 release. In the roadmap the features are mentioned > in the 3.3 release. We need to clarify this. Is it released in 3.2 or 3.3 > and move all the content accordingly. > > - Real/Virtual Interaction > There is no update in R3.3, but the roadmap contains features for R3.3. > UTP R3.2: contains tests for 40 Features, roadmap contains 41 features > (incl. R3.3). (?) > > - KIARA > SW: R3.3.3 SW for RPC over DDS, RPC over REST & FastBuffers components > missing. > Is promised to be updated today. Integrated KIARA is OK. > > All the rest seems to be OK. > > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > -- Jarkko Vatjus-Anttila VP, Technology Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com Go to www.cybersli.de and enrich your presentations! www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Apr 30 08:32:04 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 30 Apr 2014 06:32:04 +0000 Subject: [Fiware-miwi] Agenda/Minutes for todays meeting Message-ID: <65ADFE9B-D3E4-486D-AB7B-E91B793EEF7B@zhaw.ch> Hi Agenda/Minutes: https://docs.google.com/document/d/1tmYimvBC0RYTo2CPhTDZULRMFEfjgrW_962-1PfcqG8/edit Hangout: https://plus.google.com/hangouts/_/7ecpirb6onne1ns34rnt72o9j8?hl=de Best regards Christof ---- InIT Cloud Computing Lab - ICCLab Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti