From lasse.oorni at ludocraft.com Tue Jun 3 14:41:40 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Tue, 3 Jun 2014 15:41:40 +0300 Subject: [Fiware-miwi] Agenda / Minutes of todays meeting In-Reply-To: <58544E9C-AB86-4DE4-92D4-2234646842DC@zhaw.ch> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> <58544E9C-AB86-4DE4-92D4-2234646842DC@zhaw.ch> Message-ID: Hi, Just to notify, I'll be out on a teaching gig the whole Wednesday and Thursday so I'm unable to attend the weekly meeting tomorrow. - Lasse > Hi > > Sorry the before mail went to the wrong mailing-list. > > And here is the link hangout link: > https://plus.google.com/hangouts/_/g5b3bgri2wfhozrkmjvta636naa?hl=de > > Christof From toni at playsign.net Wed Jun 4 07:36:23 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 4 Jun 2014 08:36:23 +0300 Subject: [Fiware-miwi] pong in testbed Message-ID: Hi, some of you tested already when I posted this link on irc on Monday but here's the info for everyone: WebTundra Pong is finally up in the fi-ware testing place. Folks with IPs registered to the testlab should be able to join an n-player pong room at http://130.206.81.111/pong/Pong.html now. It requires minimum two to play so I'm leaving a client open from here so that even if you join alone you should be able to test .. and if more come it scales, should be fine with tens of clients :) An idea is to use this over the Internet testing opportunity to see how the current Sync GE with websockets & knet messages works for such direct realtime action over perhaps laggy connections etc. Has seemed ok - not perfect but works. Note that there are no optimized movement messages in use here yet (like we have in native Tundra) - but there is client side interpolation for the movement. I've tested this with desktop Chrome & Microsoft IE 11 (on win 8.1 metro) now, Firefox and Chrome on Android should work too. Tundra server seems to stable there, is Lasse's / Ludocraft's VM + fi-ware 3.3 release Tundra install in Ubuntu 12.04 .. I started that Pong there on Monday and haven't noticed probs, keeps on working *knocked-on-wood*. The client side code is what's featured in WebTundra's User Guide & available in https://github.com/playsign/PongThreeJS/tree/ec (master is the original WebRTC version which does not use Tundra, requires one of the web clients to be the server with ammo.js doing the physics. in the Tundra version all the physics and logic are on the server, the client sides are light that way). Cheers, ~Toni -------------- next part -------------- An HTML attachment was scrubbed... URL: From philipp.slusallek at dfki.de Wed Jun 4 08:30:01 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Wed, 04 Jun 2014 08:30:01 +0200 Subject: [Fiware-miwi] Agenda / Minutes of todays meeting In-Reply-To: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> Message-ID: <538EBCE9.80305@dfki.de> Hi And here is the link hangout link: https://plus.google.com/hangouts/_/gs7gh42e5ff7jxngtixouzpeo4a And here are the minutes for today's meeting: https://docs.google.com/document/d/161tLTvD4TqFNOZwVU1UatK8tXGgeTT52oWfZulr_Z84 See you now, Philipp -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- From arto.heikkinen at cie.fi Mon Jun 9 14:46:20 2014 From: arto.heikkinen at cie.fi (Arto Heikkinen) Date: Mon, 09 Jun 2014 15:46:20 +0300 Subject: [Fiware-miwi] Agenda / Minutes of todays meeting In-Reply-To: <538EBCE9.80305@dfki.de> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> <538EBCE9.80305@dfki.de> Message-ID: <5395AC9C.8070303@cie.fi> Hi all, I started working on creating entries of our GEs on the catalogue. There seems to be one major problem: when creating a new enabler, you must specify the Chapter in which the enabler belongs. However, the Catalogue does not seem to know our chapter (Advanced Middleware and Web User Interfaces). Perhaps Christof or Philipp could ask them to add us there? Br, Arto On 4.6.2014 9:30, Philipp Slusallek wrote: > Hi > > And here is the link hangout link: > https://plus.google.com/hangouts/_/gs7gh42e5ff7jxngtixouzpeo4a > > And here are the minutes for today's meeting: > https://docs.google.com/document/d/161tLTvD4TqFNOZwVU1UatK8tXGgeTT52oWfZulr_Z84 > > > See you now, > > Philipp From philipp.slusallek at dfki.de Mon Jun 9 16:16:37 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Mon, 09 Jun 2014 16:16:37 +0200 Subject: [Fiware-miwi] Agenda / Minutes of todays meeting In-Reply-To: <5395AC9C.8070303@cie.fi> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> <538EBCE9.80305@dfki.de> <5395AC9C.8070303@cie.fi> Message-ID: <5395C1C5.90201@dfki.de> Hi, relaying this to Miguel who probably knows what to do or whom to ask. Thanks, Philipp Am 09.06.2014 14:46, schrieb Arto Heikkinen: > Hi all, > > I started working on creating entries of our GEs on the catalogue. > > There seems to be one major problem: when creating a new enabler, you > must specify the Chapter in which the enabler belongs. However, the > Catalogue does not seem to know our chapter (Advanced Middleware and Web > User Interfaces). > > Perhaps Christof or Philipp could ask them to add us there? > > Br, > Arto > > On 4.6.2014 9:30, Philipp Slusallek wrote: >> Hi >> >> And here is the link hangout link: >> https://plus.google.com/hangouts/_/gs7gh42e5ff7jxngtixouzpeo4a >> >> And here are the minutes for today's meeting: >> https://docs.google.com/document/d/161tLTvD4TqFNOZwVU1UatK8tXGgeTT52oWfZulr_Z84 >> >> >> >> See you now, >> >> Philipp > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mcp at tid.es Mon Jun 9 16:19:39 2014 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 09 Jun 2014 16:19:39 +0200 Subject: [Fiware-miwi] Agenda / Minutes of todays meeting In-Reply-To: <5395C1C5.90201@dfki.de> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> <538EBCE9.80305@dfki.de> <5395AC9C.8070303@cie.fi> <5395C1C5.90201@dfki.de> Message-ID: <5395C27B.5050706@tid.es> Hi there, Can you please add WP13 to the catalogue? Thanks a lot! Miguel El 09/06/2014 16:16, Philipp Slusallek escribi?: > Hi, > > relaying this to Miguel who probably knows what to do or whom to ask. > > Thanks, > > Philipp > > Am 09.06.2014 14:46, schrieb Arto Heikkinen: >> Hi all, >> >> I started working on creating entries of our GEs on the catalogue. >> >> There seems to be one major problem: when creating a new enabler, you >> must specify the Chapter in which the enabler belongs. However, the >> Catalogue does not seem to know our chapter (Advanced Middleware and Web >> User Interfaces). >> >> Perhaps Christof or Philipp could ask them to add us there? >> >> Br, >> Arto >> >> On 4.6.2014 9:30, Philipp Slusallek wrote: >>> Hi >>> >>> And here is the link hangout link: >>> https://plus.google.com/hangouts/_/gs7gh42e5ff7jxngtixouzpeo4a >>> >>> And here are the minutes for today's meeting: >>> https://docs.google.com/document/d/161tLTvD4TqFNOZwVU1UatK8tXGgeTT52oWfZulr_Z84 >>> >>> >>> >>> >>> See you now, >>> >>> Philipp >> > > -- ---------------------------------------------------------------------- _/ _/_/ 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 From prodriguez at dit.upm.es Mon Jun 9 16:29:43 2014 From: prodriguez at dit.upm.es (Pedro Rodriguez) Date: Mon, 9 Jun 2014 16:29:43 +0200 Subject: [Fiware-miwi] [Fiware-catalogue] Agenda / Minutes of todays meeting In-Reply-To: <5395C27B.5050706@tid.es> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> <538EBCE9.80305@dfki.de> <5395AC9C.8070303@cie.fi> <5395C1C5.90201@dfki.de> <5395C27B.5050706@tid.es> Message-ID: Hi all, I have added "Advanced Middleware and Web User Interfaces? to the list of Chapters. Keep in mind it will appear in the ?Browse by Chapter? in the Enabler List once there is content associated with it. You should be able to select it when creating a new Enabler. Please write to fiware-catalogue at lists.fi-ware.org if you have any problems. Best, --? Pedro Rodr?guez On 9 Jun 2014 at 16:20:43, Miguel Carrillo (mcp at tid.es) wrote: Hi there, Can you please add WP13 to the catalogue? Thanks a lot! Miguel El 09/06/2014 16:16, Philipp Slusallek escribi?: > Hi, > > relaying this to Miguel who probably knows what to do or whom to ask. > > Thanks, > > Philipp > > Am 09.06.2014 14:46, schrieb Arto Heikkinen: >> Hi all, >> >> I started working on creating entries of our GEs on the catalogue. >> >> There seems to be one major problem: when creating a new enabler, you >> must specify the Chapter in which the enabler belongs. However, the >> Catalogue does not seem to know our chapter (Advanced Middleware and Web >> User Interfaces). >> >> Perhaps Christof or Philipp could ask them to add us there? >> >> Br, >> Arto >> >> On 4.6.2014 9:30, Philipp Slusallek wrote: >>> Hi >>> >>> And here is the link hangout link: >>> https://plus.google.com/hangouts/_/gs7gh42e5ff7jxngtixouzpeo4a >>> >>> And here are the minutes for today's meeting: >>> https://docs.google.com/document/d/161tLTvD4TqFNOZwVU1UatK8tXGgeTT52oWfZulr_Z84 >>> >>> >>> >>> >>> See you now, >>> >>> Philipp >> > > -- ---------------------------------------------------------------------- _/ _/_/ 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 _______________________________________________ Fiware-catalogue mailing list Fiware-catalogue at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-catalogue -------------- next part -------------- An HTML attachment was scrubbed... URL: From arto.heikkinen at cie.fi Tue Jun 10 14:47:20 2014 From: arto.heikkinen at cie.fi (Arto Heikkinen) Date: Tue, 10 Jun 2014 15:47:20 +0300 Subject: [Fiware-miwi] [Fiware-catalogue] Agenda / Minutes of todays meeting In-Reply-To: References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> <538EBCE9.80305@dfki.de> <5395AC9C.8070303@cie.fi> <5395C1C5.90201@dfki.de> <5395C27B.5050706@tid.es> Message-ID: <5396FE58.4020003@cie.fi> Thanks Pedro and all, I was now able to create new Enablers in the catalogue. Br, Arto On 9.6.2014 17:29, Pedro Rodriguez wrote: > Hi all, > > I have added "Advanced Middleware and Web User Interfaces? to the list > of Chapters. Keep in mind it will appear in the ?Browse by Chapter? in > the Enabler List once there is content associated with it. You should > be able to select it when creating a new Enabler. Please write to > fiware-catalogue at lists.fi-ware.org if you have any problems. > > Best, > -- > Pedro Rodr?guez > > On 9 Jun 2014 at 16:20:43, Miguel Carrillo (mcp at tid.es > ) wrote: > >> Hi there, >> >> Can you please add WP13 to the catalogue? >> >> Thanks a lot! >> >> Miguel >> >> El 09/06/2014 16:16, Philipp Slusallek escribi?: >> > Hi, >> > >> > relaying this to Miguel who probably knows what to do or whom to ask. >> > >> > Thanks, >> > >> > Philipp >> > >> > Am 09.06.2014 14:46, schrieb Arto Heikkinen: >> >> Hi all, >> >> >> >> I started working on creating entries of our GEs on the catalogue. >> >> >> >> There seems to be one major problem: when creating a new enabler, you >> >> must specify the Chapter in which the enabler belongs. However, the >> >> Catalogue does not seem to know our chapter (Advanced Middleware >> and Web >> >> User Interfaces). >> >> >> >> Perhaps Christof or Philipp could ask them to add us there? >> >> >> >> Br, >> >> Arto >> >> >> >> On 4.6.2014 9:30, Philipp Slusallek wrote: >> >>> Hi >> >>> >> >>> And here is the link hangout link: >> >>> https://plus.google.com/hangouts/_/gs7gh42e5ff7jxngtixouzpeo4a >> >>> >> >>> And here are the minutes for today's meeting: >> >>> >> https://docs.google.com/document/d/161tLTvD4TqFNOZwVU1UatK8tXGgeTT52oWfZulr_Z84 >> >>> >> >>> >> >>> >> >>> >> >>> See you now, >> >>> >> >>> Philipp >> >> >> > >> > >> >> -- >> ---------------------------------------------------------------------- >> _/ _/_/ 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 >> _______________________________________________ >> Fiware-catalogue mailing list >> Fiware-catalogue at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-catalogue -------------- next part -------------- An HTML attachment was scrubbed... URL: From philipp.slusallek at dfki.de Wed Jun 11 08:26:54 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Wed, 11 Jun 2014 08:26:54 +0200 Subject: [Fiware-miwi] Agenda / Minutes of todays meeting In-Reply-To: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> References: <35FED579-09A6-4F67-959B-95FF330F3F30@zhaw.ch> Message-ID: <5397F6AE.7060208@dfki.de> Hi Here is the link hangout link: https://plus.google.com/hangouts/_/gystsn5672bgoqwr3n3wds7ioya And here are the draft minutes for today's meeting: https://docs.google.com/document/d/12VyBv8ryjTqxtJzKPO6J5neQt-lklLnEDOFqonMVaYc See you now, Philipp -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- From torsten.spieldenner at dfki.de Wed Jun 11 14:51:35 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Wed, 11 Jun 2014 14:51:35 +0200 Subject: [Fiware-miwi] Paper on efficient binary transmission format Message-ID: <539850D7.5070707@dfki.de> Hello, while the paper on XML3D asset instances still awaits approval for the mailing list due to its file size, here is the paper on the binary transmission format for 3D data. As for the instancing paper, this paper is not published yet, so please handle with care and do not redistribute it :) Best Torsten -------------- next part -------------- A non-text attachment was scrubbed... Name: paper.pdf Type: application/pdf Size: 272943 bytes Desc: not available URL: From torsten.spieldenner at dfki.de Wed Jun 11 16:50:27 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Wed, 11 Jun 2014 16:50:27 +0200 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting Message-ID: <53986CB3.2020803@dfki.de> Hello all, as discussed in the weekly call this morning, we are currently looking for a suitable date for a meeting to further discuss the planned GE integration demo. A possible date for us would already be *tomorrow at 2 pm CEST *. Another option could be next week Monday or Tuesday. I've set up a doodle poll to find a date that fits best for everyone: http://doodle.com/mn2nmztxut45ukbu Best, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Jun 11 17:16:39 2014 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 11 Jun 2014 17:16:39 +0200 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: <53986CB3.2020803@dfki.de> References: <53986CB3.2020803@dfki.de> Message-ID: <539872D7.70604@tid.es> Dear all, Please use the new address (fiware-miwi at lists.fi-ware.org) and delete the old one (fiware-miwi at lists.fi-ware.eu) from your address books. It has been used twice today and it is theoretically deprecated. I am sorry to be such a boring person but someone's got to do it! :) Thanks a lot Miguel El 11/06/2014 16:50, Torsten Spieldenner escribi?: Hello all, as discussed in the weekly call this morning, we are currently looking for a suitable date for a meeting to further discuss the planned GE integration demo. A possible date for us would already be tomorrow at 2 pm CEST . Another option could be next week Monday or Tuesday. I've set up a doodle poll to find a date that fits best for everyone: http://doodle.com/mn2nmztxut45ukbu Best, Torsten _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 torsten.spieldenner at dfki.de Wed Jun 11 14:48:04 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Wed, 11 Jun 2014 14:48:04 +0200 Subject: [Fiware-miwi] Paper on XML3D Asset Instancing Message-ID: <53985004.6090503@dfki.de> Hello, as Philipp has pointed out in today's weekly call, our papers on the new XML3D asset instancing technique and the efficient transmission format for 3D data got accepted. Please find the paper on asset instancing attached. As it is not officially published in the proceedings yet, I'd like to ask you not to redistribute it. Best, Torsten -------------- next part -------------- A non-text attachment was scrubbed... Name: xml3d-instance.pdf Type: application/pdf Size: 2909473 bytes Desc: not available URL: From torsten.spieldenner at dfki.de Thu Jun 12 11:40:47 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Thu, 12 Jun 2014 11:40:47 +0200 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: <53997289.30601@gmail.com> References: <53997289.30601@gmail.com> Message-ID: <5399759F.3050405@dfki.de> Hello, due to a clash of dates on Tuesday which I was not aware of when I set up the Doodle, we are going to have the call*today at 2 pm / CEST*, which is the option with the second most answers and seems to be the alternative which works best for everyone. See you there! Best, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Thu Jun 12 12:26:55 2014 From: toni at playsign.net (toni at playsign.net) Date: Thu, 12 Jun 2014 10:26:55 +0000 Subject: [Fiware-miwi] =?utf-8?q?FI-PPP_Integration_Demo_Meeting?= In-Reply-To: <53986CB3.2020803@dfki.de> References: <53986CB3.2020803@dfki.de> Message-ID: <20140612103954.06B6E4212F1@dionysos.netplaza.fi> ok - someone from us (Playsign) will be there too, me and/or Erno I figure. BTW the oulu3d service is now in sort of private but accessible alpha testing - which will be announced a little tomorrow. Please do not distribute the link (especially towards the local press here or anything like that..) but for the purposes of planning this demo and evaluating 3D-UI & Sync etc. techs please feel free to test: http://beta.adminotech.com/virtuaalioulu/ - mostly tested with Chrome, Firefox works too, other browsers (Opera, IE) will be added later. In my thinking that is a MiWi demo, and as discussed before and written in the plan we can add AR and POIs and why not 2D & 3D capture to the same thing (like the guys guys originally did with gmaps). OTOH the content with the on-demand loading & LoDding challenges etc would be interesting to test with the new DFKI techs etc. Sent from Windows Mail From: torsten.spieldenner at dfki.de Sent: ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM To: FI-WARE, MiWi Hello all, as discussed in the weekly call this morning, we are currently looking for a suitable date for a meeting to further discuss the planned GE integration demo. A possible date for us would already be tomorrow at 2 pm CEST . Another option could be next week Monday or Tuesday. I've set up a doodle poll to find a date that fits best for everyone: http://doodle.com/mn2nmztxut45ukbu Best, Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Thu Jun 12 13:09:10 2014 From: toni at playsign.net (Toni Alatalo) Date: Thu, 12 Jun 2014 14:09:10 +0300 Subject: [Fiware-miwi] Fwd: FI-PPP Integration Demo Meeting References: <20140612103954.06B6E4212F1@dionysos.netplaza.fi> Message-ID: <748D8017-44AB-4E73-84F0-601656AB5D45@playsign.net> Oops same to .org in case V?litetty viesti: > L?hett?j?: > P?iv?ys: June 12, 2014 at 1:26:55 PM GMT+3 > Vastaanottaja: "torsten.spieldenner at dfki.de" , "FI-WARE, MiWi" > Aihe: Re: [Fiware-miwi] FI-PPP Integration Demo Meeting > > ok - someone from us (Playsign) will be there too, me and/or Erno I figure. > > BTW the oulu3d service is now in sort of private but accessible alpha testing - which will be announced a little tomorrow. Please do not distribute the link (especially towards the local press here or anything like that..) but for the purposes of planning this demo and evaluating 3D-UI & Sync etc. techs please feel free to test: > > http://beta.adminotech.com/virtuaalioulu/ - mostly tested with Chrome, Firefox works too, other browsers (Opera, IE) will be added later. > > In my thinking that is a MiWi demo, and as discussed before and written in the plan we can add AR and POIs and why not 2D & 3D capture to the same thing (like the guys guys originally did with gmaps). OTOH the content with the on-demand loading & LoDding challenges etc would be interesting to test with the new DFKI techs etc. > > Sent from Windows Mail > > From: torsten.spieldenner at dfki.de > Sent: ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM > To: FI-WARE, MiWi > > Hello all, > > as discussed in the weekly call this morning, we are currently looking for a suitable date for a meeting to further discuss the planned GE integration demo. > > A possible date for us would already be tomorrow at 2 pm CEST . > > Another option could be next week Monday or Tuesday. > > I've set up a doodle poll to find a date that fits best for everyone: > > http://doodle.com/mn2nmztxut45ukbu > > Best, > Torsten > > > _______________________________________________ > 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 jarkko at cyberlightning.com Thu Jun 12 13:33:58 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Thu, 12 Jun 2014 14:33:58 +0300 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: <20140612103954.06B6E4212F1@dionysos.netplaza.fi> References: <53986CB3.2020803@dfki.de> <20140612103954.06B6E4212F1@dionysos.netplaza.fi> Message-ID: One thing related to this note, as we discussed in the weekly meeting, was the content itself. I guess the Oulu3D is not movable to anywhere from meshmoon, which is a conflicting fact that in the end the project demos need to run in fi-cloud. Hence, we are forced also to talk about how and what content to setup there, for example, in the tundra server what Lasse set up (and Toni installed the pong demo already). This is one topic for the demonstration meeting we have shortly, btw, is it a telco or google hangout? Did someone send a link already? - jarkko On Thu, Jun 12, 2014 at 1:26 PM, wrote: > ok - someone from us (Playsign) will be there too, me and/or Erno I > figure. > > BTW the oulu3d service is now in sort of private but accessible alpha > testing - which will be announced a little tomorrow. Please do not > distribute the link (especially towards the local press here or anything > like that..) but for the purposes of planning this demo and evaluating > 3D-UI & Sync etc. techs please feel free to test: > > http://beta.adminotech.com/virtuaalioulu/ - mostly tested with Chrome, > Firefox works too, other browsers (Opera, IE) will be added later. > > In my thinking that is a MiWi demo, and as discussed before and written in > the plan we can add AR and POIs and why not 2D & 3D capture to the same > thing (like the guys guys originally did with gmaps). OTOH the content with > the on-demand loading & LoDding challenges etc would be interesting to test > with the new DFKI techs etc. > > Sent from Windows Mail > > *From:* torsten.spieldenner at dfki.de > *Sent:* ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM > *To:* FI-WARE, MiWi > > Hello all, > > as discussed in the weekly call this morning, we are currently looking for > a suitable date for a meeting to further discuss the planned GE integration > demo. > > A possible date for us would already be *tomorrow at 2 pm CEST *. > > Another option could be next week Monday or Tuesday. > > I've set up a doodle poll to find a date that fits best for everyone: > > http://doodle.com/mn2nmztxut45ukbu > > Best, > Torsten > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > > -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.spieldenner at dfki.de Thu Jun 12 13:35:07 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Thu, 12 Jun 2014 13:35:07 +0200 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: References: <53986CB3.2020803@dfki.de> <20140612103954.06B6E4212F1@dionysos.netplaza.fi> Message-ID: <5399906B.3060102@dfki.de> Hello, I am going to setup a Hangout in some minutes that should then be ready until 2 pm :) Best Torsten Am 6/12/2014 1:33 PM, schrieb Jarkko Vatjus-Anttila: > One thing related to this note, as we discussed in the weekly meeting, > was the content itself. I guess the Oulu3D is not movable to anywhere > from meshmoon, which is a conflicting fact that in the end the project > demos need to run in fi-cloud. > > Hence, we are forced also to talk about how and what content to setup > there, for example, in the tundra server what Lasse set up (and Toni > installed the pong demo already). > > This is one topic for the demonstration meeting we have shortly, btw, > is it a telco or google hangout? Did someone send a link already? > > - jarkko > > > On Thu, Jun 12, 2014 at 1:26 PM, > wrote: > > ok - someone from us (Playsign) will be there too, me and/or Erno > I figure. > > BTW the oulu3d service is now in sort of private but accessible > alpha testing - which will be announced a little tomorrow. Please > do not distribute the link (especially towards the local press > here or anything like that..) but for the purposes of planning > this demo and evaluating 3D-UI & Sync etc. techs please feel free > to test: > > http://beta.adminotech.com/virtuaalioulu/ - mostly tested with > Chrome, Firefox works too, other browsers (Opera, IE) will be > added later. > > In my thinking that is a MiWi demo, and as discussed before and > written in the plan we can add AR and POIs and why not 2D & 3D > capture to the same thing (like the guys guys originally did with > gmaps). OTOH the content with the on-demand loading & LoDding > challenges etc would be interesting to test with the new DFKI > techs etc. > > Sent from Windows Mail > > *From:* torsten.spieldenner at dfki.de > > *Sent:* ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM > *To:* FI-WARE, MiWi > > Hello all, > > as discussed in the weekly call this morning, we are currently > looking for a suitable date for a meeting to further discuss the > planned GE integration demo. > > A possible date for us would already be *tomorrow at 2 pm CEST *. > > Another option could be next week Monday or Tuesday. > > I've set up a doodle poll to find a date that fits best for everyone: > > http://doodle.com/mn2nmztxut45ukbu > > Best, > Torsten > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > > > > > -- > Jarkko Vatjus-Anttila > CTO > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > See our new press release: > http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ > > www.cyberlightning.com > > This e-mail and all attached material are confidential and may contain > legally privileged information. If you are not the intended recipient, > please contact the sender and delete the e-mail from your system > without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Thu Jun 12 13:45:18 2014 From: toni at playsign.net (Toni Alatalo) Date: Thu, 12 Jun 2014 14:45:18 +0300 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: <5399759F.3050405@dfki.de> References: <53997289.30601@gmail.com> <5399759F.3050405@dfki.de> Message-ID: Crap windows mail seems to bug for me and delete email contents by replacing it with the auto signature thing there repeatedly, had to stop using that app :p .. here's quick rewrite of what got deleted from my earlier mail about demos etc., and this time to the *.org address as well: Besides the official Oulu3D demo, there's now also a port of the old 3D-UI & POI integration working with the current POI backend -- POI folks at CIE (Ari O. & Arto) did this port recently and it's live at: http://dev.cie.fi/FI-WARE/aok/POIThreeJS/POI.html And again the main live thing targeted for end users is in WIP testing in (again please don't distribute this link before tomorrow at least..) http://beta.adminotech.com/virtuaalioulu/ I also wrote some info about the software there, quick repeat: 3D-UI WebTundra dev2 branch, against a Tundra server. Jonne has made a visibility culling manager WebTundra plugin for dealing with the mass -- similar to the GridManager we prototyped with Tapani at playsign last Fall. As a part of the alpha/beta publishing we'll also put the new codes up (memory management plugin, the apps in the city for voting and guided tour etc.) and work with WebTundra core merges etc. -- that's me and Jonne next week I think. I think we'll make a oulu3dlive git repo for the apps, or separate repos for the diff apps or something, we'll see. Cheers, ~Toni On Thu, Jun 12, 2014 at 12:40 PM, Torsten Spieldenner < torsten.spieldenner at dfki.de> wrote: > Hello, > > due to a clash of dates on Tuesday which I was not aware of when I set up > the Doodle, we are going to have the call* today at 2 pm / CEST*, which > is the option with the second most answers and seems to be the alternative > which works best for everyone. > > See you there! > > Best, > Torsten > > > > _______________________________________________ > 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 toni at playsign.net Thu Jun 12 13:51:29 2014 From: toni at playsign.net (Toni Alatalo) Date: Thu, 12 Jun 2014 14:51:29 +0300 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: References: <53986CB3.2020803@dfki.de> <20140612103954.06B6E4212F1@dionysos.netplaza.fi> Message-ID: This is actually not the case: Oulu3D is creative commons and meant for use anywhere by whatever means. We are actually using it with Unity here in UbiOulu Summer School's Mobile AR workshop right now. The SVN has both model sources (max & blender) and exports (now for Ogre for WebRocket, and I've the FBX exports for Unity in a google drive share for now). It needs to work on normal realXtend stuff for many reasons and as that already works in fi-lab (the pong demo) my goal and plan has been to get the city model there too. I think doing that can be a part of the work to set up the demos. We can save the TXML of the integrated overall scene from the current scene on Meshmoon to get started with using it also elsewhere etc. Possibly use glTF or DFKI's new stuff for optimized loading etc -- optimizing the loading is in the agenda of the city model project (outside fi-ware) as well. ~Toni On Thu, Jun 12, 2014 at 2:33 PM, Jarkko Vatjus-Anttila < jarkko at cyberlightning.com> wrote: > One thing related to this note, as we discussed in the weekly meeting, was > the content itself. I guess the Oulu3D is not movable to anywhere from > meshmoon, which is a conflicting fact that in the end the project demos > need to run in fi-cloud. > > Hence, we are forced also to talk about how and what content to setup > there, for example, in the tundra server what Lasse set up (and Toni > installed the pong demo already). > > This is one topic for the demonstration meeting we have shortly, btw, is > it a telco or google hangout? Did someone send a link already? > > - jarkko > > > On Thu, Jun 12, 2014 at 1:26 PM, wrote: > >> ok - someone from us (Playsign) will be there too, me and/or Erno I >> figure. >> >> BTW the oulu3d service is now in sort of private but accessible alpha >> testing - which will be announced a little tomorrow. Please do not >> distribute the link (especially towards the local press here or anything >> like that..) but for the purposes of planning this demo and evaluating >> 3D-UI & Sync etc. techs please feel free to test: >> >> http://beta.adminotech.com/virtuaalioulu/ - mostly tested with Chrome, >> Firefox works too, other browsers (Opera, IE) will be added later. >> >> In my thinking that is a MiWi demo, and as discussed before and written >> in the plan we can add AR and POIs and why not 2D & 3D capture to the same >> thing (like the guys guys originally did with gmaps). OTOH the content with >> the on-demand loading & LoDding challenges etc would be interesting to test >> with the new DFKI techs etc. >> >> Sent from Windows Mail >> >> *From:* torsten.spieldenner at dfki.de >> *Sent:* ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM >> *To:* FI-WARE, MiWi >> >> Hello all, >> >> as discussed in the weekly call this morning, we are currently looking >> for a suitable date for a meeting to further discuss the planned GE >> integration demo. >> >> A possible date for us would already be *tomorrow at 2 pm CEST *. >> >> Another option could be next week Monday or Tuesday. >> >> I've set up a doodle poll to find a date that fits best for everyone: >> >> http://doodle.com/mn2nmztxut45ukbu >> >> Best, >> Torsten >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-miwi >> >> > > > -- > Jarkko Vatjus-Anttila > CTO > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > See our new press release: > http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ > > www.cyberlightning.com > > This e-mail and all attached material are confidential and may contain > legally privileged information. If you are not the intended recipient, > please contact the sender and delete the e-mail from your system without > producing, distributing or retaining copies thereof. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jarkko at cyberlightning.com Thu Jun 12 13:53:27 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Thu, 12 Jun 2014 14:53:27 +0300 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: References: <53986CB3.2020803@dfki.de> <20140612103954.06B6E4212F1@dionysos.netplaza.fi> Message-ID: Maybe this was some sort of confusion on my side, but this is absolutely fantastic :) Good that you clarified. On Thu, Jun 12, 2014 at 2:51 PM, Toni Alatalo wrote: > This is actually not the case: Oulu3D is creative commons and meant for > use anywhere by whatever means. We are actually using it with Unity here in > UbiOulu Summer School's Mobile AR workshop right now. > > The SVN has both model sources (max & blender) and exports (now for Ogre > for WebRocket, and I've the FBX exports for Unity in a google drive share > for now). > > It needs to work on normal realXtend stuff for many reasons and as that > already works in fi-lab (the pong demo) my goal and plan has been to get > the city model there too. I think doing that can be a part of the work to > set up the demos. We can save the TXML of the integrated overall scene from > the current scene on Meshmoon to get started with using it also elsewhere > etc. Possibly use glTF or DFKI's new stuff for optimized loading etc -- > optimizing the loading is in the agenda of the city model project (outside > fi-ware) as well. > > ~Toni > > On Thu, Jun 12, 2014 at 2:33 PM, Jarkko Vatjus-Anttila < > jarkko at cyberlightning.com> wrote: > >> One thing related to this note, as we discussed in the weekly meeting, >> was the content itself. I guess the Oulu3D is not movable to anywhere from >> meshmoon, which is a conflicting fact that in the end the project demos >> need to run in fi-cloud. >> >> Hence, we are forced also to talk about how and what content to setup >> there, for example, in the tundra server what Lasse set up (and Toni >> installed the pong demo already). >> >> This is one topic for the demonstration meeting we have shortly, btw, is >> it a telco or google hangout? Did someone send a link already? >> >> - jarkko >> >> >> On Thu, Jun 12, 2014 at 1:26 PM, wrote: >> >>> ok - someone from us (Playsign) will be there too, me and/or Erno I >>> figure. >>> >>> BTW the oulu3d service is now in sort of private but accessible alpha >>> testing - which will be announced a little tomorrow. Please do not >>> distribute the link (especially towards the local press here or anything >>> like that..) but for the purposes of planning this demo and evaluating >>> 3D-UI & Sync etc. techs please feel free to test: >>> >>> http://beta.adminotech.com/virtuaalioulu/ - mostly tested with Chrome, >>> Firefox works too, other browsers (Opera, IE) will be added later. >>> >>> In my thinking that is a MiWi demo, and as discussed before and written >>> in the plan we can add AR and POIs and why not 2D & 3D capture to the same >>> thing (like the guys guys originally did with gmaps). OTOH the content with >>> the on-demand loading & LoDding challenges etc would be interesting to test >>> with the new DFKI techs etc. >>> >>> Sent from Windows Mail >>> >>> *From:* torsten.spieldenner at dfki.de >>> *Sent:* ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM >>> *To:* FI-WARE, MiWi >>> >>> Hello all, >>> >>> as discussed in the weekly call this morning, we are currently looking >>> for a suitable date for a meeting to further discuss the planned GE >>> integration demo. >>> >>> A possible date for us would already be *tomorrow at 2 pm CEST *. >>> >>> Another option could be next week Monday or Tuesday. >>> >>> I've set up a doodle poll to find a date that fits best for everyone: >>> >>> http://doodle.com/mn2nmztxut45ukbu >>> >>> Best, >>> Torsten >>> >>> >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-miwi >>> >>> >> >> >> -- >> Jarkko Vatjus-Anttila >> CTO >> Cyberlightning Ltd. >> >> mobile. +358 405245142 >> email. jarkko at cyberlightning.com >> >> See our new press release: >> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ >> >> www.cyberlightning.com >> >> This e-mail and all attached material are confidential and may contain >> legally privileged information. If you are not the intended recipient, >> please contact the sender and delete the e-mail from your system without >> producing, distributing or retaining copies thereof. >> > > -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.spieldenner at dfki.de Thu Jun 12 13:56:01 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Thu, 12 Jun 2014 13:56:01 +0200 Subject: [Fiware-miwi] FI-PPP Integration Demo Meeting In-Reply-To: <5399906B.3060102@dfki.de> References: <53986CB3.2020803@dfki.de> <20140612103954.06B6E4212F1@dionysos.netplaza.fi> <5399906B.3060102@dfki.de> Message-ID: <53999551.9050709@dfki.de> Hello, the Hangout is now available here: https://plus.google.com/hangouts/_/gyzkd5hobmmr2alc3yrqgohq3ia ... and as already for the weekly call, the demo planning document is available here: https://docs.google.com/document/d/1fz5-LRX4vbBWjiUSh4bYkmd66nCbt1EIdJ5N19dJq2o/edit?pli=1#heading=h.behye25r6auo ~ Torsten Am 6/12/2014 1:35 PM, schrieb Torsten Spieldenner: > Hello, > > I am going to setup a Hangout in some minutes that should then be > ready until 2 pm :) > > Best > > Torsten > > Am 6/12/2014 1:33 PM, schrieb Jarkko Vatjus-Anttila: >> One thing related to this note, as we discussed in the weekly >> meeting, was the content itself. I guess the Oulu3D is not movable to >> anywhere from meshmoon, which is a conflicting fact that in the end >> the project demos need to run in fi-cloud. >> >> Hence, we are forced also to talk about how and what content to setup >> there, for example, in the tundra server what Lasse set up (and Toni >> installed the pong demo already). >> >> This is one topic for the demonstration meeting we have shortly, btw, >> is it a telco or google hangout? Did someone send a link already? >> >> - jarkko >> >> >> On Thu, Jun 12, 2014 at 1:26 PM, > > wrote: >> >> ok - someone from us (Playsign) will be there too, me and/or Erno >> I figure. >> >> BTW the oulu3d service is now in sort of private but accessible >> alpha testing - which will be announced a little tomorrow. Please >> do not distribute the link (especially towards the local press >> here or anything like that..) but for the purposes of planning >> this demo and evaluating 3D-UI & Sync etc. techs please feel free >> to test: >> >> http://beta.adminotech.com/virtuaalioulu/ - mostly tested with >> Chrome, Firefox works too, other browsers (Opera, IE) will be >> added later. >> >> In my thinking that is a MiWi demo, and as discussed before and >> written in the plan we can add AR and POIs and why not 2D & 3D >> capture to the same thing (like the guys guys originally did with >> gmaps). OTOH the content with the on-demand loading & LoDding >> challenges etc would be interesting to test with the new DFKI >> techs etc. >> >> Sent from Windows Mail >> >> *From:* torsten.spieldenner at dfki.de >> >> *Sent:* ?Wednesday?, ?June? ?11?, ?2014 ?5?:?50? ?PM >> *To:* FI-WARE, MiWi >> >> Hello all, >> >> as discussed in the weekly call this morning, we are currently >> looking for a suitable date for a meeting to further discuss the >> planned GE integration demo. >> >> A possible date for us would already be *tomorrow at 2 pm CEST *. >> >> Another option could be next week Monday or Tuesday. >> >> I've set up a doodle poll to find a date that fits best for everyone: >> >> http://doodle.com/mn2nmztxut45ukbu >> >> Best, >> Torsten >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-miwi >> >> >> >> >> -- >> Jarkko Vatjus-Anttila >> CTO >> Cyberlightning Ltd. >> >> mobile. +358 405245142 >> email. jarkko at cyberlightning.com >> >> See our new press release: >> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ >> >> www.cyberlightning.com >> >> This e-mail and all attached material are confidential and may >> contain legally privileged information. If you are not the intended >> recipient, please contact the sender and delete the e-mail from your >> system without producing, distributing or retaining copies thereof. > > > > _______________________________________________ > 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 Jun 18 08:22:29 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 18 Jun 2014 06:22:29 +0000 Subject: [Fiware-miwi] Agenda Minutes of todays weekly meeting Message-ID: Hi I prepared the Agenda/Minutes for todays meeting: https://docs.google.com/document/d/1-nZC6m6R6EhwPbyBacu7z4vyTPOQ7s535zSGwPCvaHA/edit Hangout is here: https://plus.google.com/hangouts/_/gzzfvnqrgicotrjkmd4esk7scea?hl=de See you in a few minutes Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From philipp.slusallek at dfki.de Wed Jun 18 08:57:29 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Wed, 18 Jun 2014 08:57:29 +0200 Subject: [Fiware-miwi] Agenda Minutes of todays weekly meeting In-Reply-To: References: Message-ID: <53A13859.1060607@dfki.de> Hi, Sorry for the late notice: I had to go to Berlin on short notice and thus cannot joint today. Best, Philipp Am 18.06.2014 08:22, schrieb Marti Christof (mach): > Hi > > I prepared the Agenda/Minutes for todays meeting: > https://docs.google.com/document/d/1-nZC6m6R6EhwPbyBacu7z4vyTPOQ7s535zSGwPCvaHA/edit > > Hangout is here: > https://plus.google.com/hangouts/_/gzzfvnqrgicotrjkmd4esk7scea?hl=de > > See you in a few minutes > > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > _______________________________________________ > 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: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mcp at tid.es Fri Jun 20 12:45:27 2014 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 20 Jun 2014 12:45:27 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery Message-ID: <53A410C7.7000107@tid.es> Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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 Fri Jun 20 12:52:39 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Fri, 20 Jun 2014 10:52:39 +0000 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> Message-ID: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-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 mcp at tid.es Fri Jun 20 15:21:52 2014 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 20 Jun 2014 15:21:52 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> Message-ID: <53A43570.4070402@tid.es> Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 philipp.slusallek at dfki.de Sat Jun 21 10:59:26 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Sat, 21 Jun 2014 10:59:26 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <53A410C7.7000107@tid.es> References: <53A410C7.7000107@tid.es> Message-ID: <53A5496E.1040001@dfki.de> Excellent! Thanks you, Philipp Am 20.06.2014 12:45, schrieb Miguel Carrillo: > Dear WP13 members, > > I thought that you might appreciate an update on the Release3 manuals + > software release. > > WP13 has been prioritised in the reviews to the detriment of other WPs > because we share your concern that WP13 is the only one that actually > "does not exist" in the catalogue and the wiki. You can see the > difference with others in terms of status: > > * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 > > > On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 > exceptions) to the public wiki and generate the deliverables. > > One of the 2 remaining manuals from eProsima has been approved today > and, to avoid the usual bottleneck, I have been talking directly to > Jaime in the last interactions. > > Summary: the publication of the manuals and the delivery is in the hands > of the WPL/WPA. > > Best regards, > > 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 > ---------------------------------------------------------------------- > > > ------------------------------------------------------------------------ > > 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-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: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Mon Jun 23 09:18:40 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Mon, 23 Jun 2014 07:18:40 +0000 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> Message-ID: <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 mcp at tid.es Mon Jun 23 10:36:42 2014 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 23 Jun 2014 10:36:42 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> Message-ID: <53A7E71A.8080101@tid.es> Will look at it carefully when I can (preparing the WPL/WPA call at the moment). You have published the one that cannot be published! * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_RPC_over_DDS_-_Unit_Testing_Plan_and_Report Best regards, Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 mcp at tid.es Mon Jun 23 15:20:29 2014 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 23 Jun 2014 15:20:29 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> Message-ID: <53A8299D.1010906@tid.es> Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 mcp at tid.es Mon Jun 23 15:24:39 2014 From: mcp at tid.es (Miguel Carrillo) Date: Mon, 23 Jun 2014 15:24:39 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <53A8299D.1010906@tid.es> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> Message-ID: <53A82A97.90406@tid.es> small typo, sorry: .... "I only needed to fix two links "... El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old "Common base technologies" and "Advanced User Interfaces" pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 Jun 24 13:35:26 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 24 Jun 2014 11:35:26 +0000 Subject: [Fiware-miwi] Weekly meeting Message-ID: Hi everybody Tomorrow morning I am occupied with final exam supervision and therefore I have to postpone the meeting to the afternoon 13:00 CET. Please let me know if this is not possible for you. If required I can move it +- 1 hour. Please check the minutes of last week for open action points: https://docs.google.com/document/d/1-nZC6m6R6EhwPbyBacu7z4vyTPOQ7s535zSGwPCvaHA - Topic 4: Testing of GEi installations - Topic 6: Catalogue entries - Topic 7: 3rd Party Innovations update Sorry for short notice. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From mach at zhaw.ch Tue Jun 24 14:04:56 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Tue, 24 Jun 2014 12:04:56 +0000 Subject: [Fiware-miwi] Reminder: GEi Installation and Test verification Message-ID: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> I would like to remind you, that the internal deadline for the GEi Installation and Test verification is today (external end of week, but we need some spare time to check ensure the quality). Goal is to verify the installation of each GEi by another partner in the WP and write a short report, which will be part of deliverable D.10.5.3 "Report on Validation Process including Validation with Use Case projects?. For the moment we can only verify the local tests. We will do a second round and extend the reports, as soon the GEi?s are available on FI-LAB. See the GEi each partner has to validate in the following spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 When testing the GEi installation and verifying the tests you should fill out the following report: https://forge.fi-ware.org/docman/view.php/36/4019/I10.2_Installation_and_Test_Template_v2.docx and send it to me. In the Testbed V3 Installation and Test wiki page are also the links to the reports already produced: https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Installation_and_Test_aka_D10.5.3 The following GE/GEi reports (linked there) of WP3 (Apps & Services) are good examples, which give also feedback and enhancement tips in the appendix section: - Service Description Repository / Repository - SAP RI - Service Registry / Registry - SAP RI - Light Semantic Composition Editor / COMPEL Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti From jarkko at cyberlightning.com Wed Jun 25 08:20:09 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Wed, 25 Jun 2014 09:20:09 +0300 Subject: [Fiware-miwi] Reminder: GEi Installation and Test verification In-Reply-To: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> References: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> Message-ID: Hello, For those components which were meant to be tested by Cyberlightning, the testing was performed already last week. The reports just have been sitting on my table. :) Anyways, here are the three documents filled with relevant test information. Interface designer, web tundra and virtual characters. Should I update the testing page with test dates myself, and should I also complete the testing dashboard, or shall you Christof edit those collectively? - jarkko On Tue, Jun 24, 2014 at 3:04 PM, Marti Christof (mach) wrote: > I would like to remind you, that the internal deadline for the GEi > Installation and Test verification is today (external end of week, but we > need some spare time to check ensure the quality). > > Goal is to verify the installation of each GEi by another partner in the > WP and write a short report, which will be part of deliverable D.10.5.3 > "Report on Validation Process including Validation with Use Case projects?. > > For the moment we can only verify the local tests. We will do a second > round and extend the reports, as soon the GEi?s are available on FI-LAB. > > See the GEi each partner has to validate in the following spreadsheet: > > https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 > > When testing the GEi installation and verifying the tests you should fill > out the following report: > https://forge.fi-ware.org/docman/view.php/36/4019/I10.2_Installation_and_Test_Template_v2.docx > and send it to me. > > In the Testbed V3 Installation and Test wiki page are also the links to > the reports already produced: > https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Installation_and_Test_aka_D10.5.3 > > The following GE/GEi reports (linked there) of WP3 (Apps & Services) are > good examples, which give also feedback and enhancement tips in the > appendix section: > - Service Description Repository / Repository - SAP RI > - Service Registry / Registry - SAP RI > - Light Semantic Composition Editor / COMPEL > > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I10.2_Installation_and_Test_Template-InterfaceDesigner.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 194578 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I10.2_Installation_and_Test_Template-VirtualCharacters.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 194649 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I10.2_Installation_and_Test_Template-WebTundra.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 194646 bytes Desc: not available URL: From philipp.slusallek at dfki.de Wed Jun 25 08:35:37 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Wed, 25 Jun 2014 08:35:37 +0200 Subject: [Fiware-miwi] Weekly meeting In-Reply-To: References: Message-ID: <53AA6DB9.5070706@dfki.de> Hi, I am in Lyon at the HPG & EGSR conferences and will not be able to join. Sorry, Philipp Am 24.06.2014 13:35, schrieb Marti Christof (mach): > Hi everybody > > Tomorrow morning I am occupied with final exam supervision and therefore I have to postpone the meeting to the afternoon 13:00 CET. > Please let me know if this is not possible for you. If required I can move it +- 1 hour. > > Please check the minutes of last week for open action points: https://docs.google.com/document/d/1-nZC6m6R6EhwPbyBacu7z4vyTPOQ7s535zSGwPCvaHA > - Topic 4: Testing of GEi installations > - Topic 6: Catalogue entries > - Topic 7: 3rd Party Innovations update > > Sorry for short notice. > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > _______________________________________________ > 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: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From toni at playsign.net Wed Jun 25 11:23:22 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 25 Jun 2014 12:23:22 +0300 Subject: [Fiware-miwi] Reminder: GEi Installation and Test verification In-Reply-To: References: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> Message-ID: Hi - thanks for the reviews, just a quick note about Internet Explorer support which was mentioned in the doc: IE 11 at least in win8 metro mode has pretty good WebGL support nowadays and AFAIK websockets work too. It is true however that not all things work and are not tested that much, we'll edit to note that in the doc somehow. For example this simple standalone thing works with the controls and all, http://playsign.tklapp.com:8000/WebTundra/examples/xml3d/example-ctm.html .. also the Virtual Characters demo from http://playsign.tklapp.com:8000/WebTundra/examples/Avatar/ runs fine for me on IE now (first I got a strange bug though that not everything animated correctly, perhaps due to loading order probs) Cheers, ~Toni On Wed, Jun 25, 2014 at 9:20 AM, Jarkko Vatjus-Anttila < jarkko at cyberlightning.com> wrote: > Hello, > > For those components which were meant to be tested by Cyberlightning, the > testing was performed already last week. The reports just have been sitting > on my table. :) > > Anyways, here are the three documents filled with relevant test > information. Interface designer, web tundra and virtual characters. > > Should I update the testing page with test dates myself, and should I also > complete the testing dashboard, or shall you Christof edit those > collectively? > > - jarkko > > > > > On Tue, Jun 24, 2014 at 3:04 PM, Marti Christof (mach) > wrote: > >> I would like to remind you, that the internal deadline for the GEi >> Installation and Test verification is today (external end of week, but we >> need some spare time to check ensure the quality). >> >> Goal is to verify the installation of each GEi by another partner in the >> WP and write a short report, which will be part of deliverable D.10.5.3 >> "Report on Validation Process including Validation with Use Case projects?. >> >> For the moment we can only verify the local tests. We will do a second >> round and extend the reports, as soon the GEi?s are available on FI-LAB. >> >> See the GEi each partner has to validate in the following spreadsheet: >> >> https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 >> >> When testing the GEi installation and verifying the tests you should fill >> out the following report: >> https://forge.fi-ware.org/docman/view.php/36/4019/I10.2_Installation_and_Test_Template_v2.docx >> and send it to me. >> >> In the Testbed V3 Installation and Test wiki page are also the links to >> the reports already produced: >> https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Installation_and_Test_aka_D10.5.3 >> >> The following GE/GEi reports (linked there) of WP3 (Apps & Services) are >> good examples, which give also feedback and enhancement tips in the >> appendix section: >> - Service Description Repository / Repository - SAP RI >> - Service Registry / Registry - SAP RI >> - Light Semantic Composition Editor / COMPEL >> >> Best regards >> Christof >> ---- >> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch >> Institut of Applied Information Technology - InIT >> Zurich University of Applied Sciences - ZHAW >> School of Engineering >> Phone: +41 58 934 70 63 >> Skype: christof-marti >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-miwi >> > > > > -- > Jarkko Vatjus-Anttila > CTO > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > See our new press release: > http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ > > www.cyberlightning.com > > This e-mail and all attached material are confidential and may contain > legally privileged information. If you are not the intended recipient, > please contact the sender and delete the e-mail from your system without > producing, distributing or retaining copies thereof. > > _______________________________________________ > 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 Jun 25 11:27:16 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 25 Jun 2014 09:27:16 +0000 Subject: [Fiware-miwi] Reminder: GEi Installation and Test verification In-Reply-To: References: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> Message-ID: <26C044C6-163A-4B72-BCCB-B8973B4F6079@zhaw.ch> Hi Jarkko As much I know, you can not edit the page. I will forward the reports to WP10 and then the date will be set by Stefano. Christof Am 25.06.2014 um 08:20 schrieb Jarkko Vatjus-Anttila >: Hello, For those components which were meant to be tested by Cyberlightning, the testing was performed already last week. The reports just have been sitting on my table. :) Anyways, here are the three documents filled with relevant test information. Interface designer, web tundra and virtual characters. Should I update the testing page with test dates myself, and should I also complete the testing dashboard, or shall you Christof edit those collectively? - jarkko On Tue, Jun 24, 2014 at 3:04 PM, Marti Christof (mach) > wrote: I would like to remind you, that the internal deadline for the GEi Installation and Test verification is today (external end of week, but we need some spare time to check ensure the quality). Goal is to verify the installation of each GEi by another partner in the WP and write a short report, which will be part of deliverable D.10.5.3 "Report on Validation Process including Validation with Use Case projects?. For the moment we can only verify the local tests. We will do a second round and extend the reports, as soon the GEi?s are available on FI-LAB. See the GEi each partner has to validate in the following spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 When testing the GEi installation and verifying the tests you should fill out the following report: https://forge.fi-ware.org/docman/view.php/36/4019/I10.2_Installation_and_Test_Template_v2.docx and send it to me. In the Testbed V3 Installation and Test wiki page are also the links to the reports already produced: https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Installation_and_Test_aka_D10.5.3 The following GE/GEi reports (linked there) of WP3 (Apps & Services) are good examples, which give also feedback and enhancement tips in the appendix section: - Service Description Repository / Repository - SAP RI - Service Registry / Registry - SAP RI - Light Semantic Composition Editor / COMPEL Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jarkko at cyberlightning.com Wed Jun 25 11:34:41 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Wed, 25 Jun 2014 12:34:41 +0300 Subject: [Fiware-miwi] Reminder: GEi Installation and Test verification In-Reply-To: References: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> Message-ID: Thanks for the comments Toni, This was exactly what I was thinking, so majority(?) of WebGL features work, but there are still a lot which don't. This would be only a note for the user, that just "do not yet assume everything works flawlessly". Maybe I am looking for grounds saying: our apps and code work, do not blame us if the browser does not :D - j On Wed, Jun 25, 2014 at 12:23 PM, Toni Alatalo wrote: > Hi - thanks for the reviews, just a quick note about Internet Explorer > support which was mentioned in the doc: > > IE 11 at least in win8 metro mode has pretty good WebGL support nowadays > and AFAIK websockets work too. It is true however that not all things work > and are not tested that much, we'll edit to note that in the doc somehow. > > For example this simple standalone thing works with the controls and all, > http://playsign.tklapp.com:8000/WebTundra/examples/xml3d/example-ctm.html > .. also the Virtual Characters demo from > http://playsign.tklapp.com:8000/WebTundra/examples/Avatar/ runs fine for > me on IE now (first I got a strange bug though that not everything animated > correctly, perhaps due to loading order probs) > > Cheers, > ~Toni > > > > On Wed, Jun 25, 2014 at 9:20 AM, Jarkko Vatjus-Anttila < > jarkko at cyberlightning.com> wrote: > >> Hello, >> >> For those components which were meant to be tested by Cyberlightning, the >> testing was performed already last week. The reports just have been sitting >> on my table. :) >> >> Anyways, here are the three documents filled with relevant test >> information. Interface designer, web tundra and virtual characters. >> >> Should I update the testing page with test dates myself, and should I >> also complete the testing dashboard, or shall you Christof edit those >> collectively? >> >> - jarkko >> >> >> >> >> On Tue, Jun 24, 2014 at 3:04 PM, Marti Christof (mach) >> wrote: >> >>> I would like to remind you, that the internal deadline for the GEi >>> Installation and Test verification is today (external end of week, but we >>> need some spare time to check ensure the quality). >>> >>> Goal is to verify the installation of each GEi by another partner in the >>> WP and write a short report, which will be part of deliverable D.10.5.3 >>> "Report on Validation Process including Validation with Use Case projects?. >>> >>> For the moment we can only verify the local tests. We will do a second >>> round and extend the reports, as soon the GEi?s are available on FI-LAB. >>> >>> See the GEi each partner has to validate in the following spreadsheet: >>> >>> https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 >>> >>> When testing the GEi installation and verifying the tests you should >>> fill out the following report: >>> https://forge.fi-ware.org/docman/view.php/36/4019/I10.2_Installation_and_Test_Template_v2.docx >>> and send it to me. >>> >>> In the Testbed V3 Installation and Test wiki page are also the links to >>> the reports already produced: >>> https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Installation_and_Test_aka_D10.5.3 >>> >>> The following GE/GEi reports (linked there) of WP3 (Apps & Services) are >>> good examples, which give also feedback and enhancement tips in the >>> appendix section: >>> - Service Description Repository / Repository - SAP RI >>> - Service Registry / Registry - SAP RI >>> - Light Semantic Composition Editor / COMPEL >>> >>> Best regards >>> Christof >>> ---- >>> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch >>> Institut of Applied Information Technology - InIT >>> Zurich University of Applied Sciences - ZHAW >>> School of Engineering >>> Phone: +41 58 934 70 63 >>> Skype: christof-marti >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-miwi >>> >> >> >> >> -- >> Jarkko Vatjus-Anttila >> CTO >> Cyberlightning Ltd. >> >> mobile. +358 405245142 >> email. jarkko at cyberlightning.com >> >> See our new press release: >> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ >> >> www.cyberlightning.com >> >> This e-mail and all attached material are confidential and may contain >> legally privileged information. If you are not the intended recipient, >> please contact the sender and delete the e-mail from your system without >> producing, distributing or retaining copies thereof. >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-miwi >> >> > -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jun 25 13:03:12 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 25 Jun 2014 11:03:12 +0000 Subject: [Fiware-miwi] Weekly meeting In-Reply-To: References: Message-ID: Hi Minutes: https://docs.google.com/document/d/1dcEhc9fF5BuNuXyaQS6CP6-ThNnRwBWesU-nQJP0m7U/edit?usp=sharing Hankgout: https://plus.google.com/hangouts/_/gshkjg6c73v7qanbtxz655ktfea?hl=de Christof Am 24.06.2014 um 13:35 schrieb Marti Christof (mach) : > Hi everybody > > Tomorrow morning I am occupied with final exam supervision and therefore I have to postpone the meeting to the afternoon 13:00 CET. > Please let me know if this is not possible for you. If required I can move it +- 1 hour. > > Please check the minutes of last week for open action points: https://docs.google.com/document/d/1-nZC6m6R6EhwPbyBacu7z4vyTPOQ7s535zSGwPCvaHA > - Topic 4: Testing of GEi installations > - Topic 6: Catalogue entries > - Topic 7: 3rd Party Innovations update > > Sorry for short notice. > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti From mcp at tid.es Wed Jun 25 14:26:00 2014 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 25 Jun 2014 14:26:00 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <53A8299D.1010906@tid.es> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> Message-ID: <53AABFD8.7040306@tid.es> Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 Wed Jun 25 14:50:22 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 25 Jun 2014 12:50:22 +0000 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> Message-ID: Hi Miguel It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. They are now created and I just ran the document tool for all the deliverables: * D.13.2.3 FI-WARE SW Release (containing SW Release report) * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report (containing Unit Testing Report) I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. Best regards Christof Am 25.06.2014 um 14:26 schrieb Miguel Carrillo >: Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 mcp at tid.es Wed Jun 25 14:54:10 2014 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 25 Jun 2014 14:54:10 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> Message-ID: <53AAC672.2040500@tid.es> ok, tomorrow count on a couple of hours of mytime to review all - will try to deliver. If we do so, WP13 will go first (WP3 was about to deliver but Alessandra has recently taken over the coordination and despite her enthusiasm and good work, coming to terms with the complexities of all this is not so simple!) El 25/06/2014 14:50, Marti Christof (mach) escribi?: Hi Miguel It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. They are now created and I just ran the document tool for all the deliverables: * D.13.2.3 FI-WARE SW Release (containing SW Release report) * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report (containing Unit Testing Report) I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. Best regards Christof Am 25.06.2014 um 14:26 schrieb Miguel Carrillo >: Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 philipp.slusallek at dfki.de Wed Jun 25 16:26:50 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Wed, 25 Jun 2014 16:26:50 +0200 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Campus Party Europe from 25 to 30 of August in Madrid In-Reply-To: <53AAD8F0.20805@tid.es> References: <53AAD8F0.20805@tid.es> Message-ID: <53AADC2A.1080100@dfki.de> Hi, This seems like a very interesting option to present our stuff to a larger audience (that will likely go public the next few days according to Miguel -- finally), I put a foot in the door already with Juanjo, but we need to agree on this as well (and I was not at the last event). It would be instrumental to go there with a clear vision of what we want to achieve there, Suggestions are welcome. It seems that your joint demos work would fit really well there. Best, Philipp -------- Original-Nachricht -------- Betreff: [Fiware-wpa] Campus Party Europe from 25 to 30 of August in Madrid Datum: Wed, 25 Jun 2014 16:13:04 +0200 Von: Juanjo Hierro An: fiware at lists.fi-ware.eu Kopie (CC): fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear all, This is to inform you that the Campus Party Europe event is going to finally take place in Madrid during the last week of August (from 25 to 30 of August). It is expected that FI-WARE will have a quite relevant presence and visibility. Besides the standard workshops we have organized in the last Campus Party Brasil and Mexico, I would like to prepare some specific workshops regarding the new GEs in the MiWi chapter (particularly those related to advanced Web-based UI GEs). Bottom line, it is expected that there is a enough representation of all the chapters, so I would encourage all chapter leaders to discuss with the rest of the chapter team and come with a proposal on workshops to setup. Bear in mind that this is an event where we will run the finals of the Smart Society challenge as well as the final of the FI-WARE Excellence challenge !! Therefore, it is expected that there will be enough representation to give the necessary support to people running the finals. I would like to count on presence of chapter leaders and architects to be members of the jury of the finals. We will also have to design the contents of the slots we will have on the different stages. At least there will be a) one slot on the main stage which will be mostly focused on promotion of FI-WARE/FI-Lab and phase 3 of the FI-PPP (FI-Ops will be promoted as well but the target audience here are not potential FI-WARE providers but developers/entrepreneurs) and b) two slots on secondary stages, we'll see if we will have one focused on technical overview (giving pointers to workshops) and another one on entrepreneurship (promoting accelerator projects in phase 3 of the FI-PPP) or the two being technical. We will discuss a first proposal with the FI-WARE chapter leaders/architects. I would encourage that you plan your trip to Madrid that week. For those participating in FI-Core, I'll tell you that we will setup a doodle to choose between first and second week of September for the kick-off meeting. I have decided to setup this doodle upon request of some of you who see the opportunity to arrange a trip to merge presence in both events and ... enjoy the staying in Madrid during the weekend ! 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 -- ------------------------------------------------------------------------- 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-wpa mailing list Fiware-wpa at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-wpa -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Wed Jun 25 21:51:07 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 25 Jun 2014 21:51:07 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> Message-ID: <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> Hi Miguel Finally the R3 Documents are all on Forge: D.13.2.3 SW Release D.13.3.3 Installation and Administration Guide D.13.4.3 User and Programmers Guide D.13.5.3 Unit Testing Plan and Report It took me several iterations, while I also fixed some layout issues (images, spacing, etc.) But it looks good now. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Am 25.06.2014 um 14:54 schrieb Miguel Carrillo : > ok, tomorrow count on a couple of hours of mytime to review all - will try to deliver. If we do so, WP13 will go first (WP3 was about to deliver but Alessandra has recently taken over the coordination and despite her enthusiasm and good work, coming to terms with the complexities of all this is not so simple!) > > > El 25/06/2014 14:50, Marti Christof (mach) escribi?: >> Hi Miguel >> >> It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. >> They are now created and I just ran the document tool for all the deliverables: >> >> D.13.2.3 >> FI-WARE SW Release (containing >> SW >> Release report) >> >> D.13.3.3 >> Installation and Administration Guide >> >> D.13.4.3 >> User and Programmers Guide >> >> D.13.5.3 >> Unit Testing Plan and Report (containing >> Unit >> Testing Report) >> >> I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. >> >> Best regards >> Christof >> >> >> Am 25.06.2014 um 14:26 schrieb Miguel Carrillo : >> >>> Dear Christof, >>> >>> It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. >>> >>> Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? >>> >>> Thanks, >>> >>> Miguel >>> >>> >>> El 23/06/2014 15:20, Miguel Carrillo escribi?: >>>> Hi Christof, >>>> >>>> 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. >>>> >>>> Please publish it now, this is suitable for publication. >>>> >>>> 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. >>>> >>>> 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. >>>> >>>> 4) Tips for the generation of the deliverables >>>> Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: >>>> https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx >>>> Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) >>>> Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) >>>> Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx >>>> 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. >>>> >>>> Br >>>> >>>> Miguel >>>> >>>> >>>> El 23/06/2014 9:18, Marti Christof (mach) escribi?: >>>>> Hi Miguel >>>>> >>>>> I updated the Materializing page for WP13 and added all the Guides and UTP Links. >>>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE >>>>> I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. >>>>> The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. >>>>> Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? >>>>> >>>>> In addition I also created the Front-Pages for the Guides and UTP: >>>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page >>>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page >>>>> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page >>>>> and am ready to create the documents. >>>>> >>>>> I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. >>>>> But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? >>>>> >>>>> Best regards >>>>> Christof >>>>> >>>>> >>>>> Am 20.06.2014 um 15:21 schrieb Miguel Carrillo : >>>>> >>>>>> Hi Christof, >>>>>> >>>>>> I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! >>>>>> >>>>>> Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: >>>>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide >>>>>> I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. >>>>>> >>>>>> While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. >>>>>> >>>>>> Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. >>>>>> >>>>>> Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Miguel >>>>>> >>>>>> El 20/06/2014 12:52, Marti Christof (mach) escribi?: >>>>>>> Hi Miguel >>>>>>> >>>>>>> Thank you very much. >>>>>>> The guides and UTP (except the two which were not approved) are already copied to the public wiki. >>>>>>> This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. >>>>>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE >>>>>>> >>>>>>> Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. >>>>>>> >>>>>>> Best regards >>>>>>> Christof >>>>>>> ---- >>>>>>> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch >>>>>>> Institut f?r angewandte Informationstechnologie - InIT >>>>>>> Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW >>>>>>> School of Engineering >>>>>>> ? Postfach, CH-8401 Winterthur >>>>>>> ? TD O3.18, Obere Kirchgasse 2 >>>>>>> ? +41 58 934 70 63 >>>>>>> ? mach at zhaw.ch >>>>>>> Skype: christof-marti >>>>>>> >>>>>>> Am 20.06.2014 um 12:45 schrieb Miguel Carrillo : >>>>>>> >>>>>>>> Dear WP13 members, >>>>>>>> >>>>>>>> I thought that you might appreciate an update on the Release3 manuals + software release. >>>>>>>> >>>>>>>> WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: >>>>>>>> https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 >>>>>>>> On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. >>>>>>>> >>>>>>>> One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. >>>>>>>> >>>>>>>> Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> 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 >>>>>>>> ---------------------------------------------------------------------- >>>>>>>> >>>>>>>> >>>>>>>> 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-miwi mailing list >>>>>>>> Fiware-miwi at lists.fi-ware.org >>>>>>>> https://lists.fi-ware.org/listinfo/fiware-miwi >>>>>>> >>>>>> >>>>>> -- >>>>>> ---------------------------------------------------------------------- >>>>>> _/ _/_/ 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 >>>>> >>>> >>>> -- >>>> ---------------------------------------------------------------------- >>>> _/ _/_/ 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 >> > > -- > ---------------------------------------------------------------------- > _/ _/_/ 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 mcp at tid.es Wed Jun 25 22:25:26 2014 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 25 Jun 2014 22:25:26 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> Message-ID: <53AB3036.7070701@tid.es> Great!!! I will start the review of it tomorrow. Thanks, Miguel El 25/06/2014 21:51, Christof Marti escribi?: Hi Miguel Finally the R3 Documents are all on Forge: * D.13.2.3 SW Release * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report It took me several iterations, while I also fixed some layout issues (images, spacing, etc.) But it looks good now. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Am 25.06.2014 um 14:54 schrieb Miguel Carrillo >: ok, tomorrow count on a couple of hours of mytime to review all - will try to deliver. If we do so, WP13 will go first (WP3 was about to deliver but Alessandra has recently taken over the coordination and despite her enthusiasm and good work, coming to terms with the complexities of all this is not so simple!) El 25/06/2014 14:50, Marti Christof (mach) escribi?: Hi Miguel It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. They are now created and I just ran the document tool for all the deliverables: * D.13.2.3 FI-WARE SW Release (containing SW Release report) * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report (containing Unit Testing Report) I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. Best regards Christof Am 25.06.2014 um 14:26 schrieb Miguel Carrillo >: Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 ________________________________ 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 Thu Jun 26 11:26:01 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 09:26:01 +0000 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> Message-ID: <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> Dear WP13 GEi owners The problem with the naming of the epics is, that we need to add an EpicId. Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId At the moment many WP13-epics are only named after the GE itself. e.g. - FIWARE.Epic.MiWi.2D-UI So we either need to add a generic EpicId (see below) or split up the Epics in multiple meaningful peaces. - FIWARE.Epic.MiWi.2D-UI.FunctionalityX - FIWARE.Epic.MiWi.2D-UI.FunctionalityY Because some of the Epic Description are also to long (see report ?All issues?) and need to be shortened, this might be a good possiblity to fix these issues too. Please let me know ASAP [today before EOB] if and how it would be possible to split your current GEs Epic. Best regards Christof Anfang der weitergeleiteten Nachricht: Von: "Marti Christof (mach)" > Betreff: Aw: [Fiware-ge-owners] Backlog content: updated reviews Datum: 26. Juni 2014 [26] 11:05:08 MESZ An: MANUEL ESCRICHE VICENTE > Kopie: MIGUEL CARRILLO PACHECO > Hi Manuel The problem is, that in OpenCall 2 more or less the WebUI GEs have been based on the defined Epics. So the epics where available before the GEs. The problem did not show up before, because they were named FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got the error there and had to rename them to the correct GE-names. I do not care to rename the Epics, but is there a rule or a schema in other WPs how to extend the name in such a case? - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) or - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) or - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) or - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality or - ? We can schedule a call to discuss this. I am available from 13:00 to 13:45 and then again from 16:00-... Best regards Christof Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >: Hi Christof, Rules haven?t changed. It doesn?t make sense to have an Epic named as the GEI. Epics are organising items, it should add some organising value to the items added below. If you wish, we can do some research to the past to check how it was at some definite time. Let me know and we schedule a meeting. Kind regards, Manuel From: Marti Christof (mach) [mailto:mach at zhaw.ch] Sent: jueves, 26 de junio de 2014 10:24 To: MANUEL ESCRICHE VICENTE Cc: MIGUEL CARRILLO PACHECO Subject: Re: [Fiware-ge-owners] Backlog content: updated reviews Hi Manuel I am working on fixing the problems with the backlog. One point I have problems to fix is the Epic naming error, because you expect an EpicId at the end, but most of our Epics are similar to the GEs itself. So for the following GEs the Epics and the GE are identical: - FIWARE.Epic.MiWi.2D-UI - FIWARE.Epic.MiWi.3D-UI - FIWARE.Epic.MiWi.AugmentedReality - FIWARE.Epic.MiWi.CloudRendering - FIWARE.Epic.MiWi.DisplayAsAService - FIWARE.Epic.MiWi.GISDataProvider - FIWARE.Epic.MiWi.POIDataProvider - FIWARE.Epic.MiWi.InterfaceDesigner - FIWARE.Epic.MiWi.RealVirtualInteraction - FIWARE.Epic.MiWi.Synchronization - FIWARE.Epic.MiWi.VirtualCharacters To accomplish the rules we would have to add some artificial EpicId like .Basic oder .BaseFunctionality Is this really intended? I also wonder, why this errors did not show up earlier, when we fixed the last round of bugs. Best regards Christof Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >: Dear Partners, Please, find below updated reports. REVIEWS: https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx DASHBOARDS: https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx If any support were required, please, don?t hesitate to let me know. 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 y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o _______________________________________________ Fiware-ge-owners mailing list Fiware-ge-owners at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-ge-owners ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o -------------- next part -------------- An HTML attachment was scrubbed... URL: From ari.okkonen at cie.fi Thu Jun 26 11:44:33 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Thu, 26 Jun 2014 12:44:33 +0300 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> Message-ID: <53ABEB81.9010201@cie.fi> I am worried! Is there a danger that the suggested change in epic naming cascades to all documents, backlog items, materializing items etc. (features, user stories, and work items) due to *inconsistencies that will be subsequently found by "C4 - Valid and Consistent Hierarchy" checks*? What is the estimated amount of work before everything is settled? What risks correcting these 11 identifiers introduces to the real goals of the project? BR Ari On 2014-06-26 12:26, Marti Christof (mach) wrote: > Dear WP13 GEi owners > > The problem with the naming of the epics is, that we need to add an > EpicId. > Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId > > At the moment many WP13-epics are only named after the GE itself. e.g. > - FIWARE.Epic.MiWi.2D-UI > So we either need to add a generic EpicId (see below) or split up the > Epics in multiple meaningful peaces. > - FIWARE.Epic.MiWi.2D-UI.FunctionalityX > - FIWARE.Epic.MiWi.2D-UI.FunctionalityY > Because some of the Epic Description are also to long (see report "All > issues") and need to be shortened, this might be a good possiblity to > fix these issues too. > > Please let me know ASAP [today before EOB] if and how it would be > possible to split your current GEs Epic. > > Best regards > Christof > > > > Anfang der weitergeleiteten Nachricht: > >> *Von: *"Marti Christof (mach)" > >> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >> *An: *MANUEL ESCRICHE VICENTE > > >> *Kopie: *MIGUEL CARRILLO PACHECO > >> >> Hi Manuel >> >> The problem is, that in OpenCall 2 more or less the WebUI GEs have >> been based on the defined Epics. So the epics where available before >> the GEs. >> The problem did not show up before, because they were named >> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >> the error there and had to rename them to the correct GE-names. >> >> I do not care to rename the Epics, but is there a rule or a schema in >> other WPs how to extend the name in such a case? >> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >> or >> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >> or >> - ... >> >> We can schedule a call to discuss this. I am available from 13:00 to >> 13:45 and then again from 16:00-... >> >> Best regards >> Christof >> >> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >> > >: >> >>> Hi Christof, >>> >>> Rules haven't changed. >>> It doesn't make sense to have an Epic named as the GEI. Epics are >>> organising items, it should add some organising value to the items >>> added below. >>> If you wish, we can do some research to the past to check how it was >>> at some definite time. >>> Let me know and we schedule a meeting. >>> >>> Kind regards, >>> Manuel >>> >>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>> *Sent:*jueves, 26 de junio de 2014 10:24 >>> *To:*MANUEL ESCRICHE VICENTE >>> *Cc:*MIGUEL CARRILLO PACHECO >>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>> >>> Hi Manuel >>> >>> I am working on fixing the problems with the backlog. >>> One point I have problems to fix is the Epic naming error, because >>> you expect an EpicId at the end, but most of our Epics are similar >>> to the GEs itself. So for the following GEs the Epics and the GE are >>> identical: >>> - FIWARE.Epic.MiWi.2D-UI >>> - FIWARE.Epic.MiWi.3D-UI >>> - FIWARE.Epic.MiWi.AugmentedReality >>> - FIWARE.Epic.MiWi.CloudRendering >>> - FIWARE.Epic.MiWi.DisplayAsAService >>> - FIWARE.Epic.MiWi.GISDataProvider >>> - FIWARE.Epic.MiWi.POIDataProvider >>> - FIWARE.Epic.MiWi.InterfaceDesigner >>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>> - FIWARE.Epic.MiWi.Synchronization >>> - FIWARE.Epic.MiWi.VirtualCharacters >>> >>> To accomplish the rules we would have to add some artificial EpicId >>> like .Basic oder .BaseFunctionality >>> Is this really intended? >>> >>> I also wonder, why this errors did not show up earlier, when we >>> fixed the last round of bugs. >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>> >> >: >>> >>> >>> Dear Partners, >>> >>> Please, find below updated reports. >>> >>> REVIEWS: >>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>> DASHBOARDS: >>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>> >>> If any support were required, please, don't hesitate to let me know. >>> >>> 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 y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o >>> confidencial y es para uso exclusivo de la persona o entidad de >>> destino. Si no es usted. el destinatario indicado, queda >>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>> sin autorizaci?n puede estar prohibida en virtud de la >>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>> proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the >>> individual or entity named above. If the reader of this message >>> is not the intended recipient, you are hereby notified that any >>> dissemination, distribution or copying of this communication is >>> strictly prohibited. If you have received this transmission in >>> error, do not read it. Please immediately reply to the sender >>> that you have received this communication in error and then >>> delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou >>> confidencial e ? para uso exclusivo da pessoa ou entidade de >>> destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica >>> notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia >>> sem autoriza??o pode estar proibida em virtude da legisla??o >>> vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos >>> o comunique imediatamente por esta mesma via e proceda a sua >>> destrui??o >>> _______________________________________________ >>> Fiware-ge-owners mailing list >>> Fiware-ge-owners at lists.fi-ware.org >>> >>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o confidencial >>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> usted. el destinatario indicado, queda notificado de que la lectura, >>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>> por esta misma v?a y proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual >>> or entity named above. If the reader of this message is not the >>> intended recipient, you are hereby notified that any dissemination, >>> distribution or copying of this communication is strictly >>> prohibited. If you have received this transmission in error, do not >>> read it. Please immediately reply to the sender that you have >>> received this communication in error and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>> ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente por >>> esta mesma via e proceda a sua destrui??o >> > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lasse.oorni at ludocraft.com Thu Jun 26 11:54:12 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Thu, 26 Jun 2014 12:54:12 +0300 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <53ABEB81.9010201@cie.fi> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <53ABEB81.9010201@cie.fi> Message-ID: <556a1d070be8685409ea0d00d29ab376.squirrel@urho.ludocraft.com> Hi, from a pure functionality point of view the LudoCraft GE's could be split up as follows: FIWARE.Epic.MiWi.Synchronization.RealTimeProtocol FIWARE.Epic.MiWi.Synchronization.SceneAPI (this page already exists) FIWARE.Epic.MiWi.VirtualCharacters.CharacterDescription FIWARE.Epic.MiWi.VirtualCharacters.Animation However this would practically involve rewriting the epic descriptions, during which the original "Open Call 2" epic texts would be at least partially lost. If this is not a problem then it's fine by me. > I am worried! > Is there a danger that the suggested change in epic naming cascades to > all documents, backlog items, materializing items etc. (features, user > stories, and work items) due to *inconsistencies that will be > subsequently found by "C4 - Valid and Consistent Hierarchy" checks*? > What is the estimated amount of work before everything is settled? > What risks correcting these 11 identifiers introduces to the real goals > of the project? > > BR > Ari > > > On 2014-06-26 12:26, Marti Christof (mach) wrote: >> Dear WP13 GEi owners >> >> The problem with the naming of the epics is, that we need to add an >> EpicId. >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >> >> At the moment many WP13-epics are only named after the GE itself. e.g. >> - FIWARE.Epic.MiWi.2D-UI >> So we either need to add a generic EpicId (see below) or split up the >> Epics in multiple meaningful peaces. >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >> Because some of the Epic Description are also to long (see report "All >> issues") and need to be shortened, this might be a good possiblity to >> fix these issues too. -- Lasse ??rni Game Programmer LudoCraft Ltd. From philipp.slusallek at dfki.de Thu Jun 26 12:19:01 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Thu, 26 Jun 2014 12:19:01 +0200 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> Message-ID: <53ABF395.1040509@dfki.de> Hi, This is something that is only really visible internally, right? Externally people only care about the GE and its functionality. So please, lets do whatever minimizes the amount of work right now. Those names are really not very meaningful for most people. Best, Philipp Am 26.06.2014 11:26, schrieb Marti Christof (mach): > Dear WP13 GEi owners > > The problem with the naming of the epics is, that we need to add an EpicId. > Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId > > At the moment many WP13-epics are only named after the GE itself. e.g. > - FIWARE.Epic.MiWi.2D-UI > So we either need to add a generic EpicId (see below) or split up the > Epics in multiple meaningful peaces. > - FIWARE.Epic.MiWi.2D-UI.FunctionalityX > - FIWARE.Epic.MiWi.2D-UI.FunctionalityY > Because some of the Epic Description are also to long (see report ?All > issues?) and need to be shortened, this might be a good possiblity to > fix these issues too. > > Please let me know ASAP [today before EOB] if and how it would be > possible to split your current GEs Epic. > > Best regards > Christof > > > > Anfang der weitergeleiteten Nachricht: > >> *Von: *"Marti Christof (mach)" > >> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >> *An: *MANUEL ESCRICHE VICENTE > > >> *Kopie: *MIGUEL CARRILLO PACHECO > >> >> Hi Manuel >> >> The problem is, that in OpenCall 2 more or less the WebUI GEs have >> been based on the defined Epics. So the epics where available before >> the GEs. >> The problem did not show up before, because they were named >> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >> the error there and had to rename them to the correct GE-names. >> >> I do not care to rename the Epics, but is there a rule or a schema in >> other WPs how to extend the name in such a case? >> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >> or >> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >> or >> - ? >> >> We can schedule a call to discuss this. I am available from 13:00 to >> 13:45 and then again from 16:00-... >> >> Best regards >> Christof >> >> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >> > >: >> >>> Hi Christof, >>> >>> Rules haven?t changed. >>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>> organising items, it should add some organising value to the items >>> added below. >>> If you wish, we can do some research to the past to check how it was >>> at some definite time. >>> Let me know and we schedule a meeting. >>> >>> Kind regards, >>> Manuel >>> >>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>> *Sent:*jueves, 26 de junio de 2014 10:24 >>> *To:*MANUEL ESCRICHE VICENTE >>> *Cc:*MIGUEL CARRILLO PACHECO >>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>> >>> Hi Manuel >>> >>> I am working on fixing the problems with the backlog. >>> One point I have problems to fix is the Epic naming error, because >>> you expect an EpicId at the end, but most of our Epics are similar to >>> the GEs itself. So for the following GEs the Epics and the GE are >>> identical: >>> - FIWARE.Epic.MiWi.2D-UI >>> - FIWARE.Epic.MiWi.3D-UI >>> - FIWARE.Epic.MiWi.AugmentedReality >>> - FIWARE.Epic.MiWi.CloudRendering >>> - FIWARE.Epic.MiWi.DisplayAsAService >>> - FIWARE.Epic.MiWi.GISDataProvider >>> - FIWARE.Epic.MiWi.POIDataProvider >>> - FIWARE.Epic.MiWi.InterfaceDesigner >>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>> - FIWARE.Epic.MiWi.Synchronization >>> - FIWARE.Epic.MiWi.VirtualCharacters >>> >>> To accomplish the rules we would have to add some artificial EpicId >>> like .Basic oder .BaseFunctionality >>> Is this really intended? >>> >>> I also wonder, why this errors did not show up earlier, when we fixed >>> the last round of bugs. >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>> >> >: >>> >>> >>> Dear Partners, >>> >>> Please, find below updated reports. >>> >>> REVIEWS: >>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>> DASHBOARDS: >>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>> >>> If any support were required, please, don?t hesitate to let me know. >>> >>> 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 y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o >>> confidencial y es para uso exclusivo de la persona o entidad de >>> destino. Si no es usted. el destinatario indicado, queda >>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>> sin autorizaci?n puede estar prohibida en virtud de la >>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>> proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the >>> individual or entity named above. If the reader of this message >>> is not the intended recipient, you are hereby notified that any >>> dissemination, distribution or copying of this communication is >>> strictly prohibited. If you have received this transmission in >>> error, do not read it. Please immediately reply to the sender >>> that you have received this communication in error and then >>> delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>> por esta mesma via e proceda a sua destrui??o >>> _______________________________________________ >>> Fiware-ge-owners mailing list >>> Fiware-ge-owners at lists.fi-ware.org >>> >>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o confidencial >>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> usted. el destinatario indicado, queda notificado de que la lectura, >>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>> mensaje por error, le rogamos que nos lo comunique inmediatamente por >>> esta misma v?a y proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual >>> or entity named above. If the reader of this message is not the >>> intended recipient, you are hereby notified that any dissemination, >>> distribution or copying of this communication is strictly prohibited. >>> If you have received this transmission in error, do not read it. >>> Please immediately reply to the sender that you have received this >>> communication in error and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou confidencial e ? >>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida >>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, >>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>> proceda a sua destrui??o >> > > > > _______________________________________________ > Fiware-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: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From ari.okkonen at cie.fi Thu Jun 26 12:39:46 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Thu, 26 Jun 2014 13:39:46 +0300 Subject: [Fiware-miwi] Messed up already! Was: Re: Epic naming. Splitting up Epics? In-Reply-To: <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> Message-ID: <53ABF872.6070903@cie.fi> Sorry. I tried to test what happens by moving the POI epic page. However, I carelessly moved the GIS epic page to FIWARE.Epic.MiWi.GISDataProvider.Basic . I have no idea how to revoke the erroneous action. What to do? BR Ari On 2014-06-26 12:26, Marti Christof (mach) wrote: > Dear WP13 GEi owners > > The problem with the naming of the epics is, that we need to add an > EpicId. > Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId > > At the moment many WP13-epics are only named after the GE itself. e.g. > - FIWARE.Epic.MiWi.2D-UI > So we either need to add a generic EpicId (see below) or split up the > Epics in multiple meaningful peaces. > - FIWARE.Epic.MiWi.2D-UI.FunctionalityX > - FIWARE.Epic.MiWi.2D-UI.FunctionalityY > Because some of the Epic Description are also to long (see report "All > issues") and need to be shortened, this might be a good possiblity to > fix these issues too. > > Please let me know ASAP [today before EOB] if and how it would be > possible to split your current GEs Epic. > > Best regards > Christof > > > > Anfang der weitergeleiteten Nachricht: > >> *Von: *"Marti Christof (mach)" > >> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >> *An: *MANUEL ESCRICHE VICENTE > > >> *Kopie: *MIGUEL CARRILLO PACHECO > >> >> Hi Manuel >> >> The problem is, that in OpenCall 2 more or less the WebUI GEs have >> been based on the defined Epics. So the epics where available before >> the GEs. >> The problem did not show up before, because they were named >> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >> the error there and had to rename them to the correct GE-names. >> >> I do not care to rename the Epics, but is there a rule or a schema in >> other WPs how to extend the name in such a case? >> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >> or >> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >> or >> - ... >> >> We can schedule a call to discuss this. I am available from 13:00 to >> 13:45 and then again from 16:00-... >> >> Best regards >> Christof >> >> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >> > >: >> >>> Hi Christof, >>> >>> Rules haven't changed. >>> It doesn't make sense to have an Epic named as the GEI. Epics are >>> organising items, it should add some organising value to the items >>> added below. >>> If you wish, we can do some research to the past to check how it was >>> at some definite time. >>> Let me know and we schedule a meeting. >>> >>> Kind regards, >>> Manuel >>> >>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>> *Sent:*jueves, 26 de junio de 2014 10:24 >>> *To:*MANUEL ESCRICHE VICENTE >>> *Cc:*MIGUEL CARRILLO PACHECO >>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>> >>> Hi Manuel >>> >>> I am working on fixing the problems with the backlog. >>> One point I have problems to fix is the Epic naming error, because >>> you expect an EpicId at the end, but most of our Epics are similar >>> to the GEs itself. So for the following GEs the Epics and the GE are >>> identical: >>> - FIWARE.Epic.MiWi.2D-UI >>> - FIWARE.Epic.MiWi.3D-UI >>> - FIWARE.Epic.MiWi.AugmentedReality >>> - FIWARE.Epic.MiWi.CloudRendering >>> - FIWARE.Epic.MiWi.DisplayAsAService >>> - FIWARE.Epic.MiWi.GISDataProvider >>> - FIWARE.Epic.MiWi.POIDataProvider >>> - FIWARE.Epic.MiWi.InterfaceDesigner >>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>> - FIWARE.Epic.MiWi.Synchronization >>> - FIWARE.Epic.MiWi.VirtualCharacters >>> >>> To accomplish the rules we would have to add some artificial EpicId >>> like .Basic oder .BaseFunctionality >>> Is this really intended? >>> >>> I also wonder, why this errors did not show up earlier, when we >>> fixed the last round of bugs. >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>> >> >: >>> >>> >>> Dear Partners, >>> >>> Please, find below updated reports. >>> >>> REVIEWS: >>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>> DASHBOARDS: >>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>> >>> If any support were required, please, don't hesitate to let me know. >>> >>> 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 y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o >>> confidencial y es para uso exclusivo de la persona o entidad de >>> destino. Si no es usted. el destinatario indicado, queda >>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>> sin autorizaci?n puede estar prohibida en virtud de la >>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>> proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the >>> individual or entity named above. If the reader of this message >>> is not the intended recipient, you are hereby notified that any >>> dissemination, distribution or copying of this communication is >>> strictly prohibited. If you have received this transmission in >>> error, do not read it. Please immediately reply to the sender >>> that you have received this communication in error and then >>> delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou >>> confidencial e ? para uso exclusivo da pessoa ou entidade de >>> destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica >>> notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia >>> sem autoriza??o pode estar proibida em virtude da legisla??o >>> vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos >>> o comunique imediatamente por esta mesma via e proceda a sua >>> destrui??o >>> _______________________________________________ >>> Fiware-ge-owners mailing list >>> Fiware-ge-owners at lists.fi-ware.org >>> >>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o confidencial >>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> usted. el destinatario indicado, queda notificado de que la lectura, >>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>> por esta misma v?a y proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual >>> or entity named above. If the reader of this message is not the >>> intended recipient, you are hereby notified that any dissemination, >>> distribution or copying of this communication is strictly >>> prohibited. If you have received this transmission in error, do not >>> read it. Please immediately reply to the sender that you have >>> received this communication in error and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>> ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente por >>> esta mesma via e proceda a sua destrui??o >> > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ari.okkonen at cie.fi Thu Jun 26 12:54:25 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Thu, 26 Jun 2014 13:54:25 +0300 Subject: [Fiware-miwi] Messed up already! Was: Re: Epic naming. Splitting up Epics? In-Reply-To: <53ABF872.6070903@cie.fi> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <53ABF872.6070903@cie.fi> Message-ID: <53ABFBE1.7080303@cie.fi> I found a *revert* link from move log and used it. Hope its all right now. BR Ari On 2014-06-26 13:39, Ari Okkonen CIE wrote: > Sorry. > > I tried to test what happens by moving the POI epic page. However, I > carelessly moved the GIS epic page to > FIWARE.Epic.MiWi.GISDataProvider.Basic > . > I have no idea how to revoke the erroneous action. What to do? > > BR > Ari > > On 2014-06-26 12:26, Marti Christof (mach) wrote: >> Dear WP13 GEi owners >> >> The problem with the naming of the epics is, that we need to add an >> EpicId. >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >> >> At the moment many WP13-epics are only named after the GE itself. e.g. >> - FIWARE.Epic.MiWi.2D-UI >> So we either need to add a generic EpicId (see below) or split up the >> Epics in multiple meaningful peaces. >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >> Because some of the Epic Description are also to long (see report >> "All issues") and need to be shortened, this might be a good >> possiblity to fix these issues too. >> >> Please let me know ASAP [today before EOB] if and how it would be >> possible to split your current GEs Epic. >> >> Best regards >> Christof >> >> >> >> Anfang der weitergeleiteten Nachricht: >> >>> *Von: *"Marti Christof (mach)" > >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>> *An: *MANUEL ESCRICHE VICENTE >> > >>> *Kopie: *MIGUEL CARRILLO PACHECO > >>> >>> Hi Manuel >>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>> been based on the defined Epics. So the epics where available before >>> the GEs. >>> The problem did not show up before, because they were named >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >>> the error there and had to rename them to the correct GE-names. >>> >>> I do not care to rename the Epics, but is there a rule or a schema >>> in other WPs how to extend the name in such a case? >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>> or >>> - ... >>> >>> We can schedule a call to discuss this. I am available from 13:00 to >>> 13:45 and then again from 16:00-... >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>> >> >: >>> >>>> Hi Christof, >>>> >>>> Rules haven't changed. >>>> It doesn't make sense to have an Epic named as the GEI. Epics are >>>> organising items, it should add some organising value to the items >>>> added below. >>>> If you wish, we can do some research to the past to check how it >>>> was at some definite time. >>>> Let me know and we schedule a meeting. >>>> >>>> Kind regards, >>>> Manuel >>>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>>> *To:*MANUEL ESCRICHE VICENTE >>>> *Cc:*MIGUEL CARRILLO PACHECO >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>>> >>>> Hi Manuel >>>> >>>> I am working on fixing the problems with the backlog. >>>> One point I have problems to fix is the Epic naming error, because >>>> you expect an EpicId at the end, but most of our Epics are similar >>>> to the GEs itself. So for the following GEs the Epics and the GE >>>> are identical: >>>> - FIWARE.Epic.MiWi.2D-UI >>>> - FIWARE.Epic.MiWi.3D-UI >>>> - FIWARE.Epic.MiWi.AugmentedReality >>>> - FIWARE.Epic.MiWi.CloudRendering >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>>> - FIWARE.Epic.MiWi.GISDataProvider >>>> - FIWARE.Epic.MiWi.POIDataProvider >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>>> - FIWARE.Epic.MiWi.Synchronization >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>>> >>>> To accomplish the rules we would have to add some artificial EpicId >>>> like .Basic oder .BaseFunctionality >>>> Is this really intended? >>>> >>>> I also wonder, why this errors did not show up earlier, when we >>>> fixed the last round of bugs. >>>> >>>> Best regards >>>> Christof >>>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>>> >>> >: >>>> >>>> >>>> Dear Partners, >>>> >>>> Please, find below updated reports. >>>> >>>> REVIEWS: >>>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>> >>>> DASHBOARDS: >>>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>>> >>>> If any support were required, please, don't hesitate to let me >>>> know. >>>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> destino. Si no es usted. el destinatario indicado, queda >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o >>>> copia sin autorizaci?n puede estar prohibida en virtud de la >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a >>>> y proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged >>>> and confidential information intended only for the use of the >>>> individual or entity named above. If the reader of this message >>>> is not the intended recipient, you are hereby notified that any >>>> dissemination, distribution or copying of this communication is >>>> strictly prohibited. If you have received this transmission in >>>> error, do not read it. Please immediately reply to the sender >>>> that you have received this communication in error and then >>>> delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou >>>> confidencial e ? para uso exclusivo da pessoa ou entidade de >>>> destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica >>>> notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia >>>> sem autoriza??o pode estar proibida em virtude da legisla??o >>>> vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos >>>> o comunique imediatamente por esta mesma via e proceda a sua >>>> destrui??o >>>> _______________________________________________ >>>> Fiware-ge-owners mailing list >>>> Fiware-ge-owners at lists.fi-ware.org >>>> >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> destino. Si no es usted. el destinatario indicado, queda notificado >>>> de que la lectura, utilizaci?n, divulgaci?n y/o copia sin >>>> autorizaci?n puede estar prohibida en virtud de la legislaci?n >>>> vigente. Si ha recibido este mensaje por error, le rogamos que nos >>>> lo comunique inmediatamente por esta misma v?a y proceda a su >>>> destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the >>>> individual or entity named above. If the reader of this message is >>>> not the intended recipient, you are hereby notified that any >>>> dissemination, distribution or copying of this communication is >>>> strictly prohibited. If you have received this transmission in >>>> error, do not read it. Please immediately reply to the sender that >>>> you have received this communication in error and then delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>>> ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>>> por esta mesma via e proceda a sua destrui??o >>> >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-miwi > > > -- > Ari Okkonen > CIE, University of Oulu > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni.alatalo at gmail.com Thu Jun 26 13:08:09 2014 From: toni.alatalo at gmail.com (toni.alatalo at gmail.com) Date: Thu, 26 Jun 2014 11:08:09 +0000 Subject: [Fiware-miwi] =?utf-8?q?Messed_up_already!_Was=3A_Re=3A_Epic_nami?= =?utf-8?q?ng=2E_Splitting_up_Epics=3F?= In-Reply-To: <53ABF872.6070903@cie.fi> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch>, <53ABF872.6070903@cie.fi> Message-ID: <53abff3a.43a3700a.71dc.0813@mx.google.com> I think you can just move it back. Possibly use mediawiki?s undo for it, or just do another move back to the correct name. From: Ari Okkonen CIE Sent: ?Thursday?, ?June? ?26?, ?2014 ?1?:?39? ?PM To: FI-WARE, MiWi Sorry. I tried to test what happens by moving the POI epic page. However, I carelessly moved the GIS epic page to FIWARE.Epic.MiWi.GISDataProvider.Basic. I have no idea how to revoke the erroneous action. What to do? BR Ari On 2014-06-26 12:26, Marti Christof (mach) wrote: Dear WP13 GEi owners The problem with the naming of the epics is, that we need to add an EpicId. Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId At the moment many WP13-epics are only named after the GE itself. e.g. - FIWARE.Epic.MiWi.2D-UI So we either need to add a generic EpicId (see below) or split up the Epics in multiple meaningful peaces. - FIWARE.Epic.MiWi.2D-UI.FunctionalityX - FIWARE.Epic.MiWi.2D-UI.FunctionalityY Because some of the Epic Description are also to long (see report ?All issues?) and need to be shortened, this might be a good possiblity to fix these issues too. Please let me know ASAP [today before EOB] if and how it would be possible to split your current GEs Epic. Best regards Christof Anfang der weitergeleiteten Nachricht: Von: "Marti Christof (mach)" Betreff: Aw: [Fiware-ge-owners] Backlog content: updated reviews Datum: 26. Juni 2014 [26] 11:05:08 MESZ An: MANUEL ESCRICHE VICENTE Kopie: MIGUEL CARRILLO PACHECO Hi Manuel The problem is, that in OpenCall 2 more or less the WebUI GEs have been based on the defined Epics. So the epics where available before the GEs. The problem did not show up before, because they were named FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got the error there and had to rename them to the correct GE-names. I do not care to rename the Epics, but is there a rule or a schema in other WPs how to extend the name in such a case? - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) or - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) or - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) or - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality or - ? We can schedule a call to discuss this. I am available from 13:00 to 13:45 and then again from 16:00-... Best regards Christof Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE : Hi Christof, Rules haven?t changed. It doesn?t make sense to have an Epic named as the GEI. Epics are organising items, it should add some organising value to the items added below. If you wish, we can do some research to the past to check how it was at some definite time. Let me know and we schedule a meeting. Kind regards, Manuel From: Marti Christof (mach) [mailto:mach at zhaw.ch] Sent: jueves, 26 de junio de 2014 10:24 To: MANUEL ESCRICHE VICENTE Cc: MIGUEL CARRILLO PACHECO Subject: Re: [Fiware-ge-owners] Backlog content: updated reviews Hi Manuel I am working on fixing the problems with the backlog. One point I have problems to fix is the Epic naming error, because you expect an EpicId at the end, but most of our Epics are similar to the GEs itself. So for the following GEs the Epics and the GE are identical: - FIWARE.Epic.MiWi.2D-UI - FIWARE.Epic.MiWi.3D-UI - FIWARE.Epic.MiWi.AugmentedReality - FIWARE.Epic.MiWi.CloudRendering - FIWARE.Epic.MiWi.DisplayAsAService - FIWARE.Epic.MiWi.GISDataProvider - FIWARE.Epic.MiWi.POIDataProvider - FIWARE.Epic.MiWi.InterfaceDesigner - FIWARE.Epic.MiWi.RealVirtualInteraction - FIWARE.Epic.MiWi.Synchronization - FIWARE.Epic.MiWi.VirtualCharacters To accomplish the rules we would have to add some artificial EpicId like .Basic oder .BaseFunctionality Is this really intended? I also wonder, why this errors did not show up earlier, when we fixed the last round of bugs. Best regards Christof Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE : Dear Partners, Please, find below updated reports. REVIEWS: https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx DASHBOARDS: https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx If any support were required, please, don?t hesitate to let me know. 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 y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o _______________________________________________ Fiware-ge-owners mailing list Fiware-ge-owners at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-ge-owners Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Thu Jun 26 13:09:56 2014 From: mcp at tid.es (Miguel Carrillo) Date: Thu, 26 Jun 2014 13:09:56 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> Message-ID: <53ABFF84.8010905@tid.es> Hi, It finally took more than 3 hours to inspect, this is huge. I did not read it all (it would take a week) but gave it a serious go, looking at consistency, general aspect, the overall structure and testing links here and there. This is what we have (please have mercy on me and avoid bombarding me with individual messages from individual GE owners!) The general aspect is rather good and this is suitable for delivery. Once you fix the comments I provide (all easy to fix), please create the MiWi folder in the PUBLIC project (FI-WARE) and upload the docs (word and pdf) to it. The pdf files will be public and the doc files have to be made private after uploading them (pretty much the same as R2). Let me know when this is done and we will deliver. [cid:part1.04010605.04040200 at tid.es] Detailed comments follow. I want to remark that I am not asking you to regenerate the docs, all can be directly edited on the word doc and/or the wiki. If comments are addressed, all this is done before 4pm and I do not find further issues, I commit myself to deliver WP13 today. (hooray!!!) Best regards, Miguel ============================================================================== D13.2.3. SW ============= Basically, ok. Please remove the link under 1.5 and leave it as plain text D13.3.3 INS ========== Basically, ok. (really) minor comment: in 1.4 I read " aka. as MiWi" - the "as" is redundant (AKA = also known as) Under MIWI virtual characters I read " Download a packaged release from https://forge.fi-ware.org/frs/download.php/1138/MIWI-VirtualCharacters-3.3.3.zip " However, the link on the forge for this is https://forge.fi-ware.org/frs/download.php/1151/MIWI-VirtualCharacters-3.3.3.zip (at least this is the one I find) " RPC over DDS is based on the Data Distribution Service (DDS) specifications, an OMG Standard defining the API and Protocol for high performance publish-subscribe middleware. eProsima RPC over DDS is an Remote Procedure Call framework using DDS as the transport and is based on the ongoing OMG RPC for DDS standard. In this release of the middleware for FI-WARE (R3.2),..." -> do you mean R3.3, maybe?? (fix in the word doc directly and also on the source wiki page) D13.4.3 USER ============ Basically, ok. The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Change history with a typo: Initaial Version Repeated sections in "Middleware - KIARA - User and Programmers Guide". No need to regenerate the doc, just: * Fix this on the word doc directly * Fix it on the source page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_KIARA_-_User_and_Programmers_Guide D13.5.3 UTP ============ The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Remove links to non public wikis: * Leave as plain text the link "Unit Testing Report R3 - MiWi" under "1.5 Structure of this Document " * Ditto at the beginning of "20 Unit Testing Report R3 - MiWi" ("You can find the content of this chapter as well in the wiki of fi-ware.") There is a mistake in all the "Materializing" page that I failed to spot when I reviewed it. We will deliver as it is now(we can live with this in the deliverables. No one will notice it, hopefully). But it has to be fixed immediately after. The pages should not have the "and report" part in the name. Example: * Cloud Rendering - Unit Testing Plan and Report This should be called Cloud Rendering - Unit Testing Plan and Report (rationale: can you see any report in the page at all??) "and report" is part of the deliverable name - it does not apply to the name of individual pages. This is easy to fix with the "move" tab on the wiki and changing the links on "materializing ... " - if you do not have access to this functionality, let me know. El 25/06/2014 21:51, Christof Marti escribi?: Hi Miguel Finally the R3 Documents are all on Forge: * D.13.2.3 SW Release * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report It took me several iterations, while I also fixed some layout issues (images, spacing, etc.) But it looks good now. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Am 25.06.2014 um 14:54 schrieb Miguel Carrillo >: ok, tomorrow count on a couple of hours of mytime to review all - will try to deliver. If we do so, WP13 will go first (WP3 was about to deliver but Alessandra has recently taken over the coordination and despite her enthusiasm and good work, coming to terms with the complexities of all this is not so simple!) El 25/06/2014 14:50, Marti Christof (mach) escribi?: Hi Miguel It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. They are now created and I just ran the document tool for all the deliverables: * D.13.2.3 FI-WARE SW Release (containing SW Release report) * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report (containing Unit Testing Report) I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. Best regards Christof Am 25.06.2014 um 14:26 schrieb Miguel Carrillo >: Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: hdhcjdhc.png Type: image/png Size: 9954 bytes Desc: not available URL: From ari.okkonen at cie.fi Thu Jun 26 13:18:36 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Thu, 26 Jun 2014 14:18:36 +0300 Subject: [Fiware-miwi] Correction test. Was: Re: Epic naming. Splitting up Epics? In-Reply-To: <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> Message-ID: <53AC018C.4060406@cie.fi> Hi I am testing the suggested correction to the epic naming issue. I have changed the wiki page FIWARE.Epic.MiWi.POIDataProvider to FIWARE.Epic.MiWi.POIDataProvider*.Basic* . I changed the references in Roadmap and Tracker , also. Let's see what the next Backlog Content review says. BR Ari On 2014-06-26 12:26, Marti Christof (mach) wrote: > Dear WP13 GEi owners > > The problem with the naming of the epics is, that we need to add an > EpicId. > Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId > > At the moment many WP13-epics are only named after the GE itself. e.g. > - FIWARE.Epic.MiWi.2D-UI > So we either need to add a generic EpicId (see below) or split up the > Epics in multiple meaningful peaces. > - FIWARE.Epic.MiWi.2D-UI.FunctionalityX > - FIWARE.Epic.MiWi.2D-UI.FunctionalityY > Because some of the Epic Description are also to long (see report "All > issues") and need to be shortened, this might be a good possiblity to > fix these issues too. > > Please let me know ASAP [today before EOB] if and how it would be > possible to split your current GEs Epic. > > Best regards > Christof > > > > Anfang der weitergeleiteten Nachricht: > >> *Von: *"Marti Christof (mach)" > >> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >> *An: *MANUEL ESCRICHE VICENTE > > >> *Kopie: *MIGUEL CARRILLO PACHECO > >> >> Hi Manuel >> >> The problem is, that in OpenCall 2 more or less the WebUI GEs have >> been based on the defined Epics. So the epics where available before >> the GEs. >> The problem did not show up before, because they were named >> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >> the error there and had to rename them to the correct GE-names. >> >> I do not care to rename the Epics, but is there a rule or a schema in >> other WPs how to extend the name in such a case? >> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >> or >> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >> or >> - ... >> >> We can schedule a call to discuss this. I am available from 13:00 to >> 13:45 and then again from 16:00-... >> >> Best regards >> Christof >> >> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >> > >: >> >>> Hi Christof, >>> >>> Rules haven't changed. >>> It doesn't make sense to have an Epic named as the GEI. Epics are >>> organising items, it should add some organising value to the items >>> added below. >>> If you wish, we can do some research to the past to check how it was >>> at some definite time. >>> Let me know and we schedule a meeting. >>> >>> Kind regards, >>> Manuel >>> >>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>> *Sent:*jueves, 26 de junio de 2014 10:24 >>> *To:*MANUEL ESCRICHE VICENTE >>> *Cc:*MIGUEL CARRILLO PACHECO >>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>> >>> Hi Manuel >>> >>> I am working on fixing the problems with the backlog. >>> One point I have problems to fix is the Epic naming error, because >>> you expect an EpicId at the end, but most of our Epics are similar >>> to the GEs itself. So for the following GEs the Epics and the GE are >>> identical: >>> - FIWARE.Epic.MiWi.2D-UI >>> - FIWARE.Epic.MiWi.3D-UI >>> - FIWARE.Epic.MiWi.AugmentedReality >>> - FIWARE.Epic.MiWi.CloudRendering >>> - FIWARE.Epic.MiWi.DisplayAsAService >>> - FIWARE.Epic.MiWi.GISDataProvider >>> - FIWARE.Epic.MiWi.POIDataProvider >>> - FIWARE.Epic.MiWi.InterfaceDesigner >>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>> - FIWARE.Epic.MiWi.Synchronization >>> - FIWARE.Epic.MiWi.VirtualCharacters >>> >>> To accomplish the rules we would have to add some artificial EpicId >>> like .Basic oder .BaseFunctionality >>> Is this really intended? >>> >>> I also wonder, why this errors did not show up earlier, when we >>> fixed the last round of bugs. >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>> >> >: >>> >>> >>> Dear Partners, >>> >>> Please, find below updated reports. >>> >>> REVIEWS: >>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>> DASHBOARDS: >>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>> >>> If any support were required, please, don't hesitate to let me know. >>> >>> 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 y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o >>> confidencial y es para uso exclusivo de la persona o entidad de >>> destino. Si no es usted. el destinatario indicado, queda >>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>> sin autorizaci?n puede estar prohibida en virtud de la >>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>> proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the >>> individual or entity named above. If the reader of this message >>> is not the intended recipient, you are hereby notified that any >>> dissemination, distribution or copying of this communication is >>> strictly prohibited. If you have received this transmission in >>> error, do not read it. Please immediately reply to the sender >>> that you have received this communication in error and then >>> delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou >>> confidencial e ? para uso exclusivo da pessoa ou entidade de >>> destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica >>> notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia >>> sem autoriza??o pode estar proibida em virtude da legisla??o >>> vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos >>> o comunique imediatamente por esta mesma via e proceda a sua >>> destrui??o >>> _______________________________________________ >>> Fiware-ge-owners mailing list >>> Fiware-ge-owners at lists.fi-ware.org >>> >>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener informaci?n privilegiada o confidencial >>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> usted. el destinatario indicado, queda notificado de que la lectura, >>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>> por esta misma v?a y proceda a su destrucci?n. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual >>> or entity named above. If the reader of this message is not the >>> intended recipient, you are hereby notified that any dissemination, >>> distribution or copying of this communication is strictly >>> prohibited. If you have received this transmission in error, do not >>> read it. Please immediately reply to the sender that you have >>> received this communication in error and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>> ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente por >>> esta mesma via e proceda a sua destrui??o >> > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Thu Jun 26 13:25:38 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 11:25:38 +0000 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <7056843ddf6b4c6e97719856e9ec3c03@SRV-MAIL-001.zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <7056843ddf6b4c6e97719856e9ec3c03@SRV-MAIL-001.zhaw.ch> Message-ID: <4DB093B3-3482-4E2E-AEF0-951938894A43@zhaw.ch> Hi Ari No Features do not have to depend on an Epic (name wise). They can depend on the GE directly. See the schema instructions here: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) They can depend on epics and it would make sense to move for some, but it is in my point of view to much work. Best regards Christof Am 26.06.2014 um 11:44 schrieb Ari Okkonen CIE >: I am worried! Is there a danger that the suggested change in epic naming cascades to all documents, backlog items, materializing items etc. (features, user stories, and work items) due to inconsistencies that will be subsequently found by "C4 - Valid and Consistent Hierarchy" checks? What is the estimated amount of work before everything is settled? What risks correcting these 11 identifiers introduces to the real goals of the project? BR Ari On 2014-06-26 12:26, Marti Christof (mach) wrote: Dear WP13 GEi owners The problem with the naming of the epics is, that we need to add an EpicId. Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId At the moment many WP13-epics are only named after the GE itself. e.g. - FIWARE.Epic.MiWi.2D-UI So we either need to add a generic EpicId (see below) or split up the Epics in multiple meaningful peaces. - FIWARE.Epic.MiWi.2D-UI.FunctionalityX - FIWARE.Epic.MiWi.2D-UI.FunctionalityY Because some of the Epic Description are also to long (see report ?All issues?) and need to be shortened, this might be a good possiblity to fix these issues too. Please let me know ASAP [today before EOB] if and how it would be possible to split your current GEs Epic. Best regards Christof Anfang der weitergeleiteten Nachricht: Von: "Marti Christof (mach)" > Betreff: Aw: [Fiware-ge-owners] Backlog content: updated reviews Datum: 26. Juni 2014 [26] 11:05:08 MESZ An: MANUEL ESCRICHE VICENTE > Kopie: MIGUEL CARRILLO PACHECO > Hi Manuel The problem is, that in OpenCall 2 more or less the WebUI GEs have been based on the defined Epics. So the epics where available before the GEs. The problem did not show up before, because they were named FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got the error there and had to rename them to the correct GE-names. I do not care to rename the Epics, but is there a rule or a schema in other WPs how to extend the name in such a case? - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) or - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) or - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) or - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality or - ? We can schedule a call to discuss this. I am available from 13:00 to 13:45 and then again from 16:00-... Best regards Christof Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >: Hi Christof, Rules haven?t changed. It doesn?t make sense to have an Epic named as the GEI. Epics are organising items, it should add some organising value to the items added below. If you wish, we can do some research to the past to check how it was at some definite time. Let me know and we schedule a meeting. Kind regards, Manuel From: Marti Christof (mach) [mailto:mach at zhaw.ch] Sent: jueves, 26 de junio de 2014 10:24 To: MANUEL ESCRICHE VICENTE Cc: MIGUEL CARRILLO PACHECO Subject: Re: [Fiware-ge-owners] Backlog content: updated reviews Hi Manuel I am working on fixing the problems with the backlog. One point I have problems to fix is the Epic naming error, because you expect an EpicId at the end, but most of our Epics are similar to the GEs itself. So for the following GEs the Epics and the GE are identical: - FIWARE.Epic.MiWi.2D-UI - FIWARE.Epic.MiWi.3D-UI - FIWARE.Epic.MiWi.AugmentedReality - FIWARE.Epic.MiWi.CloudRendering - FIWARE.Epic.MiWi.DisplayAsAService - FIWARE.Epic.MiWi.GISDataProvider - FIWARE.Epic.MiWi.POIDataProvider - FIWARE.Epic.MiWi.InterfaceDesigner - FIWARE.Epic.MiWi.RealVirtualInteraction - FIWARE.Epic.MiWi.Synchronization - FIWARE.Epic.MiWi.VirtualCharacters To accomplish the rules we would have to add some artificial EpicId like .Basic oder .BaseFunctionality Is this really intended? I also wonder, why this errors did not show up earlier, when we fixed the last round of bugs. Best regards Christof Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >: Dear Partners, Please, find below updated reports. REVIEWS: https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx DASHBOARDS: https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx If any support were required, please, don?t hesitate to let me know. 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 y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o _______________________________________________ Fiware-ge-owners mailing list Fiware-ge-owners at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-ge-owners ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu _______________________________________________ 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 Thu Jun 26 13:45:15 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 11:45:15 +0000 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> Message-ID: <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> Hi Philipp, Hi all Epic- and Feature- descriptions are in the public wiki and are referenced from the Materializing page as soon they are closed or on the roadmap page as long they are worked on. Renaming it in the Tracker is the minor part. The problem is, that without extending the name the backlog report will show many errors, which will also be in a deliverable. Goal is to find a consistent and good way to remove the errors without putting to much work into it. To fulfill the naming rules we need to extend the Epic names, either bei splitting large epics into two or by extending it with a generic term, representing the whole epic. Here you find the links to all the epics available in the public wiki: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 @All: Please check the latest report ?All issues tab": https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx There are some Epics which have to much words in the description (>250) - 2D-UI - 3D-UI - 3D-UI.DataflowProcessing - DisplayAsAService and all of the following are missing content in the Rational Field (>=20 words): - 2D-UI - 3D-UI - 3D-UI.DataflowProcessing - 3D-UI.HW-Support - AugmentedReality - CloudRendering - DisplayAsAService - InterfaceDesigner - Synchronization - Synchronization.SceneAPI - VirtualCharacters Would be nice if you can fix the content part also while looking into the naming. Cheers Christof Am 26.06.2014 um 12:19 schrieb Philipp Slusallek : > Hi, > > This is something that is only really visible internally, right? > Externally people only care about the GE and its functionality. > > So please, lets do whatever minimizes the amount of work right now. > Those names are really not very meaningful for most people. > > > Best, > > Philipp > > > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >> Dear WP13 GEi owners >> >> The problem with the naming of the epics is, that we need to add an EpicId. >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >> >> At the moment many WP13-epics are only named after the GE itself. e.g. >> - FIWARE.Epic.MiWi.2D-UI >> So we either need to add a generic EpicId (see below) or split up the >> Epics in multiple meaningful peaces. >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >> Because some of the Epic Description are also to long (see report ?All >> issues?) and need to be shortened, this might be a good possiblity to >> fix these issues too. >> >> Please let me know ASAP [today before EOB] if and how it would be >> possible to split your current GEs Epic. >> >> Best regards >> Christof >> >> >> >> Anfang der weitergeleiteten Nachricht: >> >>> *Von: *"Marti Christof (mach)" > >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>> *An: *MANUEL ESCRICHE VICENTE >> > >>> *Kopie: *MIGUEL CARRILLO PACHECO > >>> >>> Hi Manuel >>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>> been based on the defined Epics. So the epics where available before >>> the GEs. >>> The problem did not show up before, because they were named >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >>> the error there and had to rename them to the correct GE-names. >>> >>> I do not care to rename the Epics, but is there a rule or a schema in >>> other WPs how to extend the name in such a case? >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>> or >>> - ? >>> >>> We can schedule a call to discuss this. I am available from 13:00 to >>> 13:45 and then again from 16:00-... >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>> >> >: >>> >>>> Hi Christof, >>>> >>>> Rules haven?t changed. >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>>> organising items, it should add some organising value to the items >>>> added below. >>>> If you wish, we can do some research to the past to check how it was >>>> at some definite time. >>>> Let me know and we schedule a meeting. >>>> >>>> Kind regards, >>>> Manuel >>>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>>> *To:*MANUEL ESCRICHE VICENTE >>>> *Cc:*MIGUEL CARRILLO PACHECO >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>>> >>>> Hi Manuel >>>> >>>> I am working on fixing the problems with the backlog. >>>> One point I have problems to fix is the Epic naming error, because >>>> you expect an EpicId at the end, but most of our Epics are similar to >>>> the GEs itself. So for the following GEs the Epics and the GE are >>>> identical: >>>> - FIWARE.Epic.MiWi.2D-UI >>>> - FIWARE.Epic.MiWi.3D-UI >>>> - FIWARE.Epic.MiWi.AugmentedReality >>>> - FIWARE.Epic.MiWi.CloudRendering >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>>> - FIWARE.Epic.MiWi.GISDataProvider >>>> - FIWARE.Epic.MiWi.POIDataProvider >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>>> - FIWARE.Epic.MiWi.Synchronization >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>>> >>>> To accomplish the rules we would have to add some artificial EpicId >>>> like .Basic oder .BaseFunctionality >>>> Is this really intended? >>>> >>>> I also wonder, why this errors did not show up earlier, when we fixed >>>> the last round of bugs. >>>> >>>> Best regards >>>> Christof >>>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>>> >>> >: >>>> >>>> >>>> Dear Partners, >>>> >>>> Please, find below updated reports. >>>> >>>> REVIEWS: >>>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>> >>>> DASHBOARDS: >>>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>>> >>>> If any support were required, please, don?t hesitate to let me know. >>>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> destino. Si no es usted. el destinatario indicado, queda >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>>> sin autorizaci?n puede estar prohibida en virtud de la >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>>> proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the >>>> individual or entity named above. If the reader of this message >>>> is not the intended recipient, you are hereby notified that any >>>> dissemination, distribution or copying of this communication is >>>> strictly prohibited. If you have received this transmission in >>>> error, do not read it. Please immediately reply to the sender >>>> that you have received this communication in error and then >>>> delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>>> por esta mesma via e proceda a sua destrui??o >>>> _______________________________________________ >>>> Fiware-ge-owners mailing list >>>> Fiware-ge-owners at lists.fi-ware.org >>>> >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o confidencial >>>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>>> usted. el destinatario indicado, queda notificado de que la lectura, >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente por >>>> esta misma v?a y proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the individual >>>> or entity named above. If the reader of this message is not the >>>> intended recipient, you are hereby notified that any dissemination, >>>> distribution or copying of this communication is strictly prohibited. >>>> If you have received this transmission in error, do not read it. >>>> Please immediately reply to the sender that you have received this >>>> communication in error and then delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e ? >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>> proceda a sua destrui??o >>> >> >> >> >> _______________________________________________ >> Fiware-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 mach at zhaw.ch Thu Jun 26 13:48:32 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 11:48:32 +0000 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> Message-ID: Great Thanks I have a meeting from 14:00 - ~15:00, but after this I will immediately update the docs and wiki. Best regards Christof Am 26.06.2014 um 13:09 schrieb Miguel Carrillo >: Hi, It finally took more than 3 hours to inspect, this is huge. I did not read it all (it would take a week) but gave it a serious go, looking at consistency, general aspect, the overall structure and testing links here and there. This is what we have (please have mercy on me and avoid bombarding me with individual messages from individual GE owners!) The general aspect is rather good and this is suitable for delivery. Once you fix the comments I provide (all easy to fix), please create the MiWi folder in the PUBLIC project (FI-WARE) and upload the docs (word and pdf) to it. The pdf files will be public and the doc files have to be made private after uploading them (pretty much the same as R2). Let me know when this is done and we will deliver. Detailed comments follow. I want to remark that I am not asking you to regenerate the docs, all can be directly edited on the word doc and/or the wiki. If comments are addressed, all this is done before 4pm and I do not find further issues, I commit myself to deliver WP13 today. (hooray!!!) Best regards, Miguel ============================================================================== D13.2.3. SW ============= Basically, ok. Please remove the link under 1.5 and leave it as plain text D13.3.3 INS ========== Basically, ok. (really) minor comment: in 1.4 I read " aka. as MiWi" - the "as" is redundant (AKA = also known as) Under MIWI virtual characters I read " Download a packaged release from https://forge.fi-ware.org/frs/download.php/1138/MIWI-VirtualCharacters-3.3.3.zip " However, the link on the forge for this is https://forge.fi-ware.org/frs/download.php/1151/MIWI-VirtualCharacters-3.3.3.zip (at least this is the one I find) " RPC over DDS is based on the Data Distribution Service (DDS) specifications, an OMG Standard defining the API and Protocol for high performance publish-subscribe middleware. eProsima RPC over DDS is an Remote Procedure Call framework using DDS as the transport and is based on the ongoing OMG RPC for DDS standard. In this release of the middleware for FI-WARE (R3.2),..." -> do you mean R3.3, maybe?? (fix in the word doc directly and also on the source wiki page) D13.4.3 USER ============ Basically, ok. The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Change history with a typo: Initaial Version Repeated sections in "Middleware - KIARA - User and Programmers Guide". No need to regenerate the doc, just: * Fix this on the word doc directly * Fix it on the source page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_KIARA_-_User_and_Programmers_Guide D13.5.3 UTP ============ The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Remove links to non public wikis: * Leave as plain text the link "Unit Testing Report R3 - MiWi" under "1.5 Structure of this Document " * Ditto at the beginning of "20 Unit Testing Report R3 - MiWi" ("You can find the content of this chapter as well in the wiki of fi-ware.") There is a mistake in all the "Materializing" page that I failed to spot when I reviewed it. We will deliver as it is now(we can live with this in the deliverables. No one will notice it, hopefully). But it has to be fixed immediately after. The pages should not have the "and report" part in the name. Example: * Cloud Rendering - Unit Testing Plan and Report This should be called Cloud Rendering - Unit Testing Plan and Report (rationale: can you see any report in the page at all??) "and report" is part of the deliverable name - it does not apply to the name of individual pages. This is easy to fix with the "move" tab on the wiki and changing the links on "materializing ... " - if you do not have access to this functionality, let me know. El 25/06/2014 21:51, Christof Marti escribi?: Hi Miguel Finally the R3 Documents are all on Forge: * D.13.2.3 SW Release * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report It took me several iterations, while I also fixed some layout issues (images, spacing, etc.) But it looks good now. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Am 25.06.2014 um 14:54 schrieb Miguel Carrillo >: ok, tomorrow count on a couple of hours of mytime to review all - will try to deliver. If we do so, WP13 will go first (WP3 was about to deliver but Alessandra has recently taken over the coordination and despite her enthusiasm and good work, coming to terms with the complexities of all this is not so simple!) El 25/06/2014 14:50, Marti Christof (mach) escribi?: Hi Miguel It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. They are now created and I just ran the document tool for all the deliverables: * D.13.2.3 FI-WARE SW Release (containing SW Release report) * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report (containing Unit Testing Report) I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. Best regards Christof Am 25.06.2014 um 14:26 schrieb Miguel Carrillo >: Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 torsten.spieldenner at dfki.de Thu Jun 26 14:42:17 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Thu, 26 Jun 2014 14:42:17 +0200 Subject: [Fiware-miwi] Asset instancing mechanism for XML3D query responses of GIS Data Provider Message-ID: <53AC1529.2060309@dfki.de> Hello, as mentioned in the call yesterday, I think the delivery of the XML3D ground geometry as reply from GIS-Data-Provider could be improved based on the new asset instancing technique of XML3D. Currently, the result is returned as .xml3d - file, that contains the geometry in a format similar to that: ..... // indices, positions, texcoords ... // /// Client handles the request by copying this reply into the client's xml3d-node. This works fine, the drawback here is just that all geometry is present in the DOM. What could work instead, is returning an .xml file (response-type application/xml) with the following content: ..... // indices, positions, texcoords as before // ... Now instead of querying $PROVIDER-HOST/QUERY and copy the response, the client would create and add a node that references the by specifying the query as external source: What happens then, is that the client creates an instance of the externally described asset that describes the ground geometry. This should create exactly the same scene as before, just that the description of the ground geometry in the client's DOM is reduced from the full vertex data to this single model node. Best Torsten -------------- next part -------------- An HTML attachment was scrubbed... URL: From philipp.slusallek at dfki.de Thu Jun 26 16:00:09 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Thu, 26 Jun 2014 16:00:09 +0200 Subject: [Fiware-miwi] Fwd: Re: [Fiware-wpa] [Fiware-wpl] Bundles' availability at FI-LAB In-Reply-To: <53AC1DBD.8090308@tid.es> References: <53AC1DBD.8090308@tid.es> Message-ID: <53AC2769.1010805@dfki.de> Hi, It seems that he work we are doing here already in really important -- not just for the demos. Best, Philipp -------- Original-Nachricht -------- Betreff: Re: [Fiware-wpa] [Fiware-wpl] Bundles' availability at FI-LAB Datum: Thu, 26 Jun 2014 15:18:53 +0200 Von: Juanjo Hierro An: fiware-wpl at lists.fi-ware.org Kopie (CC): fiware-wpa at lists.fi-ware.eu Dear all, I want to remind to you that this activity was crucial. I believe that one of points that will be carefully reviewed in the final review will be the availability of this bundles ... It is worth remaining that the EC and reviewers clearly told us that for the remaining of the project we should focus on getting the GEis stable, accompanied by well-elaborated documentation (guides and tutorials) as well as contents in the e-learning platform. But they also asked for the definition of some GEi bundles helping developers can use to deploy GEi instances in an integrated manner. Best regards, -- Juanjo On 23/06/14 10:18, MANUEL ESCRICHE VICENTE wrote: > > Dear Partners, > > Besides our concern on GE/GEIs availability on FI-LAB, we are also > worried on availability of GE/GEI?s bundles. > > I?ve also prepared a small dashboard for the purpose: > > https://docs.google.com/spreadsheets/d/11iyBxdhxvkoQRFYJyPA2GMfKUo0eeLq6ymODwBl3FKk/edit?usp=sharing > > I?m unware of existing other dashboard for this purpose. In that case, > or had you any suggestion, please, don?t hesitate to let me know. > > Although I have in mind checking previous meeting minutes to identity > all bundles declared, I?d appreciate you took a minute and provide > information related to your WP, if possible. > > Thanks for cooperation!! > > 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 y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener informaci?n privilegiada o confidencial y > es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > prohibida en virtud de la legislaci?n vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > senhoria o destinat?rio indicado, fica notificado de que a leitura, > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destrui??o > > > _______________________________________________ > Fiware-wpl mailing list > Fiware-wpl at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-wpl ------------------------------------------------------------------------ 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-wpa mailing list Fiware-wpa at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-wpa -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Thu Jun 26 16:20:54 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 14:20:54 +0000 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> Message-ID: <52FDB088-0887-4AAD-AED3-28E35BA115B8@zhaw.ch> Hi Miguel Thanks your great effort and fast response. I fixed the Word-Documents and uploaded the DOCX and PDF files to the FI-WARE (public) Docs Folder. PDFs are set to active, DOCX files are set to private. I am now working on fixing the wiki and renaming the Unit Testing Plan (and Report) pages. Will send another email, when done. Best regards Christof Am 26.06.2014 um 13:09 schrieb Miguel Carrillo >: Hi, It finally took more than 3 hours to inspect, this is huge. I did not read it all (it would take a week) but gave it a serious go, looking at consistency, general aspect, the overall structure and testing links here and there. This is what we have (please have mercy on me and avoid bombarding me with individual messages from individual GE owners!) The general aspect is rather good and this is suitable for delivery. Once you fix the comments I provide (all easy to fix), please create the MiWi folder in the PUBLIC project (FI-WARE) and upload the docs (word and pdf) to it. The pdf files will be public and the doc files have to be made private after uploading them (pretty much the same as R2). Let me know when this is done and we will deliver. Detailed comments follow. I want to remark that I am not asking you to regenerate the docs, all can be directly edited on the word doc and/or the wiki. If comments are addressed, all this is done before 4pm and I do not find further issues, I commit myself to deliver WP13 today. (hooray!!!) Best regards, Miguel ============================================================================== D13.2.3. SW ============= Basically, ok. Please remove the link under 1.5 and leave it as plain text D13.3.3 INS ========== Basically, ok. (really) minor comment: in 1.4 I read " aka. as MiWi" - the "as" is redundant (AKA = also known as) Under MIWI virtual characters I read " Download a packaged release from https://forge.fi-ware.org/frs/download.php/1138/MIWI-VirtualCharacters-3.3.3.zip " However, the link on the forge for this is https://forge.fi-ware.org/frs/download.php/1151/MIWI-VirtualCharacters-3.3.3.zip (at least this is the one I find) " RPC over DDS is based on the Data Distribution Service (DDS) specifications, an OMG Standard defining the API and Protocol for high performance publish-subscribe middleware. eProsima RPC over DDS is an Remote Procedure Call framework using DDS as the transport and is based on the ongoing OMG RPC for DDS standard. In this release of the middleware for FI-WARE (R3.2),..." -> do you mean R3.3, maybe?? (fix in the word doc directly and also on the source wiki page) D13.4.3 USER ============ Basically, ok. The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Change history with a typo: Initaial Version Repeated sections in "Middleware - KIARA - User and Programmers Guide". No need to regenerate the doc, just: * Fix this on the word doc directly * Fix it on the source page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_KIARA_-_User_and_Programmers_Guide D13.5.3 UTP ============ The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Remove links to non public wikis: * Leave as plain text the link "Unit Testing Report R3 - MiWi" under "1.5 Structure of this Document " * Ditto at the beginning of "20 Unit Testing Report R3 - MiWi" ("You can find the content of this chapter as well in the wiki of fi-ware.") There is a mistake in all the "Materializing" page that I failed to spot when I reviewed it. We will deliver as it is now(we can live with this in the deliverables. No one will notice it, hopefully). But it has to be fixed immediately after. The pages should not have the "and report" part in the name. Example: * Cloud Rendering - Unit Testing Plan and Report This should be called Cloud Rendering - Unit Testing Plan and Report (rationale: can you see any report in the page at all??) "and report" is part of the deliverable name - it does not apply to the name of individual pages. This is easy to fix with the "move" tab on the wiki and changing the links on "materializing ... " - if you do not have access to this functionality, let me know. El 25/06/2014 21:51, Christof Marti escribi?: Hi Miguel Finally the R3 Documents are all on Forge: * D.13.2.3 SW Release * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report It took me several iterations, while I also fixed some layout issues (images, spacing, etc.) But it looks good now. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Am 25.06.2014 um 14:54 schrieb Miguel Carrillo >: ok, tomorrow count on a couple of hours of mytime to review all - will try to deliver. If we do so, WP13 will go first (WP3 was about to deliver but Alessandra has recently taken over the coordination and despite her enthusiasm and good work, coming to terms with the complexities of all this is not so simple!) El 25/06/2014 14:50, Marti Christof (mach) escribi?: Hi Miguel It took me some time yesterday and this morning to create the missing SW release report and the Unit Testing report pages. It is not difficult, but still a lot of copy paste and modifications and checks to do. They are now created and I just ran the document tool for all the deliverables: * D.13.2.3 FI-WARE SW Release (containing SW Release report) * D.13.3.3 Installation and Administration Guide * D.13.4.3 User and Programmers Guide * D.13.5.3 Unit Testing Plan and Report (containing Unit Testing Report) I?m right now working on creating the word documents and hope deliver them within the next 2-3 hours, if I do not find a major issue in the formatting. Best regards Christof Am 25.06.2014 um 14:26 schrieb Miguel Carrillo >: Dear Christof, It seems that we are in a position to deliver R3 , I do not not if there are any particular circumstances that could justify to delay it any further. Can you please update us and let me know when should I allocate time to read the deliverables prior to the final delivery? Thanks, Miguel El 23/06/2014 15:20, Miguel Carrillo escribi?: Hi Christof, 1) I checked the new Materilizing page , manual per manual, to assess whether the links were working and also that all of them were there. It is a fine work and I only needed to fix to links to "R3.3" pages. Please publish it now, this is suitable for publication. 2) I checked the remaining UTP. It is approved. The change was in the roadmap, not in the test itself. The page you initially ported is fine. Please ensure that the UPT of PRC over DSS is pusblished in its current form. 3) I am unable to answer your question about Arquitecture and Open Specs as it is in Juanjo's scope. AFAIK this is not approved by Juanjo so I guess that the answer is no. 4) Tips for the generation of the deliverables * Yes, the UTP has a report at the end. The long (and official) title is "Unit Testing plan and report". Example: * https://forge.fi-ware.org/docman/view.php/7/2343/D.6.5.2+FI-WARE+Unit+Testing+Plan+and+Report.docx * Note that this report is private (PPP restricted) so it makes sense to have it in the PPP restricted project and the associated wiki (the one that has the R2 report page as well) * Do not forget to create the report for D.13.2.3 (do not panic! - it is easy and quick) * Example: https://forge.fi-ware.org/docman/view.php/7/2337/D.6.2.2+FI-WARE+SW+Release.docx 5) I fixed a mistake in the cover of the Installation guide. Other than that, this cover looks ok. I did not find any obvious mistakes in the other two covers. Br Miguel El 23/06/2014 9:18, Marti Christof (mach) escribi?: Hi Miguel I updated the Materializing page for WP13 and added all the Guides and UTP Links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE I also went through all the copied R3 pages and fixed all references to R3.3 manuals or to the private wiki. The only links, which are not yet valid are those to the OpenSpecification, Open API Specification and Architecture pages, which are not yet on the public wiki for WP13. Question: if (resp. when) it is OK to copy the Architecture and OpenSpecification pages? In addition I also created the Front-Pages for the Guides and UTP: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.3.3_Installation_and_Administration_Guide_front_page https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.4.3_User_and_Programmers_Guide_front_page http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/D.13.5.3_Unit_Testing_Plan_and_Report_front_page and am ready to create the documents. I have one question regarding the UTP deliverable. There is a link to a Unit Test Report page in the restricted wiki. But there are only pages available for R2. Do we have to create the same pages for MiWi and R3? Best regards Christof Am 20.06.2014 um 15:21 schrieb Miguel Carrillo >: Hi Christof, I checked as soon as read this message and saw that you copied many pages 3 hours hours ago, excellent! Yes, I want to take a look at the "Materializing ..." page before linking it from the main page. Note that we need a bit of browsing of each page to be sure that all in in order. For instance, see the link here: * https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Virtual_Characters_-_User_and_Programmers_Guide I checked a few at random and most of them seem to be all right, I guess that this will not take you too much time but not five minutes either. Maybe one or two hours since there a is a long list of manuals. While I react (I guess that you will report on our Monday call on the status) you can always start editing the cover of the documents to deliver. Usual method, you already know how this works but feel free to ask if anything is unclear. Please note that one UTP is not yet approved, leave this one as a "broken" link until Jaime changes a small detail. I am hopeful that it will be fixed soon (and will try to find a way around to make sure that in any case this does not cause a delay to the final delivery). You can already add the link to it under "Materializing..." and also in the deliverable covers. The link will start working once we port it. Just to reassure the chapter members: my top priority on Monday is the coordination call and the second one is this thing. Best regards, Miguel El 20/06/2014 12:52, Marti Christof (mach) escribi?: Hi Miguel Thank you very much. The guides and UTP (except the two which were not approved) are already copied to the public wiki. This afternoon I will copy the two remaining UTPs and update the Materializing page with all the links. https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_Advanced_Middleware_and_Web_User_Interfaces_in_FI-WARE Is it OK to add the WP13-Materializing page to the FI-WARE Materializing page afterwards, replacing the old ?Common base technologies? and ?Advanced User Interfaces? pages? Or do you want to approve the new page first. Best regards Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut f?r angewandte Informationstechnologie - InIT Z?rcher Hochschule f?r Angewandte Wissenschaften - ZHAW School of Engineering ? Postfach, CH-8401 Winterthur ? TD O3.18, Obere Kirchgasse 2 ? +41 58 934 70 63 ? mach at zhaw.ch Skype: christof-marti Am 20.06.2014 um 12:45 schrieb Miguel Carrillo >: Dear WP13 members, I thought that you might appreciate an update on the Release3 manuals + software release. WP13 has been prioritised in the reviews to the detriment of other WPs because we share your concern that WP13 is the only one that actually "does not exist" in the catalogue and the wiki. You can see the difference with others in terms of status: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdGlvRWJrQl96M1VNTHBlc3hvUGF0Zmc#gid=2 On June, 11 I cleared the WPL/WPA to port all the manuals (with 2 exceptions) to the public wiki and generate the deliverables. One of the 2 remaining manuals from eProsima has been approved today and, to avoid the usual bottleneck, I have been talking directly to Jaime in the last interactions. Summary: the publication of the manuals and the delivery is in the hands of the WPL/WPA. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 Thu Jun 26 17:53:19 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 15:53:19 +0000 Subject: [Fiware-miwi] Fwd: Submission of FI-WARE MiWi deliverables D13.2.3, D13.3.3, D13.4.3 & D13.5.3 References: <0c66114fb2f542b480dbabb651a8e7be@SRV-MAIL-001.zhaw.ch> Message-ID: <61943C34-57DD-4055-B288-257693142812@zhaw.ch> Hi The R3 deliverables we were working on the last months are now officially delivered (see below) (Note: I removed the ZIP attachment). Thanks to you all for your good work and contributions. Lets now focus to make the results more accessible to the public (in FI-Lab, catalogue, e-learning, demos, etc.). Cheers Christof ---- InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering Phone: +41 58 934 70 63 Skype: christof-marti Anfang der weitergeleiteten Nachricht: Dear all, This is the official submission of the following deliverables from WP13 in the project FI-WARE for M36: * D.13.2.3 FI-WARE SW Release * D.13.3.3 FI-WARE Installation and Administration Guide * D.13.4.3 FI-WARE User and Programmers Guide * D.13.5.3 FI-WARE Unit Testing Plan and Report The documents are publicly available on: * https://forge.fi-ware.org/docman/view.php/7/4239/D.13.2.3+SW+Release.pdf * https://forge.fi-ware.org/docman/view.php/7/4241/D.13.3.3+Installation+and+Administration+Guide.pdf * https://forge.fi-ware.org/docman/view.php/7/4243/D.13.4.3+User+and+Programmers+Guide.pdf * https://forge.fi-ware.org/docman/view.php/7/4245/D.13.5.3+Unit+Testing+Plan+and+Report.pdf The public source pages are always up to date on our wiki under Materializing Advanced Middleware and Web User Interfaces in FI-WARE I also attach them with this message in a zip file for your convenience. Best regards, 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 ---------------------------------------------------------------------- ________________________________ 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 Thu Jun 26 18:32:56 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Thu, 26 Jun 2014 16:32:56 +0000 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: <769464dc8fe942b2b1f2a2984e6c4f31@SRV-MAIL-001.zhaw.ch> References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> <52FDB088-0887-4AAD-AED3-28E35BA115B8@zhaw.ch> <769464dc8fe942b2b1f2a2984e6c4f31@SRV-MAIL-001.zhaw.ch> Message-ID: Hi Miguel The R3 issues are now also fixed in the wiki (incl. Cover pages and MiWi context page -> aka.) The Unit Testing Plans (and Report) pages are also moved and I updated the links on the materializing page and all the other pages I could find references (in the public wiki). I even updated the links in the Unit Testing Report R3 wiki page and on the UTP Cover page. So no links to the wrong pages on the public wiki. I also checked that the links from external sources (private wiki, PDFs, Word documents) are getting redirected to the correct page. Hope this fixes this issue. Best regards Christof Am 26.06.2014 um 16:42 schrieb Miguel Carrillo >: renaming the Unit Testing Plan can be done tomorrow ... not to be left forgotten but not vitally urgent important: leave redirects to the old pages, this is something you can automatically do when you "move" a wiki page (there is a checkbox or something, I do not remember how it was) . If not, the links in the doc we are delivering will take to broken links El 26/06/2014 16:20, Marti Christof (mach) escribi?: Hi Miguel Thanks your great effort and fast response. I fixed the Word-Documents and uploaded the DOCX and PDF files to the FI-WARE (public) Docs Folder. PDFs are set to active, DOCX files are set to private. I am now working on fixing the wiki and renaming the Unit Testing Plan (and Report) pages. Will send another email, when done. Best regards Christof Am 26.06.2014 um 13:09 schrieb Miguel Carrillo >: Hi, It finally took more than 3 hours to inspect, this is huge. I did not read it all (it would take a week) but gave it a serious go, looking at consistency, general aspect, the overall structure and testing links here and there. This is what we have (please have mercy on me and avoid bombarding me with individual messages from individual GE owners!) The general aspect is rather good and this is suitable for delivery. Once you fix the comments I provide (all easy to fix), please create the MiWi folder in the PUBLIC project (FI-WARE) and upload the docs (word and pdf) to it. The pdf files will be public and the doc files have to be made private after uploading them (pretty much the same as R2). Let me know when this is done and we will deliver. Detailed comments follow. I want to remark that I am not asking you to regenerate the docs, all can be directly edited on the word doc and/or the wiki. If comments are addressed, all this is done before 4pm and I do not find further issues, I commit myself to deliver WP13 today. (hooray!!!) Best regards, Miguel ============================================================================== D13.2.3. SW ============= Basically, ok. Please remove the link under 1.5 and leave it as plain text D13.3.3 INS ========== Basically, ok. (really) minor comment: in 1.4 I read " aka. as MiWi" - the "as" is redundant (AKA = also known as) Under MIWI virtual characters I read " Download a packaged release from https://forge.fi-ware.org/frs/download.php/1138/MIWI-VirtualCharacters-3.3.3.zip " However, the link on the forge for this is https://forge.fi-ware.org/frs/download.php/1151/MIWI-VirtualCharacters-3.3.3.zip (at least this is the one I find) " RPC over DDS is based on the Data Distribution Service (DDS) specifications, an OMG Standard defining the API and Protocol for high performance publish-subscribe middleware. eProsima RPC over DDS is an Remote Procedure Call framework using DDS as the transport and is based on the ongoing OMG RPC for DDS standard. In this release of the middleware for FI-WARE (R3.2),..." -> do you mean R3.3, maybe?? (fix in the word doc directly and also on the source wiki page) D13.4.3 USER ============ Basically, ok. The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Change history with a typo: Initaial Version Repeated sections in "Middleware - KIARA - User and Programmers Guide". No need to regenerate the doc, just: * Fix this on the word doc directly * Fix it on the source page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_KIARA_-_User_and_Programmers_Guide D13.5.3 UTP ============ The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Remove links to non public wikis: * Leave as plain text the link "Unit Testing Report R3 - MiWi" under "1.5 Structure of this Document " * Ditto at the beginning of "20 Unit Testing Report R3 - MiWi" ("You can find the content of this chapter as well in the wiki of fi-ware.") There is a mistake in all the "Materializing" page that I failed to spot when I reviewed it. We will deliver as it is now(we can live with this in the deliverables. No one will notice it, hopefully). But it has to be fixed immediately after. The pages should not have the "and report" part in the name. Example: * Cloud Rendering - Unit Testing Plan and Report This should be called Cloud Rendering - Unit Testing Plan and Report (rationale: can you see any report in the page at all??) "and report" is part of the deliverable name - it does not apply to the name of individual pages. This is easy to fix with the "move" tab on the wiki and changing the links on "materializing ... " - if you do not have access to this functionality, let me know. -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 philipp.slusallek at dfki.de Thu Jun 26 19:36:14 2014 From: philipp.slusallek at dfki.de (Philipp Slusallek) Date: Thu, 26 Jun 2014 19:36:14 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> <52FDB088-0887-4AAD-AED3-28E35BA115B8@zhaw.ch> <769464dc8fe942b2b1f2a2984e6c4f31@SRV-MAIL-001.zhaw.ch> Message-ID: <53AC5A0E.4000904@dfki.de> Thanks you very much, Christof, for taking care of this! Much appreciated, Philipp Am 26.06.2014 18:32, schrieb Marti Christof (mach): > Hi Miguel > > The R3 issues are now also fixed in the wiki (incl. Cover pages and MiWi > context page -> aka.) > > The Unit Testing Plans (and Report) pages are also moved and I updated > the links on the materializing page and all the other pages I could > find references (in the public wiki). I even updated the links in the > Unit Testing Report R3 wiki page and on the UTP Cover page. > So no links to the wrong pages on the public wiki. > I also checked that the links from external sources (private wiki, PDFs, > Word documents) are getting redirected to the correct page. > > Hope this fixes this issue. > > Best regards > Christof > > Am 26.06.2014 um 16:42 schrieb Miguel Carrillo >: > >> renaming the Unit Testing Plan can be done tomorrow ... not to be left >> forgotten but not vitally urgent >> >> important: leave redirects to the old pages, this is something you >> can automatically do when you "move" a wiki page (there is a checkbox >> or something, I do not remember how it was) . If not, the links in the >> doc we are delivering will take to broken links >> >> >> >> >> El 26/06/2014 16:20, Marti Christof (mach) escribi?: >>> Hi Miguel >>> >>> Thanks your great effort and fast response. >>> I fixed the Word-Documents and uploaded the DOCX and PDF files to the >>> FI-WARE (public) Docs Folder >>> . >>> PDFs are set to active, DOCX files are set to private. >>> >>> I am now working on fixing the wiki and renaming the Unit Testing >>> Plan (and Report) pages. >>> Will send another email, when done. >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 13:09 schrieb Miguel Carrillo >> >: >>> >>>> Hi, >>>> >>>> It finally took more than 3 hours to inspect, this is huge. I did >>>> not read it all (it would take a week) but gave it a serious go, >>>> looking at consistency, general aspect, the overall structure and >>>> testing links here and there. This is what we have (please have >>>> mercy on me and avoid bombarding me with individual messages from >>>> individual GE owners!) >>>> >>>> The general aspect is rather good and this is suitable for delivery. >>>> Once you fix the comments I provide (all easy to fix), please create >>>> the MiWi folder in the*_PUBLIC_*project (FI-WARE) and upload the >>>> docs (word and pdf) to it. The pdf files will be public and the doc >>>> files have to be made private after uploading them (pretty much the >>>> same as R2). Let me know when this is done and we will deliver. >>>> >>>> >>>> >>>> Detailed comments follow. >>>> >>>> I want to remark that I am not asking you to regenerate the docs, >>>> all can be directly edited on the word doc and/or the wiki. >>>> >>>> If comments are addressed, all this is done before 4pm and I do not >>>> find further issues, I commit myself to deliver WP13 today. >>>> >>>> (hooray!!!) >>>> >>>> Best regards, >>>> >>>> Miguel >>>> ============================================================================== >>>> >>>> D13.2.3. SW >>>> ============= >>>> Basically, ok. >>>> >>>> Please remove the link under 1.5 and leave it as plain text >>>> >>>> D13.3.3 INS >>>> ========== >>>> Basically, ok. >>>> >>>> (really) minor comment: in 1.4 I read "aka. asMiWi" - the "as" is >>>> redundant (AKA = also known as) >>>> >>>> Under MIWI virtual characters I read "Download a packaged release >>>> fromhttps://forge.fi-ware.org/frs/download.php/*1138*/MIWI-VirtualCharacters-3.3.3.zip >>>> " >>>> However, the link on the forge for this >>>> ishttps://forge.fi-ware.org/frs/download.php/_*1151*_/MIWI-VirtualCharacters-3.3.3.zip >>>> (at least this is the one I find) >>>> >>>> " RPC over DDS is based on the Data Distribution Service (DDS) >>>> specifications, an OMG Standard defining the API and Protocol for >>>> high performance publish-subscribe middleware. eProsima RPC over DDS >>>> is an Remote Procedure Call framework using DDS as the transport and >>>> is based on the ongoing OMG RPC for DDS standard.*_In this release >>>> of the middleware for FI-WARE (R3.2)_*,..." -> do you mean R3.3, >>>> maybe?? (fix in the word doc directly and also on the source wiki page) >>>> >>>> >>>> D13.4.3 USER >>>> ============ >>>> Basically, ok. >>>> >>>> The same (really) minor comment: in 1.4 I read "aka. asMiWi" - the >>>> "as" is redundant (AKA = also known as) >>>> >>>> Change history with a typo:Initaial Version >>>> >>>> Repeated sections in "Middleware - KIARA - User and Programmers >>>> Guide". No need to regenerate the doc, just: >>>> * Fix this on the word doc directly >>>> * Fix it on the source page: >>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_KIARA_-_User_and_Programmers_Guide >>>> >>>> >>>> D13.5.3 UTP >>>> ============ >>>> The same (really) minor comment: in 1.4 I read "aka. asMiWi" - the >>>> "as" is redundant (AKA = also known as) >>>> >>>> Remove links to non public wikis: >>>> >>>> * Leave as plain text the link "Unit Testing Report R3 - MiWi" >>>> under "1.5 Structure of this Document " >>>> * Ditto at the beginning of "20 Unit Testing Report R3 - MiWi" >>>> ("You can find the content of this chapter as well in >>>> the_*wiki*_of fi-ware.") >>>> >>>> >>>> >>>> There is a mistake in all the "Materializing" page that I failed to >>>> spot when I reviewed it. We will deliver as it is now(we can live >>>> with this in the deliverables. No one will notice it, hopefully). >>>> But it has to be fixed immediately after. The pages should not have >>>> the "and report" part in the name. Example: >>>> >>>> * Cloud Rendering - Unit Testing Plan and Report >>>> >>>> >>>> >>>> This should be called Cloud Rendering - Unit Testing Planand Report >>>> (rationale: can you see any report in the page at all??) >>>> >>>> "and report" is part of the deliverable name - it does not apply to >>>> the name of individual pages. This is easy to fix with the "move" >>>> tab on the wiki and changing the links on "materializing ... " - if >>>> you do not have access to this functionality, let me know. >>>> >>>> -- >>>> ---------------------------------------------------------------------- >>>> _/ _/_/ 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 >>> >> >> -- >> ---------------------------------------------------------------------- >> _/ _/_/ 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 > > > > _______________________________________________ > 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: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mcp at tid.es Fri Jun 27 09:29:46 2014 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 27 Jun 2014 09:29:46 +0200 Subject: [Fiware-miwi] Status of manuals and software delivery In-Reply-To: References: <5b18b77582504b0db221073f440cc9a9@SRV-MAIL-001.zhaw.ch> <4ae60e64375f433e8be9020792e48a9a@SRV-MAIL-001.zhaw.ch> <3DD4B0FD-C4BB-4CD0-A900-282E937BCC3D@zhaw.ch> <53A8299D.1010906@tid.es> <4db6d7c6166a4759b01c488211f6d691@SRV-MAIL-001.zhaw.ch> <832FCC2A-28D4-4BD3-B5B5-6199CEF19EDE@zhaw.ch> <8fde6cd6f25e4561a3bda9cfc1c3b8f2@SRV-MAIL-001.zhaw.ch> <52FDB088-0887-4AAD-AED3-28E35BA115B8@zhaw.ch> <769464dc8fe942b2b1f2a2984e6c4f31@SRV-MAIL-001.zhaw.ch> Message-ID: <53AD1D6A.2090009@tid.es> Hi, Thanks for that, it looks spotless. I superficially checked the Materializing page and a couple of redirects at random. It looks good. Now WP13 has passed from not being there to being the only one up to date in FI-WARE! Others will follow soon, hopefully. Now it is time to complete the work: * Automated deployment * Bundles/packaging * Catalogue entries Note that the reviewers left it very clear: they wanted precisely these and we will be judged on the basis of making our work easy to use and available via FI-Lab. Best regards, Miguel El 26/06/2014 18:32, Marti Christof (mach) escribi?: Hi Miguel The R3 issues are now also fixed in the wiki (incl. Cover pages and MiWi context page -> aka.) The Unit Testing Plans (and Report) pages are also moved and I updated the links on the materializing page and all the other pages I could find references (in the public wiki). I even updated the links in the Unit Testing Report R3 wiki page and on the UTP Cover page. So no links to the wrong pages on the public wiki. I also checked that the links from external sources (private wiki, PDFs, Word documents) are getting redirected to the correct page. Hope this fixes this issue. Best regards Christof Am 26.06.2014 um 16:42 schrieb Miguel Carrillo >: renaming the Unit Testing Plan can be done tomorrow ... not to be left forgotten but not vitally urgent important: leave redirects to the old pages, this is something you can automatically do when you "move" a wiki page (there is a checkbox or something, I do not remember how it was) . If not, the links in the doc we are delivering will take to broken links El 26/06/2014 16:20, Marti Christof (mach) escribi?: Hi Miguel Thanks your great effort and fast response. I fixed the Word-Documents and uploaded the DOCX and PDF files to the FI-WARE (public) Docs Folder. PDFs are set to active, DOCX files are set to private. I am now working on fixing the wiki and renaming the Unit Testing Plan (and Report) pages. Will send another email, when done. Best regards Christof Am 26.06.2014 um 13:09 schrieb Miguel Carrillo >: Hi, It finally took more than 3 hours to inspect, this is huge. I did not read it all (it would take a week) but gave it a serious go, looking at consistency, general aspect, the overall structure and testing links here and there. This is what we have (please have mercy on me and avoid bombarding me with individual messages from individual GE owners!) The general aspect is rather good and this is suitable for delivery. Once you fix the comments I provide (all easy to fix), please create the MiWi folder in the PUBLIC project (FI-WARE) and upload the docs (word and pdf) to it. The pdf files will be public and the doc files have to be made private after uploading them (pretty much the same as R2). Let me know when this is done and we will deliver. Detailed comments follow. I want to remark that I am not asking you to regenerate the docs, all can be directly edited on the word doc and/or the wiki. If comments are addressed, all this is done before 4pm and I do not find further issues, I commit myself to deliver WP13 today. (hooray!!!) Best regards, Miguel ============================================================================== D13.2.3. SW ============= Basically, ok. Please remove the link under 1.5 and leave it as plain text D13.3.3 INS ========== Basically, ok. (really) minor comment: in 1.4 I read " aka. as MiWi" - the "as" is redundant (AKA = also known as) Under MIWI virtual characters I read " Download a packaged release from https://forge.fi-ware.org/frs/download.php/1138/MIWI-VirtualCharacters-3.3.3.zip " However, the link on the forge for this is https://forge.fi-ware.org/frs/download.php/1151/MIWI-VirtualCharacters-3.3.3.zip (at least this is the one I find) " RPC over DDS is based on the Data Distribution Service (DDS) specifications, an OMG Standard defining the API and Protocol for high performance publish-subscribe middleware. eProsima RPC over DDS is an Remote Procedure Call framework using DDS as the transport and is based on the ongoing OMG RPC for DDS standard. In this release of the middleware for FI-WARE (R3.2),..." -> do you mean R3.3, maybe?? (fix in the word doc directly and also on the source wiki page) D13.4.3 USER ============ Basically, ok. The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Change history with a typo: Initaial Version Repeated sections in "Middleware - KIARA - User and Programmers Guide". No need to regenerate the doc, just: * Fix this on the word doc directly * Fix it on the source page: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Middleware_-_KIARA_-_User_and_Programmers_Guide D13.5.3 UTP ============ The same (really) minor comment: in 1.4 I read "aka. as MiWi" - the "as" is redundant (AKA = also known as) Remove links to non public wikis: * Leave as plain text the link "Unit Testing Report R3 - MiWi" under "1.5 Structure of this Document " * Ditto at the beginning of "20 Unit Testing Report R3 - MiWi" ("You can find the content of this chapter as well in the wiki of fi-ware.") There is a mistake in all the "Materializing" page that I failed to spot when I reviewed it. We will deliver as it is now(we can live with this in the deliverables. No one will notice it, hopefully). But it has to be fixed immediately after. The pages should not have the "and report" part in the name. Example: * Cloud Rendering - Unit Testing Plan and Report This should be called Cloud Rendering - Unit Testing Plan and Report (rationale: can you see any report in the page at all??) "and report" is part of the deliverable name - it does not apply to the name of individual pages. This is easy to fix with the "move" tab on the wiki and changing the links on "materializing ... " - if you do not have access to this functionality, let me know. -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 -- ---------------------------------------------------------------------- _/ _/_/ 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 antti.kokko at adminotech.com Fri Jun 27 09:32:04 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Fri, 27 Jun 2014 10:32:04 +0300 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> Message-ID: Hello, I need some guidance with these issues: FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) F IWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide reference in tracker; remove reference from materializing;) What is the correct way of getting rid of these issues? There might have been already answers to these but seems pretty much every Ge still have the same issues. For 2D-UI Epic I reduced the word count and added the rationale. Thanks, - Antti On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) wrote: > Hi Philipp, Hi all > > Epic- and Feature- descriptions are in the public wiki and are referenced > from the Materializing page as soon they are closed or on the roadmap page > as long they are worked on. > Renaming it in the Tracker is the minor part. > > The problem is, that without extending the name the backlog report will > show many errors, which will also be in a deliverable. Goal is to find a > consistent and good way to remove the errors without putting to much work > into it. > > To fulfill the naming rules we need to extend the Epic names, either bei > splitting large epics into two or by extending it with a generic term, > representing the whole epic. > > Here you find the links to all the epics available in the public wiki: > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 > > > @All: Please check the latest report ?All issues tab": > > https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx > > There are some Epics which have to much words in the description (>250) > - 2D-UI > - 3D-UI > - 3D-UI.DataflowProcessing > - DisplayAsAService > > and all of the following are missing content in the Rational Field (>=20 > words): > - 2D-UI > - 3D-UI > - 3D-UI.DataflowProcessing > - 3D-UI.HW-Support > - AugmentedReality > - CloudRendering > - DisplayAsAService > - InterfaceDesigner > - Synchronization > - Synchronization.SceneAPI > - VirtualCharacters > > Would be nice if you can fix the content part also while looking into the > naming. > > Cheers > Christof > > > Am 26.06.2014 um 12:19 schrieb Philipp Slusallek < > philipp.slusallek at dfki.de>: > > > Hi, > > > > This is something that is only really visible internally, right? > > Externally people only care about the GE and its functionality. > > > > So please, lets do whatever minimizes the amount of work right now. > > Those names are really not very meaningful for most people. > > > > > > Best, > > > > Philipp > > > > > > Am 26.06.2014 11:26, schrieb Marti Christof (mach): > >> Dear WP13 GEi owners > >> > >> The problem with the naming of the epics is, that we need to add an > EpicId. > >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId > >> > >> At the moment many WP13-epics are only named after the GE itself. e.g. > >> - FIWARE.Epic.MiWi.2D-UI > >> So we either need to add a generic EpicId (see below) or split up the > >> Epics in multiple meaningful peaces. > >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX > >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY > >> Because some of the Epic Description are also to long (see report ?All > >> issues?) and need to be shortened, this might be a good possiblity to > >> fix these issues too. > >> > >> Please let me know ASAP [today before EOB] if and how it would be > >> possible to split your current GEs Epic. > >> > >> Best regards > >> Christof > >> > >> > >> > >> Anfang der weitergeleiteten Nachricht: > >> > >>> *Von: *"Marti Christof (mach)" > > >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* > >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ > >>> *An: *MANUEL ESCRICHE VICENTE >>> > > >>> *Kopie: *MIGUEL CARRILLO PACHECO > > >>> > >>> Hi Manuel > >>> > >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have > >>> been based on the defined Epics. So the epics where available before > >>> the GEs. > >>> The problem did not show up before, because they were named > >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got > >>> the error there and had to rename them to the correct GE-names. > >>> > >>> I do not care to rename the Epics, but is there a rule or a schema in > >>> other WPs how to extend the name in such a case? > >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) > >>> or > >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) > >>> or > >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) > >>> or > >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality > >>> or > >>> - ? > >>> > >>> We can schedule a call to discuss this. I am available from 13:00 to > >>> 13:45 and then again from 16:00-... > >>> > >>> Best regards > >>> Christof > >>> > >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE > >>> >>> >: > >>> > >>>> Hi Christof, > >>>> > >>>> Rules haven?t changed. > >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are > >>>> organising items, it should add some organising value to the items > >>>> added below. > >>>> If you wish, we can do some research to the past to check how it was > >>>> at some definite time. > >>>> Let me know and we schedule a meeting. > >>>> > >>>> Kind regards, > >>>> Manuel > >>>> > >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] > >>>> *Sent:*jueves, 26 de junio de 2014 10:24 > >>>> *To:*MANUEL ESCRICHE VICENTE > >>>> *Cc:*MIGUEL CARRILLO PACHECO > >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews > >>>> > >>>> Hi Manuel > >>>> > >>>> I am working on fixing the problems with the backlog. > >>>> One point I have problems to fix is the Epic naming error, because > >>>> you expect an EpicId at the end, but most of our Epics are similar to > >>>> the GEs itself. So for the following GEs the Epics and the GE are > >>>> identical: > >>>> - FIWARE.Epic.MiWi.2D-UI > >>>> - FIWARE.Epic.MiWi.3D-UI > >>>> - FIWARE.Epic.MiWi.AugmentedReality > >>>> - FIWARE.Epic.MiWi.CloudRendering > >>>> - FIWARE.Epic.MiWi.DisplayAsAService > >>>> - FIWARE.Epic.MiWi.GISDataProvider > >>>> - FIWARE.Epic.MiWi.POIDataProvider > >>>> - FIWARE.Epic.MiWi.InterfaceDesigner > >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction > >>>> - FIWARE.Epic.MiWi.Synchronization > >>>> - FIWARE.Epic.MiWi.VirtualCharacters > >>>> > >>>> To accomplish the rules we would have to add some artificial EpicId > >>>> like .Basic oder .BaseFunctionality > >>>> Is this really intended? > >>>> > >>>> I also wonder, why this errors did not show up earlier, when we fixed > >>>> the last round of bugs. > >>>> > >>>> Best regards > >>>> Christof > >>>> > >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE > >>>> >>>> >: > >>>> > >>>> > >>>> Dear Partners, > >>>> > >>>> Please, find below updated reports. > >>>> > >>>> REVIEWS: > >>>> > https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx > >>>> > >>>> DASHBOARDS: > >>>> > https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx > >>>> > https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx > >>>> > >>>> If any support were required, please, don?t hesitate to let me > know. > >>>> > >>>> 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 y sus adjuntos se dirigen exclusivamente a su > >>>> destinatario, puede contener informaci?n privilegiada o > >>>> confidencial y es para uso exclusivo de la persona o entidad de > >>>> destino. Si no es usted. el destinatario indicado, queda > >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia > >>>> sin autorizaci?n puede estar prohibida en virtud de la > >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le > >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y > >>>> proceda a su destrucci?n. > >>>> > >>>> The information contained in this transmission is privileged and > >>>> confidential information intended only for the use of the > >>>> individual or entity named above. If the reader of this message > >>>> is not the intended recipient, you are hereby notified that any > >>>> dissemination, distribution or copying of this communication is > >>>> strictly prohibited. If you have received this transmission in > >>>> error, do not read it. Please immediately reply to the sender > >>>> that you have received this communication in error and then > >>>> delete it. > >>>> > >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu > >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial > >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? > >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a > >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode > >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta > >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente > >>>> por esta mesma via e proceda a sua destrui??o > >>>> _______________________________________________ > >>>> Fiware-ge-owners mailing list > >>>> Fiware-ge-owners at lists.fi-ware.org > >>>> > >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners > >>>> > >>>> > >>>> > ------------------------------------------------------------------------ > >>>> > >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su > >>>> destinatario, puede contener informaci?n privilegiada o confidencial > >>>> y es para uso exclusivo de la persona o entidad de destino. Si no es > >>>> usted. el destinatario indicado, queda notificado de que la lectura, > >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este > >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente por > >>>> esta misma v?a y proceda a su destrucci?n. > >>>> > >>>> The information contained in this transmission is privileged and > >>>> confidential information intended only for the use of the individual > >>>> or entity named above. If the reader of this message is not the > >>>> intended recipient, you are hereby notified that any dissemination, > >>>> distribution or copying of this communication is strictly prohibited. > >>>> If you have received this transmission in error, do not read it. > >>>> Please immediately reply to the sender that you have received this > >>>> communication in error and then delete it. > >>>> > >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu > >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, > >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e > >>>> proceda a sua destrui??o > >>> > >> > >> > >> > >> _______________________________________________ > >> Fiware-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 > > > --------------------------------------------------------------------------- > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Fri Jun 27 10:06:02 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Fri, 27 Jun 2014 08:06:02 +0000 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> Message-ID: Hi Antti, and all others having the same errors in the report. The first error is what we are discussing about splitting up the current epics into 2 or more smaller entries. The problem is, that an Epic name has to have the following schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId (Schema definitions are defined here: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow)) For 2D-UI this means we need an Epic name like: FIWARE.Epic.MiWi.2D-UI.X (where X is a reasonable name for the current Epic; I still look for a better name than ?Basic?, ?Basis?, ...) or to split the content of the epic in two parts: FIWARE.Epic.MiWi.2D-UI.X1 FIWARE.Epic.MiWi.2D-UI.X2 (where X1 contains a part of the current epic and X2 the remaining part of the current epic; X1 and X2 would be reasonable names for these functionalities) In 3D-UI we would then have for example: FIWARE.Epic.MiWi.3D-UI.HTMLModelExtension (new: previous FIWARE.Epic.MiWi.3D-UI; Is there a better name?) FIWARE.Epic.MiWi.3D-UI.DataFlowProcessing FIWARE.Epic.MiWi.3D-UI.HW-Support Maybe there is a similar rename or split possible in 2D-UI (and all the other with this error) For the second error it is simply a referencing issue. - Any Epic and Feature can only be referenced in the Materializing page, if it is closed in the tracker. - If it is still open it should have a reference in the roadmap (features in the left column, epics in the right column) This is simple to fix, as soon the first (naming issue) is fixed. Best regards Christof Am 27.06.2014 um 09:32 schrieb Antti Kokko >: Hello, I need some guidance with these issues: FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) FIWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide reference in tracker; remove reference from materializing;) What is the correct way of getting rid of these issues? There might have been already answers to these but seems pretty much every Ge still have the same issues. For 2D-UI Epic I reduced the word count and added the rationale. Thanks, - Antti On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) > wrote: Hi Philipp, Hi all Epic- and Feature- descriptions are in the public wiki and are referenced from the Materializing page as soon they are closed or on the roadmap page as long they are worked on. Renaming it in the Tracker is the minor part. The problem is, that without extending the name the backlog report will show many errors, which will also be in a deliverable. Goal is to find a consistent and good way to remove the errors without putting to much work into it. To fulfill the naming rules we need to extend the Epic names, either bei splitting large epics into two or by extending it with a generic term, representing the whole epic. Here you find the links to all the epics available in the public wiki: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 @All: Please check the latest report ?All issues tab": https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx There are some Epics which have to much words in the description (>250) - 2D-UI - 3D-UI - 3D-UI.DataflowProcessing - DisplayAsAService and all of the following are missing content in the Rational Field (>=20 words): - 2D-UI - 3D-UI - 3D-UI.DataflowProcessing - 3D-UI.HW-Support - AugmentedReality - CloudRendering - DisplayAsAService - InterfaceDesigner - Synchronization - Synchronization.SceneAPI - VirtualCharacters Would be nice if you can fix the content part also while looking into the naming. Cheers Christof Am 26.06.2014 um 12:19 schrieb Philipp Slusallek >: > Hi, > > This is something that is only really visible internally, right? > Externally people only care about the GE and its functionality. > > So please, lets do whatever minimizes the amount of work right now. > Those names are really not very meaningful for most people. > > > Best, > > Philipp > > > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >> Dear WP13 GEi owners >> >> The problem with the naming of the epics is, that we need to add an EpicId. >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >> >> At the moment many WP13-epics are only named after the GE itself. e.g. >> - FIWARE.Epic.MiWi.2D-UI >> So we either need to add a generic EpicId (see below) or split up the >> Epics in multiple meaningful peaces. >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >> Because some of the Epic Description are also to long (see report ?All >> issues?) and need to be shortened, this might be a good possiblity to >> fix these issues too. >> >> Please let me know ASAP [today before EOB] if and how it would be >> possible to split your current GEs Epic. >> >> Best regards >> Christof >> >> >> >> Anfang der weitergeleiteten Nachricht: >> >>> *Von: *"Marti Christof (mach)" >> >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>> *An: *MANUEL ESCRICHE VICENTE >>> >> >>> *Kopie: *MIGUEL CARRILLO PACHECO >> >>> >>> Hi Manuel >>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>> been based on the defined Epics. So the epics where available before >>> the GEs. >>> The problem did not show up before, because they were named >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >>> the error there and had to rename them to the correct GE-names. >>> >>> I do not care to rename the Epics, but is there a rule or a schema in >>> other WPs how to extend the name in such a case? >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>> or >>> - ? >>> >>> We can schedule a call to discuss this. I am available from 13:00 to >>> 13:45 and then again from 16:00-... >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>> >>> >>: >>> >>>> Hi Christof, >>>> >>>> Rules haven?t changed. >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>>> organising items, it should add some organising value to the items >>>> added below. >>>> If you wish, we can do some research to the past to check how it was >>>> at some definite time. >>>> Let me know and we schedule a meeting. >>>> >>>> Kind regards, >>>> Manuel >>>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>>> *To:*MANUEL ESCRICHE VICENTE >>>> *Cc:*MIGUEL CARRILLO PACHECO >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>>> >>>> Hi Manuel >>>> >>>> I am working on fixing the problems with the backlog. >>>> One point I have problems to fix is the Epic naming error, because >>>> you expect an EpicId at the end, but most of our Epics are similar to >>>> the GEs itself. So for the following GEs the Epics and the GE are >>>> identical: >>>> - FIWARE.Epic.MiWi.2D-UI >>>> - FIWARE.Epic.MiWi.3D-UI >>>> - FIWARE.Epic.MiWi.AugmentedReality >>>> - FIWARE.Epic.MiWi.CloudRendering >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>>> - FIWARE.Epic.MiWi.GISDataProvider >>>> - FIWARE.Epic.MiWi.POIDataProvider >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>>> - FIWARE.Epic.MiWi.Synchronization >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>>> >>>> To accomplish the rules we would have to add some artificial EpicId >>>> like .Basic oder .BaseFunctionality >>>> Is this really intended? >>>> >>>> I also wonder, why this errors did not show up earlier, when we fixed >>>> the last round of bugs. >>>> >>>> Best regards >>>> Christof >>>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>>> >>>> >>: >>>> >>>> >>>> Dear Partners, >>>> >>>> Please, find below updated reports. >>>> >>>> REVIEWS: >>>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>> >>>> DASHBOARDS: >>>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>>> >>>> If any support were required, please, don?t hesitate to let me know. >>>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> destino. Si no es usted. el destinatario indicado, queda >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>>> sin autorizaci?n puede estar prohibida en virtud de la >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>>> proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the >>>> individual or entity named above. If the reader of this message >>>> is not the intended recipient, you are hereby notified that any >>>> dissemination, distribution or copying of this communication is >>>> strictly prohibited. If you have received this transmission in >>>> error, do not read it. Please immediately reply to the sender >>>> that you have received this communication in error and then >>>> delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>>> por esta mesma via e proceda a sua destrui??o >>>> _______________________________________________ >>>> Fiware-ge-owners mailing list >>>> Fiware-ge-owners at lists.fi-ware.org >>>> > >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o confidencial >>>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>>> usted. el destinatario indicado, queda notificado de que la lectura, >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente por >>>> esta misma v?a y proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the individual >>>> or entity named above. If the reader of this message is not the >>>> intended recipient, you are hereby notified that any dissemination, >>>> distribution or copying of this communication is strictly prohibited. >>>> If you have received this transmission in error, do not read it. >>>> Please immediately reply to the sender that you have received this >>>> communication in error and then delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e ? >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>> proceda a sua destrui??o >>> >> >> >> >> _______________________________________________ >> Fiware-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 > --------------------------------------------------------------------------- > _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From antti.kokko at adminotech.com Fri Jun 27 10:16:06 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Fri, 27 Jun 2014 11:16:06 +0300 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> Message-ID: Hi, Has anyone succeeded in splitting already? It will affect so many places. Thanks, - Antti On Fri, Jun 27, 2014 at 11:06 AM, Marti Christof (mach) wrote: > Hi Antti, and all others having the same errors in the report. > > The first error is what we are discussing about splitting up the current > epics into 2 or more smaller entries. > The problem is, that an Epic name has to have the following schema: > FIWARE.Epic.Chapter.Enabler[.EpicId]*.*EpicId* > > (Schema definitions are defined here: > http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) > ) > > For 2D-UI this means we need an Epic name like: > FIWARE.Epic.MiWi.2D-UI.*X* > *(where X is a reasonable name for the current Epic; I still look for a > better name than ?Basic?, ?Basis?, ...)* > > or to split the content of the epic in two parts: > FIWARE.Epic.MiWi.2D-UI.*X1* > FIWARE.Epic.MiWi.2D-UI.*X2* > *(where X1 contains a part of the current epic and X2 the remaining part > of the current epic; X1 and X2 would be reasonable names for these > functionalities)* > > In 3D-UI we would then have for example: > FIWARE.Epic.MiWi.3D-UI.HTMLModelExtension (new: previous > FIWARE.Epic.MiWi.3D-UI; Is there a better name?) > FIWARE.Epic.MiWi.3D-UI.DataFlowProcessing > FIWARE.Epic.MiWi.3D-UI.HW-Support > > Maybe there is a similar rename or split possible in 2D-UI (and all the > other with this error) > > > For the second error it is simply a referencing issue. > - Any Epic and Feature can only be referenced in the Materializing page, > if it is closed in the tracker. > - If it is still open it should have a reference in the roadmap (features > in the left column, epics in the right column) > > This is simple to fix, as soon the first (naming issue) is fixed. > > Best regards > Christof > > > Am 27.06.2014 um 09:32 schrieb Antti Kokko : > > Hello, > > I need some guidance with these issues: > FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) F > IWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide > reference in tracker; remove reference from materializing;) > What is the correct way of getting rid of these issues? There might have > been already answers to these but seems pretty much every Ge still have the > same issues. > > For 2D-UI Epic I reduced the word count and added the rationale. > > Thanks, > > - Antti > > > > On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) > wrote: > >> Hi Philipp, Hi all >> >> Epic- and Feature- descriptions are in the public wiki and are referenced >> from the Materializing page as soon they are closed or on the roadmap page >> as long they are worked on. >> Renaming it in the Tracker is the minor part. >> >> The problem is, that without extending the name the backlog report will >> show many errors, which will also be in a deliverable. Goal is to find a >> consistent and good way to remove the errors without putting to much work >> into it. >> >> To fulfill the naming rules we need to extend the Epic names, either bei >> splitting large epics into two or by extending it with a generic term, >> representing the whole epic. >> >> Here you find the links to all the epics available in the public wiki: >> >> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 >> >> >> >> @All: Please check the latest report ?All issues tab": >> >> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >> >> There are some Epics which have to much words in the description (>250) >> - 2D-UI >> - 3D-UI >> - 3D-UI.DataflowProcessing >> - DisplayAsAService >> >> and all of the following are missing content in the Rational Field (>=20 >> words): >> - 2D-UI >> - 3D-UI >> - 3D-UI.DataflowProcessing >> - 3D-UI.HW-Support >> - AugmentedReality >> - CloudRendering >> - DisplayAsAService >> - InterfaceDesigner >> - Synchronization >> - Synchronization.SceneAPI >> - VirtualCharacters >> >> Would be nice if you can fix the content part also while looking into the >> naming. >> >> Cheers >> Christof >> >> >> Am 26.06.2014 um 12:19 schrieb Philipp Slusallek < >> philipp.slusallek at dfki.de>: >> >> > Hi, >> > >> > This is something that is only really visible internally, right? >> > Externally people only care about the GE and its functionality. >> > >> > So please, lets do whatever minimizes the amount of work right now. >> > Those names are really not very meaningful for most people. >> > >> > >> > Best, >> > >> > Philipp >> > >> > >> > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >> >> Dear WP13 GEi owners >> >> >> >> The problem with the naming of the epics is, that we need to add an >> EpicId. >> >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >> >> >> >> At the moment many WP13-epics are only named after the GE itself. e.g. >> >> - FIWARE.Epic.MiWi.2D-UI >> >> So we either need to add a generic EpicId (see below) or split up the >> >> Epics in multiple meaningful peaces. >> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >> >> Because some of the Epic Description are also to long (see report ?All >> >> issues?) and need to be shortened, this might be a good possiblity to >> >> fix these issues too. >> >> >> >> Please let me know ASAP [today before EOB] if and how it would be >> >> possible to split your current GEs Epic. >> >> >> >> Best regards >> >> Christof >> >> >> >> >> >> >> >> Anfang der weitergeleiteten Nachricht: >> >> >> >>> *Von: *"Marti Christof (mach)" > >> >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >> >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >> >>> *An: *MANUEL ESCRICHE VICENTE > >>> > >> >>> *Kopie: *MIGUEL CARRILLO PACHECO > >> >>> >> >>> Hi Manuel >> >>> >> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >> >>> been based on the defined Epics. So the epics where available before >> >>> the GEs. >> >>> The problem did not show up before, because they were named >> >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >> >>> the error there and had to rename them to the correct GE-names. >> >>> >> >>> I do not care to rename the Epics, but is there a rule or a schema in >> >>> other WPs how to extend the name in such a case? >> >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >> >>> or >> >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >> >>> or >> >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >> >>> or >> >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >> >>> or >> >>> - ? >> >>> >> >>> We can schedule a call to discuss this. I am available from 13:00 to >> >>> 13:45 and then again from 16:00-... >> >>> >> >>> Best regards >> >>> Christof >> >>> >> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >> >>> > >>> >: >> >>> >> >>>> Hi Christof, >> >>>> >> >>>> Rules haven?t changed. >> >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >> >>>> organising items, it should add some organising value to the items >> >>>> added below. >> >>>> If you wish, we can do some research to the past to check how it was >> >>>> at some definite time. >> >>>> Let me know and we schedule a meeting. >> >>>> >> >>>> Kind regards, >> >>>> Manuel >> >>>> >> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >> >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >> >>>> *To:*MANUEL ESCRICHE VICENTE >> >>>> *Cc:*MIGUEL CARRILLO PACHECO >> >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >> >>>> >> >>>> Hi Manuel >> >>>> >> >>>> I am working on fixing the problems with the backlog. >> >>>> One point I have problems to fix is the Epic naming error, because >> >>>> you expect an EpicId at the end, but most of our Epics are similar to >> >>>> the GEs itself. So for the following GEs the Epics and the GE are >> >>>> identical: >> >>>> - FIWARE.Epic.MiWi.2D-UI >> >>>> - FIWARE.Epic.MiWi.3D-UI >> >>>> - FIWARE.Epic.MiWi.AugmentedReality >> >>>> - FIWARE.Epic.MiWi.CloudRendering >> >>>> - FIWARE.Epic.MiWi.DisplayAsAService >> >>>> - FIWARE.Epic.MiWi.GISDataProvider >> >>>> - FIWARE.Epic.MiWi.POIDataProvider >> >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >> >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >> >>>> - FIWARE.Epic.MiWi.Synchronization >> >>>> - FIWARE.Epic.MiWi.VirtualCharacters >> >>>> >> >>>> To accomplish the rules we would have to add some artificial EpicId >> >>>> like .Basic oder .BaseFunctionality >> >>>> Is this really intended? >> >>>> >> >>>> I also wonder, why this errors did not show up earlier, when we fixed >> >>>> the last round of bugs. >> >>>> >> >>>> Best regards >> >>>> Christof >> >>>> >> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >> >>>> > >>>> >: >> >>>> >> >>>> >> >>>> Dear Partners, >> >>>> >> >>>> Please, find below updated reports. >> >>>> >> >>>> REVIEWS: >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >> >>>> >> >>>> DASHBOARDS: >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >> >>>> >> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >> >>>> >> >>>> If any support were required, please, don?t hesitate to let me >> know. >> >>>> >> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >> >>>> destinatario, puede contener informaci?n privilegiada o >> >>>> confidencial y es para uso exclusivo de la persona o entidad de >> >>>> destino. Si no es usted. el destinatario indicado, queda >> >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >> >>>> sin autorizaci?n puede estar prohibida en virtud de la >> >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >> >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >> >>>> proceda a su destrucci?n. >> >>>> >> >>>> The information contained in this transmission is privileged and >> >>>> confidential information intended only for the use of the >> >>>> individual or entity named above. If the reader of this message >> >>>> is not the intended recipient, you are hereby notified that any >> >>>> dissemination, distribution or copying of this communication is >> >>>> strictly prohibited. If you have received this transmission in >> >>>> error, do not read it. Please immediately reply to the sender >> >>>> that you have received this communication in error and then >> >>>> delete it. >> >>>> >> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >> >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >> >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >> >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >> >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >> >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >> >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >> >>>> por esta mesma via e proceda a sua destrui??o >> >>>> _______________________________________________ >> >>>> Fiware-ge-owners mailing list >> >>>> Fiware-ge-owners at lists.fi-ware.org >> >>>> >> >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >> >>>> >> >>>> >> >>>> >> ------------------------------------------------------------------------ >> >>>> >> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >> >>>> destinatario, puede contener informaci?n privilegiada o confidencial >> >>>> y es para uso exclusivo de la persona o entidad de destino. Si no es >> >>>> usted. el destinatario indicado, queda notificado de que la lectura, >> >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >> >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >> >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente por >> >>>> esta misma v?a y proceda a su destrucci?n. >> >>>> >> >>>> The information contained in this transmission is privileged and >> >>>> confidential information intended only for the use of the individual >> >>>> or entity named above. If the reader of this message is not the >> >>>> intended recipient, you are hereby notified that any dissemination, >> >>>> distribution or copying of this communication is strictly prohibited. >> >>>> If you have received this transmission in error, do not read it. >> >>>> Please immediately reply to the sender that you have received this >> >>>> communication in error and then delete it. >> >>>> >> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >> >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e ? >> >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >> >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >> >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida >> >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, >> >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >> >>>> proceda a sua destrui??o >> >>> >> >> >> >> >> >> >> >> _______________________________________________ >> >> Fiware-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 >> > >> --------------------------------------------------------------------------- >> > >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-miwi >> > > > > -- > > Best regards, > Antti Kokko > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > > -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From antti.kokko at adminotech.com Fri Jun 27 14:07:09 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Fri, 27 Jun 2014 15:07:09 +0300 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> Message-ID: Hello, I need some detailed fast instructions. How to split the epic. Does I need to put e.g. 2 epics in the tracker and how/where to split those in the wiki? These maybe stupid questions but I need to get this done. I ?m leaving for a 1 month summer holiday within an hour. Thanks, - Antti On Fri, Jun 27, 2014 at 11:16 AM, Antti Kokko wrote: > Hi, > > Has anyone succeeded in splitting already? It will affect so many places. > > Thanks, > > - Antti > > > On Fri, Jun 27, 2014 at 11:06 AM, Marti Christof (mach) > wrote: > >> Hi Antti, and all others having the same errors in the report. >> >> The first error is what we are discussing about splitting up the >> current epics into 2 or more smaller entries. >> The problem is, that an Epic name has to have the following schema: >> FIWARE.Epic.Chapter.Enabler[.EpicId]*.*EpicId* >> >> (Schema definitions are defined here: >> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >> ) >> >> For 2D-UI this means we need an Epic name like: >> FIWARE.Epic.MiWi.2D-UI.*X* >> *(where X is a reasonable name for the current Epic; I still look for a >> better name than ?Basic?, ?Basis?, ...)* >> >> or to split the content of the epic in two parts: >> FIWARE.Epic.MiWi.2D-UI.*X1* >> FIWARE.Epic.MiWi.2D-UI.*X2* >> *(where X1 contains a part of the current epic and X2 the remaining part >> of the current epic; X1 and X2 would be reasonable names for these >> functionalities)* >> >> In 3D-UI we would then have for example: >> FIWARE.Epic.MiWi.3D-UI.HTMLModelExtension (new: previous >> FIWARE.Epic.MiWi.3D-UI; Is there a better name?) >> FIWARE.Epic.MiWi.3D-UI.DataFlowProcessing >> FIWARE.Epic.MiWi.3D-UI.HW-Support >> >> Maybe there is a similar rename or split possible in 2D-UI (and all the >> other with this error) >> >> >> For the second error it is simply a referencing issue. >> - Any Epic and Feature can only be referenced in the Materializing page, >> if it is closed in the tracker. >> - If it is still open it should have a reference in the roadmap (features >> in the left column, epics in the right column) >> >> This is simple to fix, as soon the first (naming issue) is fixed. >> >> Best regards >> Christof >> >> >> Am 27.06.2014 um 09:32 schrieb Antti Kokko > >: >> >> Hello, >> >> I need some guidance with these issues: >> FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) F >> IWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide >> reference in tracker; remove reference from materializing;) >> What is the correct way of getting rid of these issues? There might have >> been already answers to these but seems pretty much every Ge still have the >> same issues. >> >> For 2D-UI Epic I reduced the word count and added the rationale. >> >> Thanks, >> >> - Antti >> >> >> >> On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) >> wrote: >> >>> Hi Philipp, Hi all >>> >>> Epic- and Feature- descriptions are in the public wiki and are >>> referenced from the Materializing page as soon they are closed or on the >>> roadmap page as long they are worked on. >>> Renaming it in the Tracker is the minor part. >>> >>> The problem is, that without extending the name the backlog report will >>> show many errors, which will also be in a deliverable. Goal is to find a >>> consistent and good way to remove the errors without putting to much work >>> into it. >>> >>> To fulfill the naming rules we need to extend the Epic names, either bei >>> splitting large epics into two or by extending it with a generic term, >>> representing the whole epic. >>> >>> Here you find the links to all the epics available in the public wiki: >>> >>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 >>> >>> >>> >>> @All: Please check the latest report ?All issues tab": >>> >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>> There are some Epics which have to much words in the description (>250) >>> - 2D-UI >>> - 3D-UI >>> - 3D-UI.DataflowProcessing >>> - DisplayAsAService >>> >>> and all of the following are missing content in the Rational Field (>=20 >>> words): >>> - 2D-UI >>> - 3D-UI >>> - 3D-UI.DataflowProcessing >>> - 3D-UI.HW-Support >>> - AugmentedReality >>> - CloudRendering >>> - DisplayAsAService >>> - InterfaceDesigner >>> - Synchronization >>> - Synchronization.SceneAPI >>> - VirtualCharacters >>> >>> Would be nice if you can fix the content part also while looking into >>> the naming. >>> >>> Cheers >>> Christof >>> >>> >>> Am 26.06.2014 um 12:19 schrieb Philipp Slusallek < >>> philipp.slusallek at dfki.de>: >>> >>> > Hi, >>> > >>> > This is something that is only really visible internally, right? >>> > Externally people only care about the GE and its functionality. >>> > >>> > So please, lets do whatever minimizes the amount of work right now. >>> > Those names are really not very meaningful for most people. >>> > >>> > >>> > Best, >>> > >>> > Philipp >>> > >>> > >>> > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >>> >> Dear WP13 GEi owners >>> >> >>> >> The problem with the naming of the epics is, that we need to add an >>> EpicId. >>> >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >>> >> >>> >> At the moment many WP13-epics are only named after the GE itself. e.g. >>> >> - FIWARE.Epic.MiWi.2D-UI >>> >> So we either need to add a generic EpicId (see below) or split up the >>> >> Epics in multiple meaningful peaces. >>> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >>> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >>> >> Because some of the Epic Description are also to long (see report ?All >>> >> issues?) and need to be shortened, this might be a good possiblity to >>> >> fix these issues too. >>> >> >>> >> Please let me know ASAP [today before EOB] if and how it would be >>> >> possible to split your current GEs Epic. >>> >> >>> >> Best regards >>> >> Christof >>> >> >>> >> >>> >> >>> >> Anfang der weitergeleiteten Nachricht: >>> >> >>> >>> *Von: *"Marti Christof (mach)" > >>> >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >>> >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>> >>> *An: *MANUEL ESCRICHE VICENTE >> >>> > >>> >>> *Kopie: *MIGUEL CARRILLO PACHECO > >>> >>> >>> >>> Hi Manuel >>> >>> >>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>> >>> been based on the defined Epics. So the epics where available before >>> >>> the GEs. >>> >>> The problem did not show up before, because they were named >>> >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >>> >>> the error there and had to rename them to the correct GE-names. >>> >>> >>> >>> I do not care to rename the Epics, but is there a rule or a schema in >>> >>> other WPs how to extend the name in such a case? >>> >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>> >>> or >>> >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>> >>> or >>> >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>> >>> or >>> >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>> >>> or >>> >>> - ? >>> >>> >>> >>> We can schedule a call to discuss this. I am available from 13:00 to >>> >>> 13:45 and then again from 16:00-... >>> >>> >>> >>> Best regards >>> >>> Christof >>> >>> >>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>> >>> >> >>> >: >>> >>> >>> >>>> Hi Christof, >>> >>>> >>> >>>> Rules haven?t changed. >>> >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>> >>>> organising items, it should add some organising value to the items >>> >>>> added below. >>> >>>> If you wish, we can do some research to the past to check how it was >>> >>>> at some definite time. >>> >>>> Let me know and we schedule a meeting. >>> >>>> >>> >>>> Kind regards, >>> >>>> Manuel >>> >>>> >>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>> >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>> >>>> *To:*MANUEL ESCRICHE VICENTE >>> >>>> *Cc:*MIGUEL CARRILLO PACHECO >>> >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>> >>>> >>> >>>> Hi Manuel >>> >>>> >>> >>>> I am working on fixing the problems with the backlog. >>> >>>> One point I have problems to fix is the Epic naming error, because >>> >>>> you expect an EpicId at the end, but most of our Epics are similar >>> to >>> >>>> the GEs itself. So for the following GEs the Epics and the GE are >>> >>>> identical: >>> >>>> - FIWARE.Epic.MiWi.2D-UI >>> >>>> - FIWARE.Epic.MiWi.3D-UI >>> >>>> - FIWARE.Epic.MiWi.AugmentedReality >>> >>>> - FIWARE.Epic.MiWi.CloudRendering >>> >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>> >>>> - FIWARE.Epic.MiWi.GISDataProvider >>> >>>> - FIWARE.Epic.MiWi.POIDataProvider >>> >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>> >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>> >>>> - FIWARE.Epic.MiWi.Synchronization >>> >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>> >>>> >>> >>>> To accomplish the rules we would have to add some artificial EpicId >>> >>>> like .Basic oder .BaseFunctionality >>> >>>> Is this really intended? >>> >>>> >>> >>>> I also wonder, why this errors did not show up earlier, when we >>> fixed >>> >>>> the last round of bugs. >>> >>>> >>> >>>> Best regards >>> >>>> Christof >>> >>>> >>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>> >>>> >> >>>> >: >>> >>>> >>> >>>> >>> >>>> Dear Partners, >>> >>>> >>> >>>> Please, find below updated reports. >>> >>>> >>> >>>> REVIEWS: >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>>> >>> >>>> DASHBOARDS: >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>> >>>> >>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>> >>>> >>> >>>> If any support were required, please, don?t hesitate to let me >>> know. >>> >>>> >>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>> >>>> destinatario, puede contener informaci?n privilegiada o >>> >>>> confidencial y es para uso exclusivo de la persona o entidad de >>> >>>> destino. Si no es usted. el destinatario indicado, queda >>> >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>> >>>> sin autorizaci?n puede estar prohibida en virtud de la >>> >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>> >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>> >>>> proceda a su destrucci?n. >>> >>>> >>> >>>> The information contained in this transmission is privileged and >>> >>>> confidential information intended only for the use of the >>> >>>> individual or entity named above. If the reader of this message >>> >>>> is not the intended recipient, you are hereby notified that any >>> >>>> dissemination, distribution or copying of this communication is >>> >>>> strictly prohibited. If you have received this transmission in >>> >>>> error, do not read it. Please immediately reply to the sender >>> >>>> that you have received this communication in error and then >>> >>>> delete it. >>> >>>> >>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>> >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>> >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>> >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>> >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>> >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>> >>>> por esta mesma via e proceda a sua destrui??o >>> >>>> _______________________________________________ >>> >>>> Fiware-ge-owners mailing list >>> >>>> Fiware-ge-owners at lists.fi-ware.org >>> >>>> >>> >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>> >>>> >>> >>>> >>> >>>> >>> ------------------------------------------------------------------------ >>> >>>> >>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> >>>> destinatario, puede contener informaci?n privilegiada o confidencial >>> >>>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> >>>> usted. el destinatario indicado, queda notificado de que la lectura, >>> >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>> >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>> >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>> por >>> >>>> esta misma v?a y proceda a su destrucci?n. >>> >>>> >>> >>>> The information contained in this transmission is privileged and >>> >>>> confidential information intended only for the use of the individual >>> >>>> or entity named above. If the reader of this message is not the >>> >>>> intended recipient, you are hereby notified that any dissemination, >>> >>>> distribution or copying of this communication is strictly >>> prohibited. >>> >>>> If you have received this transmission in error, do not read it. >>> >>>> Please immediately reply to the sender that you have received this >>> >>>> communication in error and then delete it. >>> >>>> >>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e >>> ? >>> >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >>> >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >>> >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar >>> proibida >>> >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, >>> >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>> >>>> proceda a sua destrui??o >>> >>> >>> >> >>> >> >>> >> >>> >> _______________________________________________ >>> >> Fiware-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 >>> > >>> --------------------------------------------------------------------------- >>> > >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-miwi >>> >> >> >> >> -- >> >> Best regards, >> Antti Kokko >> Meshmoon developer at Adminotech Ltd. >> www.meshmoon.com >> >> >> > > > -- > > Best regards, > Antti Kokko > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Fri Jun 27 15:08:01 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Fri, 27 Jun 2014 13:08:01 +0000 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <57e86926247d48809de1cc6554df0beb@SRV-MAIL-001.zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> <57e86926247d48809de1cc6554df0beb@SRV-MAIL-001.zhaw.ch> Message-ID: <8995889A-A268-4D63-84D4-3065B402BB33@zhaw.ch> Hi Antti I can handle the tracker, and the roadmap/materializing pages, if you only update the wiki-pages. If you want to keep it in one epic then you only need to rename the epic. - Go to the page, select ?move? and modify the target name by extending it with the EpicId. If you want to split it, the easiest way would be to create two new wiki pages: - go to the page. open in edit mode. mark and copy the content to copy-buffer. - leave edit mode and modify the name of the page in the url to your new page name, the wiki will offer you to create the page, if it does not exist. - past the content into new page and modify it. - repeat the same for the second epic. Christof Am 27.06.2014 um 14:07 schrieb Antti Kokko >: Hello, I need some detailed fast instructions. How to split the epic. Does I need to put e.g. 2 epics in the tracker and how/where to split those in the wiki? These maybe stupid questions but I need to get this done. I ?m leaving for a 1 month summer holiday within an hour. Thanks, - Antti On Fri, Jun 27, 2014 at 11:16 AM, Antti Kokko > wrote: Hi, Has anyone succeeded in splitting already? It will affect so many places. Thanks, - Antti On Fri, Jun 27, 2014 at 11:06 AM, Marti Christof (mach) > wrote: Hi Antti, and all others having the same errors in the report. The first error is what we are discussing about splitting up the current epics into 2 or more smaller entries. The problem is, that an Epic name has to have the following schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId (Schema definitions are defined here: http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow)) For 2D-UI this means we need an Epic name like: FIWARE.Epic.MiWi.2D-UI.X (where X is a reasonable name for the current Epic; I still look for a better name than ?Basic?, ?Basis?, ...) or to split the content of the epic in two parts: FIWARE.Epic.MiWi.2D-UI.X1 FIWARE.Epic.MiWi.2D-UI.X2 (where X1 contains a part of the current epic and X2 the remaining part of the current epic; X1 and X2 would be reasonable names for these functionalities) In 3D-UI we would then have for example: FIWARE.Epic.MiWi.3D-UI.HTMLModelExtension (new: previous FIWARE.Epic.MiWi.3D-UI; Is there a better name?) FIWARE.Epic.MiWi.3D-UI.DataFlowProcessing FIWARE.Epic.MiWi.3D-UI.HW-Support Maybe there is a similar rename or split possible in 2D-UI (and all the other with this error) For the second error it is simply a referencing issue. - Any Epic and Feature can only be referenced in the Materializing page, if it is closed in the tracker. - If it is still open it should have a reference in the roadmap (features in the left column, epics in the right column) This is simple to fix, as soon the first (naming issue) is fixed. Best regards Christof Am 27.06.2014 um 09:32 schrieb Antti Kokko >: Hello, I need some guidance with these issues: FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) FIWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide reference in tracker; remove reference from materializing;) What is the correct way of getting rid of these issues? There might have been already answers to these but seems pretty much every Ge still have the same issues. For 2D-UI Epic I reduced the word count and added the rationale. Thanks, - Antti On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) > wrote: Hi Philipp, Hi all Epic- and Feature- descriptions are in the public wiki and are referenced from the Materializing page as soon they are closed or on the roadmap page as long they are worked on. Renaming it in the Tracker is the minor part. The problem is, that without extending the name the backlog report will show many errors, which will also be in a deliverable. Goal is to find a consistent and good way to remove the errors without putting to much work into it. To fulfill the naming rules we need to extend the Epic names, either bei splitting large epics into two or by extending it with a generic term, representing the whole epic. Here you find the links to all the epics available in the public wiki: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 @All: Please check the latest report ?All issues tab": https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx There are some Epics which have to much words in the description (>250) - 2D-UI - 3D-UI - 3D-UI.DataflowProcessing - DisplayAsAService and all of the following are missing content in the Rational Field (>=20 words): - 2D-UI - 3D-UI - 3D-UI.DataflowProcessing - 3D-UI.HW-Support - AugmentedReality - CloudRendering - DisplayAsAService - InterfaceDesigner - Synchronization - Synchronization.SceneAPI - VirtualCharacters Would be nice if you can fix the content part also while looking into the naming. Cheers Christof Am 26.06.2014 um 12:19 schrieb Philipp Slusallek >: > Hi, > > This is something that is only really visible internally, right? > Externally people only care about the GE and its functionality. > > So please, lets do whatever minimizes the amount of work right now. > Those names are really not very meaningful for most people. > > > Best, > > Philipp > > > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >> Dear WP13 GEi owners >> >> The problem with the naming of the epics is, that we need to add an EpicId. >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >> >> At the moment many WP13-epics are only named after the GE itself. e.g. >> - FIWARE.Epic.MiWi.2D-UI >> So we either need to add a generic EpicId (see below) or split up the >> Epics in multiple meaningful peaces. >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >> Because some of the Epic Description are also to long (see report ?All >> issues?) and need to be shortened, this might be a good possiblity to >> fix these issues too. >> >> Please let me know ASAP [today before EOB] if and how it would be >> possible to split your current GEs Epic. >> >> Best regards >> Christof >> >> >> >> Anfang der weitergeleiteten Nachricht: >> >>> *Von: *"Marti Christof (mach)" >> >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>> *An: *MANUEL ESCRICHE VICENTE >>> >> >>> *Kopie: *MIGUEL CARRILLO PACHECO >> >>> >>> Hi Manuel >>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>> been based on the defined Epics. So the epics where available before >>> the GEs. >>> The problem did not show up before, because they were named >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >>> the error there and had to rename them to the correct GE-names. >>> >>> I do not care to rename the Epics, but is there a rule or a schema in >>> other WPs how to extend the name in such a case? >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>> or >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>> or >>> - ? >>> >>> We can schedule a call to discuss this. I am available from 13:00 to >>> 13:45 and then again from 16:00-... >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>> >>> >>: >>> >>>> Hi Christof, >>>> >>>> Rules haven?t changed. >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>>> organising items, it should add some organising value to the items >>>> added below. >>>> If you wish, we can do some research to the past to check how it was >>>> at some definite time. >>>> Let me know and we schedule a meeting. >>>> >>>> Kind regards, >>>> Manuel >>>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>>> *To:*MANUEL ESCRICHE VICENTE >>>> *Cc:*MIGUEL CARRILLO PACHECO >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>>> >>>> Hi Manuel >>>> >>>> I am working on fixing the problems with the backlog. >>>> One point I have problems to fix is the Epic naming error, because >>>> you expect an EpicId at the end, but most of our Epics are similar to >>>> the GEs itself. So for the following GEs the Epics and the GE are >>>> identical: >>>> - FIWARE.Epic.MiWi.2D-UI >>>> - FIWARE.Epic.MiWi.3D-UI >>>> - FIWARE.Epic.MiWi.AugmentedReality >>>> - FIWARE.Epic.MiWi.CloudRendering >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>>> - FIWARE.Epic.MiWi.GISDataProvider >>>> - FIWARE.Epic.MiWi.POIDataProvider >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>>> - FIWARE.Epic.MiWi.Synchronization >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>>> >>>> To accomplish the rules we would have to add some artificial EpicId >>>> like .Basic oder .BaseFunctionality >>>> Is this really intended? >>>> >>>> I also wonder, why this errors did not show up earlier, when we fixed >>>> the last round of bugs. >>>> >>>> Best regards >>>> Christof >>>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>>> >>>> >>: >>>> >>>> >>>> Dear Partners, >>>> >>>> Please, find below updated reports. >>>> >>>> REVIEWS: >>>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>> >>>> DASHBOARDS: >>>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>>> >>>> If any support were required, please, don?t hesitate to let me know. >>>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> destino. Si no es usted. el destinatario indicado, queda >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>>> sin autorizaci?n puede estar prohibida en virtud de la >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>>> proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the >>>> individual or entity named above. If the reader of this message >>>> is not the intended recipient, you are hereby notified that any >>>> dissemination, distribution or copying of this communication is >>>> strictly prohibited. If you have received this transmission in >>>> error, do not read it. Please immediately reply to the sender >>>> that you have received this communication in error and then >>>> delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>>> por esta mesma via e proceda a sua destrui??o >>>> _______________________________________________ >>>> Fiware-ge-owners mailing list >>>> Fiware-ge-owners at lists.fi-ware.org >>>> > >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> destinatario, puede contener informaci?n privilegiada o confidencial >>>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>>> usted. el destinatario indicado, queda notificado de que la lectura, >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente por >>>> esta misma v?a y proceda a su destrucci?n. >>>> >>>> The information contained in this transmission is privileged and >>>> confidential information intended only for the use of the individual >>>> or entity named above. If the reader of this message is not the >>>> intended recipient, you are hereby notified that any dissemination, >>>> distribution or copying of this communication is strictly prohibited. >>>> If you have received this transmission in error, do not read it. >>>> Please immediately reply to the sender that you have received this >>>> communication in error and then delete it. >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial e ? >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>> proceda a sua destrui??o >>> >> >> >> >> _______________________________________________ >> Fiware-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 > --------------------------------------------------------------------------- > _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-miwi -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ari.okkonen at cie.fi Fri Jun 27 15:29:08 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Fri, 27 Jun 2014 16:29:08 +0300 Subject: [Fiware-miwi] A successful correction! Was: [Fiware-ge-owners] Backlog Content: updated reports In-Reply-To: References: Message-ID: <53AD71A4.8090408@cie.fi> Hi I succeeded to get rid of C3 Valid and Consistent Reference "FIWARE.Epic.MiWi.POIDataProvider (<- adjust reference to pattern)" error. My approach was * /Moving/ the wiki page FIWARE.Epic.MiWi.POIDataProvider to FIWARE.Epic.MiWi.POIDataProvider*.Basic* * /Changing/ the references in Roadmap and Tracker I was afraid that the change would cascade to new errors, but luckily that didn't happen. Apparently, Roadmap requires some more tuning, because of the remaining error: C6 - Check for consistency with Roadmap and Materializing= KO--> 1 issues detected 1 [OpenDocs.1]: Test for Open Documentation - Check for appropriate presence Item Id Entry Type - Status - Presence: Item Reference T-7481 Epic - Open -R=No; T=Yes; M=No: FIWARE.Epic.MiWi.POIDataProvider.Basic(<-- provide reference in roadmap;) *I have no idea what to do with that.* BR Ari On 2014-06-27 10:07, MANUEL ESCRICHE VICENTE wrote: > > Dear Partners, > > Please, find updated backlog reports for easy your activity on content > improvement. > > REVIEWS: > > https://forge.fi-ware.org/docman/view.php/27/4255/FIWARE.backlog.apps.review.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4256/FIWARE.backlog.cloud.review.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4257/FIWARE.backlog.iot.review.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4258/FIWARE.backlog.data.review.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4259/FIWARE.backlog.i2nd.review.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4260/FIWARE.backlog.security.review.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4261/FIWARE.backlog.miwi.review.20140627.xlsx > > DASHBOARDS: > > https://forge.fi-ware.org/docman/view.php/27/4248/FIWARE.backlog.apps.dashboard.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4249/FIWARE.backlog.cloud.dashboard.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4250/FIWARE.backlog.iot.dashboard.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4251/FIWARE.backlog.data.dashboard.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4252/FIWARE.backlog.i2nd.dashboard.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4253/FIWARE.backlog.security.dashboard.20140627.xlsx > > https://forge.fi-ware.org/docman/view.php/27/4254/FIWARE.backlog.miwi.dashboard.20140627.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 y sus adjuntos se dirigen exclusivamente a su > destinatario, puede contener informaci?n privilegiada o confidencial y > es para uso exclusivo de la persona o entidad de destino. Si no es > usted. el destinatario indicado, queda notificado de que la lectura, > utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar > prohibida en virtud de la legislaci?n vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por > esta misma v?a y proceda a su destrucci?n. > > The information contained in this transmission is privileged and > confidential information intended only for the use of the individual > or entity named above. If the reader of this message is not the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this transmission in error, do not read it. > Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu > destinat?rio, pode conter informa??o privilegiada ou confidencial e ? > para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa > senhoria o destinat?rio indicado, fica notificado de que a leitura, > utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida > em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, > rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destrui??o > > > _______________________________________________ > Fiware-ge-owners mailing list > Fiware-ge-owners at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-ge-owners -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lasse.oorni at ludocraft.com Fri Jun 27 17:43:14 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Fri, 27 Jun 2014 18:43:14 +0300 Subject: [Fiware-miwi] A successful correction! Was: [Fiware-ge-owners] Backlog Content: updated reports In-Reply-To: <53AD71A4.8090408@cie.fi> References: <53AD71A4.8090408@cie.fi> Message-ID: <7ad9edd7c574f3542f0b2e153c68d1cb.squirrel@urho.ludocraft.com> > Hi > > I succeeded to get rid of C3 Valid and Consistent Reference > "FIWARE.Epic.MiWi.POIDataProvider (<- adjust reference to pattern)" > error. My approach was Hi, I followed this lead (being the least work approach) and moved the epic wiki pages as follows: FIWARE.Epic.MiWi.Synchronization -> FIWARE.Epic.MiWi.Synchronization.Basic FIWARE.Epic.MiWi.VirtualCharacters -> FIWARE.Epic.MiWi.VirtualCharacters.Basic and updated the MiWi materializing page to match. -- Lasse ??rni Game Programmer LudoCraft Ltd. From antti.kokko at adminotech.com Fri Jun 27 18:40:02 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Fri, 27 Jun 2014 19:40:02 +0300 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: <8995889A-A268-4D63-84D4-3065B402BB33@zhaw.ch> References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> <57e86926247d48809de1cc6554df0beb@SRV-MAIL-001.zhaw.ch> <8995889A-A268-4D63-84D4-3065B402BB33@zhaw.ch> Message-ID: Thank you! I'll make it 2 epics. ..InputAPI and ..WebComponent. - Antti On Friday, June 27, 2014, Marti Christof (mach) wrote: > Hi Antti > > I can handle the tracker, and the roadmap/materializing pages, if you > only update the wiki-pages. > > If you want to keep it in one epic then you only need to rename the > epic. > - Go to the page, select ?move? and modify the target name by extending it > with the EpicId. > > If you want to split it, the easiest way would be to create two new wiki > pages: > - go to the page. open in edit mode. mark and copy the content to > copy-buffer. > - leave edit mode and modify the name of the page in the url to your new > page name, the wiki will offer you to create the page, if it does not exist. > - past the content into new page and modify it. > - repeat the same for the second epic. > > Christof > > > Am 27.06.2014 um 14:07 schrieb Antti Kokko >: > > Hello, > > I need some detailed fast instructions. How to split the epic. Does I > need to put e.g. 2 epics in the tracker and how/where to split those in the > wiki? These maybe stupid questions but I need to get this done. I ?m > leaving for a 1 month summer holiday within an hour. > > Thanks, > > - Antti > > > On Fri, Jun 27, 2014 at 11:16 AM, Antti Kokko > wrote: > >> Hi, >> >> Has anyone succeeded in splitting already? It will affect so many places. >> >> Thanks, >> >> - Antti >> >> >> On Fri, Jun 27, 2014 at 11:06 AM, Marti Christof (mach) > > wrote: >> >>> Hi Antti, and all others having the same errors in the report. >>> >>> The first error is what we are discussing about splitting up the >>> current epics into 2 or more smaller entries. >>> The problem is, that an Epic name has to have the following schema: >>> FIWARE.Epic.Chapter.Enabler[.EpicId]*.*EpicId* >>> >>> (Schema definitions are defined here: >>> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>> ) >>> >>> For 2D-UI this means we need an Epic name like: >>> FIWARE.Epic.MiWi.2D-UI.*X* >>> *(where X is a reasonable name for the current Epic; I still look for a >>> better name than ?Basic?, ?Basis?, ...)* >>> >>> or to split the content of the epic in two parts: >>> FIWARE.Epic.MiWi.2D-UI.*X1* >>> FIWARE.Epic.MiWi.2D-UI.*X2* >>> *(where X1 contains a part of the current epic and X2 the remaining part >>> of the current epic; X1 and X2 would be reasonable names for these >>> functionalities)* >>> >>> In 3D-UI we would then have for example: >>> FIWARE.Epic.MiWi.3D-UI.HTMLModelExtension (new: previous >>> FIWARE.Epic.MiWi.3D-UI; Is there a better name?) >>> FIWARE.Epic.MiWi.3D-UI.DataFlowProcessing >>> FIWARE.Epic.MiWi.3D-UI.HW-Support >>> >>> Maybe there is a similar rename or split possible in 2D-UI (and all >>> the other with this error) >>> >>> >>> For the second error it is simply a referencing issue. >>> - Any Epic and Feature can only be referenced in the Materializing page, >>> if it is closed in the tracker. >>> - If it is still open it should have a reference in the roadmap >>> (features in the left column, epics in the right column) >>> >>> This is simple to fix, as soon the first (naming issue) is fixed. >>> >>> Best regards >>> Christof >>> >>> >>> Am 27.06.2014 um 09:32 schrieb Antti Kokko >> >: >>> >>> Hello, >>> >>> I need some guidance with these issues: >>> FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) F >>> IWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide >>> reference in tracker; remove reference from materializing;) >>> What is the correct way of getting rid of these issues? There might have >>> been already answers to these but seems pretty much every Ge still have the >>> same issues. >>> >>> For 2D-UI Epic I reduced the word count and added the rationale. >>> >>> Thanks, >>> >>> - Antti >>> >>> >>> >>> On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) >> > wrote: >>> >>>> Hi Philipp, Hi all >>>> >>>> Epic- and Feature- descriptions are in the public wiki and are >>>> referenced from the Materializing page as soon they are closed or on the >>>> roadmap page as long they are worked on. >>>> Renaming it in the Tracker is the minor part. >>>> >>>> The problem is, that without extending the name the backlog report will >>>> show many errors, which will also be in a deliverable. Goal is to find a >>>> consistent and good way to remove the errors without putting to much work >>>> into it. >>>> >>>> To fulfill the naming rules we need to extend the Epic names, either >>>> bei splitting large epics into two or by extending it with a generic term, >>>> representing the whole epic. >>>> >>>> Here you find the links to all the epics available in the public wiki: >>>> >>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 >>>> >>>> >>>> >>>> @All: Please check the latest report ?All issues tab": >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>> >>>> There are some Epics which have to much words in the description (>250) >>>> - 2D-UI >>>> - 3D-UI >>>> - 3D-UI.DataflowProcessing >>>> - DisplayAsAService >>>> >>>> and all of the following are missing content in the Rational Field >>>> (>=20 words): >>>> - 2D-UI >>>> - 3D-UI >>>> - 3D-UI.DataflowProcessing >>>> - 3D-UI.HW-Support >>>> - AugmentedReality >>>> - CloudRendering >>>> - DisplayAsAService >>>> - InterfaceDesigner >>>> - Synchronization >>>> - Synchronization.SceneAPI >>>> - VirtualCharacters >>>> >>>> Would be nice if you can fix the content part also while looking into >>>> the naming. >>>> >>>> Cheers >>>> Christof >>>> >>>> >>>> Am 26.06.2014 um 12:19 schrieb Philipp Slusallek < >>>> philipp.slusallek at dfki.de >>>> >: >>>> >>>> > Hi, >>>> > >>>> > This is something that is only really visible internally, right? >>>> > Externally people only care about the GE and its functionality. >>>> > >>>> > So please, lets do whatever minimizes the amount of work right now. >>>> > Those names are really not very meaningful for most people. >>>> > >>>> > >>>> > Best, >>>> > >>>> > Philipp >>>> > >>>> > >>>> > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >>>> >> Dear WP13 GEi owners >>>> >> >>>> >> The problem with the naming of the epics is, that we need to add an >>>> EpicId. >>>> >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >>>> >> >>>> >> At the moment many WP13-epics are only named after the GE itself. >>>> e.g. >>>> >> - FIWARE.Epic.MiWi.2D-UI >>>> >> So we either need to add a generic EpicId (see below) or split up the >>>> >> Epics in multiple meaningful peaces. >>>> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >>>> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >>>> >> Because some of the Epic Description are also to long (see report >>>> ?All >>>> >> issues?) and need to be shortened, this might be a good possiblity >>>> to >>>> >> fix these issues too. >>>> >> >>>> >> Please let me know ASAP [today before EOB] if and how it would be >>>> >> possible to split your current GEs Epic. >>>> >> >>>> >> Best regards >>>> >> Christof >>>> >> >>>> >> >>>> >> >>>> >> Anfang der weitergeleiteten Nachricht: >>>> >> >>>> >>> *Von: *"Marti Christof (mach)" >>> >>> >> >>>> >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated >>>> reviews* >>>> >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>>> >>> *An: *MANUEL ESCRICHE VICENTE < >>>> manuel.escrichevicente at telefonica.com >>>> >>>> >>> >>> >>>> >> >>>> >>> *Kopie: *MIGUEL CARRILLO PACHECO >>> >>> >> >>>> >>> >>>> >>> Hi Manuel >>>> >>> >>>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>>> >>> been based on the defined Epics. So the epics where available before >>>> >>> the GEs. >>>> >>> The problem did not show up before, because they were named >>>> >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >>>> >>> the error there and had to rename them to the correct GE-names. >>>> >>> >>>> >>> I do not care to rename the Epics, but is there a rule or a schema >>>> in >>>> >>> other WPs how to extend the name in such a case? >>>> >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>>> >>> or >>>> >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>>> >>> or >>>> >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>>> >>> or >>>> >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>>> >>> or >>>> >>> - ? >>>> >>> >>>> >>> We can schedule a call to discuss this. I am available from 13:00 to >>>> >>> 13:45 and then again from 16:00-... >>>> >>> >>>> >>> Best regards >>>> >>> Christof >>>> >>> >>>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>>> >>> >>> >>>> >>> >>> >>>> >>: >>>> >>> >>>> >>>> Hi Christof, >>>> >>>> >>>> >>>> Rules haven?t changed. >>>> >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>>> >>>> organising items, it should add some organising value to the items >>>> >>>> added below. >>>> >>>> If you wish, we can do some research to the past to check how it >>>> was >>>> >>>> at some definite time. >>>> >>>> Let me know and we schedule a meeting. >>>> >>>> >>>> >>>> Kind regards, >>>> >>>> Manuel >>>> >>>> >>>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch >>>> ] >>>> >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>>> >>>> *To:*MANUEL ESCRICHE VICENTE >>>> >>>> *Cc:*MIGUEL CARRILLO PACHECO >>>> >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>>> >>>> >>>> >>>> Hi Manuel >>>> >>>> >>>> >>>> I am working on fixing the problems with the backlog. >>>> >>>> One point I have problems to fix is the Epic naming error, because >>>> >>>> you expect an EpicId at the end, but most of our Epics are similar >>>> to >>>> >>>> the GEs itself. So for the following GEs the Epics and the GE are >>>> >>>> identical: >>>> >>>> - FIWARE.Epic.MiWi.2D-UI >>>> >>>> - FIWARE.Epic.MiWi.3D-UI >>>> >>>> - FIWARE.Epic.MiWi.AugmentedReality >>>> >>>> - FIWARE.Epic.MiWi.CloudRendering >>>> >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>>> >>>> - FIWARE.Epic.MiWi.GISDataProvider >>>> >>>> - FIWARE.Epic.MiWi.POIDataProvider >>>> >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>>> >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>>> >>>> - FIWARE.Epic.MiWi.Synchronization >>>> >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>>> >>>> >>>> >>>> To accomplish the rules we would have to add some artificial EpicId >>>> >>>> like .Basic oder .BaseFunctionality >>>> >>>> Is this really intended? >>>> >>>> >>>> >>>> I also wonder, why this errors did not show up earlier, when we >>>> fixed >>>> >>>> the last round of bugs. >>>> >>>> >>>> >>>> Best regards >>>> >>>> Christof >>>> >>>> >>>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>>> >>>> >>> >>>> >>>> >>> >>>> >>: >>>> >>>> >>>> >>>> >>>> >>>> Dear Partners, >>>> >>>> >>>> >>>> Please, find below updated reports. >>>> >>>> >>>> >>>> REVIEWS: >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>> >>>> >>>> >>>> DASHBOARDS: >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>>> >>>> >>>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>>> >>>> >>>> >>>> If any support were required, please, don?t hesitate to let me >>>> know. >>>> >>>> >>>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>>> >>>> destinatario, puede contener informaci?n privilegiada o >>>> >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>> >>>> destino. Si no es usted. el destinatario indicado, queda >>>> >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia >>>> >>>> sin autorizaci?n puede estar prohibida en virtud de la >>>> >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>>> >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a y >>>> >>>> proceda a su destrucci?n. >>>> >>>> >>>> >>>> The information contained in this transmission is privileged and >>>> >>>> confidential information intended only for the use of the >>>> >>>> individual or entity named above. If the reader of this message >>>> >>>> is not the intended recipient, you are hereby notified that any >>>> >>>> dissemination, distribution or copying of this communication is >>>> >>>> strictly prohibited. If you have received this transmission in >>>> >>>> error, do not read it. Please immediately reply to the sender >>>> >>>> that you have received this communication in error and then >>>> >>>> delete it. >>>> >>>> >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> >>>> destinat?rio, pode conter informa??o privilegiada ou >>>> confidencial >>>> >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o >>>> ? >>>> >>>> vossa senhoria o destinat?rio indicado, fica notificado de que a >>>> >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>> >>>> estar proibida em virtude da legisla??o vigente. Se recebeu esta >>>> >>>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente >>>> >>>> por esta mesma via e proceda a sua destrui??o >>>> >>>> _______________________________________________ >>>> >>>> Fiware-ge-owners mailing list >>>> >>>> Fiware-ge-owners at lists.fi-ware.org >>>> >>>> >>>> >>> > >>>> >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>>> >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>> >>>> destinatario, puede contener informaci?n privilegiada o >>>> confidencial >>>> >>>> y es para uso exclusivo de la persona o entidad de destino. Si no >>>> es >>>> >>>> usted. el destinatario indicado, queda notificado de que la >>>> lectura, >>>> >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>>> >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>>> >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>>> por >>>> >>>> esta misma v?a y proceda a su destrucci?n. >>>> >>>> >>>> >>>> The information contained in this transmission is privileged and >>>> >>>> confidential information intended only for the use of the >>>> individual >>>> >>>> or entity named above. If the reader of this message is not the >>>> >>>> intended recipient, you are hereby notified that any dissemination, >>>> >>>> distribution or copying of this communication is strictly >>>> prohibited. >>>> >>>> If you have received this transmission in error, do not read it. >>>> >>>> Please immediately reply to the sender that you have received this >>>> >>>> communication in error and then delete it. >>>> >>>> >>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>> >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>>> e ? >>>> >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa >>>> >>>> senhoria o destinat?rio indicado, fica notificado de que a leitura, >>>> >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar >>>> proibida >>>> >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por >>>> erro, >>>> >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>> >>>> proceda a sua destrui??o >>>> >>> >>>> >> >>>> >> >>>> >> >>>> >> _______________________________________________ >>>> >> Fiware-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 >>>> > >>>> --------------------------------------------------------------------------- >>>> > >>>> >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.org >>>> >>>> https://lists.fi-ware.org/listinfo/fiware-miwi >>>> >>> >>> >>> >>> -- >>> >>> Best regards, >>> Antti Kokko >>> Meshmoon developer at Adminotech Ltd. >>> www.meshmoon.com >>> >>> >>> >> >> >> -- >> >> Best regards, >> Antti Kokko >> Meshmoon developer at Adminotech Ltd. >> www.meshmoon.com >> > > > > -- > > Best regards, > Antti Kokko > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > > -- Best regards, Antti Kokko Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jarkko at cyberlightning.com Sat Jun 28 15:05:44 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Sat, 28 Jun 2014 16:05:44 +0300 Subject: [Fiware-miwi] A successful correction! Was: [Fiware-ge-owners] Backlog Content: updated reports In-Reply-To: <7ad9edd7c574f3542f0b2e153c68d1cb.squirrel@urho.ludocraft.com> References: <53AD71A4.8090408@cie.fi> <7ad9edd7c574f3542f0b2e153c68d1cb.squirrel@urho.ludocraft.com> Message-ID: The same has been also applied to GIS and Real Virtual Interaction. - jarkko On Fri, Jun 27, 2014 at 6:43 PM, "Lasse ??rni" wrote: > > Hi > > > > I succeeded to get rid of C3 Valid and Consistent Reference > > "FIWARE.Epic.MiWi.POIDataProvider (<- adjust reference to pattern)" > > error. My approach was > > Hi, > I followed this lead (being the least work approach) and moved the epic > wiki pages as follows: > > FIWARE.Epic.MiWi.Synchronization -> FIWARE.Epic.MiWi.Synchronization.Basic > FIWARE.Epic.MiWi.VirtualCharacters -> > FIWARE.Epic.MiWi.VirtualCharacters.Basic > > and updated the MiWi materializing page to match. > > -- > Lasse ??rni > Game Programmer > LudoCraft Ltd. > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi > -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jarkko at cyberlightning.com Mon Jun 30 09:37:53 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Mon, 30 Jun 2014 10:37:53 +0300 Subject: [Fiware-miwi] Asset instancing mechanism for XML3D query responses of GIS Data Provider In-Reply-To: <53AC1529.2060309@dfki.de> References: <53AC1529.2060309@dfki.de> Message-ID: Torsten, The changes you suggest are surely doable and we should take those into the "TODO" -list. However, I would not yet pursue in changing the code related to this since it would affect the deliverables and also documents. I am uncertain how those changes would be incorporated at this point, given that we we have had some trouble in finalizing the documentation in the past. Maybe this could go (among other things) to the task list of Fi-Core enhancements for GIS. - j On Thu, Jun 26, 2014 at 3:42 PM, Torsten Spieldenner < torsten.spieldenner at dfki.de> wrote: > Hello, > > as mentioned in the call yesterday, I think the delivery of the XML3D > ground geometry as reply from GIS-Data-Provider could be improved based on > the new asset instancing technique of XML3D. > > Currently, the result is returned as .xml3d - file, that contains the > geometry in a format similar to that: > > > > ..... // indices, positions, texcoords ... // /// > > > > Client handles the request by copying this reply into the client's > xml3d-node. This works fine, the drawback here is just that all geometry is > present in the DOM. > > What could work instead, is returning an .xml file (response-type > application/xml) with the following content: > > > > > > > ..... // indices, positions, texcoords as before // ... > > > > > Now instead of querying $PROVIDER-HOST/QUERY and copy the response, the > client would create and add a node that references the by > specifying the query as external source: > > > > What happens then, is that the client creates an instance of the > externally described asset that describes the ground geometry. This should > create exactly the same scene as before, just that the description of the > ground geometry in the client's DOM is reduced from the full vertex data to > this single model node. > > Best > Torsten > -- Jarkko Vatjus-Anttila CTO Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com See our new press release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ari.okkonen at cie.fi Mon Jun 30 09:55:57 2014 From: ari.okkonen at cie.fi (Ari Okkonen CIE) Date: Mon, 30 Jun 2014 10:55:57 +0300 Subject: [Fiware-miwi] Fi-ware content packaging - what must be done? Message-ID: <53B1180D.40203@cie.fi> Hi I have a problem. Arto at CIE has been doing installation stuff. Now he is in vacation until August. Sorry to admit that Manuels reminder about *"making GE/GEIs available at FI-LAB" *surprised me. Could I have some pointer about what to do about it. BR Ari -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Mon Jun 30 10:09:24 2014 From: toni at playsign.net (Toni Alatalo) Date: Mon, 30 Jun 2014 11:09:24 +0300 Subject: [Fiware-miwi] Fi-ware content packaging - what must be done? In-Reply-To: <53B1180D.40203@cie.fi> References: <53B1180D.40203@cie.fi> Message-ID: I think first question is whether you have changes after the previous 3.3 release that you want to release in 3.4 now. The items in his sheet seemed to be about 3.4 release. On Mon, Jun 30, 2014 at 10:55 AM, Ari Okkonen CIE wrote: > Hi > > I have a problem. > Arto at CIE has been doing installation stuff. Now he is in vacation until > August. > Sorry to admit that Manuels reminder about *"making GE/GEIs available at > FI-LAB" *surprised me. > Could I have some pointer about what to do about it. > > BR > Ari > > -- > Ari Okkonen > CIE, University of Oulu > > > _______________________________________________ > 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 cvetan at adminotech.com Mon Jun 30 15:54:26 2014 From: cvetan at adminotech.com (Cvetan Stefanovski) Date: Mon, 30 Jun 2014 15:54:26 +0200 Subject: [Fiware-miwi] Reminder: GEi Installation and Test verification In-Reply-To: References: <7B60B5EE-D4C8-483A-B49F-184BEEBFF828@zhaw.ch> Message-ID: Hello, Here's the installation feedback by Adminotech On Wed, Jun 25, 2014 at 11:34 AM, Jarkko Vatjus-Anttila < jarkko at cyberlightning.com> wrote: > Thanks for the comments Toni, > > This was exactly what I was thinking, so majority(?) of WebGL features > work, but there are still a lot which don't. This would be only a note for > the user, that just "do not yet assume everything works flawlessly". > > Maybe I am looking for grounds saying: our apps and code work, do not > blame us if the browser does not :D > > - j > > > On Wed, Jun 25, 2014 at 12:23 PM, Toni Alatalo wrote: > >> Hi - thanks for the reviews, just a quick note about Internet Explorer >> support which was mentioned in the doc: >> >> IE 11 at least in win8 metro mode has pretty good WebGL support nowadays >> and AFAIK websockets work too. It is true however that not all things work >> and are not tested that much, we'll edit to note that in the doc somehow. >> >> For example this simple standalone thing works with the controls and all, >> http://playsign.tklapp.com:8000/WebTundra/examples/xml3d/example-ctm.html >> .. also the Virtual Characters demo from >> http://playsign.tklapp.com:8000/WebTundra/examples/Avatar/ runs fine for >> me on IE now (first I got a strange bug though that not everything animated >> correctly, perhaps due to loading order probs) >> >> Cheers, >> ~Toni >> >> >> >> On Wed, Jun 25, 2014 at 9:20 AM, Jarkko Vatjus-Anttila < >> jarkko at cyberlightning.com> wrote: >> >>> Hello, >>> >>> For those components which were meant to be tested by Cyberlightning, >>> the testing was performed already last week. The reports just have been >>> sitting on my table. :) >>> >>> Anyways, here are the three documents filled with relevant test >>> information. Interface designer, web tundra and virtual characters. >>> >>> Should I update the testing page with test dates myself, and should I >>> also complete the testing dashboard, or shall you Christof edit those >>> collectively? >>> >>> - jarkko >>> >>> >>> >>> >>> On Tue, Jun 24, 2014 at 3:04 PM, Marti Christof (mach) >>> wrote: >>> >>>> I would like to remind you, that the internal deadline for the GEi >>>> Installation and Test verification is today (external end of week, but we >>>> need some spare time to check ensure the quality). >>>> >>>> Goal is to verify the installation of each GEi by another partner in >>>> the WP and write a short report, which will be part of deliverable D.10.5.3 >>>> "Report on Validation Process including Validation with Use Case projects?. >>>> >>>> For the moment we can only verify the local tests. We will do a second >>>> round and extend the reports, as soon the GEi?s are available on FI-LAB. >>>> >>>> See the GEi each partner has to validate in the following spreadsheet: >>>> >>>> https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0 >>>> >>>> When testing the GEi installation and verifying the tests you should >>>> fill out the following report: >>>> https://forge.fi-ware.org/docman/view.php/36/4019/I10.2_Installation_and_Test_Template_v2.docx >>>> and send it to me. >>>> >>>> In the Testbed V3 Installation and Test wiki page are also the links to >>>> the reports already produced: >>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/testbed/index.php/Testbed_V3_Installation_and_Test_aka_D10.5.3 >>>> >>>> The following GE/GEi reports (linked there) of WP3 (Apps & Services) >>>> are good examples, which give also feedback and enhancement tips in the >>>> appendix section: >>>> - Service Description Repository / Repository - SAP RI >>>> - Service Registry / Registry - SAP RI >>>> - Light Semantic Composition Editor / COMPEL >>>> >>>> Best regards >>>> Christof >>>> ---- >>>> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch >>>> Institut of Applied Information Technology - InIT >>>> Zurich University of Applied Sciences - ZHAW >>>> School of Engineering >>>> Phone: +41 58 934 70 63 >>>> Skype: christof-marti >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.org >>>> https://lists.fi-ware.org/listinfo/fiware-miwi >>>> >>> >>> >>> >>> -- >>> Jarkko Vatjus-Anttila >>> CTO >>> Cyberlightning Ltd. >>> >>> mobile. +358 405245142 >>> email. jarkko at cyberlightning.com >>> >>> See our new press release: >>> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ >>> >>> www.cyberlightning.com >>> >>> This e-mail and all attached material are confidential and may contain >>> legally privileged information. If you are not the intended recipient, >>> please contact the sender and delete the e-mail from your system without >>> producing, distributing or retaining copies thereof. >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.org >>> https://lists.fi-ware.org/listinfo/fiware-miwi >>> >>> >> > > > -- > Jarkko Vatjus-Anttila > CTO > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > See our new press release: > http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/ > > www.cyberlightning.com > > This e-mail and all attached material are confidential and may contain > legally privileged information. If you are not the intended recipient, > please contact the sender and delete the e-mail from your system without > producing, distributing or retaining copies thereof. > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: I10.2_Installation_and_Test_Template_v2_AugmentedReality.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 225103 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: I10.2_Installation_and_Test_Template_v2_RealVirtualInteraction.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 225571 bytes Desc: not available URL: From cvetan at adminotech.com Mon Jun 30 16:22:38 2014 From: cvetan at adminotech.com (Cvetan Stefanovski) Date: Mon, 30 Jun 2014 16:22:38 +0200 Subject: [Fiware-miwi] Epic naming. Splitting up Epics? In-Reply-To: References: <8CBE6A07-B320-4049-B28B-82750D2162A8@zhaw.ch> <7FE1F3D9-BF66-4949-BD70-5244D1240856@zhaw.ch> <59E04EE2-CF63-4651-8474-A8EFFB0E8F9B@zhaw.ch> <101d813ebdb147e0adafe644473df8ee@SRV-MAIL-001.zhaw.ch> <57e86926247d48809de1cc6554df0beb@SRV-MAIL-001.zhaw.ch> <8995889A-A268-4D63-84D4-3065B402BB33@zhaw.ch> Message-ID: Hello, I added Epic IDs on InterfaceDesigner and CloudRendering as: FIWARE.Epic.MiWi.CloudRendering.Main and FIWARE.Epic.MiWi.InterfaceDesigner.Basic and updated the links in the Materializing page. Best regards, On Fri, Jun 27, 2014 at 6:40 PM, Antti Kokko wrote: > Thank you! I'll make it 2 epics. ..InputAPI and ..WebComponent. > > - Antti > > > On Friday, June 27, 2014, Marti Christof (mach) wrote: > >> Hi Antti >> >> I can handle the tracker, and the roadmap/materializing pages, if you >> only update the wiki-pages. >> >> If you want to keep it in one epic then you only need to rename the >> epic. >> - Go to the page, select ?move? and modify the target name by extending >> it with the EpicId. >> >> If you want to split it, the easiest way would be to create two new >> wiki pages: >> - go to the page. open in edit mode. mark and copy the content to >> copy-buffer. >> - leave edit mode and modify the name of the page in the url to your new >> page name, the wiki will offer you to create the page, if it does not exist. >> - past the content into new page and modify it. >> - repeat the same for the second epic. >> >> Christof >> >> >> Am 27.06.2014 um 14:07 schrieb Antti Kokko : >> >> Hello, >> >> I need some detailed fast instructions. How to split the epic. Does I >> need to put e.g. 2 epics in the tracker and how/where to split those in the >> wiki? These maybe stupid questions but I need to get this done. I ?m >> leaving for a 1 month summer holiday within an hour. >> >> Thanks, >> >> - Antti >> >> >> On Fri, Jun 27, 2014 at 11:16 AM, Antti Kokko > > wrote: >> >>> Hi, >>> >>> Has anyone succeeded in splitting already? It will affect so many >>> places. >>> >>> Thanks, >>> >>> - Antti >>> >>> >>> On Fri, Jun 27, 2014 at 11:06 AM, Marti Christof (mach) >>> wrote: >>> >>>> Hi Antti, and all others having the same errors in the report. >>>> >>>> The first error is what we are discussing about splitting up the >>>> current epics into 2 or more smaller entries. >>>> The problem is, that an Epic name has to have the following schema: >>>> FIWARE.Epic.Chapter.Enabler[.EpicId]*.*EpicId* >>>> >>>> (Schema definitions are defined here: >>>> http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>>> ) >>>> >>>> For 2D-UI this means we need an Epic name like: >>>> FIWARE.Epic.MiWi.2D-UI.*X* >>>> *(where X is a reasonable name for the current Epic; I still look for a >>>> better name than ?Basic?, ?Basis?, ...)* >>>> >>>> or to split the content of the epic in two parts: >>>> FIWARE.Epic.MiWi.2D-UI.*X1* >>>> FIWARE.Epic.MiWi.2D-UI.*X2* >>>> *(where X1 contains a part of the current epic and X2 the remaining >>>> part of the current epic; X1 and X2 would be reasonable names for these >>>> functionalities)* >>>> >>>> In 3D-UI we would then have for example: >>>> FIWARE.Epic.MiWi.3D-UI.HTMLModelExtension (new: previous >>>> FIWARE.Epic.MiWi.3D-UI; Is there a better name?) >>>> FIWARE.Epic.MiWi.3D-UI.DataFlowProcessing >>>> FIWARE.Epic.MiWi.3D-UI.HW-Support >>>> >>>> Maybe there is a similar rename or split possible in 2D-UI (and all >>>> the other with this error) >>>> >>>> >>>> For the second error it is simply a referencing issue. >>>> - Any Epic and Feature can only be referenced in the Materializing >>>> page, if it is closed in the tracker. >>>> - If it is still open it should have a reference in the roadmap >>>> (features in the left column, epics in the right column) >>>> >>>> This is simple to fix, as soon the first (naming issue) is fixed. >>>> >>>> Best regards >>>> Christof >>>> >>>> >>>> Am 27.06.2014 um 09:32 schrieb Antti Kokko < >>>> antti.kokko at adminotech.com>: >>>> >>>> Hello, >>>> >>>> I need some guidance with these issues: >>>> FIWARE.Epic.MiWi.2D-UI (<- adjust reference to pattern) F >>>> IWARE.Epic.MiWi.2D-UI (<-- provide reference in roadmap; provide >>>> reference in tracker; remove reference from materializing;) >>>> What is the correct way of getting rid of these issues? There might >>>> have been already answers to these but seems pretty much every Ge still >>>> have the same issues. >>>> >>>> For 2D-UI Epic I reduced the word count and added the rationale. >>>> >>>> Thanks, >>>> >>>> - Antti >>>> >>>> >>>> >>>> On Thu, Jun 26, 2014 at 2:45 PM, Marti Christof (mach) >>>> wrote: >>>> >>>>> Hi Philipp, Hi all >>>>> >>>>> Epic- and Feature- descriptions are in the public wiki and are >>>>> referenced from the Materializing page as soon they are closed or on the >>>>> roadmap page as long they are worked on. >>>>> Renaming it in the Tracker is the minor part. >>>>> >>>>> The problem is, that without extending the name the backlog report >>>>> will show many errors, which will also be in a deliverable. Goal is to find >>>>> a consistent and good way to remove the errors without putting to much work >>>>> into it. >>>>> >>>>> To fulfill the naming rules we need to extend the Epic names, either >>>>> bei splitting large epics into two or by extending it with a generic term, >>>>> representing the whole epic. >>>>> >>>>> Here you find the links to all the epics available in the public wiki: >>>>> >>>>> https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php?title=Special%3APrefixIndex&from=FIWARE.Epic.MiWi.&namespace=0 >>>>> >>>>> >>>>> >>>>> @All: Please check the latest report ?All issues tab": >>>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>>> >>>>> There are some Epics which have to much words in the description (>250) >>>>> - 2D-UI >>>>> - 3D-UI >>>>> - 3D-UI.DataflowProcessing >>>>> - DisplayAsAService >>>>> >>>>> and all of the following are missing content in the Rational Field >>>>> (>=20 words): >>>>> - 2D-UI >>>>> - 3D-UI >>>>> - 3D-UI.DataflowProcessing >>>>> - 3D-UI.HW-Support >>>>> - AugmentedReality >>>>> - CloudRendering >>>>> - DisplayAsAService >>>>> - InterfaceDesigner >>>>> - Synchronization >>>>> - Synchronization.SceneAPI >>>>> - VirtualCharacters >>>>> >>>>> Would be nice if you can fix the content part also while looking into >>>>> the naming. >>>>> >>>>> Cheers >>>>> Christof >>>>> >>>>> >>>>> Am 26.06.2014 um 12:19 schrieb Philipp Slusallek < >>>>> philipp.slusallek at dfki.de>: >>>>> >>>>> > Hi, >>>>> > >>>>> > This is something that is only really visible internally, right? >>>>> > Externally people only care about the GE and its functionality. >>>>> > >>>>> > So please, lets do whatever minimizes the amount of work right now. >>>>> > Those names are really not very meaningful for most people. >>>>> > >>>>> > >>>>> > Best, >>>>> > >>>>> > Philipp >>>>> > >>>>> > >>>>> > Am 26.06.2014 11:26, schrieb Marti Christof (mach): >>>>> >> Dear WP13 GEi owners >>>>> >> >>>>> >> The problem with the naming of the epics is, that we need to add an >>>>> EpicId. >>>>> >> Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId >>>>> >> >>>>> >> At the moment many WP13-epics are only named after the GE itself. >>>>> e.g. >>>>> >> - FIWARE.Epic.MiWi.2D-UI >>>>> >> So we either need to add a generic EpicId (see below) or split up >>>>> the >>>>> >> Epics in multiple meaningful peaces. >>>>> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityX >>>>> >> - FIWARE.Epic.MiWi.2D-UI.FunctionalityY >>>>> >> Because some of the Epic Description are also to long (see report >>>>> ?All >>>>> >> issues?) and need to be shortened, this might be a good possiblity >>>>> to >>>>> >> fix these issues too. >>>>> >> >>>>> >> Please let me know ASAP [today before EOB] if and how it would be >>>>> >> possible to split your current GEs Epic. >>>>> >> >>>>> >> Best regards >>>>> >> Christof >>>>> >> >>>>> >> >>>>> >> >>>>> >> Anfang der weitergeleiteten Nachricht: >>>>> >> >>>>> >>> *Von: *"Marti Christof (mach)" >>>> >> >>>>> >>> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated >>>>> reviews* >>>>> >>> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >>>>> >>> *An: *MANUEL ESCRICHE VICENTE < >>>>> manuel.escrichevicente at telefonica.com >>>>> >>> > >>>>> >>> *Kopie: *MIGUEL CARRILLO PACHECO > >>>>> >>> >>>>> >>> Hi Manuel >>>>> >>> >>>>> >>> The problem is, that in OpenCall 2 more or less the WebUI GEs have >>>>> >>> been based on the defined Epics. So the epics where available >>>>> before >>>>> >>> the GEs. >>>>> >>> The problem did not show up before, because they were named >>>>> >>> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we >>>>> got >>>>> >>> the error there and had to rename them to the correct GE-names. >>>>> >>> >>>>> >>> I do not care to rename the Epics, but is there a rule or a schema >>>>> in >>>>> >>> other WPs how to extend the name in such a case? >>>>> >>> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >>>>> >>> or >>>>> >>> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >>>>> >>> or >>>>> >>> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >>>>> >>> or >>>>> >>> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >>>>> >>> or >>>>> >>> - ? >>>>> >>> >>>>> >>> We can schedule a call to discuss this. I am available from 13:00 >>>>> to >>>>> >>> 13:45 and then again from 16:00-... >>>>> >>> >>>>> >>> Best regards >>>>> >>> Christof >>>>> >>> >>>>> >>> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >>>>> >>> >>>> >>> >: >>>>> >>> >>>>> >>>> Hi Christof, >>>>> >>>> >>>>> >>>> Rules haven?t changed. >>>>> >>>> It doesn?t make sense to have an Epic named as the GEI. Epics are >>>>> >>>> organising items, it should add some organising value to the items >>>>> >>>> added below. >>>>> >>>> If you wish, we can do some research to the past to check how it >>>>> was >>>>> >>>> at some definite time. >>>>> >>>> Let me know and we schedule a meeting. >>>>> >>>> >>>>> >>>> Kind regards, >>>>> >>>> Manuel >>>>> >>>> >>>>> >>>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>>>> >>>> *Sent:*jueves, 26 de junio de 2014 10:24 >>>>> >>>> *To:*MANUEL ESCRICHE VICENTE >>>>> >>>> *Cc:*MIGUEL CARRILLO PACHECO >>>>> >>>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>>>> >>>> >>>>> >>>> Hi Manuel >>>>> >>>> >>>>> >>>> I am working on fixing the problems with the backlog. >>>>> >>>> One point I have problems to fix is the Epic naming error, because >>>>> >>>> you expect an EpicId at the end, but most of our Epics are >>>>> similar to >>>>> >>>> the GEs itself. So for the following GEs the Epics and the GE are >>>>> >>>> identical: >>>>> >>>> - FIWARE.Epic.MiWi.2D-UI >>>>> >>>> - FIWARE.Epic.MiWi.3D-UI >>>>> >>>> - FIWARE.Epic.MiWi.AugmentedReality >>>>> >>>> - FIWARE.Epic.MiWi.CloudRendering >>>>> >>>> - FIWARE.Epic.MiWi.DisplayAsAService >>>>> >>>> - FIWARE.Epic.MiWi.GISDataProvider >>>>> >>>> - FIWARE.Epic.MiWi.POIDataProvider >>>>> >>>> - FIWARE.Epic.MiWi.InterfaceDesigner >>>>> >>>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>>>> >>>> - FIWARE.Epic.MiWi.Synchronization >>>>> >>>> - FIWARE.Epic.MiWi.VirtualCharacters >>>>> >>>> >>>>> >>>> To accomplish the rules we would have to add some artificial >>>>> EpicId >>>>> >>>> like .Basic oder .BaseFunctionality >>>>> >>>> Is this really intended? >>>>> >>>> >>>>> >>>> I also wonder, why this errors did not show up earlier, when we >>>>> fixed >>>>> >>>> the last round of bugs. >>>>> >>>> >>>>> >>>> Best regards >>>>> >>>> Christof >>>>> >>>> >>>>> >>>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>>>> >>>> >>>> >>>> >: >>>>> >>>> >>>>> >>>> >>>>> >>>> Dear Partners, >>>>> >>>> >>>>> >>>> Please, find below updated reports. >>>>> >>>> >>>>> >>>> REVIEWS: >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>>>> >>>> >>>>> >>>> DASHBOARDS: >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>>>> >>>> >>>>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>>>> >>>> >>>>> >>>> If any support were required, please, don?t hesitate to let me >>>>> know. >>>>> >>>> >>>>> >>>> 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 y sus adjuntos se dirigen exclusivamente a su >>>>> >>>> destinatario, puede contener informaci?n privilegiada o >>>>> >>>> confidencial y es para uso exclusivo de la persona o entidad de >>>>> >>>> destino. Si no es usted. el destinatario indicado, queda >>>>> >>>> notificado de que la lectura, utilizaci?n, divulgaci?n y/o >>>>> copia >>>>> >>>> sin autorizaci?n puede estar prohibida en virtud de la >>>>> >>>> legislaci?n vigente. Si ha recibido este mensaje por error, le >>>>> >>>> rogamos que nos lo comunique inmediatamente por esta misma v?a >>>>> y >>>>> >>>> proceda a su destrucci?n. >>>>> >>>> >>>>> >>>> The information contained in this transmission is privileged >>>>> and >>>>> >>>> confidential information intended only for the use of the >>>>> >>>> individual or entity named above. If the reader of this message >>>>> >>>> is not the intended recipient, you are hereby notified that any >>>>> >>>> dissemination, distribution or copying of this communication is >>>>> >>>> strictly prohibited. If you have received this transmission in >>>>> >>>> error, do not read it. Please immediately reply to the sender >>>>> >>>> that you have received this communication in error and then >>>>> >>>> delete it. >>>>> >>>> >>>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>>> >>>> destinat?rio, pode conter informa??o privilegiada ou >>>>> confidencial >>>>> >>>> e ? para uso exclusivo da pessoa ou entidade de destino. Se >>>>> n?o ? >>>>> >>>> vossa senhoria o destinat?rio indicado, fica notificado de que >>>>> a >>>>> >>>> leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode >>>>> >>>> estar proibida em virtude da legisla??o vigente. Se recebeu >>>>> esta >>>>> >>>> mensagem por erro, rogamos-lhe que nos o comunique >>>>> imediatamente >>>>> >>>> por esta mesma via e proceda a sua destrui??o >>>>> >>>> _______________________________________________ >>>>> >>>> Fiware-ge-owners mailing list >>>>> >>>> Fiware-ge-owners at lists.fi-ware.org >>>>> >>>> >>>>> >>>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> ------------------------------------------------------------------------ >>>>> >>>> >>>>> >>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>>>> >>>> destinatario, puede contener informaci?n privilegiada o >>>>> confidencial >>>>> >>>> y es para uso exclusivo de la persona o entidad de destino. Si no >>>>> es >>>>> >>>> usted. el destinatario indicado, queda notificado de que la >>>>> lectura, >>>>> >>>> utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar >>>>> >>>> prohibida en virtud de la legislaci?n vigente. Si ha recibido este >>>>> >>>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>>>> por >>>>> >>>> esta misma v?a y proceda a su destrucci?n. >>>>> >>>> >>>>> >>>> The information contained in this transmission is privileged and >>>>> >>>> confidential information intended only for the use of the >>>>> individual >>>>> >>>> or entity named above. If the reader of this message is not the >>>>> >>>> intended recipient, you are hereby notified that any >>>>> dissemination, >>>>> >>>> distribution or copying of this communication is strictly >>>>> prohibited. >>>>> >>>> If you have received this transmission in error, do not read it. >>>>> >>>> Please immediately reply to the sender that you have received this >>>>> >>>> communication in error and then delete it. >>>>> >>>> >>>>> >>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>>>> >>>> destinat?rio, pode conter informa??o privilegiada ou confidencial >>>>> e ? >>>>> >>>> para uso exclusivo da pessoa ou entidade de destino. Se n?o ? >>>>> vossa >>>>> >>>> senhoria o destinat?rio indicado, fica notificado de que a >>>>> leitura, >>>>> >>>> utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar >>>>> proibida >>>>> >>>> em virtude da legisla??o vigente. Se recebeu esta mensagem por >>>>> erro, >>>>> >>>> rogamos-lhe que nos o comunique imediatamente por esta mesma via e >>>>> >>>> proceda a sua destrui??o >>>>> >>> >>>>> >> >>>>> >> >>>>> >> >>>>> >> _______________________________________________ >>>>> >> Fiware-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 >>>>> > >>>>> --------------------------------------------------------------------------- >>>>> > >>>>> >>>>> _______________________________________________ >>>>> Fiware-miwi mailing list >>>>> Fiware-miwi at lists.fi-ware.org >>>>> https://lists.fi-ware.org/listinfo/fiware-miwi >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Best regards, >>>> Antti Kokko >>>> Meshmoon developer at Adminotech Ltd. >>>> www.meshmoon.com >>>> >>>> >>>> >>> >>> >>> -- >>> >>> Best regards, >>> Antti Kokko >>> Meshmoon developer at Adminotech Ltd. >>> www.meshmoon.com >>> >> >> >> >> -- >> >> Best regards, >> Antti Kokko >> Meshmoon developer at Adminotech Ltd. >> www.meshmoon.com >> >> >> > > -- > > Best regards, > Antti Kokko > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > > _______________________________________________ > 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: