<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Forwarded with consent.</div>
<div> </div>
<div>This is fyi.</div>
<div> </div>
<div>Discussion/comments welcome.</div>
<div> </div>
<div>The complete glossary can be found at <a href="http://simulrr.sourceforge.net/concepts/001_Glossary.pdf">http://simulrr.sourceforge.net/concepts/001_Glossary.pdf</a></div>
<div> </div>
<div>All the best</div>
<div>Christoph</div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Mittwoch, 27. Oktober 2021 um 20:29 Uhr<br/>
<b>Von:</b> "Christoph Valentin" <christoph.valentin@gmx.at><br/>
<b>An:</b> eric.maranne@vr-crisis.com<br/>
<b>Betreff:</b> Aw: Re: Question about Mixed Reality</div>
<div name="quoted-content">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>Hi Eric,</div>
<div> </div>
<div>Thank you for your thorough review.</div>
<div> </div>
<div>Let me answer to your comments and concerns in line, i.e. I will add marks [CPV:] (my full name is Christoph Peter Valentin) and try to answer comprehensively.</div>
<div> </div>
<div>Thank you,</div>
<div>Christoph</div>
<div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Mittwoch, 27. Oktober 2021 um 18:11 Uhr<br/>
<b>Von:</b> "Eric Maranne" <eric.maranne@vr-crisis.com><br/>
<b>An:</b> "Christoph Valentin" <christoph.valentin@gmx.at><br/>
<b>Betreff:</b> Re: Question about Mixed Reality</div>
<div>
<p>Hi Christof,</p>
<p>yes I seen your post.</p>
<p>How can I say ... you may be deceived by my way of thinking.</p>
<p> </p>
<p> </p>
<p>First, I have difficulty with your PSI approach, since, for me, multiuser means shared, so no any scene instance is personal, only the perception of it is personnal, (without reducing to personal 'point of view' ... but mainly FWIW)<br/>
[CPV:] With PSI, I mean basically one computer running a VRML Browser and some additional software (Environmental Sensors to interface ONE user (and his/her VR equipment) and Network Sensors to interface the network for SYNChronization).<br/>
Basically we have a 1:1 relation between a PSI and a renderer of the scene graph.<br/>
In this sense a PSI is just as personal as a PC (personal computer) is, for it can only be used by ONE user at a time.<br/>
Additionally, and this is the first time I reveal this secret: the acronym PSI is also used in 3GPP IMS standards --> there the PSI means "Public Service Interface" and can mean a video service at a communication server. This shall be a "little hint" towards server based rendering.</p>
<p> </p>
<p> </p>
<p>For me, reality doesn't exists, even less shared 'Real Reality'. Reality is a processed set of perception (hence interpreted, conceptualised, filtered) . Perception itself is a voluntary process depending on each person cognitive, emotive, cultural etc. involvement. My reality isn't my daughter reality nor your reality. We may eventually find grounds on wich we get a common vision of a local reality, like talking about VR ... but , even then ...</p>
<p>Reality is a personal construction.<br/>
[CPV:] Now these two paragraphs ARE philosophy. Obviously you follow the constructivistic approach (what I don't, but I have got friends, who actually do). I think, this is not the place to discuss such philosophy.</p>
<p> </p>
<p> </p>
<p>When I had to simulate forest for fire fighters, I had to define a -virtual- reality that matches a fire fighter reality. When foresters came into the 'fire fighters forest' meaning was completely different and realism (from which 'reality perception' flows) felt distorted. Same thing for hunters and other forest users.</p>
<p>VR is constructed following a conjunction of users expectations: diffferent users expect different representations that makes sense to them, even if based on the same location. Like to 'experts' representation of SMS ... All certainly on spot, but, at the same time so different. :)</p>
<p>Maybe it's a limitation of my capabilities: I am unable to provide an *universal* tangible reality. Like a 3D modeler is using triangles budget wisely to produce the best geometry fitting a representation, I am using 3D percepts budget to provide a fitting 'representation' of reality.</p>
<p>Percepts are not only geometries of course, but interactions, sounds, ambiance, whatever enables to make 'sense' in a particular population.<br/>
[CPV:] I can agree to these four paragraphs, just I would not call it the "reality of the firefighter", but the " 'perceived' reality (or perception) of the firefighter"<br/>
Please be aware of the three keys that are needed to access the conceptual database DIGITS:<br/>
- "Virtual Roaming Area" (VRA) or more future proof "Space Time Slice" (STS)<br/>
- LoD (..., ..., pedestrian indoor, pedestrian outdoor, slow ground vehicle, fast ground vehicle, slow airborne, fast airborne, ..., ...)<br/>
- Virtual Reality Identifier <------ this was my idea of how to store "many realities" in the database</p>
<p> </p>
<p> </p>
<p>In this vision, SCSI looks like an arbitrary reduction system. And I, when dealing with VR/Realitymix, I consider only reductions of 'reality' to expected percepts of users. VR is what gives team shared meaning, what makes shared 'sense'/reality.<br/>
[CPV:] in my vision the SCSI is just a VRML browser, like the PSI, but it does NOT render graphics/sounds. It just cares about the command and control of the objects, whose controllers are downloaded with the concrete scene (SMS - Simple Multiuser Scene).<br/>
In my first concept, there was only ONE SCSI for all users. Now I am considering to use each SCSI for one distinct (set of) module(s).</p>
<div> </div>
<div> </div>
<div>AFIC, most of expected percepts are embedded into the VR world, it makes the VR world the basis of the engaged team -perceived- reality: when using our systems, the -perceived- 'reality' comes from VR and is shared.</div>
<p>in VR, -Perceived- reality comes from within the VR , in AR or MR some -perceived-reality comes from 'real world' and one then need some 'SYNC'. I don't have much experience in there.<br/>
[CPV:] I understand your view. By the way: No problem. I dont have any experience at all :-) my thoughts are just phantasy.</p>
<p> </p>
<p> </p>
<p>We're doing some MR by colocating 'real' and 'VR' interfaces (like putting a user in a virtual ladder command seat, while installed in a 'real' ladder seat, with buttons, joysticks, synching VR alarms and displays with real world buttons, commands and Joysticks, going thru a Matlab based ladder model). We're doing some XR, for example linking a real terrorist attack victim flux to a VR based hospital structure.</p>
<p>I tend to picture the 'real' part of these as the 'hook points' I have to cope with in my VR environments, but still, shared meaning comes from the VR environment.</p>
<p>The only times when -perceived- reality comes from 'real world' is when I'm linking operational systems (like operational command and dispatch systems) to virtual environments to display actual forces and sensors activity during a real operation. While this helps at commanding and controlling an operation, but it's merely yet another attempt at representation. It's, representation, but the expected percepts are about the operation. The -virtual- environment participates in building the -perceived- reality, but isn't carrying the main meaningful percepts.</p>
<p>I never had, really have to design anything that would control real world from virtual world representation... unless if considering Virtual Reality simply as a 'representation' of reality. My first personal company was editing GIS software. And I came to VRML just by extension of the map representation to 3D representation of 'reality': I designed a 3D GIS system back in the 90ies ;). In this case, maps and geographic information system based applications are performing just that. Reserving a restaurant by clicking in google maps just does that.</p>
<p> I have a problem with SCSI too as a centralised point of interface of PSI: the objects in my simulation environment just react to their environment, they actually may connect to an external 'real' counterpart or controller (like synching with GPS to put a vehicle in real location, or metar station to rule atmosphear), or external model computation (fire propagation, Matlab sim). But mostly they are reacting to -virtual- environment and events without any external controller: they are autonomous. SO, the interface with reality is done on a perobject basis if necessary. Not from any scene rendering centralised point of view.</p>
<p>I reluct to use a centralised controller, that would IMHO make things more complex. On the other role of SCSI, like controlling external world from within VR. I understand you picture SCSI for each PSI that together support an SMS.<br/>
[CPV:] May I try to put my concept into a nutshell:<br/>
1) Each PSI renders (graphics, sounds, haptics, ......) all virtual objects and virtual modules that are relevant to ONE USER<br/>
1a) Exception: in case of server based rendering, one PSI might render all virtual objects and virtual modules that are relevant to a SET OF USERs<br/>
2) One SCSI cares for command and control of all real objects and real modules relevant for a GEOGRAPHIC region (in case of AR/AV this might be the real surroundings of ONE USER)<br/>
3) All instances of the objects and modules are SYNChronized by Network Sensor Nodes (among PSIs and SCSIs) and IoT protocols (between SCSIs and POIs).<br/>
4) Basically, one and the same SMS (Simple Multiuser Scene) is downloaded to all PSIs and SCSIs of a Multiuser Session (MS) - the SMS may be "adapted" by the http Server (e.g. by PHP), depending on if it is downloaded to a PSI or SCSI or whatever.</p>
<p> </p>
<p> </p>
<p>My vision is different.</p>
<p>I have objects, each performing as close to 'expected' reality restricted to a given population sharing the same 'percepts' expectation, and able to build a shared representation and understanding of the virtual environment. Any object can be 'hooked' to a piece of 'real world'/'real reality', but for it's own use only.</p>
<p>Each 'hooked' object is responsible for synching themselves with reality: real environment can't be synched : they are 'real' reality: they can only be observed by the object in charge of representing them in the VR world. Really meditate over the 'representation' word: it's simplifying an object reality to the expected percepts that will enable a perception. Be it a map, a drawing, a 3D model ... and perception depends on so many things personal and external ...</p>
<p>If an object 'changed' then, it may have two causes: either evolution or induction. Evolution is intrinsec to the object and can be monitored or modelled (GPS location, real weather conditions, pool evaporation, gas dispersion). Induction is a trigger coming from the external (pushing a -real or virtual alarm button). In the first case an hooked object will simply have to monitor it's state from reality or model. In the second case, either the induct comes from another object evolution or induction (either push the button in real or in VR) , or it may come from user interaction (in my case, EXercise CONtroller or trainee. Makes no change: a simple state change message is pushed on the network ... and may trigger cascading inductions.</p>
<p>So synchronisation, if needed, is done on an object basis. I have no SCSI. No either anything like PSI. Only a shared representation of 'reality' working on causality spreading and interaction.... well a bit like in reality ...but limited to a team common 'senses' and virtual ;)</p>
<p>Not sure this helps you, but it may hopefully make you dream or nightmare ... words are not easy, so you benefit of a nicely fuzzy attempt to share my vision ...<br/>
[CPV:] for sure this helps :-)</p>
<p> </p>
<p> </p>
<p>Good evening ?</p>
<p>Eric.</p>
<div class="moz-cite-prefix">Le 27/10/2021 à 10:42, Christoph Valentin a écrit :</div>
<blockquote>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>Dear Eric,</div>
<div> </div>
<div>You might have read my e-mail to the x3d-public mailing list (see below, the link to the complete glossary).</div>
<div> </div>
<div>Additionally, I would like to ask you about the idea to use scene instances dedicated to the interfacing to the "real reality".</div>
<div> </div>
<div>I call them SCSIs (Server/Controller Scene Instances) and they would not render any 3D graphics, but they would care for simulation and for command and control of the "real life objects".</div>
<div> </div>
<div>What's your opinion about Figure 1 and Figure 2 out of of the glossary (I have copied the chapter about "Multiuser Session" into the mail below):</div>
<div> </div>
<div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;">x) Multiuser Session</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> A multiuser session is an instantiation of an SMS for a concrete set of<br/>
(potential) users.</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> Those (potential) users will be able to inhabit the SMS together.</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> Technically spoken, a multiuser session is a collection of one or more PSIs<br/>
and of zero or more SCSIs (see below), all of which are synchronized to each<br/>
other and connected to the users or to the real reality, respectively.</span></div>
<div style="margin-left: 40.0px;"><br/>
<span style="font-family: Courier New , Courier , monospace;"> +-------------+ +---------+<br/>
User 1 ...... PSI 1 .......| |....... SCSI 1 ......| R R |<br/>
| | | E E |<br/>
User 2 ...... PSI 2 .......| |....... SCSI 2 ......| A A |<br/>
: : | S Y N C | | L L |<br/>
: : : : | I |<br/>
: : : : | T |<br/>
User N ...... PSI N .......| |....... SCSI M ......| Y |<br/>
+-------------+ +---------+</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;">Figure 1: Rough architecture of a Multiuser Session (MS)</span></div>
<div style="margin-left: 40.0px;"><br/>
<span style="font-family: Courier New , Courier , monospace;"> When Figure 1 shows a rough idea of a multiuser session on the one hand,<br/>
then on the other hand this is only valid in the case of pure Virtual<br/>
Reality (VR) (which may be additionally connected to the real reality).</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> This is a very basic case of "Mixed Reality (MR)", where additional cases<br/>
like "Augmented Reality (AR)" or "Augmented Virtuality (AV)" need additio-<br/>
nal considerations.</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> In case of AR/AV, each user (or at least some users) might be co-located<br/>
with a PSI AND with a SCSI (i.e. with a combined PSI/SCSI) and they might<br/>
inhabit the real reality, too.</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> In case of a combined PSI/SCSI we speak about "local SYNC". In case of<br/>
more than one user or more than zero standalone SCSIs, we speak about<br/>
"global SYNC" ("global SYNC" needs networking capabilities).</span></div>
<div style="margin-left: 40.0px;"> </div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;">For example: we have Na AR/AV users, Ms standalone SCSIs and Nv VR users<br/>
===> we have M = Na + Ms SCSIs at all<br/>
===> we have N = Na + Nv PSIs at all</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;"> ||<br/>
PSI n <--local-++-SYNC---> SCSI m +---------+<br/>
USER n (AR/AV)..../ || \............ | R R |<br/>
************** \---inhabit---------------------->/ | E E |<br/>
0 < n < Na + 1 || 0 < m < Na + 1 | A A |<br/>
G || | L L |<br/>
L || | I |<br/>
(standalone SCSI) O |+--------> SCSI m ............ | T |<br/>
***************** B ||S | Y |<br/>
A ||Y Na < m < M + 1 +---------+<br/>
L ||N<br/>
||C<br/>
USER n (VR)....... PSI n <--------+| (standalone PSI)<br/>
*********** || ****************<br/>
Na < n < N + 1</span></div>
<div style="margin-left: 40.0px;"><span style="font-family: Courier New , Courier , monospace;">Figure 2: Local Sync in AR/AV instances of the Multiuser Session (MS)</span></div>
<div> </div>
<div>Looking forward to an answer/discussion</div>
<div> </div>
<div>Yours sincerely,</div>
<div>Christoph
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Montag, 25. Oktober 2021 um 11:07 Uhr<br/>
<b>Von:</b> "Christoph Valentin" <a class="moz-txt-link-rfc2396E" href="mailto:christoph.valentin@gmx.at" onclick="parent.window.location.href='mailto:christoph.valentin@gmx.at'; return false;" target="_blank"><christoph.valentin@gmx.at></a><br/>
<b>An:</b> "Markus Sonntag" <a class="moz-txt-link-rfc2396E" href="mailto:markus.sonntag@tmo.at" onclick="parent.window.location.href='mailto:markus.sonntag@tmo.at'; return false;" target="_blank"><markus.sonntag@tmo.at></a>, "Kevin Wriston" <a class="moz-txt-link-rfc2396E" href="mailto:kevin.wriston@kontron.com" onclick="parent.window.location.href='mailto:kevin.wriston@kontron.com'; return false;" target="_blank"><kevin.wriston@kontron.com></a><br/>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org" onclick="parent.window.location.href='mailto:x3d-public@web3d.org'; return false;" target="_blank">x3d-public@web3d.org</a><br/>
<b>Betreff:</b> [x3d-public] FW: FW: DIGITS #51 - ANN: Making Plans for SrrTrains</div>
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div style="font-family: Verdana;font-size: 12.0px;">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>Dear all,</div>
<div> </div>
<div>I felt free to use a few hours of my autumn's vacations to update the "Glossary" paper of SrrTrains / SMS.</div>
<div> </div>
<div><a href="https://areasharpa.blog/2021/10/25/old-plan-a-update-of-the-glossary/" target="_blank">https://areasharpa.blog/2021/10/25/old-plan-a-update-of-the-glossary/</a></div>
<div> </div>
<div>Summary:</div>
<div>1) The definition of “reality”, “virtual reality” and “real reality” has been slightly corrected<br/>
2) The acronym DIGITS has been re-defined: the second “I” means “Infrastructure” instead of “Information”<br/>
3) In case of AR/AV, one PSI and one SCSI (two instances of the same scene) are co-located at the User Equipment (UE) of the AR/AV User. Both are “locally SYNCed”<br/>
4) In case of VR, a VR User inhabits a “standalone PSI” (without SCSI)<br/>
5) In case of “standalone ITR”, some server equipment contains a “standalone SCSI” (without PSI)<br/>
6) All PSIs and SCSIs of an MS are “globally SYNCed”<br/>
7) Re-definition of the “Operational Modes (OM)” – MRM/pVRM is now orthogonal to SUM/MUM</div>
<div> </div>
<div>Kind regards,</div>
<div>Christoph</div>
<div> </div>
<div> </div>
<div>Original Message ------------------------------------------------------------------------------------------------------------</div>
<div> </div>
<div>Dear all,</div>
<div> </div>
<div>
<div class="ecm0bbzt e5nlhep0 a8c37x1j">
<div class="kvgmc6g5 cxmmr5t8 oygrvhab
hcukyx3x c1et5uql">
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">I could not resist and read my own paper again (after years of ignorance <span class="pq6dq46d tbxw36s4 knj5qynh
kvgmc6g5 ditlmg2l oygrvhab nvdbi5me
sf5mxxl7 gl3lb2sf hhz5lgdu"><img alt="🙂" height="16" src="https://www.facebook.com/images/emoji.php/v9/ta5/1.5/16/1f642.png" width="16"/></span> )</span></div>
<div> </div>
</div>
<div class="o9v6fnle cxmmr5t8 oygrvhab
hcukyx3x c1et5uql">
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">Result: the glossary needs serious rework, because I completely ignored "augmented reality" and "augmented virtuality".</span></div>
</div>
<div class="o9v6fnle cxmmr5t8 oygrvhab
hcukyx3x c1et5uql">
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">Only pure VR is covered and its connection to the "real reality" via an ITR (interface to reality) - i.e. one special case of "Mixed Reality".</span></div>
<div> </div>
</div>
<div class="o9v6fnle cxmmr5t8 oygrvhab
hcukyx3x c1et5uql">
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">I make a distinction between "Virtual Gamer" and "Real Gamer",</span></div>
<div> </div>
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">but if I considered AR/AV additionally (i.e. with a general approach of "all kinds of Mixed Reality") both kinds of Gamers would have to be "merged" for some of all scenarios.</span></div>
<div> </div>
</div>
<div class="o9v6fnle cxmmr5t8 oygrvhab
hcukyx3x c1et5uql">
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">So I need a general approach of an "MR Gamer".</span></div>
<div> </div>
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">KR,</span></div>
<div><span class="d2edcug0 hpfvmrgz
qv66sw1b c1et5uql lr9zc1uh a8c37x1j
keod5gw0 nxhoafnm aigsh9s9 d3f4x2em
fe6kdd0r mau55g9w c8b282yb iv3no6db
jq4qci2q a3bd9o3v b1v8xokw oo9gr5id">Christoph</span></div>
</div>
</div>
</div>
<div> </div>
<div> </div>
<div>Original Message ------------------------------------------------------------------------------------------------------------</div>
<div> </div>
<div>Dear Markus! Dear Kevin! Dear Georg! Dear CCs and BCCs!</div>
<div> </div>
<div>I think, it is the time now to reveal my future plans to the community. Hope, this is OK with you :-)</div>
<div> </div>
<div><a href="https://areasharpa.blog/2021/10/23/what-is-the-way-forward-with-srrtrains/" target="_blank">https://areasharpa.blog/2021/10/23/what-is-the-way-forward-with-srrtrains/</a></div>
<div> </div>
<div>Have a nice Austrian "Nationalfeiertag" next Tuesday,</div>
<div> </div>
<div>Have a nice week,</div>
<div> </div>
<div>Yours sincerely,</div>
<div>Christoph</div>
</div>
</div>
</div>
_______________________________________________ x3d-public mailing list <a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org" onclick="parent.window.location.href='mailto:x3d-public@web3d.org'; return false;" target="_blank">x3d-public@web3d.org</a> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class="moz-signature">--<br/>
Eric Maranne CTO Crisis Simulation Engineering (C.R.I.S.E.) 13855 Aix en Provence / FRANCE Tel: +33 (0)4 42 60 05 01 <a class="moz-txt-link-freetext" href="http://www.vr-crisis.com" target="_blank">http://www.vr-crisis.com</a> -------------------------------------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is confidential and/or proprietary. If you are not the intended recipient, please notify the sender and delete this message.</div>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2">
<table style="border-top: 1.0px solid rgb(211,212,222);">
<tbody>
<tr>
<td style="width: 55.0px;padding-top: 18.0px;"><a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img alt="" height="29" src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png" style="width: 46.0px;height: 29.0px;" width="46"/></a></td>
<td style="width: 470.0px;padding-top: 17.0px;color: rgb(65,66,78);font-size: 13.0px;font-family: Arial , Helvetica , sans-serif;line-height: 18.0px;">Garanti sans virus. <a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" style="color: rgb(68,83,234);" target="_blank">www.avg.com</a></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>