<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi Sven-Erik</div>
<div> </div>
<div>Just to ensure that I have understood your explanation, let me repeat:</div>
<div> </div>
<div>1) First we have the scenario of a pure virtual multiuser session.</div>
<div> </div>
<div>In this case, each instance of a Web3D browser would be identified by a "bare JID", e.g. "myWeb3dAccount@web3d.kapsch.net".</div>
<div> </div>
<div>The chat room on the server would also be identified by a "bare JID", e.g. "temporaryRoomXYZ@web3d.chatrooms.operatorX.com".</div>
<div> </div>
<div>Now you suggest to re-use the proposed XEP http://xmpp.org/extensions/inbox/sensor-network-control.html , you suggest to identify the X3D network sensors by the resourcepart of the JID,</div>
<div> </div>
<div>e.g. identify the network sensor within the client: myWeb3dAccount@web3d.kapsch.net/scene.house.door</div>
<div>e.g. identify the network sensor within the server: temporaryRoomXYZ@web3d.chatrooms.operatorX.com/scene.house.door</div>
<div> </div>
<div>My concerns:</div>
<div style="margin-left: 40px;"> </div>
<div style="margin-left: 40px;">a) The referenced XEP is intended to be used for internet of things, not for pure virtual 3D multiuser sessions. Future development of that standard might divert from the needs of 3D multiuser sessions</div>
<div style="margin-left: 40px;"> </div>
<div style="margin-left: 40px;">b) I'm not an expert in XMPP, but I'm not sure, if the resourcepart of the JID will really be a good place to identify the X3D streamName</div>
<div> </div>
<div>2) Second we have the scenario where the multiuser session is really connected to some sensors and/or actuators in outside world</div>
<div> </div>
<div>I.e. we have an X3D multiuser session (see item (1)), where one instance of the Web3D browser is not really an instance of a Web3D browser, but it renders an interface to real world (I would call this instance the ITR - interface to reality).</div>
<div> </div>
<div>Thus to the left side of the ITR we would have a "simple 3D multiuser session", to the right side we would have "internet of things".</div>
<div> </div>
<div>In this case the proposed XEP would perfectly fit to the "right side", where the applicability to the "left side" would be questionable, imho (see above).</div>
<div> </div>
<div>Here imho I would rather suggest to take the know how from the referenced XEP and apply the know how to a new XEP, especially intended for 3D multiuser sessions and let the ITR be a relaying device between both standards.</div>
<div> </div>
<div>Just thoughts</div>
<div> </div>
<div>Kind regards</div>
<div>Christoph</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> Freitag, 19. April 2013 um 10:28 Uhr<br/>
<b>Von:</b> "Sven-Erik Tiberg" <Sven-Erik.Tiberg@ltu.se><br/>
<b>An:</b> "<x3d-public@web3d.org> mailing list (x3d-public@web3d.org)" <x3d-public@web3d.org><br/>
<b>Betreff:</b> [X3D-Public] FW: FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control</div>
<div name="quoted-content"><!--p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0.0cm; font-size: 12.0pt; font-family: "Times New Roman" , serif;}a:link, span.MsoHyperlink { color: blue; text-decoration: underline;}a:visited, span.MsoHyperlinkFollowed { color: purple; text-decoration: underline;}p.MsoAcetate, li.MsoAcetate, div.MsoAcetate { margin: 0.0cm; font-size: 8.0pt; font-family: Tahoma , sans-serif;}span.BalloonTextChar { font-family: Tahoma , sans-serif;}span.EmailStyle19 { font-family: Calibri , sans-serif; color: rgb(31,73,125);}span.EmailStyle20 { font-family: Calibri , sans-serif; color: rgb(31,73,125);}*.MsoChpDefault { font-size: 10.0pt;}div.WordSection1 { page: WordSection1;}-->
<div>
<div class="WordSection1">
<p class="MsoNormal"><b><span style="font-size: 10.0pt;font-family: Tahoma , sans-serif;"> </span></b></p>
<p class="MsoNormal"><span style="font-size: 10.0pt;font-family: Tahoma , sans-serif;color: rgb(31,73,125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">Hi Christoph</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">XMPP uses JabberID method for to / from</span><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);"> addressing </span><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">as for example “ <a href="me@rad.siemens.at" target="_parent">me@rad.siemens.at</a> ” </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">N.B. the JID domain are completely independent of any dns entry. </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">Is’s possible to add location to the JID as for example“ <a href="me@rad.siemens.at/officedesk" target="_parent">me@rad.siemens.at/officedesk</a> ”</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">PS. Jabber/XMPP servers as ejabberd uses server2server protocol to transmit stanzas between jabber domains.</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">Ejabbed are originally based on LM Ericsson system for phone switchboards and are fast to setup connections and transmit packages.</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">To map stanzas to f.ex. a X3D sceene use either strophe.js ( or libstrophe ( C++ ) ) scripts and ROUTE events to the sceene.</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">/Sven-Erik</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);"> </span></p>
<div>
<div style="border: none;border-top: solid rgb(181,196,223) 1.0pt;padding: 3.0pt 0.0cm 0.0cm 0.0cm;">
<p class="MsoNormal"><b><span style="font-size: 10.0pt;font-family: Tahoma , sans-serif;">From:</span></b><span style="font-size: 10.0pt;font-family: Tahoma , sans-serif;"> Christoph Valentin <a href="[mailto:christoph.valentin@gmx.at]" target="_parent">[mailto:christoph.valentin@gmx.at]</a><br/>
<b>Sent:</b> den 17 april 2013 18:39<br/>
<b>To:</b> Sven-Erik Tiberg<br/>
<b>Cc:</b> <<a href="x3d-public@web3d.org" target="_parent">x3d-public@web3d.org</a>> mailing list (<a href="x3d-public@web3d.org" target="_parent">x3d-public@web3d.org</a>)<br/>
<b>Subject:</b> Aw: [X3D-Public] FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control</span></p>
</div>
</div>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Hi Sven-Erik</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Interesting for me: yes (you know). Interesting for someone else: sorry, don't know</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Mainly I see an issue in addressing.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">This proposed XEP addresses a sensor in the network by "to"/"from" (an URI) and by name_of_the_parameter.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Network sensor addresses a value by "streamName" + name_of_the_parameter.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">How to relay "to"/"from" URIs to stream names and vice versa?</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">How to map message stanzas and iq stanzas to events and states?</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Just two cent</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Christoph</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
<div style="border: none;border-left: solid rgb(195,217,229) 1.5pt;padding: 0.0cm 0.0cm 0.0cm 8.0pt;margin-left: 7.5pt;margin-top: 7.5pt;margin-right: 3.75pt;margin-bottom: 3.75pt;">
<div style="margin-bottom: 7.5pt;">
<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">Gesendet:</span></b><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> Mittwoch, 17. </span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">April 2013 um 10:45 Uhr<br/>
<b>Von:</b> "Sven-Erik Tiberg" <</span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="Sven-Erik.Tiberg@ltu.se" target="_parent"><span>Sven-Erik.Tiberg@ltu.se</span></a></span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">><br/>
<b>An:</b> "<</span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="x3d-public@web3d.org" target="_parent"><span>x3d-public@web3d.org</span></a></span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">> mailing list (</span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="x3d-public@web3d.org" target="_parent"><span>x3d-public@web3d.org</span></a></span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">)" <</span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="x3d-public@web3d.org" target="_parent"><span>x3d-public@web3d.org</span></a></span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">><br/>
<b>Betreff:</b> [X3D-Public] FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">FYI: can this be of interest for the definition and implementation of X3D Network Sensor Node.<br/>
/Sven-Erik Tiberg<br/>
<br/>
-----Original Message-----<br/>
From: </span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="standards@xmpp.org" target="_parent"><span>standards@xmpp.org</span></a></span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> .. </span><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">On Behalf Of XMPP Extensions Editor<br/>
Sent: den 16 april 2013 22:21<br/>
<br/>
The XMPP Extensions Editor has received a proposal for a new XEP.<br/>
<br/>
Title: Sensor Networks - Control<br/>
<br/>
Abstract: This specification describes how to control devices or actuators in an XMPP-based sensor network.<br/>
<br/>
URL: <a href="http://xmpp.org/extensions/inbox/sensor-network-control.html" target="_blank"> http://xmpp.org/extensions/inbox/sensor-network-control.html</a><br/>
<br/>
The XMPP Council will decide in the next two weeks whether to accept this proposal as an official XEP.</span><br/>
<br/>
<br/>
<span style="font-size: 9.0pt;font-family: Verdana , sans-serif;">_______________________________________________<br/>
X3D-Public mailing list</span><br/>
<span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="X3D-Public@web3d.org" target="_parent"><span>X3D-Public@web3d.org</span></a></span><br/>
<span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank"><span>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</span></a></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: Verdana , sans-serif;"> </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div> </div>
<div class="signature"> </div></div></body></html>