[X3D-Public] FW: FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control

Sat Apr 20 02:17:32 PDT 2013

Guess I jumped ahead to far in my ideas.

Forgott to explain the idea that "Sensor Networks - Control" can be a complement to the X3D sceen Network protocoll suggested and used for X3D-sceen in that sence that "Sensor Networks - Control" could be used to extend the X3D-spaces to real or virtual sesor and control units or simulation units or,,,

An example A X3D-sceene in a X3D-space can be used as a gateway between "XMPP Sensor Networks - Control" setup and f.ex OpenDIS.

As the Proposed XMPP extension for sensor networks - control can be a used by a veriety of unit suppliers we do not need to implement any X3D suggested protocoll.

This can open up the application areas of factory / plant / traffic control management.

Where X3D-sceens in the X3D-space can present and interact of different scope of the control system.

Just a possibility.

/Sven-Erik

________________________________
From: X3D-Public [x3d-public-bounces at web3d.org] on behalf of Sven-Erik Tiberg [Sven-Erik.Tiberg at ltu.se]
Sent: Friday, April 19, 2013 10:28 AM
To: <x3d-public at web3d.org> mailing list (x3d-public at web3d.org)
Subject: [X3D-Public] FW: FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control

Hi Christoph

XMPP uses JabberID method for to / from addressing as for example “ me at rad.siemens.at<mailto:me at rad.siemens.at> ”
N.B. the JID domain are completely independent of any dns entry.
Is’s possible to add location to the JID as for example“ me at rad.siemens.at/officedesk<mailto:me at rad.siemens.at/officedesk> ”
PS. Jabber/XMPP servers as ejabberd uses server2server protocol to transmit stanzas between jabber domains.
Ejabbed are originally based on LM Ericsson system for phone switchboards and are fast to setup connections and transmit packages.

To map stanzas to f.ex. a X3D sceene use either strophe.js ( or libstrophe ( C++ ) ) scripts and ROUTE events to the sceene.

/Sven-Erik

From: Christoph Valentin [mailto:christoph.valentin at gmx.at]<mailto:[mailto:christoph.valentin at gmx.at]>
Sent: den 17 april 2013 18:39
To: Sven-Erik Tiberg
Cc: <x3d-public at web3d.org<mailto:x3d-public at web3d.org>> mailing list (x3d-public at web3d.org<mailto:x3d-public at web3d.org>)
Subject: Aw: [X3D-Public] FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control

Hi Sven-Erik

Interesting for me: yes (you know). Interesting for someone else: sorry, don't know

Mainly I see an issue in addressing.

This proposed XEP addresses a sensor in the network by "to"/"from" (an URI) and by name_of_the_parameter.

Network sensor addresses a value by "streamName" + name_of_the_parameter.

How to relay "to"/"from" URIs to stream names and vice versa?

How to map message stanzas and iq stanzas to events and states?

Just two cent
Christoph

Gesendet: Mittwoch, 17. April 2013 um 10:45 Uhr
Von: "Sven-Erik Tiberg" <Sven-Erik.Tiberg at ltu.se<mailto:Sven-Erik.Tiberg at ltu.se>>
An: "<x3d-public at web3d.org<mailto:x3d-public at web3d.org>> mailing list (x3d-public at web3d.org<mailto:x3d-public at web3d.org>)" <x3d-public at web3d.org<mailto:x3d-public at web3d.org>>
Betreff: [X3D-Public] FW: [Standards] Proposed XMPP Extension: Sensor Networks - Control
FYI: can this be of interest for the definition and implementation of X3D Network Sensor Node.
/Sven-Erik Tiberg

-----Original Message-----
From: standards at xmpp.org<mailto:standards at xmpp.org> .. On Behalf Of XMPP Extensions Editor
Sent: den 16 april 2013 22:21

The XMPP Extensions Editor has received a proposal for a new XEP.

Title: Sensor Networks - Control

Abstract: This specification describes how to control devices or actuators in an XMPP-based sensor network.

URL: http://xmpp.org/extensions/inbox/sensor-network-control.html

The XMPP Council will decide in the next two weeks whether to accept this proposal as an official XEP.

_______________________________________________
X3D-Public mailing list
X3D-Public at web3d.org<mailto:X3D-Public at web3d.org>
http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20130420/9843886a/attachment-0001.html>