From Philipp.Slusallek at dfki.de Thu Jan 2 14:37:41 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Thu, 02 Jan 2014 14:37:41 +0100 Subject: [Fiware-miwi] SceneAPI features: original intent of the EPIC vs . current plans? In-Reply-To: <4CEA5C22-038C-46C2-B00E-1E6699866821@playsign.net> References: <1819400B-5329-414E-BCE8-F1C7890600DD@playsign.net> <4CEA5C22-038C-46C2-B00E-1E6699866821@playsign.net> Message-ID: <52C56BA5.5060502@dfki.de> Hi, All the best for the new year to all of you! I am just catching up on some email that got stuck in my inbox over a very busy end of the year. So do not be surprised to get responses on old email :-). Sorry for the long delays here. Regarding the SceneAPI. I believe that it is still very much worth looking into the original intention of the Epic and not tie it too much to the server (however, the server could implement the same interface as well). There are clearly some similarities to the synchronization protocol. But that it assumes that a server is in full control over the client (or at least parts of it) and knows what to do. With the SceneAPI it may also be a matter of finding out things about the target scene first before making changes. An AI service could for example find the location to go to before starting to move the character. This would not be possible with pure Synchronization. One obvious issue that Toni already talked about is the direction. Contacting a browser instance is not possible without a server as we know from Server-Based Rendering. But then we could design an interface that allows for querying and changing a scene. There is already is such a suggestion by Behr et, al (http://dl.acm.org/citation.cfm?id=1836057&CFID=394541370&CFTOKEN=82263824) that may be a good lpace to start. It based on HTTP/REST, though, which would not work for a connection towards the browser, so we should use WebRTC instead. Best, Philipp Am 21.11.2013 22:24, schrieb Toni Alatalo: > On 21 Nov 2013, at 10:54, Lasse ??rni wrote: >> If there is a good concrete plan to how it should be done instead it's not >> at all too late to change (as any implementation has not began), and if >> it's administratively OK, for example our architecture pictures now >> include the REST scene API described. > > I talked today with a guy who is working on the vw / visualization front in the university project with the traffic sensors in the city. > > We agreed preliminarily that could use their data and system as a use case for this SceneAPI biz on the fi-ware side ? if you and others here find it?s a good idea. > > Their data currently updates once per hour, though, so http would work :) > > But he had already proposed as a next step a visualisation where traffic is simulated / visualized as actual individual cars. We could have that simulation service as a user of the scene api / sync biz to control the cars so we?d get streaming nature for the data and much harder reqs for the usage (in the spirit of the EPIC). > > I still have to confirm with the prof whose leading that project that this all would be ok. We could do it so that the actual implementation of the visualization and even the integration comes from the uni and fi-ware (Ludocraft) only provides the API. I can use some of my university time for this as the integration of the city model and the traffic data is good to get there. > > This is not a must and I don?t mean to overcomplicate thing but just figured that a real use case would help to make the *concrete plan* that you called for above. > > The experience with the quick and simple POI & 3DUI integration (completed yesterday) was great, I?ll post about it tomorrow hopefully (the POI guys checked the demo today on ok?d it as this first minimal step). So I hope more integrations and usage of the GEs takes us well forward. > >> Lasse ??rni > > Cheers, > ~Toni > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Thu Jan 2 15:02:29 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Thu, 02 Jan 2014 15:02:29 +0100 Subject: [Fiware-miwi] EntSys: has Scene, integrates Networking & 3DUI + possibilities for XML3D In-Reply-To: References: Message-ID: <52C57175.3090805@dfki.de> Hi Toni, Nice work! The internal separation certainly makes a lot of sense. It would be great to add option (b) so that we can test a full XML3D-based connection to realXtend soon. Would be a great step forward for the integration. Great! Our sync server is getting into shape as well right now and already can move animated XML3D/Xflow characters around in a larger city model. Sergiy and Torsten are ironing out some performance issues right now and are working on a modified version of scalability approach, so we can separate and distribute larger worlds dynamically. There is still quite a bit of work that remains, though. Our KIARA work is also progressing nicely. There will be a first release coming now in January. This could be a basis for discussing if or how this may be a good basis for abstracting the networking layer behind a nice API. Best, Philipp Am 22.12.2013 10:25, schrieb Toni Alatalo: > About 3 weeks ago we presented a plan for an implementation of the > entity system and how it would integrate networking (Synch GE) and > rendering (3DUI GE). > > A key aspect in the design was to separate data and view parts of the EC > implementations ? unlike in any previous Tundra implementation, where > the scene internals and all EC implementations have been directly tied > to certain graphics renderer (Ogre or Three.js). The motivation here was > to support ?headless clients? or ?simulation servers? ? for example for > a Node.js server side service running some simulation or AI code to use > this library to connect to a Tundra server to manipulate the scene > (possibly what the SceneAPI Epic is after). Without ugly hacks like the > !headless checks in many parts of the C++ Tundra code. When the > renderer-dependent view code is a separate optional module the scene & > network parts can be used also without it but the programming model > (against the scene with the entities) is always the same. Consequently, > the proposal in this plan was to *not* use the DOM as the internal data > storage for the Scene ? simply because there is no (native) DOM > implementation available e.g. in the Node.js environment. The original > post with more explanations is > https://lists.fi-ware.eu/private/fiware-miwi/2013-November/000330.html > > No one objected, so we went with the plan and I?m very happy to tell > that the basics for it are implemented and work now. As planned in that > post, we (Ludocraft & Playsign so far) moved to work in a common > repository based on Lasse?s Synchronization GE work ? > WebTundraNetworking was renamed to WebTundra and we added a view/ > directory there: https://github.com/realXtend/WebTundra > > To see it in action you'll need a recent development build of Tundra > WebSocketServer plugin enabled. realXtend will make an official release > in January so it will become readily available then. And perhaps we can > run Tundra servers in FI-LAB at some point to be able to host web > services then. But if you build it yourself, it?s very easy to test with > the web-hosted test scene we provide: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/3DUI-WebTundra_-_Installation_and_Administration_Guide#Test_with_provided_web_hosting_for_scene_data > > To test the tech and verify and improve the application programming > model etc. we?ve ported the Pong example on top of Tundra (server-side > js) and WebTundra (browser client-side) ? more info about that later > separately, but if someone wants a pre-peek that work is in > https://github.com/playsign/PongThreeJS/tree/ec (includes server/ dir > for the Tundra scene). The Pong example is used also in the dev guide > docs in > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/3DUI-WebTundra_-_User_and_Programmers_Guide (to > be improved but has basics now). > > With this some things are clear: we already have a platform on which can > develop apps. But all FI-WARE goals are not delivered yet and there are > some options so I?ll describe the status briefly here: > > XML3D Support: in the F2F I promised we?ll do 3 things: 1. the entity > system integration (done as reported here now), 2. recommended asset > pipeline research & impl (on-going, now waiting for the updated three.js > glTF loader by mr. Parisi) and finally 3. a proposal how to proceed with > the rendering choice / alternatives. The current WebTundra > implementation gives two, I find quite nice, alternatives for XML3D support: > > a) add XML3D parsing to WebTundra so that it can read XML3D declarations > and populate the internal Scene correspondingly, hence resulting in a 3d > rendering when the view module is enabled. Erno actually implemented a > first version of this this week. It was made by changing the > pre-existing WebTundra TXML parser in Toni Dahl?s Chiru-WebClient to > read XML3D instead, this work is in > https://github.com/playsign/WebTundraNetworking/commits/sceneparser . I > find this approach has interesting upsides: is simple, and thanks to the > entity-system is transparent to the other parts ? for example the > networking works normally so that in fact this works as a way to > populate a Tundra server from XML3D (when the client reads xml3d and > creates the entities, they get replicated to the server too :) . Also > for XML3D standardization efforts it can be interesting that there is > another implementation of it. Obvious downsides are that it?s a small > incomplete subset of the spec (at least now) and it doesn?t use the > xml3d.js engine which has xflow support with hw acceleration coming etc. > > b) add XML3D.js view module to WebTundra. Now that the core scene and > ECs are renderer independent, it is easy and totally feasible to add a > xml3d.js renderer. The ThreeView is currently just one file with not an > awful lot of code ? same with XML3D.js would probably be as simple. This > is helped by Erno having applied the MVC pattern in the code so that > besides the data in the scene there are model and controller codes which > manage the state and observe data coming in from the net and track > Placeable and Mesh references and dependencies etc. so that the View is > told to display things when they are ready (instead of the view > requiring all that tracking in itself). So with the complexities in > Model & Controller parts, possibly already in a renderer agnostic way > (we didn?t check with this in mind), possibly not so much is left for > the potential alternative Views to handle. We currently need the > Three.js view in any case as e.g. Meshmoon has a lot of components & > rendering made with three so at least first the XML3D.js view would be > an alternative only. > > Another topic is the DOM integration. Current WebTundra has none. There > again I think there are two ways: > > 1. The previously discussed ?DOM as UI? idea where the internal Scene is > just mirrored to DOM (this is simple and Jonne already did it in > WebRocket). This might also be one way to implement xml3d.js view > support .. if we just populate the DOM it should show when xml3d.js is > active (but when using ThreeView the DOM population would be only for > developer purposes, to allow seeing the values in debugger etc). > > 2. Change the scene internals so that it would use the DOM directly. > Erno actually prototyped this before we decided to not require DOM in > the core to support the node.js case. I don?t know if the scene core > could somehow sensibly use the DOM when it?s there, but work without it > when it?s not (except ofc with the simply optional mirroring option of > 1.). Perhaps somehow doing what Philipp outlined at the F2F, put own JS > objects to the DOM nodes (so we could have the Attribute objects with > the type info that the net sync (& interface designer) require there). > > Anyhow, this is where we are now ? I?m very happy that the basics work > and we have a common base on which can work and where to integrate > things (e.g. 2D UI, Input, Interface Designer, possibly app specific > components from other GEs like POI & real-virtual interaction or GIS?) > and on which we can implement apps like the Pong example illustrates. > > The XML3D support and DOM integration we can have at least with the a) > and 1) options that have already been implemented. We are however open > to discuss alternatives and possible clever techniques to address those. > > Thanks to everyone for the efforts so far! Looking forward to tackling > the last remaining issues & packaging first releases after the holidays > then.. > ~Toni > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From toni at playsign.net Thu Jan 2 15:08:09 2014 From: toni at playsign.net (Toni Alatalo) Date: Thu, 2 Jan 2014 16:08:09 +0200 Subject: [Fiware-miwi] SceneAPI features: original intent of the EPIC vs . current plans? In-Reply-To: <52C56BA5.5060502@dfki.de> References: <1819400B-5329-414E-BCE8-F1C7890600DD@playsign.net> <4CEA5C22-038C-46C2-B00E-1E6699866821@playsign.net> <52C56BA5.5060502@dfki.de> Message-ID: <30DBA17F-975A-4754-8B1B-17CC82F1EA12@playsign.net> On 02 Jan 2014, at 15:37, Philipp Slusallek wrote: Hi again and thanks for the remarks, quick reply to one point again (before traveling with the kids in the evening, am away till Sunday then): > There are clearly some similarities to the synchronization protocol. But that it assumes that a server is in full control over the client (or at least parts of it) and knows what to do. With the SceneAPI it may also be a matter of finding out things about the target scene first before making changes. An AI service could for example find the location to go to before starting to move the character. This would not be possible with pure Synchronization. With the usage of Sync GE for connecting separate e.g. simulation or AI servers to the scene that would work. With the current WebTundra you could do this in a non-graphical AI instance, for example running as a node.js app: 1. use the library to connect to the scene server 2. use the WebTundra Scene API (in-memory JS) to examine the scene, for example to do pathfinding ? the whole scene data is replicated to this AI client so the object positions etc. all are there automatically (just the ec-data though, not assets, so it?s not that heavy) 3. move a character, either by modifying the position directly in the client (again using the scene api there) or by sending commands to the server I think what I?m saying in your terms is that the scene model and the client code in general in WebTundra is not pure synchronization (which is just the network messaging part) but, well, a client with scene replication. As mentioned before, with the Second Life protocol used with Opensimulator there?s the LibOMV (Open Metaverse) which gives the same for e.g. AI bots ? a headless client which connects to a server, gets the scene state automatically and provides it as an easy to use in-memory API that e.g. AI code can use to query and modify the scene. AFAIK people have been happy and productive with that. > One obvious issue that Toni already talked about is the direction. Contacting a browser instance is not possible without a server as we know from Server-Based Rendering. But then we could design an interface that allows for querying and changing a scene. Again the Sync GE does provide that, both in form of a WebSocket protocol and a JS client lib made on top of that ? you can query the scene and modify it. But I think is a good idea for us (Lasse perhaps but I?m probably too curious to skip it too :) to check that article to understand more of what you are after. Cheers, ~Toni > > There is already is such a suggestion by Behr et, al (http://dl.acm.org/citation.cfm?id=1836057&CFID=394541370&CFTOKEN=82263824) that may be a good lpace to start. It based on HTTP/REST, though, which would not work for a connection towards the browser, so we should use WebRTC instead. > > > Best, > > Philipp > > Am 21.11.2013 22:24, schrieb Toni Alatalo: >> On 21 Nov 2013, at 10:54, Lasse ??rni wrote: >>> If there is a good concrete plan to how it should be done instead it's not >>> at all too late to change (as any implementation has not began), and if >>> it's administratively OK, for example our architecture pictures now >>> include the REST scene API described. >> >> I talked today with a guy who is working on the vw / visualization front in the university project with the traffic sensors in the city. >> >> We agreed preliminarily that could use their data and system as a use case for this SceneAPI biz on the fi-ware side ? if you and others here find it?s a good idea. >> >> Their data currently updates once per hour, though, so http would work :) >> >> But he had already proposed as a next step a visualisation where traffic is simulated / visualized as actual individual cars. We could have that simulation service as a user of the scene api / sync biz to control the cars so we?d get streaming nature for the data and much harder reqs for the usage (in the spirit of the EPIC). >> >> I still have to confirm with the prof whose leading that project that this all would be ok. We could do it so that the actual implementation of the visualization and even the integration comes from the uni and fi-ware (Ludocraft) only provides the API. I can use some of my university time for this as the integration of the city model and the traffic data is good to get there. >> >> This is not a must and I don?t mean to overcomplicate thing but just figured that a real use case would help to make the *concrete plan* that you called for above. >> >> The experience with the quick and simple POI & 3DUI integration (completed yesterday) was great, I?ll post about it tomorrow hopefully (the POI guys checked the demo today on ok?d it as this first minimal step). So I hope more integrations and usage of the GEs takes us well forward. >> >>> Lasse ??rni >> >> Cheers, >> ~Toni >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Gesch?ftsf?hrung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > --------------------------------------------------------------------------- > From Philipp.Slusallek at dfki.de Thu Jan 2 15:30:16 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Thu, 02 Jan 2014 15:30:16 +0100 Subject: [Fiware-miwi] SceneAPI features: original intent of the EPIC vs . current plans? In-Reply-To: <30DBA17F-975A-4754-8B1B-17CC82F1EA12@playsign.net> References: <1819400B-5329-414E-BCE8-F1C7890600DD@playsign.net> <4CEA5C22-038C-46C2-B00E-1E6699866821@playsign.net> <52C56BA5.5060502@dfki.de> <30DBA17F-975A-4754-8B1B-17CC82F1EA12@playsign.net> Message-ID: <52C577F8.40206@dfki.de> Hi, Am 02.01.2014 15:08, schrieb Toni Alatalo: > 1. use the library to connect to the scene server > 2. use the WebTundra Scene API (in-memory JS) to examine the scene, for example to do pathfinding ? the whole scene data is replicated to this AI client so the object positions etc. all are there automatically (just the ec-data though, not assets, so it?s not that heavy) > 3. move a character, either by modifying the position directly in the client (again using the scene api there) or by sending commands to the server > > I think what I?m saying in your terms is that the scene model and the client code in general in WebTundra is not pure synchronization (which is just the network messaging part) but, well, a client with scene replication. > > As mentioned before, with the Second Life protocol used with Opensimulator there?s the LibOMV (Open Metaverse) which gives the same for e.g. AI bots ? a headless client which connects to a server, gets the scene state automatically and provides it as an easy to use in-memory API that e.g. AI code can use to query and modify the scene. AFAIK people have been happy and productive with that. But this is exactly what I would like NOT to do. Why should the simulation server have the full scene. This might be necessary in some cases, but there are many where it is not. But I agree that the SceneAPI may be something that is more tailored towards queries and isolated changes. One way to combine the two things could be to use the Scene API to set up selected synchronization to the simulation server for just the interesting aspects for cases where continuous updates are necessary. The simulation server could then decide to send back changes either through the sync channel (where appropriate) or the Scene API. >> One obvious issue that Toni already talked about is the direction. Contacting a browser instance is not possible without a server as we know from Server-Based Rendering. But then we could design an interface that allows for querying and changing a scene. > > Again the Sync GE does provide that, both in form of a WebSocket protocol and a JS client lib made on top of that ? you can query the scene and modify it. > > But I think is a good idea for us (Lasse perhaps but I?m probably too curious to skip it too :) to check that article to understand more of what you are after. But WebSocket is again a server-only transport mechanism (and it is what we are currently using as well). That may be fine for some cases but for others a P2P connection through Web RTC might be required if all we have are two Web applications. BTW, the paper used REST and this is quite limited connectionwise. Best, Philipp > Cheers, > ~Toni > >> >> There is already is such a suggestion by Behr et, al (http://dl.acm.org/citation.cfm?id=1836057&CFID=394541370&CFTOKEN=82263824) that may be a good lpace to start. It based on HTTP/REST, though, which would not work for a connection towards the browser, so we should use WebRTC instead. >> >> >> Best, >> >> Philipp >> >> Am 21.11.2013 22:24, schrieb Toni Alatalo: >>> On 21 Nov 2013, at 10:54, Lasse ??rni wrote: >>>> If there is a good concrete plan to how it should be done instead it's not >>>> at all too late to change (as any implementation has not began), and if >>>> it's administratively OK, for example our architecture pictures now >>>> include the REST scene API described. >>> >>> I talked today with a guy who is working on the vw / visualization front in the university project with the traffic sensors in the city. >>> >>> We agreed preliminarily that could use their data and system as a use case for this SceneAPI biz on the fi-ware side ? if you and others here find it?s a good idea. >>> >>> Their data currently updates once per hour, though, so http would work :) >>> >>> But he had already proposed as a next step a visualisation where traffic is simulated / visualized as actual individual cars. We could have that simulation service as a user of the scene api / sync biz to control the cars so we?d get streaming nature for the data and much harder reqs for the usage (in the spirit of the EPIC). >>> >>> I still have to confirm with the prof whose leading that project that this all would be ok. We could do it so that the actual implementation of the visualization and even the integration comes from the uni and fi-ware (Ludocraft) only provides the API. I can use some of my university time for this as the integration of the city model and the traffic data is good to get there. >>> >>> This is not a must and I don?t mean to overcomplicate thing but just figured that a real use case would help to make the *concrete plan* that you called for above. >>> >>> The experience with the quick and simple POI & 3DUI integration (completed yesterday) was great, I?ll post about it tomorrow hopefully (the POI guys checked the demo today on ok?d it as this first minimal step). So I hope more integrations and usage of the GEs takes us well forward. >>> >>>> Lasse ??rni >>> >>> Cheers, >>> ~Toni >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >> >> >> -- >> >> ------------------------------------------------------------------------- >> Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> >> Gesch?ftsf?hrung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 >> --------------------------------------------------------------------------- >> > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Tue Jan 7 07:44:32 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Tue, 07 Jan 2014 07:44:32 +0100 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Agile Dynamic: Release 3.3 and Sprint 3.3.1 Planning - deadline 10.Jan In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89158824@EX10-MB2-MAD.hi.inet> <52C6C1C0.8050006@dfki.de> Message-ID: <52CBA250.5060505@dfki.de> Hi, No, I had the same problem. There seems to be a technical problem and yesterday was a big holiday in Spain, so there was no one available. I guess it will be fixed today. Best, Philipp Am 07.01.2014 07:37, schrieb Jarkko Vatjus-Anttila: > The forge has been down for the past 4 days I've been trying to access. > Anyone else has luck in this matter? > > - jarkko > > > On Fri, Jan 3, 2014 at 3:57 PM, Philipp Slusallek > > wrote: > > Hi, > > More work :-(. It would be good if you can start putting together he > plans for the next release early next week. We can then discuss this > in the meeting. > > Christof, could you put together the infrastructure in the Wiki? > > Thanks, > > Philipp > > > -------- Original-Nachricht -------- > Betreff: [Fiware-wpa] Agile Dynamic: Release 3.3 and Sprint 3.3.1 > Planning - deadline 10.Jan > Datum: Fri, 03 Jan 2014 12:21:57 +0000 > Von: MANUEL ESCRICHE VICENTE > > An: fiware-ge-owners at lists.fi-__ware.eu > > > > Kopie (CC): fiware-wpl at lists.fi-ware.eu > >, > fiware-wpa at lists.fi-ware.eu > > > > > > Dear Partners, > > Find below the corresponding dashboards for due release and sprint > planning. > > Given the circumstances, I propose 10.January as deadline for the > release and sprint planning. > > Apps: Items: 70 = 23 Features, 10 User stories, 37 Work items, 0 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3275/__FIWARE.backlog.apps.dashboard.__20140103.xlsx > > > Cloud: Items: 21 = 11 Features, 7 User stories, 3 Work items, 0 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3276/__FIWARE.backlog.cloud.__dashboard.20140103.xlsx > > > IoT: Items: 36 = 29 Features, 5 User stories, 2 Work items, 0 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3279/__FIWARE.backlog.iot.dashboard.__20140103.xlsx > > > Data: Items: 53 = 27 Features, 13 User stories, 11 Work items, 2 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3277/__FIWARE.backlog.data.dashboard.__20140103.xlsx > > > I2ND: Items: 51 = 33 Features, 2 User stories, 16 Work items, 0 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3278/__FIWARE.backlog.i2nd.dashboard.__20140103.xlsx > > > Security: Items: 26 = 17 Features, 1 User stories, 8 Work items, 0 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3281/__FIWARE.backlog.security.__dashboard.20140103.xlsx > > > MiWi: Items: 33 = 33 Features, 0 User stories, 0 Work items, 0 Bugs > > https://forge.fi-ware.eu/__docman/view.php/27/3280/__FIWARE.backlog.miwi.dashboard.__20140103.xlsx > > > If anything, 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 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 > ------------------------------__------------------------------__--------------- > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > > > > -- > Jarkko Vatjus-Anttila > VP, Technology > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > Go to www.cybersli.de and enrich your > presentations! > > www.cyberlightning.com -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From jonne at adminotech.com Wed Jan 8 10:07:39 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Wed, 8 Jan 2014 11:07:39 +0200 Subject: [Fiware-miwi] doc reviews: did AR review, finished edits for 3DUI-WebTundra parts In-Reply-To: <05eace015f0ce182d242affae25ac305.squirrel@urho.ludocraft.com> References: <97934C0A-A431-4A43-93B2-4E889A2AF146@playsign.net> <4807D3BF-29BC-4696-B2CC-FF37A69A3407@playsign.net> <05eace015f0ce182d242affae25ac305.squirrel@urho.ludocraft.com> Message-ID: Yeah I've been on holidays until today. Still needs a review or? :P Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com On Mon, Dec 23, 2013 at 7:32 PM, "Lasse ??rni" wrote: > Hi, > it seems Jonne has not reviewed the Synchronization documents. If someone > wants to do a quick check I'd be glad. However note that I'm on holiday so > I won't have time for extensive edits but I can check the cockpit & email > late Wednesday / early Thursday. > > And of course, Merry Christmas to everyone! > > -- > Lasse ??rni > Game Programmer > LudoCraft Ltd. > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.jylkka at cyberlightning.com Thu Jan 9 09:53:31 2014 From: sami.jylkka at cyberlightning.com (Sami J) Date: Thu, 9 Jan 2014 10:53:31 +0200 Subject: [Fiware-miwi] FI-WARE testbed and creating blueprint Message-ID: Hi, has somebody successfully created blueprints for GE? I'm trying to create one for GIS GE, but haven't succeeded with that. When I'm creating blueprint template and adding tier to it, I can see only one available image: "chef-client".That's the only one and when selecting it and trying to launch blueprint server gives after trying to deploy it "ERROR" message. I can't see any logs anywhere. In the testbed Images section there is plenty of images, however I'm not able to launch images neither from there. I haven't tried every image, but at least Ubuntu images fails to launch. So if somebody has succesfully created blueprint for GE and also successfully launched new instance in testbed, I'd be happy to get some guidance how I could reach that :) Cheers, Sami -- Sami Jylkk? Software Designer Cyberlightning Ltd. Go to www.cybersli.de and enrich your presentations! 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 Philipp.Slusallek at dfki.de Thu Jan 9 23:47:04 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Thu, 09 Jan 2014 23:47:04 +0100 Subject: [Fiware-miwi] FI-WARE testbed and creating blueprint In-Reply-To: References: Message-ID: <52CF26E8.4070006@dfki.de> Hi, It may be related to the outage they had. Please report it to fi-lab. AT least launching an unmodified image should work :-). Best, Philipp Am 09.01.2014 09:53, schrieb Sami J: > Hi, > has somebody successfully created blueprints for GE? > I'm trying to create one for GIS GE, but haven't succeeded with that. > When I'm creating blueprint template and adding tier to it, I can see > only one available image: "chef-client".That's the only one and when > selecting it and trying to launch blueprint server gives after trying to > deploy it "ERROR" message. I can't see any logs anywhere. > > In the testbed Images section there is plenty of images, however I'm not > able to launch images neither from there. I haven't tried every image, > but at least Ubuntu images fails to launch. > > So if somebody has succesfully created blueprint for GE and also > successfully launched new instance in testbed, I'd be happy to get some > guidance how I could reach that :) > > Cheers, > Sami > > -- > Sami Jylkk? > Software Designer > Cyberlightning Ltd. > > Go to www.cybersli.de and enrich your > presentations! > > 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.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From tomi.sarni at cyberlightning.com Fri Jan 10 07:15:22 2014 From: tomi.sarni at cyberlightning.com (Tomi Sarni) Date: Fri, 10 Jan 2014 08:15:22 +0200 Subject: [Fiware-miwi] FI-WARE testbed and creating blueprint In-Reply-To: <52CF26E8.4070006@dfki.de> References: <52CF26E8.4070006@dfki.de> Message-ID: I was also not able to start any images. On Fri, Jan 10, 2014 at 12:47 AM, Philipp Slusallek < Philipp.Slusallek at dfki.de> wrote: > Hi, > > It may be related to the outage they had. Please report it to fi-lab. AT > least launching an unmodified image should work :-). > > > Best, > > Philipp > > Am 09.01.2014 09:53, schrieb Sami J: > >> Hi, >> has somebody successfully created blueprints for GE? >> I'm trying to create one for GIS GE, but haven't succeeded with that. >> When I'm creating blueprint template and adding tier to it, I can see >> only one available image: "chef-client".That's the only one and when >> selecting it and trying to launch blueprint server gives after trying to >> deploy it "ERROR" message. I can't see any logs anywhere. >> >> In the testbed Images section there is plenty of images, however I'm not >> able to launch images neither from there. I haven't tried every image, >> but at least Ubuntu images fails to launch. >> >> So if somebody has succesfully created blueprint for GE and also >> successfully launched new instance in testbed, I'd be happy to get some >> guidance how I could reach that :) >> >> Cheers, >> Sami >> >> -- >> Sami Jylkk? >> Software Designer >> Cyberlightning Ltd. >> >> Go to www.cybersli.de and enrich your >> presentations! >> >> 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Gesch?ftsf?hrung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > ------------------------------------------------------------ > --------------- > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > -- Tomi Sarni Software Engineer Cyberlightning Ltd. email. tomi.sarni at cyberlightning.com Go to www.cybersli.de and enrich your presentations! 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 sami.jylkka at cyberlightning.com Fri Jan 10 09:00:10 2014 From: sami.jylkka at cyberlightning.com (Sami J) Date: Fri, 10 Jan 2014 10:00:10 +0200 Subject: [Fiware-miwi] FI-WARE testbed and creating blueprint In-Reply-To: References: <52CF26E8.4070006@dfki.de> Message-ID: Thanks Philipp, still no luck when trying to launch unmodified image. Problem might be related to recent outage, I'll contact to helpdesk with this matter. Cheers, Sami On Fri, Jan 10, 2014 at 8:15 AM, Tomi Sarni wrote: > I was also not able to start any images. > > > On Fri, Jan 10, 2014 at 12:47 AM, Philipp Slusallek < > Philipp.Slusallek at dfki.de> wrote: > >> Hi, >> >> It may be related to the outage they had. Please report it to fi-lab. AT >> least launching an unmodified image should work :-). >> >> >> Best, >> >> Philipp >> >> Am 09.01.2014 09:53, schrieb Sami J: >> >>> Hi, >>> has somebody successfully created blueprints for GE? >>> I'm trying to create one for GIS GE, but haven't succeeded with that. >>> When I'm creating blueprint template and adding tier to it, I can see >>> only one available image: "chef-client".That's the only one and when >>> selecting it and trying to launch blueprint server gives after trying to >>> deploy it "ERROR" message. I can't see any logs anywhere. >>> >>> In the testbed Images section there is plenty of images, however I'm not >>> able to launch images neither from there. I haven't tried every image, >>> but at least Ubuntu images fails to launch. >>> >>> So if somebody has succesfully created blueprint for GE and also >>> successfully launched new instance in testbed, I'd be happy to get some >>> guidance how I could reach that :) >>> >>> Cheers, >>> Sami >>> >>> -- >>> Sami Jylkk? >>> Software Designer >>> Cyberlightning Ltd. >>> >>> Go to www.cybersli.de and enrich your >>> presentations! >>> >>> 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.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> >> >> -- >> >> ------------------------------------------------------------------------- >> Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> >> Gesch?ftsf?hrung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 >> ------------------------------------------------------------ >> --------------- >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> > > > -- > > Tomi Sarni > Software Engineer > Cyberlightning Ltd. > > email. tomi.sarni at cyberlightning.com > > > Go to www.cybersli.de > > and enrich your presentations! > > 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. > -- Sami Jylkk? Software Designer Cyberlightning Ltd. Go to www.cybersli.de and enrich your presentations! 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 jonne at adminotech.com Fri Jan 10 12:47:16 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Fri, 10 Jan 2014 13:47:16 +0200 Subject: [Fiware-miwi] Synchonization review done Message-ID: Sorry, I was so late on this, as said had a bit extra winter holiday and now forge was down when I got to work. On the bright side I don't have very many notes for Lasse (as I expected). I've marked all of the pages as "ok" to go forward. Lasse can do tweaks if he wishes as per my info when he has time before the january release. https://docs.google.com/a/adminotech.com/document/d/1wThuPpSHsWkLihEnho14J7JvIoa7wE5H9XkqDPYd2z4 Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Philipp.Slusallek at dfki.de Fri Jan 10 13:04:07 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Fri, 10 Jan 2014 13:04:07 +0100 Subject: [Fiware-miwi] Synchonization review done In-Reply-To: References: Message-ID: <52CFE1B7.3080906@dfki.de> Thanks, Philipp Am 10.01.2014 12:47, schrieb Jonne Nauha: > Sorry, I was so late on this, as said had a bit extra winter holiday and > now forge was down when I got to work. > > On the bright side I don't have very many notes for Lasse (as I > expected). I've marked all of the pages as "ok" to go forward. Lasse can > do tweaks if he wishes as per my info when he has time before the > january release. > > https://docs.google.com/a/adminotech.com/document/d/1wThuPpSHsWkLihEnho14J7JvIoa7wE5H9XkqDPYd2z4 > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From torsten.spieldenner at dfki.de Fri Jan 10 13:42:27 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Fri, 10 Jan 2014 13:42:27 +0100 Subject: [Fiware-miwi] Review for 2D UI done Message-ID: <52CFEAB3.3050701@dfki.de> Hello, I've finished the review of the revised version of 2D UI documentation and now marked all 3 documents as OK Best, Torsten From mcp at tid.es Fri Jan 10 17:50:00 2014 From: mcp at tid.es (Miguel Carrillo) Date: Fri, 10 Jan 2014 17:50:00 +0100 Subject: [Fiware-miwi] FI-WARE testbed and creating blueprint In-Reply-To: References: <52CF26E8.4070006@dfki.de> Message-ID: <52D024B8.4080609@tid.es> Dear all, Just to clarify. FI-LAB is a different datacentre and has nothing to do with the servers that host the forge. It is unrelated to the computing outage. I see that Sami already contacted the support team. Best regards, Miguel El 10/01/2014 9:00, Sami J escribi?: Thanks Philipp, still no luck when trying to launch unmodified image. Problem might be related to recent outage, I'll contact to helpdesk with this matter. Cheers, Sami On Fri, Jan 10, 2014 at 8:15 AM, Tomi Sarni > wrote: I was also not able to start any images. On Fri, Jan 10, 2014 at 12:47 AM, Philipp Slusallek > wrote: Hi, It may be related to the outage they had. Please report it to fi-lab. AT least launching an unmodified image should work :-). Best, Philipp Am 09.01.2014 09:53, schrieb Sami J: Hi, has somebody successfully created blueprints for GE? I'm trying to create one for GIS GE, but haven't succeeded with that. When I'm creating blueprint template and adding tier to it, I can see only one available image: "chef-client".That's the only one and when selecting it and trying to launch blueprint server gives after trying to deploy it "ERROR" message. I can't see any logs anywhere. In the testbed Images section there is plenty of images, however I'm not able to launch images neither from there. I haven't tried every image, but at least Ubuntu images fails to launch. So if somebody has succesfully created blueprint for GE and also successfully launched new instance in testbed, I'd be happy to get some guidance how I could reach that :) Cheers, Sami -- Sami Jylkk? Software Designer Cyberlightning Ltd. Go to www.cybersli.de and enrich your presentations! 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.eu https://lists.fi-ware.eu/listinfo/fiware-miwi -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.eu https://lists.fi-ware.eu/listinfo/fiware-miwi -- Tomi Sarni Software Engineer Cyberlightning Ltd. email. tomi.sarni at cyberlightning.com Go to www.cybersli.de and enrich your presentations! 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. -- Sami Jylkk? Software Designer Cyberlightning Ltd. Go to www.cybersli.de and enrich your presentations! 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.eu https://lists.fi-ware.eu/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.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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni.alatalo at gmail.com Mon Jan 13 13:13:02 2014 From: toni.alatalo at gmail.com (Toni Alatalo) Date: Mon, 13 Jan 2014 14:13:02 +0200 Subject: [Fiware-miwi] =?iso-8859-1?q?Oulu-MIWI_meet_at_M=E4kelininkatu=2C?= =?iso-8859-1?q?_at_13_tomorrow=3F_=28Fwd=3A__Oulu_FI-WARE_gettogether_is_?= =?iso-8859-1?q?on_Tuesday_13=3A00=29?= References: <20130925134254.GM62563@ee.oulu.fi> Message-ID: <3DEE2C00-AFF8-47FA-A68C-76BF5F42266F@gmail.com> tomorrow Tue ok 13:00 for folks? a basic status + plans check. we can demo multipong on tundra & webtundra, and everyone what they want :) M?kelininkatu 15 fi-ware space. ~Toni Begin forwarded message: > From: Erno Kuusela > Subject: [Fiware-miwi] Oulu FI-WARE gettogether is on Tuesday 13:00 > Date: 25 Sep 2013 16:42:54 GMT+3 > To: Fiware-miwi , Kari Autio > > Hello, > > The doodle has spoken, let's make it Tuesday 13:00. > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Wed Jan 15 07:32:11 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 15 Jan 2014 08:32:11 +0200 Subject: [Fiware-miwi] SceneAPI features: original intent of the EPIC vs . current plans? In-Reply-To: <20140103071307.AC5881E8840@dionysos.netplaza.fi> References: <1819400B-5329-414E-BCE8-F1C7890600DD@playsign.net> <4CEA5C22-038C-46C2-B00E-1E6699866821@playsign.net> <52C56BA5.5060502@dfki.de> <30DBA17F-975A-4754-8B1B-17CC82F1EA12@playsign.net> <52C577F8.40206@dfki.de> <20140103071307.AC5881E8840@dionysos.netplaza.fi> Message-ID: a brief note about this, Jonne noted in the meet yesterday when this was discussed a little: we already can do selective sync ? exactly due to existing IM things in Tundra. there?s no protocol for it but apps can do it with app level logic: for example a server side script that the client can command to configure the collection of entities of interest for that client. so the mechanisms for simulation servers to participate in scenes is there, just not tested that way yet (no demo / use case). thanks to Lasse?s recent (this & last week or so) refactoring in Tundra the kNet and WebSocket sync things are now integrated so that the same IM mechanisms work for WS connections too. however http interfacing can easily be useful too so might be a good idea to implement the original SceneAPI plan, for different cases than realtime sync. that does not help the browser-browser p2p case though that Philipp has also brought up. ~Toni On 03 Jan 2014, at 08:46, toni at playsign.net wrote: > Yes I agree that a selective form of how the sync / client works by default might be good for e.g. AI or simulation nodes. But that is basically just an optimization which does not change the architecture fundamentally. That is, if there?s a use case for that kind of SceneAPI (like the traffic data visualization I discussed with Uni Oulu folks), we could just implement it right away on top of what we have now. > > Support for selective Sync is required anyhow for scalability, for large / with-much-constant-changes scenes and for large numbers of users. We have a few such Interest Management strategies, and support for IM in general, implemented in Tundra by CIE/Chiru a while back. I think improving that is in Ludocraft?s fi-ware plans. > > In those usages it is typically the server which decides what updates are of interest for a certain client, utilizing info that the client has sent (in Chiru?s Tundra thing the client sends the active camera view info for the server to use -- Second Life does the same I think). > > For these headless server-clients, we should support the client subscribing explicitly to certain changes -- either changes to certain objects, or perhaps changes of certain type to any object in the scene. That should be easy to add when the support for IM in general is well in place. Perhaps a good use case to be kept in mind when working on IM. The Verse protocol, made many years ago for live sync of changes between 3d authoring apps for realtime collaboration, works like that: after connecting, clients subscribe to the kind of changes they want to get from the scene (quite normal pub-sub style). > > For isolated queries and changes HTTP is fine, that would be implemented by the current SceneAPI plan, and is simple. Just is not suitable for more realtime simulation visualisations for which the Websocket impl from Sync GE is better. > > WebRTC is certainly cool for direct browser-to-browser comms, works well for us in the original browser-code-only n-player Pong implementation (which was later ported to Tundra + WebTundra too). One limitation there is that support had been in Chrome only, I don?t know how that situation has developed. Lasse mentions WebRTC as a possible alternative transport in the continuation plans for Sync (in the FI-CORE proposal). I think it is totally feasible to allow peer-to-peer sync with the generic scene replication messages over WebRTC. > > ~Toni > > Sent from Windows Mail > > From: Philipp Slusallek > Sent: ?Thursday?, ?January? ?2?, ?2014 ?4?:?30? ?PM > To: Toni Alatalo > Cc: FI-WARE, MiWi > > Hi, > > Am 02.01.2014 15:08, schrieb Toni Alatalo: > > 1. use the library to connect to the scene server > > 2. use the WebTundra Scene API (in-memory JS) to examine the scene, for example to do pathfinding ? the whole scene data is replicated to this AI client so the object positions etc. all are there automatically (just the ec-data though, not assets, so it?s not that heavy) > > 3. move a character, either by modifying the position directly in the client (again using the scene api there) or by sending commands to the server > > > > I think what I?m saying in your terms is that the scene model and the client code in general in WebTundra is not pure synchronization (which is just the network messaging part) but, well, a client with scene replication. > > > > As mentioned before, with the Second Life protocol used with Opensimulator there?s the LibOMV (Open Metaverse) which gives the same for e.g. AI bots ? a headless client which connects to a server, gets the scene state automatically and provides it as an easy to use in-memory API that e.g. AI code can use to query and modify the scene. AFAIK people have been happy and productive with that. > > But this is exactly what I would like NOT to do. Why should the > simulation server have the full scene. This might be necessary in some > cases, but there are many where it is not. > > But I agree that the SceneAPI may be something that is more tailored > towards queries and isolated changes. One way to combine the two things > could be to use the Scene API to set up selected synchronization to the > simulation server for just the interesting aspects for cases where > continuous updates are necessary. The simulation server could then > decide to send back changes either through the sync channel (where > appropriate) or the Scene API. > > >> One obvious issue that Toni already talked about is the direction. Contacting a browser instance is not possible without a server as we know from Server-Based Rendering. But then we could design an interface that allows for querying and changing a scene. > > > > Again the Sync GE does provide that, both in form of a WebSocket protocol and a JS client lib made on top of that ? you can query the scene and modify it. > > > > But I think is a good idea for us (Lasse perhaps but I?m probably too curious to skip it too :) to check that article to understand more of what you are after. > > But WebSocket is again a server-only transport mechanism (and it is what > we are currently using as well). That may be fine for some cases but for > others a P2P connection through Web RTC might be required if all we have > are two Web applications. > > BTW, the paper used REST and this is quite limited connectionwise. > > > Best, > > Philipp > > Cheers, > > ~Toni > > > >> > >> There is already is such a suggestion by Behr et, al (http://dl.acm.org/citation.cfm?id=1836057&CFID=394541370&CFTOKEN=82263824) that may be a good lpace to start. It based on HTTP/REST, though, which would not work for a connection towards the browser, so we should use WebRTC instead. > >> > >> > >> Best, > >> > >> Philipp > >> > >> Am 21.11.2013 22:24, schrieb Toni Alatalo: > >>> On 21 Nov 2013, at 10:54, Lasse ??rni wrote: > >>>> If there is a good concrete plan to how it should be done instead it's not > >>>> at all too late to change (as any implementation has not began), and if > >>>> it's administratively OK, for example our architecture pictures now > >>>> include the REST scene API described. > >>> > >>> I talked today with a guy who is working on the vw / visualization front in the university project with the traffic sensors in the city. > >>> > >>> We agreed preliminarily that could use their data and system as a use case for this SceneAPI biz on the fi-ware side ? if you and others here find it?s a good idea. > >>> > >>> Their data currently updates once per hour, though, so http would work :) > >>> > >>> But he had already proposed as a next step a visualisation where traffic is simulated / visualized as actual individual cars. We could have that simulation service as a user of the scene api / sync biz to control the cars so we?d get streaming nature for the data and much harder reqs for the usage (in the spirit of the EPIC). > >>> > >>> I still have to confirm with the prof whose leading that project that this all would be ok. We could do it so that the actual implementation of the visualization and even the integration comes from the uni and fi-ware (Ludocraft) only provides the API. I can use some of my university time for this as the integration of the city model and the traffic data is good to get there. > >>> > >>> This is not a must and I don?t mean to overcomplicate thing but just figured that a real use case would help to make the *concrete plan* that you called for above. > >>> > >>> The experience with the quick and simple POI & 3DUI integration (completed yesterday) was great, I?ll post about it tomorrow hopefully (the POI guys checked the demo today on ok?d it as this first minimal step). So I hope more integrations and usage of the GEs takes us well forward. > >>> > >>>> Lasse ??rni > >>> > >>> Cheers, > >>> ~Toni > >>> > >>> _______________________________________________ > >>> Fiware-miwi mailing list > >>> Fiware-miwi at lists.fi-ware.eu > >>> https://lists.fi-ware.eu/listinfo/fiware-miwi > >>> > >> > >> > >> -- > >> > >> ------------------------------------------------------------------------- > >> Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH > >> Trippstadter Strasse 122, D-67663 Kaiserslautern > >> > >> Gesch?ftsf?hrung: > >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > >> Dr. Walter Olthoff > >> Vorsitzender des Aufsichtsrats: > >> Prof. Dr. h.c. Hans A. Aukes > >> > >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > >> --------------------------------------------------------------------------- > >> > > > > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Gesch?ftsf?hrung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > --------------------------------------------------------------------------- > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Wed Jan 15 07:44:44 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 15 Jan 2014 08:44:44 +0200 Subject: [Fiware-miwi] thu 13: meet about webtundra dom-integration & xml3d net sync vs. tundra components Message-ID: <1EC7D4CD-B87D-4C23-A9AB-CAAD5E97249D@playsign.net> Another note from yesterday: we decided to have a little meet / working session about the DOM integration and xml3d etc. in the WebTundra context. Lasse has Sync.DomIntegration as a feature tracker entry in the fi-ware forge, and as evident for many posts here we?ve worked on it a lot from the 3DUI perspective at Playsign. One topic is net sync of full xml3d, xflow, and perhaps arbitrary DOM elements. Basic 3d things like transforms and meshes we can (and already do, in Erno?s xml3d reader) map between xml3d xml elements and Tundra components. For xml elements for which there is no existing nor need for a Tundra component, an option is just to use DynamicComponent?s where use the name feature to have the XML element name (for example for Xflow and elements). But is that the best idea or would something else be better? Hierarchy is coming per Lasse?s plan to add normal xml-style hierarchy to Tundra. Idea is mostly for us (me & Erno) and Lasse to plan next steps in the work but anyone interested can participate, Jarkko said that Cyberlightning folks working on xml3djs & xflow may join in, and Jonne or someone from Admino may come too. We can discuss it in the weekly today as well, or set it so that DFKI folks can participate remotely tomorrow if it seems like a good idea. If DFKI Fives already does e.g. full sync of xml3d (and xhtml?) using a similar entity-component model, or if there?s designs for that etc., those would be obviously good to check too ? pointers are welcome. Cheers, ~Toni From Philipp.Slusallek at dfki.de Wed Jan 15 08:01:23 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 15 Jan 2014 08:01:23 +0100 Subject: [Fiware-miwi] thu 13: meet about webtundra dom-integration & xml3d net sync vs. tundra components In-Reply-To: <1EC7D4CD-B87D-4C23-A9AB-CAAD5E97249D@playsign.net> References: <1EC7D4CD-B87D-4C23-A9AB-CAAD5E97249D@playsign.net> Message-ID: <52D63243.5080603@dfki.de> Hi Toni, all, Its great to hear that you are making good progress here. And its a good idea to talk about that today. Yes, we have a sync server, a simple KIARA-based API and JSON protocol, as well as mapping to the XML3D scene, movement and animation of characters implemented and roughly working. The KIARA layer in our C#-based sync server and the JS layer in the browser are still primitive and hard coded but we are making very good progress on the C/C++ KIARA implementation (Advanced Middleware GE). An initial Version will be published by the end of the month. Its not yet connected to the C#/JS-Version but we are currently looking into that. I am currently preparing a presentation on KIARA that I can share in about two weeks. Torsten, maybe you can send pointers to the code and a video or so? I will take care of setting up the call today. Christof seems to still be ill but (according to his colleagues last Friday) it is no too serious. Get well soon again, Christof!! Best, Philipp Am 15.01.2014 07:44, schrieb Toni Alatalo: > Another note from yesterday: we decided to have a little meet / working session about the DOM integration and xml3d etc. in the WebTundra context. > > Lasse has Sync.DomIntegration as a feature tracker entry in the fi-ware forge, and as evident for many posts here we?ve worked on it a lot from the 3DUI perspective at Playsign. > > One topic is net sync of full xml3d, xflow, and perhaps arbitrary DOM elements. Basic 3d things like transforms and meshes we can (and already do, in Erno?s xml3d reader) map between xml3d xml elements and Tundra components. For xml elements for which there is no existing nor need for a Tundra component, an option is just to use DynamicComponent?s where use the name feature to have the XML element name (for example for Xflow and elements). But is that the best idea or would something else be better? Hierarchy is coming per Lasse?s plan to add normal xml-style hierarchy to Tundra. > > Idea is mostly for us (me & Erno) and Lasse to plan next steps in the work but anyone interested can participate, Jarkko said that Cyberlightning folks working on xml3djs & xflow may join in, and Jonne or someone from Admino may come too. We can discuss it in the weekly today as well, or set it so that DFKI folks can participate remotely tomorrow if it seems like a good idea. > > If DFKI Fives already does e.g. full sync of xml3d (and xhtml?) using a similar entity-component model, or if there?s designs for that etc., those would be obviously good to check too ? pointers are welcome. > > Cheers, > ~Toni > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Wed Jan 15 08:04:28 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 15 Jan 2014 08:04:28 +0100 Subject: [Fiware-miwi] SceneAPI features: original intent of the EPIC vs . current plans? In-Reply-To: References: <1819400B-5329-414E-BCE8-F1C7890600DD@playsign.net> <4CEA5C22-038C-46C2-B00E-1E6699866821@playsign.net> <52C56BA5.5060502@dfki.de> <30DBA17F-975A-4754-8B1B-17CC82F1EA12@playsign.net> <52C577F8.40206@dfki.de> <20140103071307.AC5881E8840@dionysos.netplaza.fi> Message-ID: <52D632FC.7090705@dfki.de> Hi, Lets discuss this today as well. Best, Philipp Am 15.01.2014 07:32, schrieb Toni Alatalo: > a brief note about this, Jonne noted in the meet yesterday when this was > discussed a little: > > we already can do selective sync ? exactly due to existing IM things in > Tundra. there?s no protocol for it but apps can do it with app level > logic: for example a server side script that the client can command to > configure the collection of entities of interest for that client. so the > mechanisms for simulation servers to participate in scenes is there, > just not tested that way yet (no demo / use case). thanks to Lasse?s > recent (this & last week or so) refactoring in Tundra the kNet and > WebSocket sync things are now integrated so that the same IM mechanisms > work for WS connections too. > > however http interfacing can easily be useful too so might be a good > idea to implement the original SceneAPI plan, for different cases than > realtime sync. > > that does not help the browser-browser p2p case though that Philipp has > also brought up. > > ~Toni > > On 03 Jan 2014, at 08:46, toni at playsign.net > wrote: > >> Yes I agree that a selective form of how the sync / client works by >> default might be good for e.g. AI or simulation nodes. But that is >> basically just an optimization which does not change the architecture >> fundamentally. That is, if there?s a use case for that kind of >> SceneAPI (like the traffic data visualization I discussed with Uni >> Oulu folks), we could just implement it right away on top of what we >> have now. >> >> Support for selective Sync is required anyhow for scalability, for >> large / with-much-constant-changes scenes and for large numbers of >> users. We have a few such Interest Management strategies, and support >> for IM in general, implemented in Tundra by CIE/Chiru a while back. I >> think improving that is in Ludocraft?s fi-ware plans. >> >> In those usages it is typically the server which decides what updates >> are of interest for a certain client, utilizing info that the client >> has sent (in Chiru?s Tundra thing the client sends the active camera >> view info for the server to use -- Second Life does the same I think). >> >> For these headless server-clients, we should support the client >> subscribing explicitly to certain changes -- either changes to certain >> objects, or perhaps changes of certain type to any object in the >> scene. That should be easy to add when the support for IM in general >> is well in place. Perhaps a good use case to be kept in mind when >> working on IM. The Verse protocol, made many years ago for live sync >> of changes between 3d authoring apps for realtime collaboration, works >> like that: after connecting, clients subscribe to the kind of changes >> they want to get from the scene (quite normal pub-sub style). >> >> For isolated queries and changes HTTP is fine, that would be >> implemented by the current SceneAPI plan, and is simple. Just is not >> suitable for more realtime simulation visualisations for which the >> Websocket impl from Sync GE is better. >> >> WebRTC is certainly cool for direct browser-to-browser comms, works >> well for us in the original browser-code-only n-player Pong >> implementation (which was later ported to Tundra + WebTundra too). One >> limitation there is that support had been in Chrome only, I don?t know >> how that situation has developed. Lasse mentions WebRTC as a possible >> alternative transport in the continuation plans for Sync (in the >> FI-CORE proposal). I think it is totally feasible to allow >> peer-to-peer sync with the generic scene replication messages over WebRTC. >> >> ~Toni >> >> Sent from Windows Mail >> >> *From:* Philipp Slusallek >> *Sent:* ?Thursday?, ?January? ?2?, ?2014 ?4?:?30? ?PM >> *To:* Toni Alatalo >> *Cc:* FI-WARE, MiWi >> >> Hi, >> >> Am 02.01.2014 15:08, schrieb Toni Alatalo: >> > 1. use the library to connect to the scene server >> > 2. use the WebTundra Scene API (in-memory JS) to examine the scene, >> for example to do pathfinding ? the whole scene data is replicated to >> this AI client so the object positions etc. all are there >> automatically (just the ec-data though, not assets, so it?s not that >> heavy) >> > 3. move a character, either by modifying the position directly in >> the client (again using the scene api there) or by sending commands to >> the server >> > >> > I think what I?m saying in your terms is that the scene model and >> the client code in general in WebTundra is not pure synchronization >> (which is just the network messaging part) but, well, a client with >> scene replication. >> > >> > As mentioned before, with the Second Life protocol used with >> Opensimulator there?s the LibOMV (Open Metaverse) which gives the same >> for e.g. AI bots ? a headless client which connects to a server, gets >> the scene state automatically and provides it as an easy to use >> in-memory API that e.g. AI code can use to query and modify the scene. >> AFAIK people have been happy and productive with that. >> >> But this is exactly what I would like NOT to do. Why should the >> simulation server have the full scene. This might be necessary in some >> cases, but there are many where it is not. >> >> But I agree that the SceneAPI may be something that is more tailored >> towards queries and isolated changes. One way to combine the two things >> could be to use the Scene API to set up selected synchronization to the >> simulation server for just the interesting aspects for cases where >> continuous updates are necessary. The simulation server could then >> decide to send back changes either through the sync channel (where >> appropriate) or the Scene API. >> >> >> One obvious issue that Toni already talked about is the direction. >> Contacting a browser instance is not possible without a server as we >> know from Server-Based Rendering. But then we could design an >> interface that allows for querying and changing a scene. >> > >> > Again the Sync GE does provide that, both in form of a WebSocket >> protocol and a JS client lib made on top of that ? you can query the >> scene and modify it. >> > >> > But I think is a good idea for us (Lasse perhaps but I?m probably >> too curious to skip it too :) to check that article to understand more >> of what you are after. >> >> But WebSocket is again a server-only transport mechanism (and it is what >> we are currently using as well). That may be fine for some cases but for >> others a P2P connection through Web RTC might be required if all we have >> are two Web applications. >> >> BTW, the paper used REST and this is quite limited connectionwise. >> >> >> Best, >> >> Philipp >> > Cheers, >> > ~Toni >> > >> >> >> >> There is already is such a suggestion by Behr et, al >> (http://dl.acm.org/citation.cfm?id=1836057&CFID=394541370&CFTOKEN=82263824) >> that may be a good lpace to start. It based on HTTP/REST, though, >> which would not work for a connection towards the browser, so we >> should use WebRTC instead. >> >> >> >> >> >> Best, >> >> >> >> Philipp >> >> >> >> Am 21.11.2013 22:24, schrieb Toni Alatalo: >> >>> On 21 Nov 2013, at 10:54, Lasse ??rni > > wrote: >> >>>> If there is a good concrete plan to how it should be done instead >> it's not >> >>>> at all too late to change (as any implementation has not began), >> and if >> >>>> it's administratively OK, for example our architecture pictures now >> >>>> include the REST scene API described. >> >>> >> >>> I talked today with a guy who is working on the vw / visualization >> front in the university project with the traffic sensors in the city. >> >>> >> >>> We agreed preliminarily that could use their data and system as a >> use case for this SceneAPI biz on the fi-ware side ? if you and others >> here find it?s a good idea. >> >>> >> >>> Their data currently updates once per hour, though, so http would >> work :) >> >>> >> >>> But he had already proposed as a next step a visualisation where >> traffic is simulated / visualized as actual individual cars. We could >> have that simulation service as a user of the scene api / sync biz to >> control the cars so we?d get streaming nature for the data and much >> harder reqs for the usage (in the spirit of the EPIC). >> >>> >> >>> I still have to confirm with the prof whose leading that project >> that this all would be ok. We could do it so that the actual >> implementation of the visualization and even the integration comes >> from the uni and fi-ware (Ludocraft) only provides the API. I can use >> some of my university time for this as the integration of the city >> model and the traffic data is good to get there. >> >>> >> >>> This is not a must and I don?t mean to overcomplicate thing but >> just figured that a real use case would help to make the *concrete >> plan* that you called for above. >> >>> >> >>> The experience with the quick and simple POI & 3DUI integration >> (completed yesterday) was great, I?ll post about it tomorrow hopefully >> (the POI guys checked the demo today on ok?d it as this first minimal >> step). So I hope more integrations and usage of the GEs takes us well >> forward. >> >>> >> >>>> Lasse ??rni >> >>> >> >>> Cheers, >> >>> ~Toni >> >>> >> >>> _______________________________________________ >> >>> Fiware-miwi mailing list >> >>> Fiware-miwi at lists.fi-ware.eu >> >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >>> >> >> >> >> >> >> -- >> >> >> >> >> ------------------------------------------------------------------------- >> >> Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH >> >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> >> >> >> Gesch?ftsf?hrung: >> >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> >> Dr. Walter Olthoff >> >> Vorsitzender des Aufsichtsrats: >> >> Prof. Dr. h.c. Hans A. Aukes >> >> >> >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 >> >> >> --------------------------------------------------------------------------- >> >> >> > >> >> >> -- >> >> ------------------------------------------------------------------------- >> Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> >> Gesch?ftsf?hrung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 >> --------------------------------------------------------------------------- >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 456 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Wed Jan 15 09:21:29 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 15 Jan 2014 09:21:29 +0100 Subject: [Fiware-miwi] Fwd: Re: [AR Standards Announcements] awe.js released with a demo of AR working in a standard web browser In-Reply-To: <52D58D25.7090908@buildAR.com> References: <52D58D25.7090908@buildAR.com> Message-ID: <52D64509.5050901@dfki.de> Hi, Why do people reinvent the scene graph even in the browser :-(. Here is a link to a little library that deals with the orientation sensors and displays some geometry based on that. Could be something that goes nicely into a Xflow node, I guess and one would have all the rest of the ecosystem automatically. I suggest that we spend some time soon to come up with a convincing AR demo that we can publish to the AR community. But it needs to be convincing :-). Talk to you soon, Philipp -------- Original-Nachricht -------- Betreff: Re: [AR Standards Announcements] awe.js released with a demo of AR working in a standard web browser Datum: Wed, 15 Jan 2014 06:16:53 +1100 Von: Rob Manson Organisation: buildAR.com An: cperey at perey.com, public-ar at w3.org, news at arstandards.org Hey Christine, thanks 8) We've got some ideas we're working on around adding affordances to websites - along the lines of what we showed when we first launched the Augmented Web at ARE back in 2012. But one key point is that awe.js doesn't just do location based AR. We'll be releasing lots more examples over the next few weeks showing all the different ways it can be used and then announcing a new roadmap after that. And I'll definitely be circulating some more ideas on updates to the CG soon so all feedback welcome. Happy new year 8) roBman On 15/01/14 4:41 AM, Christine Perey wrote: > Hi Rob, > > Happy New Year 2014 to you and to all those on the W3C AR Community > Group and AR Standards Community mailing lists! > > This library is a great "gift" to the community and to all those who > they serve who in the future will be able to experience AR in a standard > web browser. > > Do you think it would be possible to add a page on the CG site and/or > Github and propose a nomenclature for naming the experiences created > using this library? > > Then it would be nice for implementers who use the naming convention to > directly add the URL to their assets (or for someone to curate that > list). This would benefit the early implementers who want to be > discovered as well as the test/user community. > > The scenario I'm thinking is that when a user visits the page (catalog) > with their standard web browser, they will look for a venue or > geospatial coordinates to see if there are any experiences and then, if > available, click on the link to open the AR experience. > > thoughts? > > Christine > > Spime Wrangler > cperey at perey.com > @cperey > Skype Christine_Perey > Swiss mobile +41 (0) 79 436 6869 > VoIP from anywhere +1 (617) 848-8159 > bloghttp://www.spimewrangler.com > NOTE Temporary phone number Jan 7-23 2014: +1 (908) 723 5226 > > On 1/13/14 2:47 PM, Rob Manson wrote: >> Hi, >> >> we've kicked of 2014 by releasing our open source Augmented Web >> library (awe.js) on github. >> >> https://github.com/buildar/awe.js >> >> >> Along with a video showing our first demo of location based AR working >> in a standard web browser. >> >> http://youtu.be/OJHgBSRJNJY >> >> >> We'll be releasing a lot more demos and tutorials over the next few >> weeks and I'll also add this to the demos section. In fact it's >> probably time to step back and take a whole new look at the content on >> the CG site too. >> >> Happy new year and I hope you enjoyed the holidays. >> >> roBman >> >> > -- Rob Checkout my new book - Getting started with WebRTC http://www.packtpub.com/getting-started-with-webrtc/book CEO & co-founder https://buildAR.com Overlay your content on the real world! Chair of the W3C Augmented Web Community Group http://www.w3.org/community/ar Invited Expert with the ISO, Khronos Group & W3C _______________________________________________ News mailing list News at arstandards.org http://arstandards.org/mailman/listinfo/news -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From torsten.spieldenner at dfki.de Wed Jan 15 09:23:31 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Wed, 15 Jan 2014 09:23:31 +0100 Subject: [Fiware-miwi] thu 13: meet about webtundra dom-integration & xml3d net sync vs. tundra components In-Reply-To: <52D63243.5080603@dfki.de> References: <1EC7D4CD-B87D-4C23-A9AB-CAAD5E97249D@playsign.net> <52D63243.5080603@dfki.de> Message-ID: <52D64583.1000002@dfki.de> Hello, we are currently planning to have version 0.2 of FiVES finished very soon (in 1 or 2 weeks), until then you find a stable version on develop branch. Features in this branch include, as Philipp already said, synchronization of XML3D scenes that consist of a static environment (e.g. city scene) and user controlled, animated avatars. Physics / Collision is not included yet, but work in progress. The client code will be revised right after the next release as well. It works nicely, but the code needs some refactoring and nicer separation of responsibilities as well as optimization in several classes. But the current way the scene manager works already gives a good impression of how linking the ECA model to XML3D works (see for example lines 122 to 140 for how position, orientation and mesh updates are applied): https://github.com/rryk/FiVES/blob/develop/WebClient/scripts/resources/scene_manager.js Data is read from and kept in sync with the server in the fives_communicator class. That class actually creates the function wrappers to communicate with the server using KIARA: https://github.com/rryk/FiVES/blob/develop/WebClient/scripts/communication/fives_communicator.js Upon receiving updates for an entity, this entity updates the internal data representation (java script objects) and updates the respective fields in its XML3D DOM element via sceneManager, if necessary: https://github.com/rryk/FiVES/blob/develop/WebClient/scripts/models/entity.js (Line 43) I'm happy to answer any detailed question, either on the mailing list directly, or in a separate discussion. A short demo video of how our Web-client currently looks like can be found here: https://www.dropbox.com/s/sdgr7wxf0t0bixu/FIVES-Demo.avi Best, Torsten Am 1/15/2014 8:01 AM, schrieb Philipp Slusallek: > Hi Toni, all, > > Its great to hear that you are making good progress here. And its a > good idea to talk about that today. > > Yes, we have a sync server, a simple KIARA-based API and JSON > protocol, as well as mapping to the XML3D scene, movement and > animation of characters implemented and roughly working. > > The KIARA layer in our C#-based sync server and the JS layer in the > browser are still primitive and hard coded but we are making very good > progress on the C/C++ KIARA implementation (Advanced Middleware GE). > An initial Version will be published by the end of the month. Its not > yet connected to the C#/JS-Version but we are currently looking into > that. > > I am currently preparing a presentation on KIARA that I can share in > about two weeks. > > Torsten, maybe you can send pointers to the code and a video or so? > > I will take care of setting up the call today. Christof seems to still > be ill but (according to his colleagues last Friday) it is no too > serious. Get well soon again, Christof!! > > > Best, > > Philipp > > > > Am 15.01.2014 07:44, schrieb Toni Alatalo: >> Another note from yesterday: we decided to have a little meet / >> working session about the DOM integration and xml3d etc. in the >> WebTundra context. >> >> Lasse has Sync.DomIntegration as a feature tracker entry in the >> fi-ware forge, and as evident for many posts here we've worked on it >> a lot from the 3DUI perspective at Playsign. >> >> One topic is net sync of full xml3d, xflow, and perhaps arbitrary DOM >> elements. Basic 3d things like transforms and meshes we can (and >> already do, in Erno's xml3d reader) map between xml3d xml elements >> and Tundra components. For xml elements for which there is no >> existing nor need for a Tundra component, an option is just to use >> DynamicComponent's where use the name feature to have the XML element >> name (for example for Xflow and elements). But >> is that the best idea or would something else be better? Hierarchy is >> coming per Lasse's plan to add normal xml-style hierarchy to Tundra. >> >> Idea is mostly for us (me & Erno) and Lasse to plan next steps in the >> work but anyone interested can participate, Jarkko said that >> Cyberlightning folks working on xml3djs & xflow may join in, and >> Jonne or someone from Admino may come too. We can discuss it in the >> weekly today as well, or set it so that DFKI folks can participate >> remotely tomorrow if it seems like a good idea. >> >> If DFKI Fives already does e.g. full sync of xml3d (and xhtml?) using >> a similar entity-component model, or if there's designs for that >> etc., those would be obviously good to check too --- pointers are >> welcome. >> >> Cheers, >> ~Toni >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Wed Jan 15 09:34:48 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 15 Jan 2014 10:34:48 +0200 Subject: [Fiware-miwi] EntSys: has Scene, integrates Networking & 3DUI + possibilities for XML3D In-Reply-To: <52C57175.3090805@dfki.de> References: <52C57175.3090805@dfki.de> Message-ID: <724268DF-C804-4CBF-A832-B5809B02E310@playsign.net> Thanks, and a note about the option b) considered there -- implementing xml3d.js rendering: With the current WebTundra implementation with that MVC idea the XML3dJsView would still mean that the internal scene model is the reX EC one ? at least in our current thinking, the API for devs to move objects etc would be the WebTundra Scene API (as documented in the 3dui-webtundra & sync GE docs now), and the network synchronization would be however we get it done now (a topic of the tomorrow thu 13 meet). That might be completely fine if the mappings turn out perfect but it?s possible that there?ll be problems too. Is good to check the situation and discuss issues and alternatives etc. so I?m very happy that the tomorrow thing is coming, and the meet now. BTW we discussed Admino?s Interface Designer (or ?scene editor?) yesterday too, and after completing the rex-ec implementation of it they?ve now implemented it as an editor for xml3d too. Is good that we can now take a look at those too, for example how the editor works with the APIs of webrocket (~webtundra scene api) and xml3d(.js?, or using dom?) regarding attribute metadata requirements etc. which have been discussed earlier. And very cool to hear about the fives & KIARA works, looking forward to looking into those at some point. Ah and very good to know from Torsten?s mail this part: "Upon receiving updates for an entity, this entity updates the internal data representation (java script objects) and updates the respective fields in its XML3D DOM element via sceneManager, if necessary:? ? so that?s the other ?b)? alternative from the ?DOM as UI? talks .. as in internal reprs being js objects like current webtundra too, the case of this diagram: https://rawgithub.com/realXtend/doc/master/dom/rexdom-dom_as_ui.svg (instead of https://rawgithub.com/realXtend/doc/master/dom/rexdom.svg) ~Toni On 02 Jan 2014, at 16:02, Philipp Slusallek wrote: > Hi Toni, > > Nice work! The internal separation certainly makes a lot of sense. > > It would be great to add option (b) so that we can test a full XML3D-based connection to realXtend soon. Would be a great step forward for the integration. Great! > > Our sync server is getting into shape as well right now and already can move animated XML3D/Xflow characters around in a larger city model. > > Sergiy and Torsten are ironing out some performance issues right now and are working on a modified version of scalability approach, so we can separate and distribute larger worlds dynamically. There is still quite a bit of work that remains, though. > > Our KIARA work is also progressing nicely. There will be a first release coming now in January. This could be a basis for discussing if or how this may be a good basis for abstracting the networking layer behind a nice API. > > > Best, > > Philipp > > Am 22.12.2013 10:25, schrieb Toni Alatalo: >> About 3 weeks ago we presented a plan for an implementation of the >> entity system and how it would integrate networking (Synch GE) and >> rendering (3DUI GE). >> >> A key aspect in the design was to separate data and view parts of the EC >> implementations ? unlike in any previous Tundra implementation, where >> the scene internals and all EC implementations have been directly tied >> to certain graphics renderer (Ogre or Three.js). The motivation here was >> to support ?headless clients? or ?simulation servers? ? for example for >> a Node.js server side service running some simulation or AI code to use >> this library to connect to a Tundra server to manipulate the scene >> (possibly what the SceneAPI Epic is after). Without ugly hacks like the >> !headless checks in many parts of the C++ Tundra code. When the >> renderer-dependent view code is a separate optional module the scene & >> network parts can be used also without it but the programming model >> (against the scene with the entities) is always the same. Consequently, >> the proposal in this plan was to *not* use the DOM as the internal data >> storage for the Scene ? simply because there is no (native) DOM >> implementation available e.g. in the Node.js environment. The original >> post with more explanations is >> https://lists.fi-ware.eu/private/fiware-miwi/2013-November/000330.html >> >> No one objected, so we went with the plan and I?m very happy to tell >> that the basics for it are implemented and work now. As planned in that >> post, we (Ludocraft & Playsign so far) moved to work in a common >> repository based on Lasse?s Synchronization GE work ? >> WebTundraNetworking was renamed to WebTundra and we added a view/ >> directory there: https://github.com/realXtend/WebTundra >> >> To see it in action you'll need a recent development build of Tundra >> WebSocketServer plugin enabled. realXtend will make an official release >> in January so it will become readily available then. And perhaps we can >> run Tundra servers in FI-LAB at some point to be able to host web >> services then. But if you build it yourself, it?s very easy to test with >> the web-hosted test scene we provide: >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/3DUI-WebTundra_-_Installation_and_Administration_Guide#Test_with_provided_web_hosting_for_scene_data >> >> To test the tech and verify and improve the application programming >> model etc. we?ve ported the Pong example on top of Tundra (server-side >> js) and WebTundra (browser client-side) ? more info about that later >> separately, but if someone wants a pre-peek that work is in >> https://github.com/playsign/PongThreeJS/tree/ec (includes server/ dir >> for the Tundra scene). The Pong example is used also in the dev guide >> docs in >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/3DUI-WebTundra_-_User_and_Programmers_Guide (to >> be improved but has basics now). >> >> With this some things are clear: we already have a platform on which can >> develop apps. But all FI-WARE goals are not delivered yet and there are >> some options so I?ll describe the status briefly here: >> >> XML3D Support: in the F2F I promised we?ll do 3 things: 1. the entity >> system integration (done as reported here now), 2. recommended asset >> pipeline research & impl (on-going, now waiting for the updated three.js >> glTF loader by mr. Parisi) and finally 3. a proposal how to proceed with >> the rendering choice / alternatives. The current WebTundra >> implementation gives two, I find quite nice, alternatives for XML3D support: >> >> a) add XML3D parsing to WebTundra so that it can read XML3D declarations >> and populate the internal Scene correspondingly, hence resulting in a 3d >> rendering when the view module is enabled. Erno actually implemented a >> first version of this this week. It was made by changing the >> pre-existing WebTundra TXML parser in Toni Dahl?s Chiru-WebClient to >> read XML3D instead, this work is in >> https://github.com/playsign/WebTundraNetworking/commits/sceneparser . I >> find this approach has interesting upsides: is simple, and thanks to the >> entity-system is transparent to the other parts ? for example the >> networking works normally so that in fact this works as a way to >> populate a Tundra server from XML3D (when the client reads xml3d and >> creates the entities, they get replicated to the server too :) . Also >> for XML3D standardization efforts it can be interesting that there is >> another implementation of it. Obvious downsides are that it?s a small >> incomplete subset of the spec (at least now) and it doesn?t use the >> xml3d.js engine which has xflow support with hw acceleration coming etc. >> >> b) add XML3D.js view module to WebTundra. Now that the core scene and >> ECs are renderer independent, it is easy and totally feasible to add a >> xml3d.js renderer. The ThreeView is currently just one file with not an >> awful lot of code ? same with XML3D.js would probably be as simple. This >> is helped by Erno having applied the MVC pattern in the code so that >> besides the data in the scene there are model and controller codes which >> manage the state and observe data coming in from the net and track >> Placeable and Mesh references and dependencies etc. so that the View is >> told to display things when they are ready (instead of the view >> requiring all that tracking in itself). So with the complexities in >> Model & Controller parts, possibly already in a renderer agnostic way >> (we didn?t check with this in mind), possibly not so much is left for >> the potential alternative Views to handle. We currently need the >> Three.js view in any case as e.g. Meshmoon has a lot of components & >> rendering made with three so at least first the XML3D.js view would be >> an alternative only. >> >> Another topic is the DOM integration. Current WebTundra has none. There >> again I think there are two ways: >> >> 1. The previously discussed ?DOM as UI? idea where the internal Scene is >> just mirrored to DOM (this is simple and Jonne already did it in >> WebRocket). This might also be one way to implement xml3d.js view >> support .. if we just populate the DOM it should show when xml3d.js is >> active (but when using ThreeView the DOM population would be only for >> developer purposes, to allow seeing the values in debugger etc). >> >> 2. Change the scene internals so that it would use the DOM directly. >> Erno actually prototyped this before we decided to not require DOM in >> the core to support the node.js case. I don?t know if the scene core >> could somehow sensibly use the DOM when it?s there, but work without it >> when it?s not (except ofc with the simply optional mirroring option of >> 1.). Perhaps somehow doing what Philipp outlined at the F2F, put own JS >> objects to the DOM nodes (so we could have the Attribute objects with >> the type info that the net sync (& interface designer) require there). >> >> Anyhow, this is where we are now ? I?m very happy that the basics work >> and we have a common base on which can work and where to integrate >> things (e.g. 2D UI, Input, Interface Designer, possibly app specific >> components from other GEs like POI & real-virtual interaction or GIS?) >> and on which we can implement apps like the Pong example illustrates. >> >> The XML3D support and DOM integration we can have at least with the a) >> and 1) options that have already been implemented. We are however open >> to discuss alternatives and possible clever techniques to address those. >> >> Thanks to everyone for the efforts so far! Looking forward to tackling >> the last remaining issues & packaging first releases after the holidays >> then.. >> ~Toni >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Gesch?ftsf?hrung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > --------------------------------------------------------------------------- > From mach at zhaw.ch Wed Jan 15 09:57:23 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 15 Jan 2014 08:57:23 +0000 Subject: [Fiware-miwi] weekly meeting Message-ID: Hi I?m back again (at least 60%). Starting to get up do date today. I prepared agenda/minutes for todays meeting: https://docs.google.com/document/d/1oFMNkmjnwzVx1KtDhXY5xSo7WT-Umw2JnxAlw2dxWgw/edit# And I will open the bridge at 10 CET. 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3894 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Wed Jan 15 09:58:41 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 15 Jan 2014 09:58:41 +0100 Subject: [Fiware-miwi] MiWi-Hangout Message-ID: <52D64DC1.2010306@dfki.de> Hi all, Here is the link to the Hangout: https://plus.google.com/hangouts/_/7ecpi1871h4a5rh8b12drts3go?hl=de Talk to you, 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: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Wed Jan 15 09:59:44 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 15 Jan 2014 09:59:44 +0100 Subject: [Fiware-miwi] weekly meeting In-Reply-To: References: Message-ID: <52D64E00.1060804@dfki.de> Hi, Sorry, did not see that you are back agian. Welcome! Should we use my the Hangout or do you set up something else? Best, Philipp Am 15.01.2014 09:57, schrieb Marti Christof (mach): > Hi > > I?m back again (at least 60%). Starting to get up do date today. > > I prepared agenda/minutes for todays meeting: > https://docs.google.com/document/d/1oFMNkmjnwzVx1KtDhXY5xSo7WT-Umw2JnxAlw2dxWgw/edit# > > And I will open the bridge at 10 CET. > > 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.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From Philipp.Slusallek at dfki.de Wed Jan 15 10:02:22 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 15 Jan 2014 10:02:22 +0100 Subject: [Fiware-miwi] weekly meeting In-Reply-To: <52D64E00.1060804@dfki.de> References: <52D64E00.1060804@dfki.de> Message-ID: <52D64E9E.7050509@dfki.de> Hi, I closed the Hangout. Meet you at the other telco. Best, Philipp Am 15.01.2014 09:59, schrieb Philipp Slusallek: > Hi, > > Sorry, did not see that you are back agian. Welcome! > > Should we use my the Hangout or do you set up something else? > > Best, > > Philipp > > Am 15.01.2014 09:57, schrieb Marti Christof (mach): >> Hi >> >> I?m back again (at least 60%). Starting to get up do date today. >> >> I prepared agenda/minutes for todays meeting: >> https://docs.google.com/document/d/1oFMNkmjnwzVx1KtDhXY5xSo7WT-Umw2JnxAlw2dxWgw/edit# >> >> >> And I will open the bridge at 10 CET. >> >> 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Wed Jan 15 10:04:41 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 15 Jan 2014 10:04:41 +0100 Subject: [Fiware-miwi] weekly meeting In-Reply-To: <7d6cfcd65d8447eba49650d14240edc9@SRV-MAIL-001.zhaw.ch> References: <52D64E00.1060804@dfki.de> <7d6cfcd65d8447eba49650d14240edc9@SRV-MAIL-001.zhaw.ch> Message-ID: <9AE63B94-D471-422B-9F20-D261E0C731DF@zhaw.ch> OK. Let?s try the hangout. Sound is normally better. Christof Am 15.01.2014 um 10:02 schrieb Philipp Slusallek : > Hi, > > I closed the Hangout. Meet you at the other telco. > > Best, > > Philipp > > Am 15.01.2014 09:59, schrieb Philipp Slusallek: >> Hi, >> >> Sorry, did not see that you are back agian. Welcome! >> >> Should we use my the Hangout or do you set up something else? >> >> Best, >> >> Philipp >> >> Am 15.01.2014 09:57, schrieb Marti Christof (mach): >>> Hi >>> >>> I?m back again (at least 60%). Starting to get up do date today. >>> >>> I prepared agenda/minutes for todays meeting: >>> https://docs.google.com/document/d/1oFMNkmjnwzVx1KtDhXY5xSo7WT-Umw2JnxAlw2dxWgw/edit# >>> >>> >>> And I will open the bridge at 10 CET. >>> >>> 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.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >> >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > -- > > ------------------------------------------------------------------------- > 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: smime.p7s Type: application/pkcs7-signature Size: 3894 bytes Desc: not available URL: From mach at zhaw.ch Wed Jan 15 12:29:37 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 15 Jan 2014 11:29:37 +0000 Subject: [Fiware-miwi] IP-address range to access testbed instances Message-ID: <023E8349-D69A-4AE0-91A7-842F9B7FDF2D@zhaw.ch> Hi To make sure you have proper access to the testbed instances we need to register the IP-address range of all WP13 partners on the testbed firewall. Can you (each partner) please send me the outgoing public address range(s) of your organization before tomorrow noon. I will then send them to the testbed team to add them to the firewall rule. Here you?ll find the description of the testbed access (this is vor V2 and the user registration process is outdated, but to my knowledge the firewall is still active; the V3 document is not yet available): https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Operation_Cockpit (access is restricted to fi-ware testbed project members). 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 Sun Jan 19 20:58:02 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Sun, 19 Jan 2014 20:58:02 +0100 Subject: [Fiware-miwi] EntSys: has Scene, integrates Networking & 3DUI + possibilities for XML3D In-Reply-To: <724268DF-C804-4CBF-A832-B5809B02E310@playsign.net> References: <52C57175.3090805@dfki.de> <724268DF-C804-4CBF-A832-B5809B02E310@playsign.net> Message-ID: <52DC2E4A.3000101@dfki.de> Hi, Am 15.01.2014 09:34, schrieb Toni Alatalo: > BTW we discussed Admino?s Interface Designer (or ?scene editor?) > yesterday too, and after completing the rex-ec implementation of it > they?ve now implemented it as an editor for xml3d too. Is good that > we can now take a look at those too, for example how the editor works > with the APIs of webrocket (~webtundra scene api) and xml3d(.js?, or > using dom?) regarding attribute metadata requirements etc. which have > been discussed earlier. Thins sounds great. Is there a chance to see anything of the editor yet? We would be extremely interested to get our hand dirty with it. I am sure we find people interested in working on this, too. > And very cool to hear about the fives & KIARA works, looking forward > to looking into those at some point. Ah and very good to know from > Torsten?s mail this part: "Upon receiving updates for an entity, this > entity updates the internal data representation (java script objects) > and updates the respective fields in its XML3D DOM element via > sceneManager, if necessary:? ? so that?s the other ?b)? alternative > from the ?DOM as UI? talks .. as in internal reprs being js objects > like current webtundra too, the case of this diagram: > https://rawgithub.com/realXtend/doc/master/dom/rexdom-dom_as_ui.svg > (instead of > https://rawgithub.com/realXtend/doc/master/dom/rexdom.svg) Well, we never store the JS objects, they are only used in the API from KIARA to communicate the changes to the scene (and back). Best, Philipp > ~Toni > > On 02 Jan 2014, at 16:02, Philipp Slusallek wrote: > >> Hi Toni, >> >> Nice work! The internal separation certainly makes a lot of sense. >> >> It would be great to add option (b) so that we can test a full XML3D-based connection to realXtend soon. Would be a great step forward for the integration. Great! >> >> Our sync server is getting into shape as well right now and already can move animated XML3D/Xflow characters around in a larger city model. >> >> Sergiy and Torsten are ironing out some performance issues right now and are working on a modified version of scalability approach, so we can separate and distribute larger worlds dynamically. There is still quite a bit of work that remains, though. >> >> Our KIARA work is also progressing nicely. There will be a first release coming now in January. This could be a basis for discussing if or how this may be a good basis for abstracting the networking layer behind a nice API. >> >> >> Best, >> >> Philipp >> >> Am 22.12.2013 10:25, schrieb Toni Alatalo: >>> About 3 weeks ago we presented a plan for an implementation of the >>> entity system and how it would integrate networking (Synch GE) and >>> rendering (3DUI GE). >>> >>> A key aspect in the design was to separate data and view parts of the EC >>> implementations ? unlike in any previous Tundra implementation, where >>> the scene internals and all EC implementations have been directly tied >>> to certain graphics renderer (Ogre or Three.js). The motivation here was >>> to support ?headless clients? or ?simulation servers? ? for example for >>> a Node.js server side service running some simulation or AI code to use >>> this library to connect to a Tundra server to manipulate the scene >>> (possibly what the SceneAPI Epic is after). Without ugly hacks like the >>> !headless checks in many parts of the C++ Tundra code. When the >>> renderer-dependent view code is a separate optional module the scene & >>> network parts can be used also without it but the programming model >>> (against the scene with the entities) is always the same. Consequently, >>> the proposal in this plan was to *not* use the DOM as the internal data >>> storage for the Scene ? simply because there is no (native) DOM >>> implementation available e.g. in the Node.js environment. The original >>> post with more explanations is >>> https://lists.fi-ware.eu/private/fiware-miwi/2013-November/000330.html >>> >>> No one objected, so we went with the plan and I?m very happy to tell >>> that the basics for it are implemented and work now. As planned in that >>> post, we (Ludocraft & Playsign so far) moved to work in a common >>> repository based on Lasse?s Synchronization GE work ? >>> WebTundraNetworking was renamed to WebTundra and we added a view/ >>> directory there: https://github.com/realXtend/WebTundra >>> >>> To see it in action you'll need a recent development build of Tundra >>> WebSocketServer plugin enabled. realXtend will make an official release >>> in January so it will become readily available then. And perhaps we can >>> run Tundra servers in FI-LAB at some point to be able to host web >>> services then. But if you build it yourself, it?s very easy to test with >>> the web-hosted test scene we provide: >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/3DUI-WebTundra_-_Installation_and_Administration_Guide#Test_with_provided_web_hosting_for_scene_data >>> >>> To test the tech and verify and improve the application programming >>> model etc. we?ve ported the Pong example on top of Tundra (server-side >>> js) and WebTundra (browser client-side) ? more info about that later >>> separately, but if someone wants a pre-peek that work is in >>> https://github.com/playsign/PongThreeJS/tree/ec (includes server/ dir >>> for the Tundra scene). The Pong example is used also in the dev guide >>> docs in >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/3DUI-WebTundra_-_User_and_Programmers_Guide (to >>> be improved but has basics now). >>> >>> With this some things are clear: we already have a platform on which can >>> develop apps. But all FI-WARE goals are not delivered yet and there are >>> some options so I?ll describe the status briefly here: >>> >>> XML3D Support: in the F2F I promised we?ll do 3 things: 1. the entity >>> system integration (done as reported here now), 2. recommended asset >>> pipeline research & impl (on-going, now waiting for the updated three.js >>> glTF loader by mr. Parisi) and finally 3. a proposal how to proceed with >>> the rendering choice / alternatives. The current WebTundra >>> implementation gives two, I find quite nice, alternatives for XML3D support: >>> >>> a) add XML3D parsing to WebTundra so that it can read XML3D declarations >>> and populate the internal Scene correspondingly, hence resulting in a 3d >>> rendering when the view module is enabled. Erno actually implemented a >>> first version of this this week. It was made by changing the >>> pre-existing WebTundra TXML parser in Toni Dahl?s Chiru-WebClient to >>> read XML3D instead, this work is in >>> https://github.com/playsign/WebTundraNetworking/commits/sceneparser . I >>> find this approach has interesting upsides: is simple, and thanks to the >>> entity-system is transparent to the other parts ? for example the >>> networking works normally so that in fact this works as a way to >>> populate a Tundra server from XML3D (when the client reads xml3d and >>> creates the entities, they get replicated to the server too :) . Also >>> for XML3D standardization efforts it can be interesting that there is >>> another implementation of it. Obvious downsides are that it?s a small >>> incomplete subset of the spec (at least now) and it doesn?t use the >>> xml3d.js engine which has xflow support with hw acceleration coming etc. >>> >>> b) add XML3D.js view module to WebTundra. Now that the core scene and >>> ECs are renderer independent, it is easy and totally feasible to add a >>> xml3d.js renderer. The ThreeView is currently just one file with not an >>> awful lot of code ? same with XML3D.js would probably be as simple. This >>> is helped by Erno having applied the MVC pattern in the code so that >>> besides the data in the scene there are model and controller codes which >>> manage the state and observe data coming in from the net and track >>> Placeable and Mesh references and dependencies etc. so that the View is >>> told to display things when they are ready (instead of the view >>> requiring all that tracking in itself). So with the complexities in >>> Model & Controller parts, possibly already in a renderer agnostic way >>> (we didn?t check with this in mind), possibly not so much is left for >>> the potential alternative Views to handle. We currently need the >>> Three.js view in any case as e.g. Meshmoon has a lot of components & >>> rendering made with three so at least first the XML3D.js view would be >>> an alternative only. >>> >>> Another topic is the DOM integration. Current WebTundra has none. There >>> again I think there are two ways: >>> >>> 1. The previously discussed ?DOM as UI? idea where the internal Scene is >>> just mirrored to DOM (this is simple and Jonne already did it in >>> WebRocket). This might also be one way to implement xml3d.js view >>> support .. if we just populate the DOM it should show when xml3d.js is >>> active (but when using ThreeView the DOM population would be only for >>> developer purposes, to allow seeing the values in debugger etc). >>> >>> 2. Change the scene internals so that it would use the DOM directly. >>> Erno actually prototyped this before we decided to not require DOM in >>> the core to support the node.js case. I don?t know if the scene core >>> could somehow sensibly use the DOM when it?s there, but work without it >>> when it?s not (except ofc with the simply optional mirroring option of >>> 1.). Perhaps somehow doing what Philipp outlined at the F2F, put own JS >>> objects to the DOM nodes (so we could have the Attribute objects with >>> the type info that the net sync (& interface designer) require there). >>> >>> Anyhow, this is where we are now ? I?m very happy that the basics work >>> and we have a common base on which can work and where to integrate >>> things (e.g. 2D UI, Input, Interface Designer, possibly app specific >>> components from other GEs like POI & real-virtual interaction or GIS?) >>> and on which we can implement apps like the Pong example illustrates. >>> >>> The XML3D support and DOM integration we can have at least with the a) >>> and 1) options that have already been implemented. We are however open >>> to discuss alternatives and possible clever techniques to address those. >>> >>> Thanks to everyone for the efforts so far! Looking forward to tackling >>> the last remaining issues & packaging first releases after the holidays >>> then.. >>> ~Toni >>> >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >> >> >> -- >> >> ------------------------------------------------------------------------- >> Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> >> Gesch?ftsf?hrung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 >> --------------------------------------------------------------------------- >> > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From torsten.spieldenner at dfki.de Mon Jan 20 13:28:18 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Mon, 20 Jan 2014 13:28:18 +0100 Subject: [Fiware-miwi] EntSys: has Scene, integrates Networking & 3DUI + possibilities for XML3D In-Reply-To: <52DC2E4A.3000101@dfki.de> References: <52C57175.3090805@dfki.de> <724268DF-C804-4CBF-A832-B5809B02E310@playsign.net> <52DC2E4A.3000101@dfki.de> Message-ID: <52DD1662.4070704@dfki.de> Hello, A small correction here: Am 1/19/2014 8:58 PM, schrieb Philipp Slusallek: >> [....] like current webtundra too, the case of this diagram: >> https://rawgithub.com/realXtend/doc/master/dom/rexdom-dom_as_ui.svg >> (instead of >> https://rawgithub.com/realXtend/doc/master/dom/rexdom.svg) > > Well, we never store the JS objects, they are only used in the API > from KIARA to communicate the changes to the scene (and back). > We actually do store a high-level representation of an entity as JS object in addition to its XML3D-DOM-object. This has two reasons: First, we can store a reference to the XML3D object in the DOM. By this, we can directly adapt attributes of an entity instance without having to do a DOM lookup by entity ID first. Second, we can also maintain attributes that are not represented in the XML3D object, like for example velocity (which is used to compute position updates which are then propagated to the DOM representation), or in future applications maybe additional semantic information to an entity. The actual scene graph representation of the XML3D object, however, is not stored as separate JS object, but directly copied to the DOM from an external document, which in turn is referenced by an attribute of the entity. The XML3D renderer then renders the object solely from its DOM representation. Best, Torsten From Philipp.Slusallek at dfki.de Mon Jan 20 14:32:59 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Mon, 20 Jan 2014 14:32:59 +0100 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: Delivery M33 - Sprint Planning (yet?) In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90B89160CB1@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89160CB1@EX10-MB2-MAD.hi.inet> Message-ID: <52DD258B.40806@dfki.de> FYI. Please take care of the Backlog entries! Thanks, Philipp -------- Original-Nachricht -------- Betreff: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: Delivery M33 - Sprint Planning (yet?) Datum: Mon, 20 Jan 2014 12:21:04 +0000 Von: MANUEL ESCRICHE VICENTE An: fiware-ge-owners at lists.fi-ware.eu Kopie (CC): fiware-wpl at lists.fi-ware.eu , fiware-wpa at lists.fi-ware.eu Dear Partners, By exploring the backlogs I get quite a negative perspective of the on-going work leading to successfully meet our commitments due by the end of the month. I hope it?s consequence of having the backlog outdated. Therefore, I?d appreciate having it fixed as soon as possible. Otherwise, I?d have no option but to show concern. Thanks for cooperation!! *_UPDATES REQUIRED FOR Backlog Delivery (due end of December)_* Find below the number of items needing updates in the different chapters: ?Apps (31 items), Cloud ( 45 items), IoT (40 items), Data (23 items), I2nd (42 items), Sec(4 items), MiWi (27 items) ?I?d appreciate your collaboration to get them updated ASAP otherwise they appear in red in the deliverable. Have updated the reports of the backlog: hot topic (delivery M33) and dashboards. *_HOT TOPIC ? Delivery M33_* https://forge.fi-ware.eu/docman/view.php/27/3307/FIWARE.backlog.deliveryM33.search.20140120.xlsx I?m missing contributions from many GEIs to the current delivery. I?d appreciate knowing whether they aren?t contributing because those enablers put off their delivery to next release or any other reason. Otherwise, I?d appreciate your collaboration and create those work items. *_DASHBOARDS ? Sprint planning_* *Apps*:Items: 46 = 0 Epics, 22 Features, 8 User stories, 16 Work items, 0 Bugs There are still enablers with nothing scheduled for the current timeframes https://forge.fi-ware.eu/docman/view.php/27/3300/FIWARE.backlog.apps.dashboard.20140120.xlsx *Cloud*: Items: 67 = 0 Epics, 26 Features, 18 User stories, 23 Work items, 0 Bugs There are still enablers with nothing scheduled for the current timeframes https://forge.fi-ware.eu/docman/view.php/27/3301/FIWARE.backlog.cloud.dashboard.20140120.xlsx *IoT*: Items: 47 = 0 Epics, 29 Features, 8 User stories, 10 Work items, 0 Bugs There are still enablers with nothing scheduled for the current timeframes https://forge.fi-ware.eu/docman/view.php/27/3304/FIWARE.backlog.iot.dashboard.20140120.xlsx *Data*: Items: 86 = 0 Epics, 32 Features, 20 User stories, 32 Work items, 2 Bugs There is 1 enabler with nothing scheduled for the current timeframes https://forge.fi-ware.eu/docman/view.php/27/3302/FIWARE.backlog.data.dashboard.20140120.xlsx *I2ND*: Items: 98 = 0 Epics, 36 Features, 6 User stories, 56 Work items, 0 Bugs https://forge.fi-ware.eu/docman/view.php/27/3303/FIWARE.backlog.i2nd.dashboard.20140120.xlsx There are still enablers with nothing scheduled for the current timeframes *Security*: Items: 43 = 0 Epics, 20 Features, 1 User stories, 22 Work items, 0 Bugs https://forge.fi-ware.eu/docman/view.php/27/3306/FIWARE.backlog.security.dashboard.20140120.xlsx There are still enablers with nothing scheduled for the current timeframes *MiWi*: Items: Items: 34 = 0 Epics, 34 Features, 0 User stories, 0 Work items, 0 Bugs https://forge.fi-ware.eu/docman/view.php/27/3305/FIWARE.backlog.miwi.dashboard.20140120.xlsx There are still enablers with nothing scheduled for the current timeframes There?s nothing scheduled for the current sprint since everything scheduled are features. I?m expecting content in backlogs whose GEI?s are declared active. If they had changed the status to on-hold or closed, please, let me know to update them ? and avoid non necessary concern. Thanks all 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 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.eu https://lists.fi-ware.eu/listinfo/fiware-wpa -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From toni at playsign.net Mon Jan 20 14:45:04 2014 From: toni at playsign.net (Toni Alatalo) Date: Mon, 20 Jan 2014 15:45:04 +0200 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: Delivery M33 - Sprint Planning (yet?) In-Reply-To: <52DD258B.40806@dfki.de> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89160CB1@EX10-MB2-MAD.hi.inet> <52DD258B.40806@dfki.de> Message-ID: How? Earlier we were instructed to add features to the tracker, which most of us have done. Then we?ve be updating the status as they?ve been finished etc. So I?m confused about this: (MIWI) "There?s nothing scheduled for the current sprint since everything scheduled are features.? I thought we are delivering the features now in the release, the GEis. I?ve marked our 3DUI EntitySystemIntegration feature as ?completed but not delivered? (or so) as the release is not delivered yet. Am unaware of other actions that should do and could not parse such from those mails, sorry. ~Toni On 20 Jan 2014, at 15:32, Philipp Slusallek wrote: > FYI. Please take care of the Backlog entries! > > Thanks, > > Philipp > > > -------- Original-Nachricht -------- > Betreff: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: > Delivery M33 - Sprint Planning (yet?) > Datum: Mon, 20 Jan 2014 12:21:04 +0000 > Von: MANUEL ESCRICHE VICENTE > An: fiware-ge-owners at lists.fi-ware.eu > Kopie (CC): fiware-wpl at lists.fi-ware.eu , > fiware-wpa at lists.fi-ware.eu > > > > Dear Partners, > > By exploring the backlogs I get quite a negative perspective of the > on-going work leading to successfully meet our commitments due by the > end of the month. I hope it?s consequence of having the backlog > outdated. Therefore, I?d appreciate having it fixed as soon as possible. > Otherwise, I?d have no option but to show concern. > > Thanks for cooperation!! > > *_UPDATES REQUIRED FOR Backlog Delivery (due end of December)_* > > Find below the number of items needing updates in the different chapters: > > ?Apps (31 items), Cloud ( 45 items), IoT (40 items), Data (23 items), > I2nd (42 items), Sec(4 items), MiWi (27 items) > > ?I?d appreciate your collaboration to get them updated ASAP otherwise > they appear in red in the deliverable. > > Have updated the reports of the backlog: hot topic (delivery M33) and > dashboards. > > *_HOT TOPIC ? Delivery M33_* > > https://forge.fi-ware.eu/docman/view.php/27/3307/FIWARE.backlog.deliveryM33.search.20140120.xlsx > > I?m missing contributions from many GEIs to the current delivery. > > I?d appreciate knowing whether they aren?t contributing because those > enablers put off their delivery to next release or any other reason. > Otherwise, I?d appreciate your collaboration and create those work items. > > *_DASHBOARDS ? Sprint planning_* > > *Apps*:Items: 46 = 0 Epics, 22 Features, 8 User stories, 16 Work items, > 0 Bugs > > There are still enablers with nothing scheduled for the current timeframes > > https://forge.fi-ware.eu/docman/view.php/27/3300/FIWARE.backlog.apps.dashboard.20140120.xlsx > > *Cloud*: Items: 67 = 0 Epics, 26 Features, 18 User stories, 23 Work > items, 0 Bugs > > There are still enablers with nothing scheduled for the current timeframes > > https://forge.fi-ware.eu/docman/view.php/27/3301/FIWARE.backlog.cloud.dashboard.20140120.xlsx > > *IoT*: Items: 47 = 0 Epics, 29 Features, 8 User stories, 10 Work items, > 0 Bugs > > There are still enablers with nothing scheduled for the current timeframes > > https://forge.fi-ware.eu/docman/view.php/27/3304/FIWARE.backlog.iot.dashboard.20140120.xlsx > > *Data*: Items: 86 = 0 Epics, 32 Features, 20 User stories, 32 Work > items, 2 Bugs > > There is 1 enabler with nothing scheduled for the current timeframes > > https://forge.fi-ware.eu/docman/view.php/27/3302/FIWARE.backlog.data.dashboard.20140120.xlsx > > *I2ND*: Items: 98 = 0 Epics, 36 Features, 6 User stories, 56 Work items, > 0 Bugs > > https://forge.fi-ware.eu/docman/view.php/27/3303/FIWARE.backlog.i2nd.dashboard.20140120.xlsx > > There are still enablers with nothing scheduled for the current timeframes > > *Security*: Items: 43 = 0 Epics, 20 Features, 1 User stories, 22 Work > items, 0 Bugs > > https://forge.fi-ware.eu/docman/view.php/27/3306/FIWARE.backlog.security.dashboard.20140120.xlsx > > There are still enablers with nothing scheduled for the current timeframes > > *MiWi*: Items: Items: 34 = 0 Epics, 34 Features, 0 User stories, 0 Work > items, 0 Bugs > > https://forge.fi-ware.eu/docman/view.php/27/3305/FIWARE.backlog.miwi.dashboard.20140120.xlsx > > There are still enablers with nothing scheduled for the current timeframes > > There?s nothing scheduled for the current sprint since everything > scheduled are features. > > I?m expecting content in backlogs whose GEI?s are declared active. If > they had changed the status to on-hold or closed, please, let me know to > update them ? and avoid non necessary concern. > > Thanks all 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 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 > --------------------------------------------------------------------------- > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi From Philipp.Slusallek at dfki.de Mon Jan 20 14:50:31 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Mon, 20 Jan 2014 14:50:31 +0100 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: Delivery M33 - Sprint Planning (yet?) In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89160CB1@EX10-MB2-MAD.hi.inet> <52DD258B.40806@dfki.de> Message-ID: <52DD29A7.8050307@dfki.de> Hi, I am not 100% sure myself. At least we should take care the existing backlog entries. It seems that FI-WARE is tracking the performance of the WPs through the Backlog entries. If we do not have any, this might seem strange then, but given the stage of the project, I am not really sure that we should add new entries. At some point it simply adds overhead. Christof, what do you think is the best approach here? Best, Philipp Am 20.01.2014 14:45, schrieb Toni Alatalo: > How? > > Earlier we were instructed to add features to the tracker, which most of us have done. Then we?ve be updating the status as they?ve been finished etc. So I?m confused about this: > > (MIWI) "There?s nothing scheduled for the current sprint since everything scheduled are features.? > > I thought we are delivering the features now in the release, the GEis. > > I?ve marked our 3DUI EntitySystemIntegration feature as ?completed but not delivered? (or so) as the release is not delivered yet. Am unaware of other actions that should do and could not parse such from those mails, sorry. > > ~Toni > > On 20 Jan 2014, at 15:32, Philipp Slusallek wrote: > >> FYI. Please take care of the Backlog entries! >> >> Thanks, >> >> Philipp >> >> >> -------- Original-Nachricht -------- >> Betreff: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: >> Delivery M33 - Sprint Planning (yet?) >> Datum: Mon, 20 Jan 2014 12:21:04 +0000 >> Von: MANUEL ESCRICHE VICENTE >> An: fiware-ge-owners at lists.fi-ware.eu >> Kopie (CC): fiware-wpl at lists.fi-ware.eu , >> fiware-wpa at lists.fi-ware.eu >> >> >> >> Dear Partners, >> >> By exploring the backlogs I get quite a negative perspective of the >> on-going work leading to successfully meet our commitments due by the >> end of the month. I hope it?s consequence of having the backlog >> outdated. Therefore, I?d appreciate having it fixed as soon as possible. >> Otherwise, I?d have no option but to show concern. >> >> Thanks for cooperation!! >> >> *_UPDATES REQUIRED FOR Backlog Delivery (due end of December)_* >> >> Find below the number of items needing updates in the different chapters: >> >> ?Apps (31 items), Cloud ( 45 items), IoT (40 items), Data (23 items), >> I2nd (42 items), Sec(4 items), MiWi (27 items) >> >> ?I?d appreciate your collaboration to get them updated ASAP otherwise >> they appear in red in the deliverable. >> >> Have updated the reports of the backlog: hot topic (delivery M33) and >> dashboards. >> >> *_HOT TOPIC ? Delivery M33_* >> >> https://forge.fi-ware.eu/docman/view.php/27/3307/FIWARE.backlog.deliveryM33.search.20140120.xlsx >> >> I?m missing contributions from many GEIs to the current delivery. >> >> I?d appreciate knowing whether they aren?t contributing because those >> enablers put off their delivery to next release or any other reason. >> Otherwise, I?d appreciate your collaboration and create those work items. >> >> *_DASHBOARDS ? Sprint planning_* >> >> *Apps*:Items: 46 = 0 Epics, 22 Features, 8 User stories, 16 Work items, >> 0 Bugs >> >> There are still enablers with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3300/FIWARE.backlog.apps.dashboard.20140120.xlsx >> >> *Cloud*: Items: 67 = 0 Epics, 26 Features, 18 User stories, 23 Work >> items, 0 Bugs >> >> There are still enablers with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3301/FIWARE.backlog.cloud.dashboard.20140120.xlsx >> >> *IoT*: Items: 47 = 0 Epics, 29 Features, 8 User stories, 10 Work items, >> 0 Bugs >> >> There are still enablers with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3304/FIWARE.backlog.iot.dashboard.20140120.xlsx >> >> *Data*: Items: 86 = 0 Epics, 32 Features, 20 User stories, 32 Work >> items, 2 Bugs >> >> There is 1 enabler with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3302/FIWARE.backlog.data.dashboard.20140120.xlsx >> >> *I2ND*: Items: 98 = 0 Epics, 36 Features, 6 User stories, 56 Work items, >> 0 Bugs >> >> https://forge.fi-ware.eu/docman/view.php/27/3303/FIWARE.backlog.i2nd.dashboard.20140120.xlsx >> >> There are still enablers with nothing scheduled for the current timeframes >> >> *Security*: Items: 43 = 0 Epics, 20 Features, 1 User stories, 22 Work >> items, 0 Bugs >> >> https://forge.fi-ware.eu/docman/view.php/27/3306/FIWARE.backlog.security.dashboard.20140120.xlsx >> >> There are still enablers with nothing scheduled for the current timeframes >> >> *MiWi*: Items: Items: 34 = 0 Epics, 34 Features, 0 User stories, 0 Work >> items, 0 Bugs >> >> https://forge.fi-ware.eu/docman/view.php/27/3305/FIWARE.backlog.miwi.dashboard.20140120.xlsx >> >> There are still enablers with nothing scheduled for the current timeframes >> >> There?s nothing scheduled for the current sprint since everything >> scheduled are features. >> >> I?m expecting content in backlogs whose GEI?s are declared active. If >> they had changed the status to on-hold or closed, please, let me know to >> update them ? and avoid non necessary concern. >> >> Thanks all 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 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 >> --------------------------------------------------------------------------- >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Mon Jan 20 15:10:12 2014 From: mach at zhaw.ch (Christof Marti) Date: Mon, 20 Jan 2014 15:10:12 +0100 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: Delivery M33 - Sprint Planning (yet?) In-Reply-To: <4fd81aa1029b4825841a77ada12bd207@SRV-MAIL-001.zhaw.ch> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89160CB1@EX10-MB2-MAD.hi.inet> <52DD258B.40806@dfki.de> <4fd81aa1029b4825841a77ada12bd207@SRV-MAIL-001.zhaw.ch> Message-ID: <3B560442-1546-466A-8F42-F4273F636892@zhaw.ch> Hi, I will have a call with Manuel regarding the Backlog either this afternoon or latest tomorrow and will check with him what level of detail is expected here. Best regards Christof Am 20.01.2014 um 14:50 schrieb Philipp Slusallek : > Hi, > > I am not 100% sure myself. At least we should take care the existing > backlog entries. > > It seems that FI-WARE is tracking the performance of the WPs through the > Backlog entries. If we do not have any, this might seem strange then, > but given the stage of the project, I am not really sure that we should > add new entries. At some point it simply adds overhead. > > Christof, what do you think is the best approach here? > > > Best, > > Philipp > > Am 20.01.2014 14:45, schrieb Toni Alatalo: >> How? >> >> Earlier we were instructed to add features to the tracker, which most of us have done. Then we?ve be updating the status as they?ve been finished etc. So I?m confused about this: >> >> (MIWI) "There?s nothing scheduled for the current sprint since everything scheduled are features.? >> >> I thought we are delivering the features now in the release, the GEis. >> >> I?ve marked our 3DUI EntitySystemIntegration feature as ?completed but not delivered? (or so) as the release is not delivered yet. Am unaware of other actions that should do and could not parse such from those mails, sorry. >> >> ~Toni >> >> On 20 Jan 2014, at 15:32, Philipp Slusallek wrote: >> >>> FYI. Please take care of the Backlog entries! >>> >>> Thanks, >>> >>> Philipp >>> >>> >>> -------- Original-Nachricht -------- >>> Betreff: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: >>> Delivery M33 - Sprint Planning (yet?) >>> Datum: Mon, 20 Jan 2014 12:21:04 +0000 >>> Von: MANUEL ESCRICHE VICENTE >>> An: fiware-ge-owners at lists.fi-ware.eu >>> Kopie (CC): fiware-wpl at lists.fi-ware.eu , >>> fiware-wpa at lists.fi-ware.eu >>> >>> >>> >>> Dear Partners, >>> >>> By exploring the backlogs I get quite a negative perspective of the >>> on-going work leading to successfully meet our commitments due by the >>> end of the month. I hope it?s consequence of having the backlog >>> outdated. Therefore, I?d appreciate having it fixed as soon as possible. >>> Otherwise, I?d have no option but to show concern. >>> >>> Thanks for cooperation!! >>> >>> *_UPDATES REQUIRED FOR Backlog Delivery (due end of December)_* >>> >>> Find below the number of items needing updates in the different chapters: >>> >>> ?Apps (31 items), Cloud ( 45 items), IoT (40 items), Data (23 items), >>> I2nd (42 items), Sec(4 items), MiWi (27 items) >>> >>> ?I?d appreciate your collaboration to get them updated ASAP otherwise >>> they appear in red in the deliverable. >>> >>> Have updated the reports of the backlog: hot topic (delivery M33) and >>> dashboards. >>> >>> *_HOT TOPIC ? Delivery M33_* >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3307/FIWARE.backlog.deliveryM33.search.20140120.xlsx >>> >>> I?m missing contributions from many GEIs to the current delivery. >>> >>> I?d appreciate knowing whether they aren?t contributing because those >>> enablers put off their delivery to next release or any other reason. >>> Otherwise, I?d appreciate your collaboration and create those work items. >>> >>> *_DASHBOARDS ? Sprint planning_* >>> >>> *Apps*:Items: 46 = 0 Epics, 22 Features, 8 User stories, 16 Work items, >>> 0 Bugs >>> >>> There are still enablers with nothing scheduled for the current timeframes >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3300/FIWARE.backlog.apps.dashboard.20140120.xlsx >>> >>> *Cloud*: Items: 67 = 0 Epics, 26 Features, 18 User stories, 23 Work >>> items, 0 Bugs >>> >>> There are still enablers with nothing scheduled for the current timeframes >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3301/FIWARE.backlog.cloud.dashboard.20140120.xlsx >>> >>> *IoT*: Items: 47 = 0 Epics, 29 Features, 8 User stories, 10 Work items, >>> 0 Bugs >>> >>> There are still enablers with nothing scheduled for the current timeframes >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3304/FIWARE.backlog.iot.dashboard.20140120.xlsx >>> >>> *Data*: Items: 86 = 0 Epics, 32 Features, 20 User stories, 32 Work >>> items, 2 Bugs >>> >>> There is 1 enabler with nothing scheduled for the current timeframes >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3302/FIWARE.backlog.data.dashboard.20140120.xlsx >>> >>> *I2ND*: Items: 98 = 0 Epics, 36 Features, 6 User stories, 56 Work items, >>> 0 Bugs >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3303/FIWARE.backlog.i2nd.dashboard.20140120.xlsx >>> >>> There are still enablers with nothing scheduled for the current timeframes >>> >>> *Security*: Items: 43 = 0 Epics, 20 Features, 1 User stories, 22 Work >>> items, 0 Bugs >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3306/FIWARE.backlog.security.dashboard.20140120.xlsx >>> >>> There are still enablers with nothing scheduled for the current timeframes >>> >>> *MiWi*: Items: Items: 34 = 0 Epics, 34 Features, 0 User stories, 0 Work >>> items, 0 Bugs >>> >>> https://forge.fi-ware.eu/docman/view.php/27/3305/FIWARE.backlog.miwi.dashboard.20140120.xlsx >>> >>> There are still enablers with nothing scheduled for the current timeframes >>> >>> There?s nothing scheduled for the current sprint since everything >>> scheduled are features. >>> >>> I?m expecting content in backlogs whose GEI?s are declared active. If >>> they had changed the status to on-hold or closed, please, let me know to >>> update them ? and avoid non necessary concern. >>> >>> Thanks all 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 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 >>> --------------------------------------------------------------------------- >>> >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Gesch?ftsf?hrung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > --------------------------------------------------------------------------- > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi From lasse.oorni at ludocraft.com Mon Jan 20 15:25:17 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Mon, 20 Jan 2014 16:25:17 +0200 Subject: [Fiware-miwi] Fwd: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: Delivery M33 - Sprint Planning (yet?) In-Reply-To: <52DD29A7.8050307@dfki.de> References: <65CDBE2E7E5A964BB8BC5F4328FDE90B89160CB1@EX10-MB2-MAD.hi.inet> <52DD258B.40806@dfki.de> <52DD29A7.8050307@dfki.de> Message-ID: <140cbd132de80c10c203c3c1aaffc514.squirrel@urho.ludocraft.com> Hi, I can say the same as Toni; at Ludo there's no new backlog tasks queued for execution right now because of preparing for the release and revising the docs as necessary. Further tasks will be assigned when there's no pressure from the release anymore. -- Lasse ??rni Game Programmer LudoCraft Ltd. From mach at zhaw.ch Mon Jan 20 15:36:06 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Mon, 20 Jan 2014 14:36:06 +0000 Subject: [Fiware-miwi] Architecture R3 deliverable update and GE owner contacts Message-ID: <77015205-C49E-4998-8117-FF64A6040EA8@zhaw.ch> Hi ** Architecture R3 update ** Added an additional sheet to the WP13 Dashboard regarding the update of the Architecture Description for FI-WARE R3. https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=20 We have to update (& internally review) the wiki-pages until January 24th. As discussed in the last WP13 call you should update the GE architecture pages in the private wiki (linked from the WP13 integration page and also the above Dashboard) until TODAY. Please update the architecture wiki page of your GE asap and if you are done, mark your GE as ?updated? in the Status column. ** GEi Owners/Contacts ** I also added a sheet with all the WP13 GEi owners and contacts to the WP13 Dashboard. Please verify your contact data and also add a backup contact in case you are not reachable (vacation, ?) and send me a short direct confirmation mail if DONE. https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE&usp=docslist_api#gid=18 Thank you and best regards Christof ---- InIT Cloud Computing Lab 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 Wed Jan 22 08:59:46 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 22 Jan 2014 08:59:46 +0100 Subject: [Fiware-miwi] Agenda/minutes of todays WP13 call Message-ID: Hi Here is the agenda/minutes of todays WP13 call: https://docs.google.com/document/d/1156-Sl1KrlIjNXWzfh9vcc2KsrPK8vhmf9tg9A2IXz8/edit# We have quite a long list of important infos and topics today, so it is crucial to have representatives of each GEi (at least of each partner) available. I will open the telco session at 10:00 CET. See you then. 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 Jan 22 07:25:46 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Wed, 22 Jan 2014 07:25:46 +0100 Subject: [Fiware-miwi] Call today Message-ID: <52DF646A.3060903@dfki.de> Hi, Unfortunately, I will not be able to attends todays call. Torsten will be there and will fill in for me. In case there is any urgent matters, please send separate email. Best, Philipp -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Wed Jan 22 12:29:05 2014 From: mach at zhaw.ch (Marti Christof (mach)) Date: Wed, 22 Jan 2014 12:29:05 +0100 Subject: [Fiware-miwi] Action Points from todays WP13 meeting Message-ID: <2EE9C4C6-47E1-4E13-8BCF-73ECB5515C63@zhaw.ch> Hi Following a short summary of all the action points open from this weeks meeting. For details please check the minutes on https://docs.google.com/document/d/1156-Sl1KrlIjNXWzfh9vcc2KsrPK8vhmf9tg9A2IXz8/edit# Thu 23.01.2014 EOB [GEi owner]: fix orange/red marked Install&Admin-, User&Developer-Guides & unit-testing plans. https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 Thu 23.01.2014 EOB [GEi owner]: fix historic entries in tracker (close or reschedule) Fri 24.01.2014 EOB [GEi owner]: add sprint entries for last, current (3.3.1) and next sprint (split release in user stories and add work items for non code work) Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 Sun 26.01.2014 [GE owner]: Integration Plan for your GEi (GEi dependency chain & Testcase for each chain) please use attached template. Wed 29.01.2014 [GEi owner]: deliver binary package/zip to FI-WARE files section (mandatory) Please keep the deadlines and let me know if you have problems/questions for any topic. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: geis dependencies template.doc Type: application/msword Size: 48640 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jan 22 13:40:03 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 22 Jan 2014 13:40:03 +0100 Subject: [Fiware-miwi] Action Points from todays WP13 meeting In-Reply-To: <337c7048f1a644b293316ec3d14bab98@SRV-MAIL-001.zhaw.ch> References: <2EE9C4C6-47E1-4E13-8BCF-73ECB5515C63@zhaw.ch> <337c7048f1a644b293316ec3d14bab98@SRV-MAIL-001.zhaw.ch> Message-ID: Yes. Thanks for pointing this out. The link for the architecture dashboard is: https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=20 (its the same document, but different tab). Christof Am 22.01.2014 um 13:37 schrieb Jarkko Vatjus-Anttila : > Christof, > > This link: > > Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 > Points to M36 page, surely you meant M33 arch update page? > > > - j > > > > On Wed, Jan 22, 2014 at 1:29 PM, Marti Christof (mach) wrote: > Hi > > Following a short summary of all the action points open from this weeks meeting. > For details please check the minutes on https://docs.google.com/document/d/1156-Sl1KrlIjNXWzfh9vcc2KsrPK8vhmf9tg9A2IXz8/edit# > > Thu 23.01.2014 EOB [GEi owner]: fix orange/red marked Install&Admin-, User&Developer-Guides & unit-testing plans. > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > Thu 23.01.2014 EOB [GEi owner]: fix historic entries in tracker (close or ri 24.01.2014 EOB [GEi owner]: add sprint entries for last, current (3.3.1) and next sprint (split release in user stories and add work items for non code work) > Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 > Sun 26.01.2014 [GE owner]: Integration Plan for your GEi (GEi dependency chain & Testcase for each chain) > please use attached template. > Wed 29.01.2014 [GEi owner]: deliver binary package/zip to FI-WARE files section (mandatory) > > Please keep the deadlines and let me know if you have problems/questions for any topic. > > Best regards > Christof > ---- > InIT Clou 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.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > > > > -- > Jarkko Vatjus-Anttila > VP, Technology > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > Go to www.cybersli.de and enrich your presentations! > > www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jan 22 13:51:12 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 22 Jan 2014 13:51:12 +0100 Subject: [Fiware-miwi] Hangout to discuss 3D-UI architecture Message-ID: Hi At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. It has to be quite short notice because we also have to update the page until Friday. I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z Please register your availability asap, if you are involved in the 3D-UI GE architecture. If no time-slot fits for you please let me know. 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 toni at playsign.net Wed Jan 22 17:01:37 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 22 Jan 2014 18:01:37 +0200 Subject: [Fiware-miwi] Hangout to discuss 3D-UI architecture In-Reply-To: References: Message-ID: A bit about the agenda: What prompted this to me now was reading our arch doc & 3DUI and Sync GE docs. I find the overall arch doc does an ok job for now for describing the whole, but the GE ones are from different worlds. They are both fine as themselves but don?t tell how they should work and be used together (which the arch doc does promise). The docs in question: Overall Arch: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture 3DUI GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI Sync GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization The question I think we should answer clearly for app developers is: what is the API one should use to develop an app for the overall arch. I?ll post separate notes about the meet we had last Thu about xml3d support in WebTundra in general & especially how net sync of xml3d data is planned to work there ? have the notes about it on paper now but need to type it, either later this evening or tomorrow before this session. It is a bit a different topic but closely related. Cheers, ~Toni On 22 Jan 2014, at 14:51, Christof Marti wrote: > Hi > > At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. > It has to be quite short notice because we also have to update the page until Friday. > I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z > > Please register your availability asap, if you are involved in the 3D-UI GE architecture. > If no time-slot fits for you please let me know. > > 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.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From jarkko at cyberlightning.com Thu Jan 23 08:36:24 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Thu, 23 Jan 2014 09:36:24 +0200 Subject: [Fiware-miwi] Action Points from todays WP13 meeting In-Reply-To: References: <2EE9C4C6-47E1-4E13-8BCF-73ECB5515C63@zhaw.ch> <337c7048f1a644b293316ec3d14bab98@SRV-MAIL-001.zhaw.ch> Message-ID: Hello all, I am still a little bit confused with the terminology here, especially with "work item" and "user story", so maybe a few clarifying (perhaps stupid :)) questions are needed: - Now that we are a number of features for each GE, do we need to create user story for each GE, or for each feature? - What exactly is "user story"? Is it kind of a use-case description, i.e. it describes steps how the GE are used, or is it more a general overview what is happening in the GE. - We need to add work items for documentation, updating sw arch, etc. Do we simply add those for each GE individually? - Does there need to be a link between work items and features? - Do we need to assign features also to sprints, since at the moment they are not. - Do we need to link user stories and work items somehow? or are they individual entries? Thanks a lot! On Wed, Jan 22, 2014 at 2:40 PM, Christof Marti wrote: > Yes. Thanks for pointing this out. > The link for the architecture dashboard is: > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=20 > (its the same document, but different tab). > > Christof > > Am 22.01.2014 um 13:37 schrieb Jarkko Vatjus-Anttila < > jarkko at cyberlightning.com>: > > Christof, > > This link: > > > > - *Fri 24.01.2014 [GE owner]*: updated and reviewed architecture for > your GE in private wiki (mark "updated" in dashboard) > > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 > > Points to M36 page, surely you meant M33 arch update page? > > > - j > > > > On Wed, Jan 22, 2014 at 1:29 PM, Marti Christof (mach) wrote: > >> Hi >> >> Following a short summary of all the action points open from this weeks >> meeting. >> For details please check the minutes on >> https://docs.google.com/document/d/1156-Sl1KrlIjNXWzfh9vcc2KsrPK8vhmf9tg9A2IXz8/edit# >> >> >> - *Thu 23.01.2014 EOB [GEi owner]*: fix orange/red marked >> Install&Admin-, User&Developer-Guides & unit-testing plans. >> >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 >> - *Thu 23.01.2014 EOB [GEi owner]*: fix historic entries in tracker >> (close or ri 24.01.2014 EOB [GEi owner]: add sprint entries for last, >> current (3.3.1) and next sprint (split release in user stories and add work >> items for non code work) >> - *Fri 24.01.2014 [GE owner]*: updated and reviewed architecture for >> your GE in private wiki (mark "updated" in dashboard) >> >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 >> - *Sun 26.01.2014 [GE owner]*: Integration Plan for your GEi (GEi >> dependency chain & Testcase for each chain) >> please use attached template. >> - *Wed 29.01.2014 [GEi owner]*: deliver binary package/zip to FI-WARE >> files section (mandatory) >> >> >> Please keep the deadlines and let me know if you have >> problems/questions for any topic. >> >> Best regards >> Christof >> ---- >> InIT Clou 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> > > > -- > Jarkko Vatjus-Anttila > VP, Technology > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > Go to www.cybersli.de and enrich your presentations! > > www.cyberlightning.com > > > -- Jarkko Vatjus-Anttila VP, Technology Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com Go to www.cybersli.de and enrich your presentations! www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Thu Jan 23 09:18:49 2014 From: mach at zhaw.ch (Christof Marti) Date: Thu, 23 Jan 2014 09:18:49 +0100 Subject: [Fiware-miwi] Hangout to discuss 3D-UI architecture In-Reply-To: References: Message-ID: Thanks Toni It looks like today 14:00-15:00 is the best option. Would be great if Philipp can join then too (Had no feedback so far). Best regards Christof Am 22.01.2014 um 17:01 schrieb Toni Alatalo : > A bit about the agenda: What prompted this to me now was reading our arch doc & 3DUI and Sync GE docs. I find the overall arch doc does an ok job for now for describing the whole, but the GE ones are from different worlds. They are both fine as themselves but don?t tell how they should work and be used together (which the arch doc does promise). > > The docs in question: > Overall Arch: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture > 3DUI GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI > Sync GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization > > The question I think we should answer clearly for app developers is: what is the API one should use to develop an app for the overall arch. > > I?ll post separate notes about the meet we had last Thu about xml3d support in WebTundra in general & especially how net sync of xml3d data is planned to work there ? have the notes about it on paper now but need to type it, either later this evening or tomorrow before this session. It is a bit a different topic but closely related. > > Cheers, > ~Toni > > On 22 Jan 2014, at 14:51, Christof Marti wrote: > >> Hi >> >> At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. >> It has to be quite short notice because we also have to update the page until Friday. >> I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z >> >> Please register your availability asap, if you are involved in the 3D-UI GE architecture. >> If no time-slot fits for you please let me know. >> >> 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Thu Jan 23 12:17:48 2014 From: toni at playsign.net (Toni Alatalo) Date: Thu, 23 Jan 2014 13:17:48 +0200 Subject: [Fiware-miwi] XML3D in WebTundra internal scene & sync: planned improvements for the reX EC model Message-ID: Notes from the live meet from a week ago, about XML3D and the reX EC model and how everything could and should work in WebTundra / FI-WARE. Focus here is on the network synchronisation and related internal client architecture ? that is, at least in the current implementation these points do *not* depend on what is used for rendering. Even if we implement a Xml3dView, the internal scene model used for the sync is now the reX EC one. Even when loading a xml3d from a HTML doc, instead of receiving the scene over websocket, it is still mapped to the internal scene EC implementation which the view then uses. So, currently the sync uses the reX EC model as is. But the goal is to support XML3D data. We already support that by having a mapping from XML3D scene descriptions to the internal EC model in WebTundra?s XML3D scene reader. reX EC is not hierarchical but supports parenting only via the by-id references in the Placeable component ? so the current reader maps XML hierarchy to those. This is weak, but fortunately Lasse has all along planned to add proper hierarchy support to Tundra & the reX EC model as a part of Ludocraft?s FI-WARE work. With this the reX EC model & XML get identical and we get a straightforward lossless mapping, we?re unaware of problems that will remain. Other problem is XML elements for which there is no corresponding reX Component, for example the and XFlow elements, or any html element if someone wants to sync those. Currently we?d have two options: 1. Use Tundra?s DynamicComponent mechanism to map unknown elements/components to DC?s named ?data? or ?computation?. Then if we e.g. have a Xml3dView in WebTundra for running XFlow apps it could handle those. But this is fragile as the DC name is not a strong typing mechanism. Someone could use the name ?data? for his DC for other purposes and things might break. 2. Implement server-side equivalents of the needed components in C++. At least the quick consensus was to not go there ? is useless for the C++ server to have components with which it doesn?t do anything. Is also very cumbersome to require C++ work & compiling Tundra just to have sync work for some new xml tag when e.g. introducing a new one. In the meet we came up with a new plan: let?s allow use static type IDs, the kinds used for normal components now, for proper typing of arbitrary components. We can still use the DynamicComponent mechanisms in the server and in the network protocol to have the sync work. This way the component handling in the client can use the type info properly and the name remains free for app devs to use. I didn?t get every detail of how this implementation would work but understood from Jonne and Lasse that it?s clear and straightforward. This is not scheduled yet but I propose we put this in the roadmap. This is not only for XML3D (or generic HTML doc) sync but for any reX app dev to support custom components from JS-only app code better. These were the main problems and solutions we identified. Additionally, we discussed a couple smaller issues with this combined XML3D & reX EC usage: 1. If we want to use XML3D as a replacement for TXML, which we are already doing quite happily with WebTundra?s XML3D loader to load scenes locally without needing a Tundra server, what should we do with the extra data we have in the ECs? For example reX Mesh has drawDistance and castShadows, whereas xml3d mesh does not: http://doc.meshmoon.com/doxygen/class_e_c___mesh.html vs. http://www.xml3d.org/xml3d/specification/current/#mesh . My understanding is that as the ?X? in XML is for extensible, it is fine to put non-standard additional attributes to the elements .. so we can save etc. Some things we could of course consider for standardization in XML3D specs but I?m sure many our current things are not really suitable for that. 2. Attribute names differ. For example in Mesh we have reX?s self-invented mesh.meshRef (as there is only skeletonRef and materialRefs) vs. xml3d?s web-standard src attribute. Technically it is ok to map these but I?ve only recently realized that that?s not good in the end as it gets confusing for the app developers. Is weird if you have src=?mymesh? in xml but then must say mesh.meshRef in code. I propose that the realXtend side would be open for harmonization here, as in considering changes to attribute names at least in cases where they are the same thing. In the Web client we could also work via the DOM or support alternative names in WebTundra?s EC implementations but I think that would be bad and only add to the confusion in the (typical) case where also server-side code is needed. Best would be to have xml and client & server APIs have the same names, like we have now with TXML. There?s also a bigger similar issue we did not discuss: in reX EC model and consequently TXML we define whether entities or components are Local or Replicated, i.e. whether they should exist only where they are created or synchronized also to others. A simple way to do this would be again just to extend XML3D elements with the ?sync? attribute, i.e. just doing what we do with TXML now. But do the XML3D folks here find that some other mechanism for this would be better? You can see an example for example in this TXML, there the sync=?1? means Replicated, https://github.com/realXtend/tundra/blob/tundra2/bin/scenes/Physics/scene.txml and the doc in http://doc.meshmoon.com/doxygen/class_entity.html#a12e886ac19fc9d279ea0746432f8f6bc . Obviously in a human-friendly XML such as XML3D we should at least say ?replicated? instead of the int constant 1 used in the machine readable TXML. Looking the other way, the XML3D ?defs? system is something we don?t have in reX. Currently the XML3D reader in WebTundra supports them but it just applies the values to the components and the defs library itself is lost after the initial reading. We don?t know yet whether the defs are supposed to work so that if you change e.g. a position defined there at runtime it is supposed to be applied to all objects using that pos. That might translate to many entities sharing the same placeable component in reX ? which is not supported, would have to be implemented with a parenting (this we actually discussed in the meet too). I think this sums ups the talks and plans, hopefully gives some background for today?s talks too. ~Toni From mach at zhaw.ch Thu Jan 23 14:01:10 2014 From: mach at zhaw.ch (Christof Marti) Date: Thu, 23 Jan 2014 14:01:10 +0100 Subject: [Fiware-miwi] Hangout to discuss 3D-UI architecture In-Reply-To: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> Message-ID: <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> Hi Here is the hangout link for the meeting: https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de Cheers Christof Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) : > Thanks Toni > > It looks like today 14:00-15:00 is the best option. Would be great if Philipp can join then too (Had no feedback so far). > > Best regards > Christof > > Am 22.01.2014 um 17:01 schrieb Toni Alatalo : > >> A bit about the agenda: What prompted this to me now was reading our arch doc & 3DUI and Sync GE docs. I find the overall arch doc does an ok job for now for describing the whole, but the GE ones are from different worlds. They are both fine as themselves but don?t tell how they should work and be used together (which the arch doc does promise). >> >> The docs in question: >> Overall Arch: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >> 3DUI GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >> Sync GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >> >> The question I think we should answer clearly for app developers is: what is the API one should use to develop an app for the overall arch. >> >> I?ll post separate notes about the meet we had last Thu about xml3d support in WebTundra in general & especially how net sync of xml3d data is planned to work there ? have the notes about it on paper now but need to type it, either later this evening or tomorrow before this session. It is a bit a different topic but closely related. >> >> Cheers, >> ~Toni >> >> On 22 Jan 2014, at 14:51, Christof Marti wrote: >> >>> Hi >>> >>> At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. >>> It has to be quite short notice because we also have to update the page until Friday. >>> I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z >>> >>> Please register your availability asap, if you are involved in the 3D-UI GE architecture. >>> If no time-slot fits for you please let me know. >>> >>> 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.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Thu Jan 23 15:18:52 2014 From: mach at zhaw.ch (Christof Marti) Date: Thu, 23 Jan 2014 15:18:52 +0100 Subject: [Fiware-miwi] Action Points from todays WP13 meeting In-Reply-To: <51e6bb470a5d414f9ef4e2456e1410ab@SRV-MAIL-001.zhaw.ch> References: <2EE9C4C6-47E1-4E13-8BCF-73ECB5515C63@zhaw.ch> <337c7048f1a644b293316ec3d14bab98@SRV-MAIL-001.zhaw.ch> <51e6bb470a5d414f9ef4e2456e1410ab@SRV-MAIL-001.zhaw.ch> Message-ID: <52840D21-6EAC-4B33-888A-82D6162FD32C@zhaw.ch> Hi Jarkko The definition of the terms is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology A Feature is functionality implemented within 1 release (max 3 month). A user story is functionality implemented within 1 sprint (1 month). typically part of a feature. If a feature is implemented within 1 sprint you can also schedule it for a specific sprint. Work items are all jobs you do not involving programming and are usually scheduled for a specific sprint 3.3.1, 3.3.2, 3.3.3: - writing documentation, architecture - editing catalog, ... - preparing tutorials - etc. (see my link in yesterdays minutes about the names schema for work items. With work items you document and justify all the other work. See also specific answers to your questions inline. Christof Am 23.01.2014 um 08:36 schrieb Jarkko Vatjus-Anttila : > Hello all, > > I am still a little bit confused with the terminology here, especially with "work item" and "user story", so maybe a few clarifying (perhaps stupid :)) questions are needed: > > - Now that we are a number of features for each GE, do we need to create user story for each GE, or for each feature? You can add user stories to document the work done within one sprint on a feature. > - What exactly is "user story"? Is it kind of a use-case description, i.e. it describes steps how the GE are used, or is it more a general overview what is happening in the GE. In principle it is a specific concrete implementation of a part of a feature. ( > - We need to add work items for documentation, updating sw arch, etc. Do we simply add those for each GE individually? Yes. the naming schema contains the specific GE. See the link to the naming schema in yesterdays minutes > - Does there need to be a link between work items and features? work on features and work items is completely different type of work (coding versus ?all the other stuff?) So no link is needed. > - Do we need to assign features also to sprints, since at the moment they are not. If a feature is implemented within 1 sprint you can also schedule it for a sprint. > - Do we need to link user stories and work items somehow? or are they individual entries? See above as for features. Different type of work. No link. > > Thanks a lot! > > > On Wed, Jan 22, 2014 at 2:40 PM, Christof Marti wrote: > Yes. Thanks for pointing this out. > The link for the architecture dashboard is: https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=20 > (its the same document, but different tab). > > Christof > > Am 22.01.2014 um 13:37 schrieb Jarkko Vatjus-Anttila : > >> Christof, >> >> This link: >> >> >> Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 >> Points to M36 page, surely you meant M33 arch update page? >> >> >> - j >> >> >> >> On Wed, Jan 22, 2014 at 1:29 PM, Marti Christof (mach) wrote: >> Hi >> >> Following a short summary of all the action points open from this weeks meeting. >> For details please check the minutes on https://docs.google.com/document/d/1156-Sl1KrlIjNXWzfh9vcc2KsrPK8vhmf9tg9A2IXz8/edit# >> >> Thu 23.01.2014 EOB [GEi owner]: fix orange/red marked Install&Admin-, User&Developer-Guides & unit-testing plans. >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 >> Thu 23.01.2014 EOB [GEi owner]: fix historic entries in tracker (close or ri 24.01.2014 EOB [GEi owner]: add sprint entries for last, current (3.3.1) and next sprint (split release in user stories and add work items for non code work) >> Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 >> Sun 26.01.2014 [GE owner]: Integration Plan for your GEi (GEi dependency chain & Testcase for each chain) >> please use attached template. >> Wed 29.01.2014 [GEi owner]: deliver binary package/zip to FI-WARE files section (mandatory) >> >> Please keep the deadlines and let me know if you have problems/questions for any topic. >> >> Best regards >> Christof >> ---- >> InIT Clou 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> >> >> >> -- >> Jarkko Vatjus-Anttila >> VP, Technology >> Cyberlightning Ltd. >> >> mobile. +358 405245142 >> email. jarkko at cyberlightning.com >> >> Go to www.cybersli.de and enrich your presentations! >> >> www.cyberlightning.com > > > > > -- > Jarkko Vatjus-Anttila > VP, Technology > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > Go to www.cybersli.de and enrich your presentations! > > www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Fri Jan 24 08:07:31 2014 From: toni at playsign.net (Toni Alatalo) Date: Fri, 24 Jan 2014 09:07:31 +0200 Subject: [Fiware-miwi] XML3D (<)-> reX EC mapping doc (Re: Hangout to discuss 3D-UI architecture) In-Reply-To: <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> Message-ID: As planned in the meeting yesterday, we?ll document the co-use of the XML3D vocabulary (which is somewhat identical with the reX components already) and the reX EC model ? for the integrated use of 3D-UI and Sync. I started a draft in a gdoc, is also pasted below: https://docs.google.com/document/d/1OgU7hAatSAH3foGZ1ngWCv8xagyOlKkG8C5CQOQwExo/edit Torsten can perhaps take this forward towards integration to the arch etc docs? IIRC Philipp also said he'll have some chances later today or during the weekend (Christof needs this by Sunday to ship on Monday - can and will of course be improved later but some sort of first version). Feel free to either work on & comment in the gdoc or move to the wiki suitably. I?m busy with other things till noon now but can return to this in the afternoon (and Erno can check this today too). ~Toni The scene model to integrate 3DUI & Synchronization To integrate 3D-UI with network synchronization an abstract scene model is used in the client core. It is implemented as a Javascript library and also provides the JS API for application developers to create and manipulate the scene. It uses the realXtend Entity-Component (reX EC for short) model, which is also used in the network protocol and on the server when implementing networked multi-user applications. The same API is used on the server side for scene manipulations. Here we describe the mapping from the XML3D structure and vocabulary to the realXtend scene model with entities, components and attributes. In this description XML3D is in bolded xml tags (e.g. ) and the reX EC mapping in Javascript in italic (e.g. entity.mesh). XML3D elements are reX EC entities: entity XML3D elements inside a group, for example and , are corresponding reX EC components attached to the entity: entity.mesh, entity.light A single XML3D element without an encapsulating is also a reX EC entity with the corresponding component. That is, is same as : entity.mesh . XML3D is mapped to the reX EC Placeable component which has the same transform matrix as the transform attribute correspondingly: entity.placeable.transform XML3D elements are mapped to corresponding reX EC camera components: entity.camera . The camera for the view is automatically set as the active one (the scene can have multiple cameras simultaneously but only one can be used for one view). Hierarchical XML (nested tags) in XML3D is mapped to identical hierarchy of entities in reX EC. (implementation NOTE: hierarchical structure is not implemented in reX EC yet, current implementation of the mapping uses placeable parent reference attributes. This will change in coming releases) XML3D element attributes, for example , are mapped to the corresponding reX EC attributes: entity.mesh.meshRef.x . Harmonising the attribute names to have them the same everywhere is under consideration. XML element attributes unknown to the reX EC scene vocabulary (existing Tundra components) are mapped directly: is myentity.myattr.x . (implementation NOTE: proper implementation for arbitrary types in the networked system is not yet implemented). The API to create, remove and listen for changes in the scene is documented in the Synchronization GE docs. ----- 1) The client core (in WebTundra) uses it also when running in standalone mode for single user applications, without using a server and the Synchronization GE overall. 2) This might actually currently require ent.mesh.meshRef.ref (with that additional .ref at the end) due to using an AssetReference type instead of just a string for the ref like in src - let?s consider changing that On 23 Jan 2014, at 15:01, Christof Marti wrote: > Hi > > Here is the hangout link for the meeting: > https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de > > Cheers Christof > > Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) : > >> Thanks Toni >> >> It looks like today 14:00-15:00 is the best option. Would be great if Philipp can join then too (Had no feedback so far). >> >> Best regards >> Christof >> >> Am 22.01.2014 um 17:01 schrieb Toni Alatalo : >> >>> A bit about the agenda: What prompted this to me now was reading our arch doc & 3DUI and Sync GE docs. I find the overall arch doc does an ok job for now for describing the whole, but the GE ones are from different worlds. They are both fine as themselves but don?t tell how they should work and be used together (which the arch doc does promise). >>> >>> The docs in question: >>> Overall Arch: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >>> 3DUI GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >>> Sync GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >>> >>> The question I think we should answer clearly for app developers is: what is the API one should use to develop an app for the overall arch. >>> >>> I?ll post separate notes about the meet we had last Thu about xml3d support in WebTundra in general & especially how net sync of xml3d data is planned to work there ? have the notes about it on paper now but need to type it, either later this evening or tomorrow before this session. It is a bit a different topic but closely related. >>> >>> Cheers, >>> ~Toni >>> >>> On 22 Jan 2014, at 14:51, Christof Marti wrote: >>> >>>> Hi >>>> >>>> At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. >>>> It has to be quite short notice because we also have to update the page until Friday. >>>> I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z >>>> >>>> Please register your availability asap, if you are involved in the 3D-UI GE architecture. >>>> If no time-slot fits for you please let me know. >>>> >>>> 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.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Fri Jan 24 08:11:19 2014 From: toni at playsign.net (Toni Alatalo) Date: Fri, 24 Jan 2014 09:11:19 +0200 Subject: [Fiware-miwi] XML3D (<)-> reX EC mapping doc (Re: Hangout to discuss 3D-UI architecture) In-Reply-To: References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> Message-ID: forgot to mention one point: this is not an idealized spec nor perhaps the right style for arch docs ? I simply documented what we?ve implemented and planned so far (the code that does this in WebTundra is in https://github.com/realXtend/WebTundra/blob/master/src/scene/SceneParser.js#L112 ? Erno has refactored that though while adding CTM loader support during the past couple days, an improved version is coming soon) I trust others who understand the role of the arch, ge, gei, openspec etc. etc. docs to know better how and where to put these things.. ~Toni On 24 Jan 2014, at 09:07, Toni Alatalo wrote: > As planned in the meeting yesterday, we?ll document the co-use of the XML3D vocabulary (which is somewhat identical with the reX components already) and the reX EC model ? for the integrated use of 3D-UI and Sync. > > I started a draft in a gdoc, is also pasted below: https://docs.google.com/document/d/1OgU7hAatSAH3foGZ1ngWCv8xagyOlKkG8C5CQOQwExo/edit > > Torsten can perhaps take this forward towards integration to the arch etc docs? IIRC Philipp also said he'll have some chances later today or during the weekend (Christof needs this by Sunday to ship on Monday - can and will of course be improved later but some sort of first version). Feel free to either work on & comment in the gdoc or move to the wiki suitably. I?m busy with other things till noon now but can return to this in the afternoon (and Erno can check this today too). > > ~Toni > > The scene model to integrate 3DUI & Synchronization > > To integrate 3D-UI with network synchronization an abstract scene model is used in the client core. It is implemented as a Javascript library and also provides the JS API for application developers to create and manipulate the scene. It uses the realXtend Entity-Component (reX EC for short) model, which is also used in the network protocol and on the server when implementing networked multi-user applications. The same API is used on the server side for scene manipulations. Here we describe the mapping from the XML3D structure and vocabulary to the realXtend scene model with entities, components and attributes. In this description XML3D is in bolded xml tags (e.g. ) and the reX EC mapping in Javascript in italic (e.g. entity.mesh). > > XML3D elements are reX EC entities: entity > XML3D elements inside a group, for example and , are corresponding reX EC components attached to the entity: entity.mesh, entity.light > A single XML3D element without an encapsulating is also a reX EC entity with the corresponding component. That is, is same as : entity.mesh . > XML3D is mapped to the reX EC Placeable component which has the same transform matrix as the transform attribute correspondingly: entity.placeable.transform > XML3D elements are mapped to corresponding reX EC camera components: entity.camera . The camera for the view is automatically set as the active one (the scene can have multiple cameras simultaneously but only one can be used for one view). > Hierarchical XML (nested tags) in XML3D is mapped to identical hierarchy of entities in reX EC. (implementation NOTE: hierarchical structure is not implemented in reX EC yet, current implementation of the mapping uses placeable parent reference attributes. This will change in coming releases) > XML3D element attributes, for example , are mapped to the corresponding reX EC attributes: entity.mesh.meshRef.x . Harmonising the attribute names to have them the same everywhere is under consideration. > XML element attributes unknown to the reX EC scene vocabulary (existing Tundra components) are mapped directly: is myentity.myattr.x . (implementation NOTE: proper implementation for arbitrary types in the networked system is not yet implemented). > > The API to create, remove and listen for changes in the scene is documented in the Synchronization GE docs. > > ----- > 1) The client core (in WebTundra) uses it also when running in standalone mode for single user applications, without using a server and the Synchronization GE overall. > 2) This might actually currently require ent.mesh.meshRef.ref (with that additional .ref at the end) due to using an AssetReference type instead of just a string for the ref like in src - let?s consider changing that > > > On 23 Jan 2014, at 15:01, Christof Marti wrote: > >> Hi >> >> Here is the hangout link for the meeting: >> https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de >> >> Cheers Christof >> >> Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) : >> >>> Thanks Toni >>> >>> It looks like today 14:00-15:00 is the best option. Would be great if Philipp can join then too (Had no feedback so far). >>> >>> Best regards >>> Christof >>> >>> Am 22.01.2014 um 17:01 schrieb Toni Alatalo : >>> >>>> A bit about the agenda: What prompted this to me now was reading our arch doc & 3DUI and Sync GE docs. I find the overall arch doc does an ok job for now for describing the whole, but the GE ones are from different worlds. They are both fine as themselves but don?t tell how they should work and be used together (which the arch doc does promise). >>>> >>>> The docs in question: >>>> Overall Arch: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >>>> 3DUI GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >>>> Sync GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >>>> >>>> The question I think we should answer clearly for app developers is: what is the API one should use to develop an app for the overall arch. >>>> >>>> I?ll post separate notes about the meet we had last Thu about xml3d support in WebTundra in general & especially how net sync of xml3d data is planned to work there ? have the notes about it on paper now but need to type it, either later this evening or tomorrow before this session. It is a bit a different topic but closely related. >>>> >>>> Cheers, >>>> ~Toni >>>> >>>> On 22 Jan 2014, at 14:51, Christof Marti wrote: >>>> >>>>> Hi >>>>> >>>>> At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. >>>>> It has to be quite short notice because we also have to update the page until Friday. >>>>> I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z >>>>> >>>>> Please register your availability asap, if you are involved in the 3D-UI GE architecture. >>>>> If no time-slot fits for you please let me know. >>>>> >>>>> 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.eu >>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>> >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From torsten.spieldenner at dfki.de Fri Jan 24 09:14:09 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Fri, 24 Jan 2014 09:14:09 +0100 Subject: [Fiware-miwi] XML3D (<)-> reX EC mapping doc (Re: Hangout to discuss 3D-UI architecture) In-Reply-To: References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> Message-ID: <52E220D1.3010308@dfki.de> Hello, thank you very much for the mappings. I'll add those to the 3D UI Architecture page then and give a notice when I'm done so you can have a look. ~Torsten Am 1/24/2014 8:07 AM, schrieb Toni Alatalo: > As planned in the meeting yesterday, we'll document the co-use of the > XML3D vocabulary (which is somewhat identical with the reX components > already) and the reX EC model --- for the integrated use of 3D-UI and > Sync. > > I started a draft in a gdoc, is also pasted below: > https://docs.google.com/document/d/1OgU7hAatSAH3foGZ1ngWCv8xagyOlKkG8C5CQOQwExo/edit > > Torsten can perhaps take this forward towards integration to the arch > etc docs? IIRC Philipp also said he'll have some chances later today > or during the weekend (Christof needs this by Sunday to ship on Monday > - can and will of course be improved later but some sort of first > version). Feel free to either work on & comment in the gdoc or move to > the wiki suitably. I'm busy with other things till noon now but can > return to this in the afternoon (and Erno can check this today too). > > ~Toni > > The scene model to integrate 3DUI & Synchronization > > To integrate 3D-UI with network synchronization an abstract scene > model is used in the client core. It is implemented as a Javascript > library and also provides the JS API for application developers to > create and manipulate the scene. It uses the realXtend > Entity-Component (reX EC for short) model, which is also used in the > network protocol and on the server when implementing networked > multi-user applications. The same API is used on the server side for > scene manipulations. Here we describe the mapping from the XML3D > structure and vocabulary to the realXtend scene model with entities, > components and attributes. In this description XML3D is in bolded xml > tags (e.g. ) and the reX EC mapping in Javascript in italic > (e.g. entity.mesh). > > 1. > XML3D elements are reX EC entities: entity > 2. > XML3D elements inside a group, for example and , are > corresponding reX EC components attached to the entity: > entity.mesh, entity.light > 3. > A single XML3D element without an encapsulating is also a > reX EC entity with the corresponding component. That is, is > same as : entity.mesh. > 4. > XML3D is mapped to the reX EC Placeable > component which has the same transform matrix as the transform > attribute correspondingly: entity.placeable.transform > 5. > XML3D elements are mapped to corresponding reX EC camera > components: entity.camera. The camera for the view is > automatically set as the active one (the scene can have multiple > cameras simultaneously but only one can be used for one view). > 6. > Hierarchical XML (nested tags) in XML3D is mapped to identical > hierarchy of entities in reX EC. (implementation NOTE: > hierarchical structure is not implemented in reX EC yet, current > implementation of the mapping uses placeable parent reference > attributes. This will change in coming releases) > 7. > XML3D element attributes, for example , are mapped to > the corresponding reX EC attributes: entity.mesh.meshRef.x. > Harmonising the attribute names to have them the same everywhere > is under consideration. > 8. > XML element attributes unknown to the reX EC scene vocabulary > (existing Tundra components) are mapped directly: myattr=x>is myentity.myattr.x. (implementation NOTE: proper > implementation for arbitrary types in the networked system is not > yet implemented). > > > The API to create, remove and listen for changes in the scene is > documented in the Synchronization GE docs. > > ----- > 1) The client core (in WebTundra) uses it also when running in > standalone mode for single user applications, without using a server > and the Synchronization GE overall. > 2) This might actually currently require ent.mesh.meshRef.ref (with > that additional .ref at the end) due to using an AssetReference type > instead of just a string for the ref like in src - let's consider > changing that > > > On 23 Jan 2014, at 15:01, Christof Marti > wrote: > >> Hi >> >> Here is the hangout link for the meeting: >> https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de >> >> Cheers Christof >> >> Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) > >: >> >>> Thanks Toni >>> >>> It looks like today 14:00-15:00 is the best option. Would be great >>> if Philipp can join then too (Had no feedback so far). >>> >>> Best regards >>> Christof >>> >>> Am 22.01.2014 um 17:01 schrieb Toni Alatalo >> >: >>> >>>> A bit about the agenda: What prompted this to me now was reading >>>> our arch doc & 3DUI and Sync GE docs. I find the overall arch doc >>>> does an ok job for now for describing the whole, but the GE ones >>>> are from different worlds. They are both fine as themselves but >>>> don't tell how they should work and be used together (which the >>>> arch doc does promise). >>>> >>>> The docs in question: >>>> Overall Arch: >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >>>> 3DUI GE: >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >>>> Sync GE: >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >>>> >>>> The question I think we should answer clearly for app developers >>>> is: what is the API one should use to develop an app for the >>>> overall arch. >>>> >>>> I'll post separate notes about the meet we had last Thu about xml3d >>>> support in WebTundra in general & especially how net sync of xml3d >>>> data is planned to work there --- have the notes about it on paper >>>> now but need to type it, either later this evening or tomorrow >>>> before this session. It is a bit a different topic but closely related. >>>> >>>> Cheers, >>>> ~Toni >>>> >>>> On 22 Jan 2014, at 14:51, Christof Marti >>> > wrote: >>>> >>>>> Hi >>>>> >>>>> At the meeting a short hangout dedicated to discuss the common >>>>> 3D-UI architecture description was requested. >>>>> It has to be quite short notice because we also have to update the >>>>> page until Friday. >>>>> I prepared a doodle containing dates for today and tomorrow: >>>>> http://www.doodle.com/9gzbu6ggyiit3a6z >>>>> >>>>> >>>>> Please register your availability asap, if you are involved in the >>>>> 3D-UI GE architecture. >>>>> If no time-slot fits for you please let me know. >>>>> >>>>> 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.eu >>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>> >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Fri Jan 24 09:49:29 2014 From: mach at zhaw.ch (Christof Marti) Date: Fri, 24 Jan 2014 09:49:29 +0100 Subject: [Fiware-miwi] XML3D (<)-> reX EC mapping doc (Re: Hangout to discuss 3D-UI architecture) In-Reply-To: <940dfa8e7f354b87ab798bc301988e26@SRV-MAIL-001.zhaw.ch> References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> <940dfa8e7f354b87ab798bc301988e26@SRV-MAIL-001.zhaw.ch> Message-ID: <09BC58D4-EBD5-4DCD-849D-2AB70882418C@zhaw.ch> Hi Regarding the question what has to go to the Architecture and what to the OpenSpecification. The architecture should contain as much info to understand the structure, the dependencies and how the things work and interoperate. It also contains the introduction of the basic elements. The detailed format of the models and protocols, and listings of attributes, values and types and mappings can then be in separate documents, which are part of the Open Specification. Cheers Christof Am 24.01.2014 um 09:14 schrieb Torsten Spieldenner : > Hello, > > thank you very much for the mappings. I'll add those to the 3D UI Architecture page then and give a notice when I'm done so you can have a look. > > ~Torsten > > > Am 1/24/2014 8:07 AM, schrieb Toni Alatalo: >> As planned in the meeting yesterday, we?ll document the co-use of the XML3D vocabulary (which is somewhat identical with the reX components already) and the reX EC model ? for the integrated use of 3D-UI and Sync. >> >> I started a draft in a gdoc, is also pasted below: https://docs.google.com/document/d/1OgU7hAatSAH3foGZ1ngWCv8xagyOlKkG8C5CQOQwExo/edit >> >> Torsten can perhaps take this forward towards integration to the arch etc docs? IIRC Philipp also said he'll have some chances later today or during the weekend (Christof needs this by Sunday to ship on Monday - can and will of course be improved later but some sort of first version). Feel free to either work on & comment in the gdoc or move to the wiki suitably. I?m busy with other things till noon now but can return to this in the afternoon (and Erno can check this today too). >> >> ~Toni >> >> The scene model to integrate 3DUI & Synchronization >> >> To integrate 3D-UI with network synchronization an abstract scene model is >> used in the client core. It is implemented as a Javascript library and also provides the JS API for application developers to create and manipulate the scene. It uses the realXtend Entity-Component (reX EC for short) model, which is also used in the network >> protocol and on the server when implementing networked multi-user applications. The same API is used on the server side for scene manipulations. Here we describe the mapping from the XML3D structure and vocabulary to the realXtend scene model with entities, >> components and attributes. In this description XML3D is in bolded xml tags (e.g. >> ) >> and the reX EC mapping in Javascript in italic (e.g. entity.mesh). >> >> >> XML3D >> elements are reX EC entities: >> entity >> XML3D elements inside a group, for example >> and >> , are corresponding reX EC components >> attached to the entity: entity.mesh, >> entity.light >> A single XML3D element without an encapsulating is also a reX EC entity with the corresponding component. That is, >> is same as >> : >> entity.mesh . >> XML3D >> is mapped to the reX EC Placeable component >> which has the same transform matrix as the transform attribute correspondingly: entity.placeable.transform >> XML3D >> elements are mapped to corresponding reX EC camera components: >> entity.camera . The camera for the view >> is automatically set as the active one (the scene can have multiple cameras simultaneously but only one can be used for one view). >> Hierarchical XML (nested tags) in XML3D is mapped to identical hierarchy of entities in reX EC. (implementation NOTE: hierarchical structure is not implemented in reX EC yet, >> current implementation of the mapping uses placeable parent reference attributes. This will change in coming releases) >> XML3D element attributes, for example >> , are mapped to the corresponding reX EC attributes: >> entity.mesh.meshRef.x . Harmonising the attribute names to >> have them the same everywhere is under consideration. >> XML element attributes unknown to the reX EC scene vocabulary (existing Tundra components) are mapped directly: >> is >> myentity.myattr.x . (implementation NOTE: >> proper implementation for arbitrary types in the networked system is not yet implemented). >> >> The API to create, remove and listen for changes in the scene is documented in the Synchronization GE docs. >> >> ----- >> 1) The client core (in WebTundra) uses it also when running in >> standalone mode for single user applications, without using a server and the Synchronization GE overall. >> >> >> 2) This might actually currently require ent.mesh.meshRef.ref (with that additional .ref at the end) due to using an AssetReference type instead of just a string for the ref like in src - let?s consider >> changing that >> >> >> >> >> >> On 23 Jan 2014, at 15:01, Christof Marti wrote: >> >>> Hi >>> >>> Here is the hangout link for the meeting: >>> https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de >>> >>> Cheers Christof >>> >>> Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) : >>> >>>> Thanks Toni >>>> >>>> It looks like today 14:00-15:00 is the best option. Would be great if Philipp can join then too (Had no feedback so far). >>>> >>>> Best regards >>>> Christof >>>> >>>> Am 22.01.2014 um 17:01 schrieb Toni Alatalo : >>>> >>>>> A bit about the agenda: What prompted this to me now was reading our arch doc & 3DUI and Sync GE docs. I find the overall arch doc does an ok job for now for describing the whole, but the GE ones are from different worlds. They are both fine as themselves but don?t tell how they should work and be used together (which the arch doc does promise). >>>>> >>>>> The docs in question: >>>>> Overall Arch: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >>>>> 3DUI GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >>>>> Sync GE: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >>>>> >>>>> The question I think we should answer clearly for app developers is: what is the API one should use to develop an app for the overall arch. >>>>> >>>>> I?ll post separate notes about the meet we had last Thu about xml3d support in WebTundra in general & especially how net sync of xml3d data is planned to work there ? have the notes about it on paper now but need to type it, either later this evening or tomorrow before this session. It is a bit a different topic but closely related. >>>>> >>>>> Cheers, >>>>> ~Toni >>>>> >>>>> On 22 Jan 2014, at 14:51, Christof Marti wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> At the meeting a short hangout dedicated to discuss the common 3D-UI architecture description was requested. >>>>>> It has to be quite short notice because we also have to update the page until Friday. >>>>>> I prepared a doodle containing dates for today and tomorrow: http://www.doodle.com/9gzbu6ggyiit3a6z >>>>>> >>>>>> Please register your availability asap, if you are involved in the 3D-UI GE architecture. >>>>>> If no time-slot fits for you please let me know. >>>>>> >>>>>> 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.eu >>>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>>> >>>>> _______________________________________________ >>>>> Fiware-miwi mailing list >>>>> Fiware-miwi at lists.fi-ware.eu >>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>> >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Philipp.Slusallek at dfki.de Thu Jan 23 14:47:48 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Thu, 23 Jan 2014 14:47:48 +0100 Subject: [Fiware-miwi] shade.js-Paper Message-ID: <52E11D84.2080805@dfki.de> Hi, For you information here is the shade.js paper that we have just submitted. Please treat it as an internal document for now as it is in review. Best, Philipp -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: paper_submitted.pdf Type: application/pdf Size: 5749882 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Fri Jan 24 11:26:16 2014 From: mach at zhaw.ch (Christof Marti) Date: Fri, 24 Jan 2014 11:26:16 +0100 Subject: [Fiware-miwi] historic open items in tracker and naming conventions Message-ID: Dear WP13 GE owners I was checking the tracker and still found some errors and naming inconistencies. There are still some historic entries, which are not closed or ?Finished but not released?. Historic means belong to Release 3.2 (which ended in December). https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse I created a specific advanced query for these entries named "All historic open?. All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. (e.g. with the line ?Deliverable = D.13.3.3?) List of actual deliverables: D.13.1.2 GE Open Specificatoin (M30) D.13.1.3 GE Open Specification (M33 or M36) D.13.2.3 GE SW Release (M33) D.13.3.3 GE Installation and Administration Guide (M33) D.13.4.3 GE User and Programmer Guide (M33) D.13.5.3 GE Unit Testing Plan & Report (M33) D.2.3.3 FI-WARE Architecture V3 (M33) D.2.4.3 FI-WARE Technical Roadmap V3 (M33) Please also check the naming patterns: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Specially also add the ?action? extension at the end. The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) or for update of the Architecture of the 3D-UI GE: FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) or for creating the SW package: FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). Naming conventions for Features, UserStories etc can be found here: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) 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 From mev at tid.es Fri Jan 24 11:48:53 2014 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 24 Jan 2014 10:48:53 +0000 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: References: Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010BCA@EX10-MB2-MAD.hi.inet> Please, let me a note on this sentence: "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" ->Features hold only as time frame Release ->Stories, Bugs and WorkItems hold both Release and Sprint ->Epics don't hold any timeframe -----Original Message----- From: Christof Marti [mailto:mach at zhaw.ch] Sent: viernes, 24 de enero de 2014 11:26 To: FI-WARE, MiWi Cc: MANUEL ESCRICHE VICENTE Subject: historic open items in tracker and naming conventions Dear WP13 GE owners I was checking the tracker and still found some errors and naming inconistencies. There are still some historic entries, which are not closed or ?Finished but not released?. Historic means belong to Release 3.2 (which ended in December). https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse I created a specific advanced query for these entries named "All historic open?. All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. (e.g. with the line ?Deliverable = D.13.3.3?) List of actual deliverables: D.13.1.2 GE Open Specificatoin (M30) D.13.1.3 GE Open Specification (M33 or M36) D.13.2.3 GE SW Release (M33) D.13.3.3 GE Installation and Administration Guide (M33) D.13.4.3 GE User and Programmer Guide (M33) D.13.5.3 GE Unit Testing Plan & Report (M33) D.2.3.3 FI-WARE Architecture V3 (M33) D.2.4.3 FI-WARE Technical Roadmap V3 (M33) Please also check the naming patterns: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Specially also add the ?action? extension at the end. The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) or for update of the Architecture of the 3D-UI GE: FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) or for creating the SW package: FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). Naming conventions for Features, UserStories etc can be found here: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) 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 ________________________________ 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 torsten.spieldenner at dfki.de Fri Jan 24 12:31:57 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Fri, 24 Jan 2014 12:31:57 +0100 Subject: [Fiware-miwi] XML3D (<)-> reX EC mapping doc (Re: Hangout to discuss 3D-UI architecture) In-Reply-To: <09BC58D4-EBD5-4DCD-849D-2AB70882418C@zhaw.ch> References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> <940dfa8e7f354b87ab798bc301988e26@SRV-MAIL-001.zhaw.ch> <09BC58D4-EBD5-4DCD-849D-2AB70882418C@zhaw.ch> Message-ID: <52E24F2D.8070002@dfki.de> Hello, I have now included the points Toni has sent earlier into the 3D UI Architecture description. It constitutes a new subsection in the "Main Interactions" chapter: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI#Mapping_Synchronization_GE_data_to_XML3D_objects I have switched the direction of the mapping in the descriptions, where possible, as from the point of 3D UI, I rather see the need to map the provided EC model to something we can express in terms of the 3D UI principles. ~ Torsten Am 1/24/2014 9:49 AM, schrieb Christof Marti: > Hi > > Regarding the question what has to go to the Architecture and what to > the OpenSpecification. > The architecture should contain as much info to understand the > structure, the dependencies and how the things work and interoperate. > It also contains the introduction of the basic elements. > > The detailed format of the models and protocols, and listings of > attributes, values and types and mappings can then be in separate > documents, which are part of the Open Specification. > > Cheers > Christof > > Am 24.01.2014 um 09:14 schrieb Torsten Spieldenner > >: > >> Hello, >> >> thank you very much for the mappings. I'll add those to the 3D UI >> Architecture page then and give a notice when I'm done so you can >> have a look. >> >> ~Torsten >> >> >> Am 1/24/2014 8:07 AM, schrieb Toni Alatalo: >>> As planned in the meeting yesterday, we?ll document the co-use of >>> the XML3D vocabulary (which is somewhat identical with the reX >>> components already) and the reX EC model ? for the integrated use of >>> 3D-UI and Sync. >>> >>> I started a draft in a gdoc, is also pasted below: >>> https://docs.google.com/document/d/1OgU7hAatSAH3foGZ1ngWCv8xagyOlKkG8C5CQOQwExo/edit >>> >>> Torsten can perhaps take this forward towards integration to the >>> arch etc docs? IIRC Philipp also said he'll have some chances later >>> today or during the weekend (Christof needs this by Sunday to ship >>> on Monday - can and will of course be improved later but some sort >>> of first version). Feel free to either work on & comment in the gdoc >>> or move to the wiki suitably. I?m busy with other things till noon >>> now but can return to this in the afternoon (and Erno can check this >>> today too). >>> >>> ~Toni >>> >>> The scene model to integrate 3DUI & Synchronization >>> >>> To integrate 3D-UI with network synchronization an abstract scene >>> model is used in the client core. It is implemented as a Javascript >>> library and also provides the JS API for application developers to >>> create and manipulate the scene. It uses the realXtend >>> Entity-Component (reX EC for short) model, which is also used in the >>> network protocol and on the server when implementing networked >>> multi-user applications. The same API is used on the server side for >>> scene manipulations. Here we describe the mapping from the XML3D >>> structure and vocabulary to the realXtend scene model with entities, >>> components and attributes. In this description XML3D is in bolded >>> xml tags (e.g. ) and the reX EC mapping in Javascript in >>> italic (e.g. entity.mesh). >>> >>> 1. >>> XML3D elements are reX EC entities: entity >>> 2. >>> XML3D elements inside a group, for example and , >>> are corresponding reX EC components attached to the entity: >>> entity.mesh, entity.light >>> 3. >>> A single XML3D element without an encapsulating is also >>> a reX EC entity with the corresponding component. That is, >>> is same as : entity.mesh. >>> 4. >>> XML3D is mapped to the reX EC Placeable >>> component which has the same transform matrix as the transform >>> attribute correspondingly: entity.placeable.transform >>> 5. >>> XML3D elements are mapped to corresponding reX EC camera >>> components: entity.camera. The camera for the view is >>> automatically set as the active one (the scene can have multiple >>> cameras simultaneously but only one can be used for one view). >>> 6. >>> Hierarchical XML (nested tags) in XML3D is mapped to identical >>> hierarchy of entities in reX EC. (implementation NOTE: >>> hierarchical structure is not implemented in reX EC yet, current >>> implementation of the mapping uses placeable parent reference >>> attributes. This will change in coming releases) >>> 7. >>> XML3D element attributes, for example , are mapped >>> to the corresponding reX EC attributes: entity.mesh.meshRef.x. >>> Harmonising the attribute names to have them the same everywhere >>> is under consideration. >>> 8. >>> XML element attributes unknown to the reX EC scene vocabulary >>> (existing Tundra components) are mapped directly: >> myattr=x>is myentity.myattr.x. (implementation NOTE: proper >>> implementation for arbitrary types in the networked system is >>> not yet implemented). >>> >>> >>> The API to create, remove and listen for changes in the scene is >>> documented in the Synchronization GE docs. >>> >>> ----- >>> 1) The client core (in WebTundra) uses it also when running in >>> standalone mode for single user applications, without using a server >>> and the Synchronization GE overall. >>> 2) This might actually currently require ent.mesh.meshRef.ref (with >>> that additional .ref at the end) due to using an AssetReference type >>> instead of just a string for the ref like in src - let?s consider >>> changing that >>> >>> >>> On 23 Jan 2014, at 15:01, Christof Marti >> > wrote: >>> >>>> Hi >>>> >>>> Here is the hangout link for the meeting: >>>> https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de >>>> >>>> Cheers Christof >>>> >>>> Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) >>> >: >>>> >>>>> Thanks Toni >>>>> >>>>> It looks like today 14:00-15:00 is the best option. Would be great >>>>> if Philipp can join then too (Had no feedback so far). >>>>> >>>>> Best regards >>>>> Christof >>>>> >>>>> Am 22.01.2014 um 17:01 schrieb Toni Alatalo >>>> >: >>>>> >>>>>> A bit about the agenda: What prompted this to me now was reading >>>>>> our arch doc & 3DUI and Sync GE docs. I find the overall arch doc >>>>>> does an ok job for now for describing the whole, but the GE ones >>>>>> are from different worlds. They are both fine as themselves but >>>>>> don?t tell how they should work and be used together (which the >>>>>> arch doc does promise). >>>>>> >>>>>> The docs in question: >>>>>> Overall Arch: >>>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >>>>>> 3DUI GE: >>>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >>>>>> Sync GE: >>>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >>>>>> >>>>>> The question I think we should answer clearly for app developers >>>>>> is: what is the API one should use to develop an app for the >>>>>> overall arch. >>>>>> >>>>>> I?ll post separate notes about the meet we had last Thu about >>>>>> xml3d support in WebTundra in general & especially how net sync >>>>>> of xml3d data is planned to work there ? have the notes about it >>>>>> on paper now but need to type it, either later this evening or >>>>>> tomorrow before this session. It is a bit a different topic but >>>>>> closely related. >>>>>> >>>>>> Cheers, >>>>>> ~Toni >>>>>> >>>>>> On 22 Jan 2014, at 14:51, Christof Marti >>>>> > wrote: >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> At the meeting a short hangout dedicated to discuss the common >>>>>>> 3D-UI architecture description was requested. >>>>>>> It has to be quite short notice because we also have to update >>>>>>> the page until Friday. >>>>>>> I prepared a doodle containing dates for today and tomorrow: >>>>>>> http://www.doodle.com/9gzbu6ggyiit3a6z >>>>>>> >>>>>>> Please register your availability asap, if you are involved in >>>>>>> the 3D-UI GE architecture. >>>>>>> If no time-slot fits for you please let me know. >>>>>>> >>>>>>> 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.eu >>>>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>>>> >>>>>> _______________________________________________ >>>>>> Fiware-miwi mailing list >>>>>> Fiware-miwi at lists.fi-ware.eu >>>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>>> >>>>> _______________________________________________ >>>>> Fiware-miwi mailing list >>>>> Fiware-miwi at lists.fi-ware.eu >>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>> >>> >>> >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni.alatalo at gmail.com Fri Jan 24 12:53:13 2014 From: toni.alatalo at gmail.com (Toni Alatalo) Date: Fri, 24 Jan 2014 13:53:13 +0200 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: References: Message-ID: <098835C1-B54B-4D01-A671-0E2EF53514B7@gmail.com> On 24 Jan 2014, at 12:26, Christof Marti wrote: > The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: > FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) Sorry am a bit confused: is this a) used as a correct example here, or b) point out that there is a problem with that currently? It is currently "[#6498] FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create? So it seems that you mean a) ? just doublechecking here in case I?m missing something. Ah I suppose you mean that the name/summary should include also that '(description: Deliverable = D.13.3.3)? thing, ok I?ll add those. Am almost considering writing some scripts to generate and verify these in case of errors, programmers are used to compilers or tests complaining in case of typos or misunderstandings etc :p ~Toni > or for update of the Architecture of the 3D-UI GE: > FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) > > or for creating the SW package: > FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver > > Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). > > Naming conventions for Features, UserStories etc can be found here: > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) > > 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 > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi From toni at playsign.net Fri Jan 24 12:56:43 2014 From: toni at playsign.net (Toni Alatalo) Date: Fri, 24 Jan 2014 13:56:43 +0200 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010BCA@EX10-MB2-MAD.hi.inet> References: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010BCA@EX10-MB2-MAD.hi.inet> Message-ID: On 24 Jan 2014, at 12:48, MANUEL ESCRICHE VICENTE wrote: > Please, let me a note on this sentence: > "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" > ->Features hold only as time frame Release > ->Stories, Bugs and WorkItems hold both Release and Sprint > ->Epics don't hold any timeframe Ok thanks for info, I think at least I've got these largely wrong because: current sprint is 3.3.1, right? upcoming release is 3.2, right? so the work we are currently doing is in 3.3.1 and coming out in release 3.2. but we should not mark it in the tracker like that but put also current activities for this release for the December sprint? I can change these when get a confirmation. ~Toni > -----Original Message----- > From: Christof Marti [mailto:mach at zhaw.ch] > Sent: viernes, 24 de enero de 2014 11:26 > To: FI-WARE, MiWi > Cc: MANUEL ESCRICHE VICENTE > Subject: historic open items in tracker and naming conventions > > Dear WP13 GE owners > > I was checking the tracker and still found some errors and naming inconistencies. > > There are still some historic entries, which are not closed or ?Finished but not released?. > Historic means belong to Release 3.2 (which ended in December). > https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse > I created a specific advanced query for these entries named "All historic open?. > > All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. > If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. > (e.g. with the line ?Deliverable = D.13.3.3?) > > List of actual deliverables: > D.13.1.2 GE Open Specificatoin (M30) > D.13.1.3 GE Open Specification (M33 or M36) > D.13.2.3 GE SW Release (M33) > D.13.3.3 GE Installation and Administration Guide (M33) > D.13.4.3 GE User and Programmer Guide (M33) > D.13.5.3 GE Unit Testing Plan & Report (M33) > D.2.3.3 FI-WARE Architecture V3 (M33) > D.2.4.3 FI-WARE Technical Roadmap V3 (M33) > > Please also check the naming patterns: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use > Specially also add the ?action? extension at the end. > > The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: > FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) > > or for update of the Architecture of the 3D-UI GE: > FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) > > or for creating the SW package: > FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver > > Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). > > Naming conventions for Features, UserStories etc can be found here: > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) > > 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 > > ________________________________ > > 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.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Fri Jan 24 13:00:32 2014 From: mach at zhaw.ch (Christof Marti) Date: Fri, 24 Jan 2014 13:00:32 +0100 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: <21dd7cc55263465e929013b6f9d63986@SRV-MAIL-001.zhaw.ch> References: <21dd7cc55263465e929013b6f9d63986@SRV-MAIL-001.zhaw.ch> Message-ID: <723B0591-E5AB-49CA-ADB0-96BDD8F304B0@zhaw.ch> Hi Toni The 3D-UI example was randomly chosen. I did not check if it was already correct. I simply observed that some of the GE entries did not follow the naming rules. And yes if possible the description should contain the deliverable entry, but also can contain more text describing the task. Christof Am 24.01.2014 um 12:53 schrieb Toni Alatalo : > On 24 Jan 2014, at 12:26, Christof Marti wrote: >> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) > > Sorry am a bit confused: is this a) used as a correct example here, or b) point out that there is a problem with that currently? > > It is currently "[#6498] FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create? > > So it seems that you mean a) ? just doublechecking here in case I?m missing something. > > Ah I suppose you mean that the name/summary should include also that '(description: Deliverable = D.13.3.3)? thing, ok I?ll add those. > > Am almost considering writing some scripts to generate and verify these in case of errors, programmers are used to compilers or tests complaining in case of typos or misunderstandings etc :p > > ~Toni > >> or for update of the Architecture of the 3D-UI GE: >> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >> >> or for creating the SW package: >> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >> >> Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). >> >> Naming conventions for Features, UserStories etc can be found here: >> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >> >> 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 >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi From mev at tid.es Fri Jan 24 13:08:25 2014 From: mev at tid.es (MANUEL ESCRICHE VICENTE) Date: Fri, 24 Jan 2014 12:08:25 +0000 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010BCA@EX10-MB2-MAD.hi.inet> Message-ID: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010D19@EX10-MB2-MAD.hi.inet> Toni, Current Sprint 3.3.1 - Current Release 3.3 You can see it in the dashboard [cid:image001.png at 01CF1905.092C9000] The whole picture of releases and sprints is available at the link below: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering Manuel From: Toni Alatalo [mailto:toni.alatalo at gmail.com] On Behalf Of Toni Alatalo Sent: viernes, 24 de enero de 2014 12:57 To: MANUEL ESCRICHE VICENTE Cc: Christof Marti; FI-WARE, MiWi Subject: Re: [Fiware-miwi] historic open items in tracker and naming conventions On 24 Jan 2014, at 12:48, MANUEL ESCRICHE VICENTE > wrote: Please, let me a note on this sentence: "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" ->Features hold only as time frame Release ->Stories, Bugs and WorkItems hold both Release and Sprint ->Epics don't hold any timeframe Ok thanks for info, I think at least I've got these largely wrong because: current sprint is 3.3.1, right? upcoming release is 3.2, right? so the work we are currently doing is in 3.3.1 and coming out in release 3.2. but we should not mark it in the tracker like that but put also current activities for this release for the December sprint? I can change these when get a confirmation. ~Toni -----Original Message----- From: Christof Marti [mailto:mach at zhaw.ch] Sent: viernes, 24 de enero de 2014 11:26 To: FI-WARE, MiWi Cc: MANUEL ESCRICHE VICENTE Subject: historic open items in tracker and naming conventions Dear WP13 GE owners I was checking the tracker and still found some errors and naming inconistencies. There are still some historic entries, which are not closed or "Finished but not released". Historic means belong to Release 3.2 (which ended in December). https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse I created a specific advanced query for these entries named "All historic open". All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. (e.g. with the line "Deliverable = D.13.3.3") List of actual deliverables: D.13.1.2 GE Open Specificatoin (M30) D.13.1.3 GE Open Specification (M33 or M36) D.13.2.3 GE SW Release (M33) D.13.3.3 GE Installation and Administration Guide (M33) D.13.4.3 GE User and Programmer Guide (M33) D.13.5.3 GE Unit Testing Plan & Report (M33) D.2.3.3 FI-WARE Architecture V3 (M33) D.2.4.3 FI-WARE Technical Roadmap V3 (M33) Please also check the naming patterns: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use Specially also add the "action" extension at the end. The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) or for update of the Architecture of the 3D-UI GE: FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) or for creating the SW package: FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver Watch also the difference between the GE naming "3D-UI" and the GEi naming "3D-UI-WebTundra" resp. "3D-UI-XML3D (only required if more then one implementation is available). Naming conventions for Features, UserStories etc can be found here: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) 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 ________________________________ 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.eu https://lists.fi-ware.eu/listinfo/fiware-miwi ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13608 bytes Desc: image001.png URL: From mach at zhaw.ch Fri Jan 24 13:06:51 2014 From: mach at zhaw.ch (Christof Marti) Date: Fri, 24 Jan 2014 13:06:51 +0100 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: References: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010BCA@EX10-MB2-MAD.hi.inet> Message-ID: <2E903D12-8B1E-46C3-82BB-DFEA6F7AAF49@zhaw.ch> Hi Toni No, we are already in Release 3.3 phase. Release 3.2 was due in December. All work items for sprint 3.3.1 should also have Relese 3.3 assigned. Features and items for R3.2 should be closed or ?Finished but not released?. The software we are releasing now is the one officially developed until end of December (R3.2) Next release will be 3.3 (in March). Christof Am 24.01.2014 um 12:56 schrieb Toni Alatalo : > On 24 Jan 2014, at 12:48, MANUEL ESCRICHE VICENTE wrote: >> Please, let me a note on this sentence: >> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" >> ->Features hold only as time frame Release >> ->Stories, Bugs and WorkItems hold both Release and Sprint >> ->Epics don't hold any timeframe > > Ok thanks for info, I think at least I've got these largely wrong because: > > current sprint is 3.3.1, right? > > upcoming release is 3.2, right? > > so the work we are currently doing is in 3.3.1 and coming out in release 3.2. > > but we should not mark it in the tracker like that but put also current activities for this release for the December sprint? > > I can change these when get a confirmation. > > ~Toni > >> -----Original Message----- >> From: Christof Marti [mailto:mach at zhaw.ch] >> Sent: viernes, 24 de enero de 2014 11:26 >> To: FI-WARE, MiWi >> Cc: MANUEL ESCRICHE VICENTE >> Subject: historic open items in tracker and naming conventions >> >> Dear WP13 GE owners >> >> I was checking the tracker and still found some errors and naming inconistencies. >> >> There are still some historic entries, which are not closed or ?Finished but not released?. >> Historic means belong to Release 3.2 (which ended in December). >> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >> I created a specific advanced query for these entries named "All historic open?. >> >> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. >> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. >> (e.g. with the line ?Deliverable = D.13.3.3?) >> >> List of actual deliverables: >> D.13.1.2 GE Open Specificatoin (M30) >> D.13.1.3 GE Open Specification (M33 or M36) >> D.13.2.3 GE SW Release (M33) >> D.13.3.3 GE Installation and Administration Guide (M33) >> D.13.4.3 GE User and Programmer Guide (M33) >> D.13.5.3 GE Unit Testing Plan & Report (M33) >> D.2.3.3 FI-WARE Architecture V3 (M33) >> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >> >> Please also check the naming patterns: >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >> Specially also add the ?action? extension at the end. >> >> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) >> >> or for update of the Architecture of the 3D-UI GE: >> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >> >> or for creating the SW package: >> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >> >> Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). >> >> Naming conventions for Features, UserStories etc can be found here: >> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >> >> 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 >> >> ________________________________ >> >> 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Fri Jan 24 13:19:11 2014 From: toni at playsign.net (Toni Alatalo) Date: Fri, 24 Jan 2014 14:19:11 +0200 Subject: [Fiware-miwi] historic open items in tracker and naming conventions In-Reply-To: <2E903D12-8B1E-46C3-82BB-DFEA6F7AAF49@zhaw.ch> References: <65CDBE2E7E5A964BB8BC5F4328FDE90BA3010BCA@EX10-MB2-MAD.hi.inet> <2E903D12-8B1E-46C3-82BB-DFEA6F7AAF49@zhaw.ch> Message-ID: I think that is what I said :) That is, in the tracker?s alternative reality the work we are doing today is in December, in sprint 3.2.something, for release 3.2 which is coming out now. If we do some work now which we don?t release next week then we can put that to sprint 3.3.1 I think. But most of the January work we are releasing next week. Thanks for the clarification, I?ll change ? that?s how I had those originally but got confused then yesterday evening when we looked at the official schedule in the wiki with Lasse (I think we had the same misconception untill now). ~Toni On 24 Jan 2014, at 14:06, Christof Marti wrote: > Hi Toni > > No, we are already in Release 3.3 phase. Release 3.2 was due in December. > All work items for sprint 3.3.1 should also have Relese 3.3 assigned. > Features and items for R3.2 should be closed or ?Finished but not released?. > The software we are releasing now is the one officially developed until end of December (R3.2) > Next release will be 3.3 (in March). > > > Christof > > Am 24.01.2014 um 12:56 schrieb Toni Alatalo : > >> On 24 Jan 2014, at 12:48, MANUEL ESCRICHE VICENTE wrote: >>> Please, let me a note on this sentence: >>> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" >>> ->Features hold only as time frame Release >>> ->Stories, Bugs and WorkItems hold both Release and Sprint >>> ->Epics don't hold any timeframe >> >> Ok thanks for info, I think at least I've got these largely wrong because: >> >> current sprint is 3.3.1, right? >> >> upcoming release is 3.2, right? >> >> so the work we are currently doing is in 3.3.1 and coming out in release 3.2. >> >> but we should not mark it in the tracker like that but put also current activities for this release for the December sprint? >> >> I can change these when get a confirmation. >> >> ~Toni >> >>> -----Original Message----- >>> From: Christof Marti [mailto:mach at zhaw.ch] >>> Sent: viernes, 24 de enero de 2014 11:26 >>> To: FI-WARE, MiWi >>> Cc: MANUEL ESCRICHE VICENTE >>> Subject: historic open items in tracker and naming conventions >>> >>> Dear WP13 GE owners >>> >>> I was checking the tracker and still found some errors and naming inconistencies. >>> >>> There are still some historic entries, which are not closed or ?Finished but not released?. >>> Historic means belong to Release 3.2 (which ended in December). >>> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >>> I created a specific advanced query for these entries named "All historic open?. >>> >>> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. >>> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. >>> (e.g. with the line ?Deliverable = D.13.3.3?) >>> >>> List of actual deliverables: >>> D.13.1.2 GE Open Specificatoin (M30) >>> D.13.1.3 GE Open Specification (M33 or M36) >>> D.13.2.3 GE SW Release (M33) >>> D.13.3.3 GE Installation and Administration Guide (M33) >>> D.13.4.3 GE User and Programmer Guide (M33) >>> D.13.5.3 GE Unit Testing Plan & Report (M33) >>> D.2.3.3 FI-WARE Architecture V3 (M33) >>> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >>> >>> Please also check the naming patterns: >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >>> Specially also add the ?action? extension at the end. >>> >>> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) >>> >>> or for update of the Architecture of the 3D-UI GE: >>> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >>> >>> or for creating the SW package: >>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >>> >>> Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). >>> >>> Naming conventions for Features, UserStories etc can be found here: >>> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>> >>> 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 >>> >>> ________________________________ >>> >>> 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.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lasse.oorni at ludocraft.com Fri Jan 24 17:12:37 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Fri, 24 Jan 2014 18:12:37 +0200 Subject: [Fiware-miwi] Virtual Characters GE dependency chain Message-ID: <5d49d85d041f360800de8d79f3b95dc1.squirrel@urho.ludocraft.com> Hi, here's the GE dependency chain document for Virtual Characters GE. There is not much to test as the dependency will be housed in the same WebTundra codebase so therefore it will always be satisfied as long as a stable version of the codebase is installed. Please let me know if this needs to be worded differently. And of course this is talking about future work - as of now there's no VirtualCharacters code in the WebTundra codebase yet. -- Lasse ??rni Game Programmer LudoCraft Ltd. -------------- next part -------------- A non-text attachment was scrubbed... Name: VirtualCharacters dependency chain.doc Type: application/msword Size: 41472 bytes Desc: not available URL: From jonne at adminotech.com Sat Jan 25 17:48:32 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Sat, 25 Jan 2014 18:48:32 +0200 Subject: [Fiware-miwi] Cloud Rendering GE dependency chain Message-ID: Cloud Rendering does not currently have dependencies to other FIWARE GEs. I did not fill your document, I would suppose there is no need if I don't have anything to put there? If its important to find some, we could port the cloud rendering web client input system to utilize the 2D-UI GE. We can do this for the next 3.3 release if it is desired. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Sun Jan 26 11:02:38 2014 From: toni at playsign.net (Toni Alatalo) Date: Sun, 26 Jan 2014 12:02:38 +0200 Subject: [Fiware-miwi] Cloud Rendering GE dependency chain In-Reply-To: References: Message-ID: Just for info that Tundra is listed as a GEi in the tracker at least, I think for the Synchronization GE. As the rendering + video sending part of the Cloud Rendering is implemented as a Tundra module, which obviously depends on Tundra, it might make sense to mention as a dependency. I'm not sure though how we should think of this here. ~Toni On Sat, Jan 25, 2014 at 6:48 PM, Jonne Nauha wrote: > Cloud Rendering does not currently have dependencies to other FIWARE GEs. > I did not fill your document, I would suppose there is no need if I don't > have anything to put there? > > If its important to find some, we could port the cloud rendering web > client input system to utilize the 2D-UI GE. We can do this for the next > 3.3 release if it is desired. > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jarkko at cyberlightning.com Sun Jan 26 12:20:38 2014 From: jarkko at cyberlightning.com (Jarkko Vatjus-Anttila) Date: Sun, 26 Jan 2014 13:20:38 +0200 Subject: [Fiware-miwi] Cloud Rendering GE dependency chain In-Reply-To: References: Message-ID: Christof, all, I am thinking the same how I should approach this from the perspective of 2D/3D capture and real/virtual interaction GEs. Those are both working standalone. 2D/3D capture as an additional tool for web developer (in a sense 3D-UI could be used as a dependency, even though it is not that exactly) and real/virtual is a service who provides data whenever someone asks. Naturally these are linked, but I find it difficult to see the connection from the perspective what the document expects. Should we still fill in something in these cases? On Sun, Jan 26, 2014 at 12:02 PM, Toni Alatalo wrote: > Just for info that Tundra is listed as a GEi in the tracker at least, I > think for the Synchronization GE. > > As the rendering + video sending part of the Cloud Rendering is > implemented as a Tundra module, which obviously depends on Tundra, it might > make sense to mention as a dependency. I'm not sure though how we should > think of this here. > > ~Toni > > > On Sat, Jan 25, 2014 at 6:48 PM, Jonne Nauha wrote: > >> Cloud Rendering does not currently have dependencies to other FIWARE GEs. >> I did not fill your document, I would suppose there is no need if I don't >> have anything to put there? >> >> If its important to find some, we could port the cloud rendering web >> client input system to utilize the 2D-UI GE. We can do this for the next >> 3.3 release if it is desired. >> >> Best regards, >> Jonne Nauha >> Meshmoon developer at Adminotech Ltd. >> www.meshmoon.com >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > -- Jarkko Vatjus-Anttila VP, Technology Cyberlightning Ltd. mobile. +358 405245142 email. jarkko at cyberlightning.com Go to www.cybersli.de and enrich your presentations! www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Philipp.Slusallek at dfki.de Mon Jan 27 06:23:26 2014 From: Philipp.Slusallek at dfki.de (Philipp Slusallek) Date: Mon, 27 Jan 2014 06:23:26 +0100 Subject: [Fiware-miwi] XML3D (<)-> reX EC mapping doc (Re: Hangout to discuss 3D-UI architecture) In-Reply-To: <52E24F2D.8070002@dfki.de> References: <153216d0aaa34e59a5b9a71dbdff810e@SRV-MAIL-001.zhaw.ch> <700727E7-34A0-4FFE-A9A3-0096D4A4CEA6@zhaw.ch> <940dfa8e7f354b87ab798bc301988e26@SRV-MAIL-001.zhaw.ch> <09BC58D4-EBD5-4DCD-849D-2AB70882418C@zhaw.ch> <52E24F2D.8070002@dfki.de> Message-ID: <52E5ED4E.60406@dfki.de> Hi, Looks fine to me! Best, Philipp Am 24.01.2014 12:31, schrieb Torsten Spieldenner: > Hello, > > I have now included the points Toni has sent earlier into the 3D UI > Architecture description. It constitutes a new subsection in the "Main > Interactions" chapter: > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI#Mapping_Synchronization_GE_data_to_XML3D_objects > > I have switched the direction of the mapping in the descriptions, > where possible, as from the point of 3D UI, I rather see the need to map > the provided EC model to something we can express in terms of the 3D UI > principles. > > ~ Torsten > > Am 1/24/2014 9:49 AM, schrieb Christof Marti: >> Hi >> >> Regarding the question what has to go to the Architecture and what to >> the OpenSpecification. >> The architecture should contain as much info to understand the >> structure, the dependencies and how the things work and interoperate. >> It also contains the introduction of the basic elements. >> >> The detailed format of the models and protocols, and listings of >> attributes, values and types and mappings can then be in separate >> documents, which are part of the Open Specification. >> >> Cheers >> Christof >> >> Am 24.01.2014 um 09:14 schrieb Torsten Spieldenner >> >: >> >>> Hello, >>> >>> thank you very much for the mappings. I'll add those to the 3D UI >>> Architecture page then and give a notice when I'm done so you can >>> have a look. >>> >>> ~Torsten >>> >>> >>> Am 1/24/2014 8:07 AM, schrieb Toni Alatalo: >>>> As planned in the meeting yesterday, we?ll document the co-use of >>>> the XML3D vocabulary (which is somewhat identical with the reX >>>> components already) and the reX EC model ? for the integrated use of >>>> 3D-UI and Sync. >>>> >>>> I started a draft in a gdoc, is also pasted below: >>>> https://docs.google.com/document/d/1OgU7hAatSAH3foGZ1ngWCv8xagyOlKkG8C5CQOQwExo/edit >>>> >>>> Torsten can perhaps take this forward towards integration to the >>>> arch etc docs? IIRC Philipp also said he'll have some chances later >>>> today or during the weekend (Christof needs this by Sunday to ship >>>> on Monday - can and will of course be improved later but some sort >>>> of first version). Feel free to either work on & comment in the gdoc >>>> or move to the wiki suitably. I?m busy with other things till noon >>>> now but can return to this in the afternoon (and Erno can check this >>>> today too). >>>> >>>> ~Toni >>>> >>>> The scene model to integrate 3DUI & Synchronization >>>> >>>> To integrate 3D-UI with network synchronization an abstract scene >>>> model is used in the client core. It is implemented as a Javascript >>>> library and also provides the JS API for application developers to >>>> create and manipulate the scene. It uses the realXtend >>>> Entity-Component (reX EC for short) model, which is also used in the >>>> network protocol and on the server when implementing networked >>>> multi-user applications. The same API is used on the server side for >>>> scene manipulations. Here we describe the mapping from the XML3D >>>> structure and vocabulary to the realXtend scene model with entities, >>>> components and attributes. In this description XML3D is in bolded >>>> xml tags (e.g. ) and the reX EC mapping in Javascript in >>>> italic (e.g. entity.mesh). >>>> >>>> 1. >>>> XML3D elements are reX EC entities: entity >>>> 2. >>>> XML3D elements inside a group, for example and , >>>> are corresponding reX EC components attached to the entity: >>>> entity.mesh, entity.light >>>> 3. >>>> A single XML3D element without an encapsulating is also >>>> a reX EC entity with the corresponding component. That is, >>>> is same as : entity.mesh. >>>> 4. >>>> XML3D is mapped to the reX EC Placeable >>>> component which has the same transform matrix as the transform >>>> attribute correspondingly: entity.placeable.transform >>>> 5. >>>> XML3D elements are mapped to corresponding reX EC camera >>>> components: entity.camera. The camera for the view is >>>> automatically set as the active one (the scene can have multiple >>>> cameras simultaneously but only one can be used for one view). >>>> 6. >>>> Hierarchical XML (nested tags) in XML3D is mapped to identical >>>> hierarchy of entities in reX EC. (implementation NOTE: >>>> hierarchical structure is not implemented in reX EC yet, current >>>> implementation of the mapping uses placeable parent reference >>>> attributes. This will change in coming releases) >>>> 7. >>>> XML3D element attributes, for example , are mapped >>>> to the corresponding reX EC attributes: entity.mesh.meshRef.x. >>>> Harmonising the attribute names to have them the same everywhere >>>> is under consideration. >>>> 8. >>>> XML element attributes unknown to the reX EC scene vocabulary >>>> (existing Tundra components) are mapped directly: >>> myattr=x>is myentity.myattr.x. (implementation NOTE: proper >>>> implementation for arbitrary types in the networked system is >>>> not yet implemented). >>>> >>>> >>>> The API to create, remove and listen for changes in the scene is >>>> documented in the Synchronization GE docs. >>>> >>>> ----- >>>> 1) The client core (in WebTundra) uses it also when running in >>>> standalone mode for single user applications, without using a server >>>> and the Synchronization GE overall. >>>> 2) This might actually currently require ent.mesh.meshRef.ref (with >>>> that additional .ref at the end) due to using an AssetReference type >>>> instead of just a string for the ref like in src - let?s consider >>>> changing that >>>> >>>> >>>> On 23 Jan 2014, at 15:01, Christof Marti >>> > wrote: >>>> >>>>> Hi >>>>> >>>>> Here is the hangout link for the meeting: >>>>> https://plus.google.com/hangouts/_/7acpjrv7f2be4bmhtjela651hk?hl=de >>>>> >>>>> Cheers Christof >>>>> >>>>> Am 23.01.2014 um 09:18 schrieb Marti Christof (mach) >>>> >: >>>>> >>>>>> Thanks Toni >>>>>> >>>>>> It looks like today 14:00-15:00 is the best option. Would be great >>>>>> if Philipp can join then too (Had no feedback so far). >>>>>> >>>>>> Best regards >>>>>> Christof >>>>>> >>>>>> Am 22.01.2014 um 17:01 schrieb Toni Alatalo >>>>> >: >>>>>> >>>>>>> A bit about the agenda: What prompted this to me now was reading >>>>>>> our arch doc & 3DUI and Sync GE docs. I find the overall arch doc >>>>>>> does an ok job for now for describing the whole, but the GE ones >>>>>>> are from different worlds. They are both fine as themselves but >>>>>>> don?t tell how they should work and be used together (which the >>>>>>> arch doc does promise). >>>>>>> >>>>>>> The docs in question: >>>>>>> Overall Arch: >>>>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Advanced_Middleware_and_Web_UI_Architecture >>>>>>> 3DUI GE: >>>>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.3D-UI >>>>>>> Sync GE: >>>>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.MiWi.Synchronization >>>>>>> >>>>>>> The question I think we should answer clearly for app developers >>>>>>> is: what is the API one should use to develop an app for the >>>>>>> overall arch. >>>>>>> >>>>>>> I?ll post separate notes about the meet we had last Thu about >>>>>>> xml3d support in WebTundra in general & especially how net sync >>>>>>> of xml3d data is planned to work there ? have the notes about it >>>>>>> on paper now but need to type it, either later this evening or >>>>>>> tomorrow before this session. It is a bit a different topic but >>>>>>> closely related. >>>>>>> >>>>>>> Cheers, >>>>>>> ~Toni >>>>>>> >>>>>>> On 22 Jan 2014, at 14:51, Christof Marti >>>>>> > wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> At the meeting a short hangout dedicated to discuss the common >>>>>>>> 3D-UI architecture description was requested. >>>>>>>> It has to be quite short notice because we also have to update >>>>>>>> the page until Friday. >>>>>>>> I prepared a doodle containing dates for today and tomorrow: >>>>>>>> http://www.doodle.com/9gzbu6ggyiit3a6z >>>>>>>> >>>>>>>> Please register your availability asap, if you are involved in >>>>>>>> the 3D-UI GE architecture. >>>>>>>> If no time-slot fits for you please let me know. >>>>>>>> >>>>>>>> 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.eu >>>>>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Fiware-miwi mailing list >>>>>>> Fiware-miwi at lists.fi-ware.eu >>>>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>>>> >>>>>> _______________________________________________ >>>>>> Fiware-miwi mailing list >>>>>> Fiware-miwi at lists.fi-ware.eu >>>>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Fiware-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum f?r K?nstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Gesch?ftsf?hrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: From mach at zhaw.ch Mon Jan 27 15:01:54 2014 From: mach at zhaw.ch (Christof Marti) Date: Mon, 27 Jan 2014 15:01:54 +0100 Subject: [Fiware-miwi] MiWi Tracker - Status and Advanced Queries In-Reply-To: <21cb3615cd9142fb84ca123452d332a5@SRV-MAIL-001.zhaw.ch> References: <21cb3615cd9142fb84ca123452d332a5@SRV-MAIL-001.zhaw.ch> Message-ID: <2C665781-6310-4520-AADE-EE3CE1FC417A@zhaw.ch> Dear GE owners Since my mail last Wednesday and Friday a lot of you updated the tracker entries for your GEi. The tracker looks much better now (congratulations!!) While checking today I still found some inconsistancies and errors. To help you get a better overview I created several Advanced Queries: 01 All roadmap: All entries scheduled for future sprints (3.3.2, 3.3.3) 02 All backlog: All entries valid for the current sprint 3.3.1 (including empty sprint assignment) 03 All historic: All entries from previous Releases (3.2 and older) 04 All historic and open: All entries for previous Releases which are still open, under execution or scheduled. + queries for each GEi showing all entries of that specific GEi You?ll find these queries in the ?Advanced queries? tab of the tracker. https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse All entries in "04 All historic and open? are errors and should be fixed immediately. All items for Release 3.2 should be closed or "finished but not delivered" (or dismissed). As explained in the mail from last Friday, all entries with Sprint 3.3.x should also have Release 3.3. If you are working on the documentation or software packaging of R3.2, this can be stated in the description field. Entries in ?02 All backlog? are the items/stories/features you are working on currently. including the Features for Release 3.3 (which have no sprint no. assigned to them). You should always have some Work Items, Stories assigned to the current Sprint (3.3.1 at this date) Entries in ?01 All roadmap? are items/stories/features planned for future sprints (3.3.2 or 3.3.3) Because we are approaching the end of Sprint 3.3.1 you should have some entries scheduled/assigned to next sprints. Please verify also the naming of Work Item entries as explained in my mail from last Friday (see below). There are still documentation (or software) items, which do not specify the type of document and the action. And last but not least. Please verify the Features you have in the tracker with the Features you have on the ?Technical Roadmap? wiki page. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI Are they all available (in tracker and wiki) and are they in the correct release (3.1, 3.2 or 3.3). The ?Technical Roadmap? page contains some GEi?s which have no Features planned for R3.3 (3D-UI, Display as a Service, GIS data provider, POI data provider, Augmented Reality). There is still missing the plain text short description of the features in the first part of the document for Interface Designer. https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#Advanced_Web_User_Interfaces_-_Application-oriented_Services Thanks for fixing the current errors and keeping the tracker up to date. Best regards Christof Am 24.01.2014 um 11:48 schrieb MANUEL ESCRICHE VICENTE : > Please, let me a note on this sentence: > "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" > ->Features hold only as time frame Release > ->Stories, Bugs and WorkItems hold both Release and Sprint > ->Epics don't hold any timeframe > > -----Original Message----- > From: Christof Marti [mailto:mach at zhaw.ch] > Sent: viernes, 24 de enero de 2014 11:26 > To: FI-WARE, MiWi > Cc: MANUEL ESCRICHE VICENTE > Subject: historic open items in tracker and naming conventions > > Dear WP13 GE owners > > I was checking the tracker and still found some errors and naming inconistencies. > > There are still some historic entries, which are not closed or ?Finished but not released?. > Historic means belong to Release 3.2 (which ended in December). > https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse > I created a specific advanced query for these entries named "All historic open?. > > All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. > If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. > (e.g. with the line ?Deliverable = D.13.3.3?) > > List of actual deliverables: > D.13.1.2 GE Open Specificatoin (M30) > D.13.1.3 GE Open Specification (M33 or M36) > D.13.2.3 GE SW Release (M33) > D.13.3.3 GE Installation and Administration Guide (M33) > D.13.4.3 GE User and Programmer Guide (M33) > D.13.5.3 GE Unit Testing Plan & Report (M33) > D.2.3.3 FI-WARE Architecture V3 (M33) > D.2.4.3 FI-WARE Technical Roadmap V3 (M33) > > Please also check the naming patterns: > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use > Specially also add the ?action? extension at the end. > > The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: > FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) > > or for update of the Architecture of the 3D-UI GE: > FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) > > or for creating the SW package: > FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver > > Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). > > Naming conventions for Features, UserStories etc can be found here: > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) > > 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 > > ________________________________ > > 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 Mon Jan 27 15:11:28 2014 From: torsten.spieldenner at dfki.de (Torsten Spieldenner) Date: Mon, 27 Jan 2014 15:11:28 +0100 Subject: [Fiware-miwi] MiWi Tracker - Status and Advanced Queries In-Reply-To: <2C665781-6310-4520-AADE-EE3CE1FC417A@zhaw.ch> References: <21cb3615cd9142fb84ca123452d332a5@SRV-MAIL-001.zhaw.ch> <2C665781-6310-4520-AADE-EE3CE1FC417A@zhaw.ch> Message-ID: <52E66910.80801@dfki.de> Hello, > And last but not least.*Please verify the Features you have in the > tracker with the Features you have on the "Technical Roadmap" wiki page*. > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI > Are they all available (in tracker and wiki) and are they in the > correct release (3.1, 3.2 or 3.3). Thanks for pointing this out, I corrected the Release in the tracker, but actually forgot to adapt the entries in the Roadmap page. The entries for 3D-UI and DaaS should now appear under the correct Release in both. Best regards, Torsten > The "Technical Roadmap" page contains some GEi's which have*no > Features planned for R3.3* (3D-UI, Display as a Service, GIS data > provider, POI data provider, Augmented Reality). > There is still *missing the plain text short description of the > features* in the first part of the document for Interface Designer. > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#Advanced_Web_User_Interfaces_-_Application-oriented_Services > > Thanks for fixing the current errors and keeping the tracker up to date. > > Best regards > Christof > > > Am 24.01.2014 um 11:48 schrieb MANUEL ESCRICHE VICENTE >: > >> Please, let me a note on this sentence: >> "All entries which are executed in Sprint 3.3.x should also have >> Release 3.3 assigned" >> ->Features hold only as time frame Release >> ->Stories, Bugs and WorkItems hold both Release and Sprint >> ->Epics don't hold any timeframe >> >> -----Original Message----- >> From: Christof Marti [mailto:mach at zhaw.ch] >> Sent: viernes, 24 de enero de 2014 11:26 >> To: FI-WARE, MiWi >> Cc: MANUEL ESCRICHE VICENTE >> Subject: historic open items in tracker and naming conventions >> >> Dear WP13 GE owners >> >> I was checking the tracker and still found some errors and naming >> inconistencies. >> >> There are still some historic entries, which are not closed or >> "Finished but not released". >> Historic means belong to Release 3.2 (which ended in December). >> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >> I created a specific advanced query for these entries named "All >> historic open". >> >> All entries which are executed in Sprint 3.3.x should also have >> Release 3.3 assigned. >> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) >> then this should be expressed in the description. >> (e.g. with the line "Deliverable = D.13.3.3") >> >> List of actual deliverables: >> D.13.1.2 GE Open Specificatoin (M30) >> D.13.1.3 GE Open Specification (M33 or M36) >> D.13.2.3 GE SW Release (M33) >> D.13.3.3 GE Installation and Administration Guide (M33) >> D.13.4.3 GE User and Programmer Guide (M33) >> D.13.5.3 GE Unit Testing Plan & Report (M33) >> D.2.3.3 FI-WARE Architecture V3 (M33) >> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >> >> Please also check the naming patterns: >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >> Specially also add the "action" extension at the end. >> >> The name (Summary) for creation of the Installation and >> Administration Guide for 3D-UI WebTundra GEi should be for example: >> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create >> (description: Deliverable = D.13.3.3) >> >> or for update of the Architecture of the 3D-UI GE: >> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update >> (description:D.2.3.3) >> >> or for creating the SW package: >> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >> >> Watch also the difference between the GE naming "3D-UI" and the GEi >> naming "3D-UI-WebTundra" resp. "3D-UI-XML3D (only required if >> more then one implementation is available). >> >> Naming conventions for Features, UserStories etc can be found here: >> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >> >> 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 >> >> ________________________________ >> >> 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.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Mon Jan 27 15:33:38 2014 From: mach at zhaw.ch (Christof Marti) Date: Mon, 27 Jan 2014 15:33:38 +0100 Subject: [Fiware-miwi] MiWi Tracker - Status and Advanced Queries In-Reply-To: References: <21cb3615cd9142fb84ca123452d332a5@SRV-MAIL-001.zhaw.ch> <2C665781-6310-4520-AADE-EE3CE1FC417A@zhaw.ch> Message-ID: <4F31E87B-9CE3-4B9D-A9AE-73E96862955F@zhaw.ch> Hi Torsten, Hi Toni Regarding the roadmap wiki-page, we need some more work to have separate entries for the two versions. I copied the 3D-UI feature description in the first part of the document and the 3D-UI row in the table and created an entry for the XML3D- and the WebTundra-version. Can you please update your parts of the document to reflect the features/descriptions and roadmap of your implementation. Thanks Christof Am 27.01.2014 um 15:11 schrieb Torsten Spieldenner : > Hello, > >> And last but not least. Please verify the Features you have in the tracker with the Features you have on the ?Technical Roadmap? wiki page. >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI >> Are they all available (in tracker and wiki) and are they in the correct release (3.1, 3.2 or 3.3). > Thanks for pointing this out, I corrected the Release in the tracker, but actually forgot to adapt the entries in the Roadmap page. The entries for 3D-UI and DaaS should now appear under the correct Release in both. > > Best regards, > Torsten > > > > >> The ?Technical Roadmap? page contains some GEi?s which have no Features planned for R3.3 (3D-UI, Display as a Service, GIS data provider, POI data provider, Augmented Reality). >> There is still missing the plain text short description of the features in the first part of the document for Interface Designer. >> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#Advanced_Web_User_Interfaces_-_Application-oriented_Services >> >> Thanks for fixing the current errors and keeping the tracker up to date. >> >> Best regards >> Christof >> >> >> Am 24.01.2014 um 11:48 schrieb MANUEL ESCRICHE VICENTE : >> >>> Please, let me a note on this sentence: >>> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" >>> ->Features hold only as time frame Release >>> ->Stories, Bugs and WorkItems hold both Release and Sprint >>> ->Epics don't hold any timeframe >>> >>> -----Original Message----- >>> From: Christof Marti [mailto:mach at zhaw.ch] >>> Sent: viernes, 24 de enero de 2014 11:26 >>> To: FI-WARE, MiWi >>> Cc: MANUEL ESCRICHE VICENTE >>> Subject: historic open items in tracker and naming conventions >>> >>> Dear WP13 GE owners >>> >>> I was checking the tracker and still found some errors and naming inconistencies. >>> >>> There are still some historic entries, which are not closed or ?Finished but not released?. >>> Historic means belong to Release 3.2 (which ended in December). >>> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >>> I created a specific advanced query for these entries named "All historic open?. >>> >>> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. >>> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. >>> (e.g. with the line ?Deliverable = D.13.3.3?) >>> >>> List of actual deliverables: >>> D.13.1.2 GE Open Specificatoin (M30) >>> D.13.1.3 GE Open Specification (M33 or M36) >>> D.13.2.3 GE SW Release (M33) >>> D.13.3.3 GE Installation and Administration Guide (M33) >>> D.13.4.3 GE User and Programmer Guide (M33) >>> D.13.5.3 GE Unit Testing Plan & Report (M33) >>> D.2.3.3 FI-WARE Architecture V3 (M33) >>> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >>> >>> Please also check the naming patterns: >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >>> Specially also add the ?action? extension at the end. >>> >>> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) >>> >>> or for update of the Architecture of the 3D-UI GE: >>> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >>> >>> or for creating the SW package: >>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >>> >>> Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). >>> >>> Naming conventions for Features, UserStories etc can be found here: >>> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>> >>> 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 >>> >>> ________________________________ >>> >>> 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.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Mon Jan 27 15:51:07 2014 From: toni at playsign.net (Toni Alatalo) Date: Mon, 27 Jan 2014 16:51:07 +0200 Subject: [Fiware-miwi] MiWi Tracker - Status and Advanced Queries In-Reply-To: <4F31E87B-9CE3-4B9D-A9AE-73E96862955F@zhaw.ch> References: <21cb3615cd9142fb84ca123452d332a5@SRV-MAIL-001.zhaw.ch> <2C665781-6310-4520-AADE-EE3CE1FC417A@zhaw.ch> <4F31E87B-9CE3-4B9D-A9AE-73E96862955F@zhaw.ch> Message-ID: <7C85AF86-C23A-4854-9E87-C9D3137EE5AA@playsign.net> Thank you for this Christof, I edited the pages and the tracker now to match reality. A question: how urgent is it to define the features for the 3.3 release? We have one planned already last year to that and it was in the tracker & wiki all, the RecommendedAssetPipeline ? it just didn?t show due to how the sprint was assigned I think .. now it shows in the queries. We have plans and have now began programming others too but if it?s OK we?d like to focus on shipping the current release first (on/by Wed) and then fill in more of the plans for the March release (on Thu & Fri etc). ~Toni On 27 Jan 2014, at 16:33, Christof Marti wrote: > Hi Torsten, Hi Toni > > Regarding the roadmap wiki-page, we need some more work to have separate entries for the two versions. > > I copied the 3D-UI feature description in the first part of the document and the 3D-UI row in the table and created an entry for the XML3D- and the WebTundra-version. > Can you please update your parts of the document to reflect the features/descriptions and roadmap of your implementation. > > Thanks > Christof > > Am 27.01.2014 um 15:11 schrieb Torsten Spieldenner : > >> Hello, >> >>> And last but not least. Please verify the Features you have in the tracker with the Features you have on the ?Technical Roadmap? wiki page. >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI >>> Are they all available (in tracker and wiki) and are they in the correct release (3.1, 3.2 or 3.3). >> Thanks for pointing this out, I corrected the Release in the tracker, but actually forgot to adapt the entries in the Roadmap page. The entries for 3D-UI and DaaS should now appear under the correct Release in both. >> >> Best regards, >> Torsten >> >> >> >> >>> The ?Technical Roadmap? page contains some GEi?s which have no Features planned for R3.3 (3D-UI, Display as a Service, GIS data provider, POI data provider, Augmented Reality). >>> There is still missing the plain text short description of the features in the first part of the document for Interface Designer. >>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#Advanced_Web_User_Interfaces_-_Application-oriented_Services >>> >>> Thanks for fixing the current errors and keeping the tracker up to date. >>> >>> Best regards >>> Christof >>> >>> >>> Am 24.01.2014 um 11:48 schrieb MANUEL ESCRICHE VICENTE : >>> >>>> Please, let me a note on this sentence: >>>> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" >>>> ->Features hold only as time frame Release >>>> ->Stories, Bugs and WorkItems hold both Release and Sprint >>>> ->Epics don't hold any timeframe >>>> >>>> -----Original Message----- >>>> From: Christof Marti [mailto:mach at zhaw.ch] >>>> Sent: viernes, 24 de enero de 2014 11:26 >>>> To: FI-WARE, MiWi >>>> Cc: MANUEL ESCRICHE VICENTE >>>> Subject: historic open items in tracker and naming conventions >>>> >>>> Dear WP13 GE owners >>>> >>>> I was checking the tracker and still found some errors and naming inconistencies. >>>> >>>> There are still some historic entries, which are not closed or ?Finished but not released?. >>>> Historic means belong to Release 3.2 (which ended in December). >>>> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >>>> I created a specific advanced query for these entries named "All historic open?. >>>> >>>> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. >>>> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. >>>> (e.g. with the line ?Deliverable = D.13.3.3?) >>>> >>>> List of actual deliverables: >>>> D.13.1.2 GE Open Specificatoin (M30) >>>> D.13.1.3 GE Open Specification (M33 or M36) >>>> D.13.2.3 GE SW Release (M33) >>>> D.13.3.3 GE Installation and Administration Guide (M33) >>>> D.13.4.3 GE User and Programmer Guide (M33) >>>> D.13.5.3 GE Unit Testing Plan & Report (M33) >>>> D.2.3.3 FI-WARE Architecture V3 (M33) >>>> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >>>> >>>> Please also check the naming patterns: >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >>>> Specially also add the ?action? extension at the end. >>>> >>>> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) >>>> >>>> or for update of the Architecture of the 3D-UI GE: >>>> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >>>> >>>> or for creating the SW package: >>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >>>> >>>> Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). >>>> >>>> Naming conventions for Features, UserStories etc can be found here: >>>> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>>> >>>> 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 >>>> >>>> ________________________________ >>>> >>>> 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.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Mon Jan 27 16:18:03 2014 From: mach at zhaw.ch (Christof Marti) Date: Mon, 27 Jan 2014 16:18:03 +0100 Subject: [Fiware-miwi] MiWi Tracker - Status and Advanced Queries In-Reply-To: References: <21cb3615cd9142fb84ca123452d332a5@SRV-MAIL-001.zhaw.ch> <2C665781-6310-4520-AADE-EE3CE1FC417A@zhaw.ch> <4F31E87B-9CE3-4B9D-A9AE-73E96862955F@zhaw.ch> Message-ID: Hi Toni You have to distinguish between Features and User Stories. Features contain broader functionality to be implemented within 1 Minor release cycle (3.1, 3.2, 3.3,...) which is typically 3 month (3 sprints). User Stories are more specific functionalities to be implemented within 1 month (1 sprint). So the basic idea is to split up features in several User Stories and schedule them in sprints. The Features for Minor Release 3.3 (January to March) should already be defined and in the roadmap. It is important to have them asap. The User Stories/Work Items for February (3.3.2) or March (3.3.3) should be available at the begin of the related sprint (or earlier). In your case the Features should already be available (if not please add before Thursday), They have to be in the Report going to the EC. (Features have to be in the tracker and the wiki.) The User Stories (Code) & Work Items (all the rest) for the current Sprint (3.3.1) should also be in the tracker already. Would be nice if the ones for February/March (3.3.2/3.3.3) would be available in the tracker end of this week. Best regards Christof Am 27.01.2014 um 15:51 schrieb Toni Alatalo : > Thank you for this Christof, I edited the pages and the tracker now to match reality. > > A question: how urgent is it to define the features for the 3.3 release? We have one planned already last year to that and it was in the tracker & wiki all, the RecommendedAssetPipeline ? it just didn?t show due to how the sprint was assigned I think .. now it shows in the queries. We have plans and have now began programming others too but if it?s OK we?d like to focus on shipping the current release first (on/by Wed) and then fill in more of the plans for the March release (on Thu & Fri etc). > > ~Toni > > On 27 Jan 2014, at 16:33, Christof Marti wrote: > >> Hi Torsten, Hi Toni >> >> Regarding the roadmap wiki-page, we need some more work to have separate entries for the two versions. >> >> I copied the 3D-UI feature description in the first part of the document and the 3D-UI row in the table and created an entry for the XML3D- and the WebTundra-version. >> Can you please update your parts of the document to reflect the features/descriptions and roadmap of your implementation. >> >> Thanks >> Christof >> >> Am 27.01.2014 um 15:11 schrieb Torsten Spieldenner : >> >>> Hello, >>> >>>> And last but not least. Please verify the Features you have in the tracker with the Features you have on the ?Technical Roadmap? wiki page. >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI >>>> Are they all available (in tracker and wiki) and are they in the correct release (3.1, 3.2 or 3.3). >>> Thanks for pointing this out, I corrected the Release in the tracker, but actually forgot to adapt the entries in the Roadmap page. The entries for 3D-UI and DaaS should now appear under the correct Release in both. >>> >>> Best regards, >>> Torsten >>> >>> >>> >>> >>>> The ?Technical Roadmap? page contains some GEi?s which have no Features planned for R3.3 (3D-UI, Display as a Service, GIS data provider, POI data provider, Augmented Reality). >>>> There is still missing the plain text short description of the features in the first part of the document for Interface Designer. >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#Advanced_Web_User_Interfaces_-_Application-oriented_Services >>>> >>>> Thanks for fixing the current errors and keeping the tracker up to date. >>>> >>>> Best regards >>>> Christof >>>> >>>> >>>> Am 24.01.2014 um 11:48 schrieb MANUEL ESCRICHE VICENTE : >>>> >>>>> Please, let me a note on this sentence: >>>>> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" >>>>> ->Features hold only as time frame Release >>>>> ->Stories, Bugs and WorkItems hold both Release and Sprint >>>>> ->Epics don't hold any timeframe >>>>> >>>>> -----Original Message----- >>>>> From: Christof Marti [mailto:mach at zhaw.ch] >>>>> Sent: viernes, 24 de enero de 2014 11:26 >>>>> To: FI-WARE, MiWi >>>>> Cc: MANUEL ESCRICHE VICENTE >>>>> Subject: historic open items in tracker and naming conventions >>>>> >>>>> Dear WP13 GE owners >>>>> >>>>> I was checking the tracker and still found some errors and naming inconistencies. >>>>> >>>>> There are still some historic entries, which are not closed or ?Finished but not released?. >>>>> Historic means belong to Release 3.2 (which ended in December). >>>>> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >>>>> I created a specific advanced query for these entries named "All historic open?. >>>>> >>>>> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. >>>>> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. >>>>> (e.g. with the line ?Deliverable = D.13.3.3?) >>>>> >>>>> List of actual deliverables: >>>>> D.13.1.2 GE Open Specificatoin (M30) >>>>> D.13.1.3 GE Open Specification (M33 or M36) >>>>> D.13.2.3 GE SW Release (M33) >>>>> D.13.3.3 GE Installation and Administration Guide (M33) >>>>> D.13.4.3 GE User and Programmer Guide (M33) >>>>> D.13.5.3 GE Unit Testing Plan & Report (M33) >>>>> D.2.3.3 FI-WARE Architecture V3 (M33) >>>>> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >>>>> >>>>> Please also check the naming patterns: >>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >>>>> Specially also add the ?action? extension at the end. >>>>> >>>>> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >>>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) >>>>> >>>>> or for update of the Architecture of the 3D-UI GE: >>>>> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >>>>> >>>>> or for creating the SW package: >>>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >>>>> >>>>> Watch also the difference between the GE naming ?3D-UI? and the GEi naming ?3D-UI-WebTundra? resp. "3D-UI-XML3D (only required if more then one implementation is available). >>>>> >>>>> Naming conventions for Features, UserStories etc can be found here: >>>>> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>>>> >>>>> 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 >>>>> >>>>> ________________________________ >>>>> >>>>> 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.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonne at adminotech.com Tue Jan 28 15:28:06 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Tue, 28 Jan 2014 16:28:06 +0200 Subject: [Fiware-miwi] Release files - MIWI section missing? Message-ID: So if I have understood correctly this is the place where we should put the files https://forge.fi-ware.eu/frs/?group_id=7 The main files page for forge. It however does not have a "MIWI" section, only "MIWI-KIARA-Middleware". Is someone going to make this and what the name should be? I see in the "To create a new release click here." link there is a "Or create a new package" that probably does what I'm looking for. Am I missing something, please let me know :) It would also be helpful if you could tell if there is a specific naming schema for the files. Thanks. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Tue Jan 28 16:19:12 2014 From: mach at zhaw.ch (Christof Marti) Date: Tue, 28 Jan 2014 16:19:12 +0100 Subject: [Fiware-miwi] Release files - MIWI section missing? In-Reply-To: References: Message-ID: Hi Jonne Yes the link (tool) is correct. Instructions are here: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware The process is a bit complex. - In principle you have to create a package first ?MIWI-GEiname? - After this you create the release ?3.2.3" and upload a first file. - Then you add the additional files to that release. Schema is only given for the package name and release. You can name the files as you like (especially internal version numbers), but best is to check the others and see what they use and what makes sense to you. (Place to look for the files should also be explained in the install manuals, if required) Christof Am 28.01.2014 um 15:28 schrieb Jonne Nauha : > So if I have understood correctly this is the place where we should put the files https://forge.fi-ware.eu/frs/?group_id=7 > > The main files page for forge. It however does not have a "MIWI" section, only "MIWI-KIARA-Middleware". Is someone going to make this and what the name should be? > > I see in the "To create a new release click here." link there is a "Or create a new package" that probably does what I'm looking for. > > Am I missing something, please let me know :) It would also be helpful if you could tell if there is a specific naming schema for the files. > > Thanks. > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonne at adminotech.com Tue Jan 28 16:42:55 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Tue, 28 Jan 2014 17:42:55 +0200 Subject: [Fiware-miwi] Release files - MIWI section missing? In-Reply-To: References: Message-ID: Thanks. Lasse pointed me to this tutorial on IRC :) I have made a .msi .zip and source .zip release for the Cloud Rendering Renderer GEi to the file section. The service and web client are coming in tomorrow. I have also updated all documentation to point to these file. Uploading seemed to work well at least for me, and i had ~110mb installers so seems the system is working ok :) Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com On Tue, Jan 28, 2014 at 5:19 PM, Christof Marti wrote: > Hi Jonne > > Yes the link (tool) is correct. > Instructions are here: > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware > > The process is a bit complex. > - In principle you have to create a package first "MIWI-GEiname" > - After this you create the release "3.2.3" and upload a first file. > - Then you add the additional files to that release. > > Schema is only given for the package name and release. You can name the > files as you like (especially internal version numbers), but best is to > check the others and see what they use and what makes sense to you. (Place > to look for the files should also be explained in the install manuals, if > required) > > Christof > > > Am 28.01.2014 um 15:28 schrieb Jonne Nauha : > > So if I have understood correctly this is the place where we should put > the files https://forge.fi-ware.eu/frs/?group_id=7 > > The main files page for forge. It however does not have a "MIWI" > section, only "MIWI-KIARA-Middleware". Is someone going to make this and > what the name should be? > > I see in the "To create a new release click here." link > there is a "Or create a new package" > that probably does what I'm looking for. > > Am I missing something, please let me know :) It would also be helpful > if you could tell if there is a specific naming schema for the files. > > Thanks. > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antti.karhu at cie.fi Wed Jan 29 08:22:29 2014 From: antti.karhu at cie.fi (Antti Karhu) Date: Wed, 29 Jan 2014 09:22:29 +0200 Subject: [Fiware-miwi] Features in roadmap wiki page Message-ID: I have a question about the features listed in the backlog and roadmap wiki page. At the time when the entries were created I didn't have any idea about the terminology used, like what "feature" actually means, and that there was other terms: "user story" and "work item". Now when I'm aware of them and the difference between feature and user story, I realized that every item listed as a feature in the Augmented Reality GE is actually a user story. Is this OK, or does it need a revise? -Antti- -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jan 29 09:13:39 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 29 Jan 2014 09:13:39 +0100 Subject: [Fiware-miwi] WP13 weekly meeting agenda/minutes Message-ID: <6CFC62EA-0921-4711-9360-1AC2685A9EE9@zhaw.ch> Hi Here is the agenda/minutes of todays WP13 call: https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit We have to deliver many items this week (some even today). GEi owners or please attend the meeting or send a deputy and check the minutes. I will open the telco session at 10:00 CET. 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 Wed Jan 29 09:57:29 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 29 Jan 2014 09:57:29 +0100 Subject: [Fiware-miwi] Features in roadmap wiki page In-Reply-To: References: Message-ID: Hi Antti The clean way would be to change them to UserStories and create new Features for matching groups of User Stories. This is a lot of work and (at least the entries in the technical roadmap delivered today) should be fixed until 15:00 today. Other possibility would be to keep them as Features but schedule them (like UserStories) for Sprints and close them accordingly when done. Maybe Manuel/Miguel can give feedback if this is an option. Best regards Christof Am 29.01.2014 um 08:22 schrieb Antti Karhu : > I have a question about the features listed in the backlog and roadmap wiki page. > At the time when the entries were created I didn't have any idea about the terminology used, like what "feature" actually means, and that there was other terms: "user story" and "work item". Now when I'm aware of them and the difference between feature and > user story, I realized that every item listed as a feature in the Augmented Reality GE is actually a user story. Is this OK, or does it need a revise? > > > -Antti- > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Jan 29 10:35:46 2014 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 29 Jan 2014 10:35:46 +0100 Subject: [Fiware-miwi] Features in roadmap wiki page In-Reply-To: References: Message-ID: <52E8CB72.7060609@tid.es> Dear Antti, Taking into account that we are generating the roadmap today for delivery to the EC the timing is not particularly favourable. I would expect people giving the last touch with small details, not extensive changes in GEs. Note that, as Christof rightly points out, the changes you propose propagate to a few places: tracker, roadmap, wiki features edited with the Feature template ... I do not oppose whatever you decide to do in the near future with this. I simply object changes this moment in time, we cannot be risking mistakes. Next week should be ok. Manuel, who has a better understanding of the backlog (and who is actually the owner of this) may have a different view. Best regards, Miguel El 29/01/2014 9:57, Christof Marti escribi?: Hi Antti The clean way would be to change them to UserStories and create new Features for matching groups of User Stories. This is a lot of work and (at least the entries in the technical roadmap delivered today) should be fixed until 15:00 today. Other possibility would be to keep them as Features but schedule them (like UserStories) for Sprints and close them accordingly when done. Maybe Manuel/Miguel can give feedback if this is an option. Best regards Christof Am 29.01.2014 um 08:22 schrieb Antti Karhu >: I have a question about the features listed in the backlog and roadmap wiki page. At the time when the entries were created I didn't have any idea about the terminology used, like what "feature" actually means, and that there was other terms: "user story" and "work item". Now when I'm aware of them and the difference between feature and user story, I realized that every item listed as a feature in the Augmented Reality GE is actually a user story. Is this OK, or does it need a revise? -Antti- _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.eu https://lists.fi-ware.eu/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.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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcp at tid.es Wed Jan 29 10:41:12 2014 From: mcp at tid.es (Miguel Carrillo) Date: Wed, 29 Jan 2014 10:41:12 +0100 Subject: [Fiware-miwi] Features in roadmap wiki page In-Reply-To: References: Message-ID: <52E8CCB8.2060504@tid.es> As stated, you can discuss internally how to deal with this but please do not change it this week El 29/01/2014 10:33, Antti Karhu escribi?: I can replace the current feature entries at the roadmap wiki page with couple of new broader features. Then open new entries at the backlog and rename & reschedule the current features in the backlog as user stories. Has the user stories to be linked into a specific feature at the backlog somehow? -Antti- 2014-01-29 Christof Marti > Hi Antti The clean way would be to change them to UserStories and create new Features for matching groups of User Stories. This is a lot of work and (at least the entries in the technical roadmap delivered today) should be fixed until 15:00 today. Other possibility would be to keep them as Features but schedule them (like UserStories) for Sprints and close them accordingly when done. Maybe Manuel/Miguel can give feedback if this is an option. Best regards Christof Am 29.01.2014 um 08:22 schrieb Antti Karhu >: I have a question about the features listed in the backlog and roadmap wiki page. At the time when the entries were created I didn't have any idea about the terminology used, like what "feature" actually means, and that there was other terms: "user story" and "work item". Now when I'm aware of them and the difference between feature and user story, I realized that every item listed as a feature in the Augmented Reality GE is actually a user story. Is this OK, or does it need a revise? -Antti- _______________________________________________ Fiware-miwi mailing list Fiware-miwi at lists.fi-ware.eu https://lists.fi-ware.eu/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.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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Wed Jan 29 10:44:38 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 29 Jan 2014 11:44:38 +0200 Subject: [Fiware-miwi] 2D-UI integration to WebTundra? (Re: Cloud Rendering GE dependency chain) In-Reply-To: References: Message-ID: On 25 Jan 2014, at 18:48, Jonne Nauha wrote: > If its important to find some, we could port the cloud rendering web client input system to utilize the 2D-UI GE. We can do this for the next 3.3 release if it is desired. this (and Christof?s talks about the integration docs in the meeting) reminded of integration of 2D and 3D UIs ? as we encountered in the 3DUI & POI integration with raycasting & 2d elements floating on top of the 3d view it would be useful. also for the oulu city + car driving the gamepad input would be nice. and Tapani has missed Chat for Pong ? you have (a Tundra server side chat compatible?) chat widget made with WebComponents in 2DUI, right? as Christof mentioned in the meet even if some parts don?t really depend on each other it is still good to test them together and we can plan & document that in the integration doc. the 3DUI & POI integration test that we have already we could report as such a test (the code & demo is on the web) > Jonne Nauha ~Toni -------------- next part -------------- An HTML attachment was scrubbed... URL: From antti.kokko at adminotech.com Wed Jan 29 11:02:08 2014 From: antti.kokko at adminotech.com (Antti Kokko) Date: Wed, 29 Jan 2014 12:02:08 +0200 Subject: [Fiware-miwi] 2D-UI integration to WebTundra? (Re: Cloud Rendering GE dependency chain) In-Reply-To: References: Message-ID: Hi, Polymer lib didn?t fit straight to xml3d a week ago and couple of weeks before that. I didn?t try to investigate it further since Polymer is evolving all the time. But I should test it again now since there is a new release 2 days ago. One of the integration ideas we had was to hook Polymer with the InterfaceDesigner by doing parts of the UI with web components. - Antti On Wed, Jan 29, 2014 at 11:44 AM, Toni Alatalo wrote: > On 25 Jan 2014, at 18:48, Jonne Nauha wrote: > > If its important to find some, we could port the cloud rendering web > client input system to utilize the 2D-UI GE. We can do this for the next > 3.3 release if it is desired. > > > this (and Christof's talks about the integration docs in the meeting) > reminded of integration of 2D and 3D UIs -- as we encountered in the 3DUI & > POI integration with raycasting & 2d elements floating on top of the 3d > view it would be useful. also for the oulu city + car driving the gamepad > input would be nice. > > and Tapani has missed Chat for Pong -- you have (a Tundra server side chat > compatible?) chat widget made with WebComponents in 2DUI, right? > > as Christof mentioned in the meet even if some parts don't really depend > on each other it is still good to test them together and we can plan & > document that in the integration doc. > > the 3DUI & POI integration test that we have already we could report as > such a test (the code & demo is on the web) > > Jonne Nauha > > > ~Toni > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jan 29 11:12:13 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 29 Jan 2014 11:12:13 +0100 Subject: [Fiware-miwi] Features in roadmap wiki page In-Reply-To: <2b3401ca18e24362819d664461b4862c@SRV-MAIL-001.zhaw.ch> References: <2b3401ca18e24362819d664461b4862c@SRV-MAIL-001.zhaw.ch> Message-ID: <416CB340-B955-43D1-969F-99B8024CC7A4@zhaw.ch> Hi Antti Considering the statements of Miguel and Manuel I would propose to keep the Feature entries as they are for the moment. Close the ones which are finished in Sprint 3.3.1 this week and keep the rest scheduled or open. And we can then modify update the entries in tracker and roadmap next week. BTW: You have still an open entry in the historic section of the tracker (Release 3.2 but Sprint 3.3.3) I guess this is an error and the entry should be moved to Release 3.3. ? Christof Am 29.01.2014 um 10:41 schrieb Miguel Carrillo : > As stated, you can discuss internally how to deal with this but please do not change it this week > > > El 29/01/2014 10:33, Antti Karhu escribi?: >> I can replace the current feature entries at the roadmap wiki page with couple of new broader features. Then open new entries at the backlog and rename & reschedule the current features in the backlog as user stories. Has the user stories to be linked into a specific feature at the backlog somehow? >> >> -Antti- >> >> >> 2014-01-29 Christof Marti >> Hi Antti >> >> The clean way would be to change them to UserStories and create new Features for matching groups of User Stories. >> This is a lot of work and (at least the entries in the technical roadmap delivered today) should be fixed until 15:00 today. >> >> Other possibility would be to keep them as Features but schedule them (like UserStories) for Sprints and close them accordingly when done. >> Maybe Manuel/Miguel can give feedback if this is an option. >> >> Best regards >> Christof >> >> >> >> Am 29.01.2014 um 08:22 schrieb Antti Karhu : >> >>> I have a question about the features listed in the backlog and roadmap wiki >>> page. At the time when the entries were created I didn't have any idea about the terminology used, like what "feature" actually means, and that there was other terms: "user story" and "work item". Now when I'm aware of them and the difference between feature >>> and user story, I realized that every item listed as a feature in the Augmented Reality GE is actually a user story. Is this OK, or does it need a revise? >>> >>> >>> -Antti- >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/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.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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From antti.karhu at cie.fi Wed Jan 29 11:26:33 2014 From: antti.karhu at cie.fi (Antti Karhu) Date: Wed, 29 Jan 2014 12:26:33 +0200 Subject: [Fiware-miwi] Features in roadmap wiki page In-Reply-To: <416CB340-B955-43D1-969F-99B8024CC7A4@zhaw.ch> References: <2b3401ca18e24362819d664461b4862c@SRV-MAIL-001.zhaw.ch> <416CB340-B955-43D1-969F-99B8024CC7A4@zhaw.ch> Message-ID: Ok, I do the changes next week. I checked all the open entries in the historic section, and there is no open entries for Augmented Reality. I think you confuse me with the other Antti (Kokko). 2014-01-29 Christof Marti > Hi Antti > > Considering the statements of Miguel and Manuel I would propose to keep > the Feature entries as they are for the moment. > Close the ones which are finished in Sprint 3.3.1 this week and keep the > rest scheduled or open. > And we can then modify update the entries in tracker and roadmap next week. > > BTW: You have still an open entry in the historic section of the tracker > (Release 3.2 but Sprint 3.3.3) > I guess this is an error and the entry should be moved to Release 3.3. > > > -- Christof > > Am 29.01.2014 um 10:41 schrieb Miguel Carrillo : > > As stated, you can discuss internally how to deal with this but please > do not change it this week > > > El 29/01/2014 10:33, Antti Karhu escribi?: > > I can replace the current feature entries at the roadmap wiki page with > couple of new broader features. Then open new entries at the backlog and > rename & reschedule the current features in the backlog as user stories. > Has the user stories to be linked into a specific feature at the backlog > somehow? > > -Antti- > > > 2014-01-29 Christof Marti > >> Hi Antti >> >> The clean way would be to change them to UserStories and create new >> Features for matching groups of User Stories. >> This is a lot of work and (at least the entries in the technical roadmap >> delivered today) should be fixed until 15:00 today. >> >> Other possibility would be to keep them as Features but schedule them >> (like UserStories) for Sprints and close them accordingly when done. >> Maybe Manuel/Miguel can give feedback if this is an option. >> >> Best regards >> Christof >> >> >> >> Am 29.01.2014 um 08:22 schrieb Antti Karhu : >> >> I have a question about the features listed in the backlog and roadmap >> wiki page. At the time when the entries were created I didn't have any idea >> about the terminology used, like what "feature" actually means, and that >> there was other terms: "user story" and "work item". Now when I'm aware of >> them and the difference between feature and user story, I realized that >> every item listed as a feature in the Augmented Reality GE is actually a >> user story. Is this OK, or does it need a revise? >> >> -Antti- >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/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.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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jan 29 11:43:59 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 29 Jan 2014 11:43:59 +0100 Subject: [Fiware-miwi] WP13 weekly meeting agenda/minutes In-Reply-To: <6CFC62EA-0921-4711-9360-1AC2685A9EE9@zhaw.ch> References: <6CFC62EA-0921-4711-9360-1AC2685A9EE9@zhaw.ch> Message-ID: <350F60D8-A74D-482B-860C-C66C7BECC1A6@zhaw.ch> Hi Following a short summary of the Action Points from todays meeting: (for details see the topics in todays minutes: https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit) [Today Wed 29th January before 15:00] All GEi owner: Check and update Technical roadmap https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI Is it in sync with tracker entries (Features for R3.1,R3.2, R3.3) Are the Features for Release 3.3 available? Is the textual description of the features in the first half of the document correct/missing? Specially check/update the 3D-UI implementations (XML3D & WebTundra) which now are split up in separate entries (Torsten, Toni) [Today Wed 29th January EOB] All GEi owner: Software packages available in Files section of FI-WARE or FI-WARE PPP restricted And link to release container copied to WP13 Dashboard/Software/delivery https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 [Today Wed 29th January] Affected GEi owners: Fix remaining guides (orange) and request new review from Christof https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 [Today Wed 29th January] Cvetan, Antti: Fix errors in historic section of tracker As much I can see, only the Release number is wrong. Should be Release 3.3 instead of Release 3.2. [Thursday 30th January] All GEi owners: Check tracker entries of your GE and enhance backlog & roadmap (see examples in minutes) [Friday 31th January before 18:00] All GEi owner: Sprint 3.3.1 is ending. Close finished entries and check schedule for all open entries Thanks for keeping the Deadlines. 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 29.01.2014 um 09:13 schrieb Christof Marti : > Hi > > Here is the agenda/minutes of todays WP13 call: > https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit > > We have to deliver many items this week (some even today). > GEi owners or please attend the meeting or send a deputy and check the minutes. > > I will open the telco session at 10:00 CET. > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonne at adminotech.com Wed Jan 29 12:18:26 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Wed, 29 Jan 2014 13:18:26 +0200 Subject: [Fiware-miwi] WP13 weekly meeting agenda/minutes In-Reply-To: <350F60D8-A74D-482B-860C-C66C7BECC1A6@zhaw.ch> References: <6CFC62EA-0921-4711-9360-1AC2685A9EE9@zhaw.ch> <350F60D8-A74D-482B-860C-C66C7BECC1A6@zhaw.ch> Message-ID: What? We have been talking the whole time that we make release 3.2 in January. So now it has changed to 3.3? I do understand that the current sprint is 3.3.1 but I thought we are making a delayed 3.2 release and the future releases are 3.3.x. We also have all marked the features to 3.2 release on the roadmap wiki. Why would it suddenly be that all those features are in the 3.3 release? I'm referring to your note to Antti and Cvetan. I also have all features completed now marked to the 3.2 release and the 3.2.x sprints. There are also loads of 3.2.x release/sprint entries in the other backlog features/work items from other companies. If all this needs to be changed before 15:00 now would be the time to tell about it. I haven't gotten the impression at any point that we are making a 3.3.x release now. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com On Wed, Jan 29, 2014 at 12:43 PM, Christof Marti wrote: > Hi > > Following a short summary of the Action Points from todays meeting: > (for details see the topics in todays minutes: > https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit > ) > > > - *[Today Wed 29th January before 15:00] All GEi owner*: Check and > update Technical roadmap > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI > - Is it ies (Features for R3.1,R3.2, R3.3) > - Are the Features for Release 3.3 available? > - Is the textual description of the features in the first half of > the document correct/missing? > - Specially check/update the 3D-UI implementations (XML3D & > WebTundra) which now are split up in separate entries (Torsten, Toni) > - [Today Wed 29th January EOB] All GEi owner: Software packages > available in Files section of FI-WARE or FI-WARE PPP restricted > - And link to release container copied to WP13 > Dashboard/Software/delivery > > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > - [Today Wed 29th January] Affected GEi owners: Fix remaining guides > (orange) and request new review from Christof > - > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > - [Today Wed 29th January] Cvetan, Antti: Fix errors in historic > section of tracker > - As much I can see, only the Release number is wrong. Should be > Release 3.3 instead of Release 3.2. > - [Thursday 30th January] All GEi owners: Check tracker entries of > your GE and enhance backlog & roadmap (see examples in minutes) > - *[Friday 31th January before 18:00] All GEi owner*: Sprint 3.3.1 is > ending. > - Close finished entries and check schedule for all open entries > > > Thanks for keeping the Deadlines. > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp t of Applied > Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > > Am 29.01.2014 um 09:13 schrieb Christof Marti : > > Hi > > Here is the agenda/minutes of todays WP13 call: > > https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit > > We have to deliver many items this week (some even today). > GEi owners or please attend the meeting or send a deputy and check the > minutes. > > I will open the telco session at 10:00 CET. > > Best regards > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch > Institut of Applied Information Technology - InIT > Zurich University of Applied Sciences - ering > > Phone: +41 58 934 70 63 > Skype: christof-marti > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From toni at playsign.net Wed Jan 29 12:23:57 2014 From: toni at playsign.net (Toni Alatalo) Date: Wed, 29 Jan 2014 13:23:57 +0200 Subject: [Fiware-miwi] WP13 weekly meeting agenda/minutes In-Reply-To: References: <6CFC62EA-0921-4711-9360-1AC2685A9EE9@zhaw.ch> <350F60D8-A74D-482B-860C-C66C7BECC1A6@zhaw.ch> Message-ID: <475CA381-7E2C-4F00-9478-18F7C0BF6C24@playsign.net> no 3.2 is today?s release, we just need to have info about 3.3 plans up too. but i?m now also confused as understood that it is OK to add the future release infos tomorrow on Thursday, not today yet (now that we are testing and packaging release). am referring to: [Today Wed 29th January before 15:00] Are the Features for Release 3.3 available? ~Toni On 29 Jan 2014, at 13:18, Jonne Nauha wrote: > What? We have been talking the whole time that we make release 3.2 in January. So now it has changed to 3.3? I do understand that the current sprint is 3.3.1 but I thought we are making a delayed 3.2 release and the future releases are 3.3.x. We also have all marked the features to 3.2 release on the roadmap wiki. Why would it suddenly be that all those features are in the 3.3 release? > > I'm referring to your note to Antti and Cvetan. I also have all features completed now marked to the 3.2 release and the 3.2.x sprints. There are also loads of 3.2.x release/sprint entries in the other backlog features/work items from other companies. > > If all this needs to be changed before 15:00 now would be the time to tell about it. I haven't gotten the impression at any point that we are making a 3.3.x release now. > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > > On Wed, Jan 29, 2014 at 12:43 PM, Christof Marti wrote: > Hi > > Following a short summary of the Action Points from todays meeting: > (for details see the topics in todays minutes: https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit) > > [Today Wed 29th January before 15:00] All GEi owner: Check and update Technical roadmap > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI > Is it ies (Features for R3.1,R3.2, R3.3) > Are the Features for Release 3.3 available? > Is the textual description of the features in the first half of the document correct/missing? > Specially check/update the 3D-UI implementations (XML3D & WebTundra) which now are split up in separate entries (Torsten, Toni) > [Today Wed 29th January EOB] All GEi owner: Software packages available in Files section of FI-WARE or FI-WARE PPP restricted > And link to release container copied to WP13 Dashboard/Software/delivery > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > [Today Wed 29th January] Affected GEi owners: Fix remaining guides (orange) and request new review from Christof > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > [Today Wed 29th January] Cvetan, Antti: Fix errors in historic section of tracker > As much I can see, only the Release number is wrong. Should be Release 3.3 instead of Release 3.2. > [Thursday 30th January] All GEi owners: Check tracker entries of your GE and enhance backlog & roadmap (see examples in minutes) > [Friday 31th January before 18:00] All GEi owner: Sprint 3.3.1 is ending. > Close finished entries and check schedule for all open entries > > Thanks for keeping the Deadlines. > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp t of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > > Am 29.01.2014 um 09:13 schrieb Christof Marti : > >> Hi >> >> Here is the agenda/minutes of todays WP13 call: >> https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit >> >> We have to deliver many items this week (some even today). >> GEi owners or please attend the meeting or send a deputy and check the minutes. >> >> I will open the telco session at 10:00 CET. >> >> Best regards >> Christof >> ---- >> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch >> Institut of Applied Information Technology - InIT >> Zurich University of Applied Sciences - ering >> >> Phone: +41 58 934 70 63 >> Skype: christof-marti > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Wed Jan 29 12:39:36 2014 From: mach at zhaw.ch (Christof Marti) Date: Wed, 29 Jan 2014 12:39:36 +0100 Subject: [Fiware-miwi] WP13 weekly meeting agenda/minutes In-Reply-To: <8850af63568347a3b8cc6f2a9516a9e5@SRV-MAIL-001.zhaw.ch> References: <6CFC62EA-0921-4711-9360-1AC2685A9EE9@zhaw.ch> <350F60D8-A74D-482B-860C-C66C7BECC1A6@zhaw.ch> <8850af63568347a3b8cc6f2a9516a9e5@SRV-MAIL-001.zhaw.ch> Message-ID: Hi Jonne First: Today 15:00 is the deadline for the Technical Roadmap Delivery https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI So all the Features should be there in the wiki-page in the correct release they are delivered. To update the tracker we have time until Friday 18:00 [very latest] Regarding the scheduling of the Features/Sprints: In principle it is very simple (there are 2 main rules): - All the work done in December is in Sprint 3.2.3, All the work done in January is in Sprint 3.3.1, February Sprint 3.3.2, ... - Release numbers always have to match the sprint numbers. If you have Sprint 3.3.x Release has to be 3.3. If you have Sprint 3.2.x Release has to be 3.2. Now to the confusing part. - R3.2 (SW & Guides) should have been finished in December (Sprint 3.2.3 Release 3.2). That we are working on this now in January is already an ?extension?. - So we have to schedule the WorkItems for the guides & SW release, ? for Sprint 3.3.1 / Release 3.3. This is, because the reporting tools work this way. - That we are working on the documentation for Release 3.2 can be declared in the description field of the WorkItem (not in the Release field). (See also my email from January 24th and January 27th) If you finished implementing a feature work item in December it should be set to closed with Release 3.2. This is valid for all GEis. Christof Am 29.01.2014 um 12:18 schrieb Jonne Nauha : > What? We have been talking the whole time that we make release 3.2 in January. So now it has changed to 3.3? I do understand that the current sprint is 3.3.1 but I thought we are making a delayed 3.2 release and the future releases are 3.3.x. We also have all marked the features to 3.2 release on the roadmap wiki. Why would it suddenly be that all those features are in the 3.3 release? > > I'm referring to your note to Antti and Cvetan. I also have all features completed now marked to the 3.2 release and the 3.2.x sprints. There are also loads of 3.2.x release/sprint entries in the other backlog features/work items from other companies. > > If all this needs to be changed before 15:00 now would be the time to tell about it. I haven't gotten the impression at any point that we are making a 3.3.x release now. > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com > > > On Wed, Jan 29, 2014 at 12:43 PM, Christof Marti wrote: > Hi > > Following a short summary of the Action Points from todays meeting: > (for details see the topics in todays minutes: https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit) > > [Today Wed 29th January before 15:00] All GEi owner: Check and update Technical roadmap > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI > Is it ies (Features for R3.1,R3.2, R3.3) > Are the Features for Release 3.3 available? > Is the textual description of the features in the first half of the document correct/missing? > Specially check/update the 3D-UI implementations (XML3D & WebTundra) which now are split up in separate entries (Torsten, Toni) > [Today Wed 29th January EOB] All GEi owner: Software packages available in Files section of FI-WARE or FI-WARE PPP restricted > And link to release container copied to WP13 Dashboard/Software/delivery > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > [Today Wed 29th January] Affected GEi owners: Fix remaining guides (orange) and request new review from Christof > https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 > [Today Wed 29th January] Cvetan, Antti: Fix errors in historic section of tracker > As much I can see, only the Release number is wrong. Should be Release 3.3 instead of Release 3.2. > [Thursday 30th January] All GEi owners: Check tracker entries of your GE and enhance backlog & roadmap (see examples in minutes) > [Friday 31th January before 18:00] All GEi owner: Sprint 3.3.1 is ending. > Close finished entries and check schedule for all open entries > > Thanks for keeping the Deadlines. > Christof > ---- > InIT Cloud Computing Lab - ICCLab http://cloudcomp t of Applied Information Technology - InIT > Zurich University of Applied Sciences - ZHAW > School of Engineering > Phone: +41 58 934 70 63 > Skype: christof-marti > > Am 29.01.2014 um 09:13 schrieb Christof Marti : > >> Hi >> >> Here is the agenda/minutes of todays WP13 call: >> https://docs.google.com/document/d/1q6Of53kd4kGISS1mGKmw68y7eVKVcV3B4cyF2ks1JMY/edit >> >> We have to deliver many items this week (some even today). >> GEi owners or please attend the meeting or send a deputy and check the minutes. >> >> I will open the telco session at 10:00 CET. >> >> Best regards >> Christof >> ---- >> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch >> Institut of Applied Information Technology - InIT >> Zurich University of Applied Sciences - ering >> >> Phone: +41 58 934 70 63 >> Skype: christof-marti > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lasse.oorni at ludocraft.com Thu Jan 30 15:59:24 2014 From: lasse.oorni at ludocraft.com (=?iso-8859-1?Q?=22Lasse_=D6=F6rni=22?=) Date: Thu, 30 Jan 2014 16:59:24 +0200 Subject: [Fiware-miwi] realXtend Tundra 2.5.2 released Message-ID: <577380b698e41db1b667594756fef4cc.squirrel@urho.ludocraft.com> Hello, today we made also a public binary release of the realXtend Tundra SDK, version 2.5.2, which includes the same Server part of the Synchronization GE as FI-WARE Release 3.2. The latest source code is on github: http://github.com/realXtend/tundra/ The public 2.5.2 binaries are in Google Drive: Tundra 2.5.2 Windows 32bit https://drive.google.com/uc?id=0B3nQB7kG0dM1UkJvejdxNTlMWFU&export=download Tundra 2.5.2 Windows 64bit https://drive.google.com/uc?id=0B3nQB7kG0dM1R1JsX1ZvYVNlLUU&export=download Tundra 2.5.2 OS X 64bit https://drive.google.com/uc?id=0B3nQB7kG0dM1TWVDYlFYZ1dDZVU&export=download -- Lasse ??rni Game Programmer LudoCraft Ltd. From jonne at adminotech.com Thu Jan 30 16:14:31 2014 From: jonne at adminotech.com (Jonne Nauha) Date: Thu, 30 Jan 2014 17:14:31 +0200 Subject: [Fiware-miwi] Recent Meshmoon developments with FIWARE MIWI GEs at Adminotech Message-ID: Hello everyone, MIWI just got its January release out the door. I'd like to take the opportunity to update everyone how we at Adminotech are using FIWARE GEs in our products and services. We did a big update to the Meshmoon platform today. We published the public WebRocket 1.0 web client today and updated realXtend Tundra based Meshmoon Rocket clients and our servers to 2.5.3.0. Our website also got a facelift and usability improvements. *WebRocket 1.0* As said the public WebRocket 1.0 is out now. Please visit and test it at www.meshmoon.com, sign in and head over to the WebRocket page from the top bar. Select a world and login. Latest Chrome or Firefox browser are supported/recommended. Here is WebRocket in action https://dl.dropboxusercontent.com/u/3589544/meshmoon/fiware/meshmoon-webrocket.png. Connected to one of our partners, Oulu3D, Church of Haukipudas world where an actual church near by here in Oulu Finland was modeled as a virtual Meshmoon world. Its one of the three scenes we are launching WebRocket with, but more is to come! - *FIWARE.OpenSpecification.MiWi.2D-UI * (Adminotech) The GE implementation was based on our earlier InputAPI and UiAPI from WebRocket development, which we took further during FIWARE development. Both APIs are part of the WebRocket 1.0 core. - FIWARE.OpenSpecification.MiWi.InterfaceDesigner (Adminotech) This GE is fully integrated to manipulate the scene in WebRocket 1.0. The editor application is hidden if you are not a admin in the world. Our server logic will ignore scene modification from users that dont have permission to modify that particular world, but its always good to hide the UI app on the client side when we know you don't have permissions, not just to fail later. - FIWARE.OpenSpecification.MiWi.Synchronization (Ludocraft) We have our own web browser side javascript implementation of the Tundra protocol synchronization. So essentially we are not using the GEi Lasse/Ludocraft made, but we have implemented our own GEi as per the Synchronization GE spec. Meaning that we have at least two client side implementations of this GE out in the world :) *Meshmoon Server 2.5.3.0* - *FIWARE.OpenSpecification.MiWi.Synchronization *(Ludocraft) We open sourced our Meshmoon web socket server implementation after the start of the project, which got merged to realXtend Tundra. Lasse continued great work from the initial push, updating the server to use the latest stable release of the C++ library we use for web socket networking. Another significant effort there was to modify the whole realXtend Tundra core to allow multiple network protocols to be enabled at the same time. Normally we used only UDP or TCP to allow user connections, now both those and web socket connections work at the same time. Modifying the core aspects of Tundra networking to allow flexible sub classing with different network protocols and making all of the "first class citizens" and basically making transparent to the 3rd party code handling those user connections what the underlying protocol is. This was a monumental help for us and the open source WebSocketServerModule is a part of both the Meshmoon Rocket client and the Meshmoon Server. A stable WebRocket 1.0 release would have not been possible without us adopting the Synchronization GE to our products and Ludocrafts continuation work. *Meshmoon Rocket 2.5.3.0* Cloud Rendering GEi in action https://dl.dropboxusercontent.com/u/3589544/meshmoon/fiware/adminotech-cloud-rendering.png. Shows the web service in the top right corner, facilitating the initial signaling to connect web clients with a renderer instance. At the bottom right corner the Meshmoon Rocket client acting as a cloud renderer, registered to the web service. On the left you can find the browser web client that has received a renderer from the web service and connected to it for WebRTC based video streaming. The client can control the renderer with mouse and keyboard input (using the video element as it was the actual client). - *FIWARE.OpenSpecification.MiWi.Synchronization (Ludocraft) To continue on the above test: The Tundra plugin is also a part of our client distribution so that our end users/developers can run Tundra servers locally with web client support. Once we package a WebRocket 1.0 SDK this will become reality. So devs have a full development stack at their disposal when they install our client. * - *FIWARE.OpenSpecification.MiWi.CloudRendering (Adminotech) The Cloud Rendering renderer Tundra plugin is shipped to all our end users in the 2.5.3.0 client. It is not loaded by default, but in practice anyone can register their own renderer to a Cloud Rendering GEi web service and start playing around with it. We were initially interested in participating in the Cloud Rendering GE because we saw real business cases for it. The initial release is out and shows everyone a working setup streaming server side rendering via WebRTC video to web browser clients. The reference GEi is not production quality yet, but with some performance optimization on the Tundra rendering side and making the service more user friendly we see that will utilize this GE in the Meshmoon ecosystem. As per the intent of the GE to provide low perf mobile devices with server side rendering of any application, but we also see other use cases for server side rendering.* Thanks to everyone in the MIWI project for the good cooperation and good first push for the January release! Feel free to forward the email to any parties you think might be interested. Best regards, Jonne Nauha Meshmoon developer at Adminotech Ltd. www.meshmoon.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mach at zhaw.ch Fri Jan 31 15:41:26 2014 From: mach at zhaw.ch (Christof Marti) Date: Fri, 31 Jan 2014 15:41:26 +0100 Subject: [Fiware-miwi] Fwd: [Fiware-ge-owners] Backlog Dashboard - SPRINT CLOSING - LAST CALL References: <81edb03cb7dc44c0a466784d6a18511c@SRV-MAIL-001.zhaw.ch> Message-ID: Hi REMINDER: Sprint 3.3.1 is ending today. All 3.3.1 entries should be closed or rescheduled before 18:00 CET today. I checked the MIWI tracker. There are still Sprint 3.3.1 entries open, scheduled or under execution. Because you delivered the software this week. I guess you can now also update some from ?Finished but not delivered? to closed. Please check and update your entries before 18:00 CET today. 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 Anfang der weitergeleiteten Nachricht: > Umgeleitet von: > Von: MANUEL ESCRICHE VICENTE > Betreff: [Fiware-ge-owners] Backlog Dashboard - SPRINT CLOSING - LAST CALL > Datum: 31. Januar 2014 [5] 10:58:57 MEZ > An: "fiware-ge-owners at lists.fi-ware.eu" > Kopie: "fiware-wpl at lists.fi-ware.eu" , "fiware-wpa at lists.fi-ware.eu" > > Dear GE Owners: > > Please be aware today is deadline to close sprint 3.3.1. > I?d appreciate you proceed to close in the tracker all entries finished during M33 (=Sprint 3.3.1) > Let me remind you I?m delivering on Monday morning the backlog snapshot taken today at 18:00. > > Current status: > Apps: > > > Cloud: > > > IoT: > > > Data: > > > I2ND: > > > Security: > > MiWi: > > > Thanks for cooperation!! > Have a nice weekend!! > Kind regards, > Manuel > ---------------------------- > Manuel Escriche Vicente > Agile Project Manager/Leader > FI-WARE Initiative > Telef?nica Digital > Parque Tecnol?gico > C/ Abraham Zacuto, 10 > 47151 - Boecillo > Valladolid - Spain > Tfno: +34.91.312.99.72 > Fax: +34.983.36.75.64 > http://www.tid.es > > > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > _______________________________________________ > Fiware-ge-owners mailing list > Fiware-ge-owners at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-ge-owners -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 37359 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 37533 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 38497 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 38192 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 38442 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 38576 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 38669 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.iot.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 387275 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.miwi.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 377575 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.i2nd.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 279211 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.cloud.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 379716 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.data.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 406303 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.apps.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 397448 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE.backlog.security.dashboard.20140131.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 523649 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: