quick note about the POI point: On Oct 23, 2013, at 8:00 AM, Philipp Slusallek <Philipp.Slusallek at dfki.de> wrote: > I did not get the idea why POIs are similar to ECA. At a very high level I see it, but I am not sure what it buys us. Can someone sketch that picture in some more detail? Another answer to this is that it may very well be that it does not buy anything at all. The conclusion was only that due to the similarities it is worth a check. ~Toni > BTW, what is the status with the Rendering discussion (Three.js vs. xml3d.js)? I still have the feeling that we are doing parallel work here that should probably be avoided. > > BTW, as part of our shading work (which is shaping up nicely) Felix has been looking lately at a way to describe rendering stages (passes) essentially through Xflow. It is still very experimental but he is using it to implement shadow maps right now. > > @Felix: Once this has converged into a bit more stable idea, it would be good to post this here to get feedback. The way we discussed it, this approach could form a nice basis for a modular design of advanced rasterization techniques (reflection maps, adv. face rendering, SSAO, lens flare, tone mapping, etc.), and (later) maybe also describe global illumination settings (similar to our work on LightingNetworks some years ago). > > > Best, > > Philipp > > Am 22.10.2013 23:03, schrieb toni at playsign.net: >> Just a brief note: we had some interesting preliminary discussion >> triggered by how the data schema that Ari O. presented for the POI >> system seemed at least partly similar to what the Real-Virtual >> interaction work had resulted in too -- and in fact about how the >> proposed POI schema was basically a version of the entity-component >> model which we’ve already been using for scenes in realXtend (it is >> inspired by / modeled after it, Ari told). So it can be much related to >> the Scene API work in the Synchronization GE too. As the action point we >> agreed that Ari will organize a specific work session on that. >> I was now thinking that it perhaps at least partly leads back to the >> question: how do we define (and implement) component types. I.e. what >> was mentioned in that entity-system post a few weeks back (with links >> to reX IComponent etc.). I mean: if functionality such as POIs and >> realworld interaction make sense as somehow resulting in custom data >> component types, does it mean that a key part of the framework is a way >> for those systems to declare their types .. so that it integrates nicely >> for the whole we want? I’m not sure, too tired to think it through now, >> but anyhow just wanted to mention that this was one topic that came up. >> I think Web Components is again something to check - as in XML terms reX >> Components are xml(3d) elements .. just ones that are usually in a group >> (according to the reX entity <-> xml3d group mapping). And Web >> Components are about defining & implementing new elements (as Erno >> pointed out in a different discussion about xml-html authoring in the >> session). >> BTW Thanks Kristian for the great comments in that entity system >> thread - was really good to learn about the alternative attribute access >> syntax and the validation in XML3D(.js). >> ~Toni >> P.S. for (Christof &) the DFKI folks: I’m sure you understand the >> rationale of these Oulu meets -- idea is ofc not to exclude you from the >> talks but just makes sense for us to meet live too as we are in the same >> city afterall etc -- naturally with the DFKI team you also talk there >> locally. Perhaps is a good idea that we make notes so that can post e.g. >> here then (I’m not volunteering though! 😜) . Also, the now agreed >> bi-weekly setup on Tuesdays luckily works so that we can then summarize >> fresh in the global Wed meetings and continue the talks etc. >> *From:* Erno Kuusela >> *Sent:* Tuesday, October 22, 2013 9:57 AM >> *To:* Fiware-miwi >> >> Kari from CIE offered to host it this time, so see you there at 13:00. >> >> Erno >> _______________________________________________ >> 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 > --------------------------------------------------------------------------- > <slusallek.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy