[x3d-public] WG: Fw: FW: The SP-ARK project

Mon Feb 5 03:03:07 PST 2018

Any thoughts?

Von meinem Samsung Gerät gesendet.
-------- Ursprüngliche Nachricht --------
Von: Christoph Valentin <christoph.valentin at gmx.at>
Datum: 05.02.18 11:58 (GMT+01:00)
An: Valentin Christoph <Christoph.Valentin at kapsch.net>
Betreff: Wg: Fw: FW: The SP-ARK project

--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 05.02.18, 10:51, Christoph Valentin <christoph.valentin at gmx.at> schrieb:
f.y.i. Most important e-mail in the e-mail chain is 4.2.2018, 13:17

Gesendet: Montag, 05. Februar 2018 um 10:33 Uhr
Von: "Valentin Christoph" <Christoph.Valentin at kapsch.net>
An: "christoph.valentin at gmx.at" <christoph.valentin at gmx.at>
Betreff: FW: The SP-ARK project
f.y.i.
________________________________
From: Valentin Christoph
Sent: 05 February 2018 03:23
To: Sven-Erik Tiberg (Sven-Erik.Tiberg at ltu.se)
Cc: brutzman at nps.edu
Subject: RE: The SP-ARK project

Hi Sven-Erik,

I know, I am annoying, because I send e-mail after e-mail without waiting for an answer (probably you cannot answer, it's weekend - so sorry).

But for the sake of our mission, let me explain, what I WOULD do with the SP-ARK project, if I had supporters.

Democratic Approach:
1) I would try to get more info from WebVR, WebAR, WebXR, whatever, and from gaming consoles, from game engines like Unity etc to get an overview, whether anybody is interested in IETF standards for multiuser VR scenes and mixed reality scenes. I fear, not everybody has understood the force of global communication protocols (separating client from server by defining their interface independent from a specific product).
2) I would try to break down all existing protocols to "something like network sensor", where I would suggest to keep the "3D Web" and the "IoT" separate (sensor networks vs. network sensor :-) )

Expert Approach
1a) I would take the Event Stream Sensor from BS Collaborate / BS Contact
2a) I would add the fourth use case of the ESS (see the slides at GIT repository)

3) With this "Mature Network Sensor (MNS)" I would ask one provider of a Web3D Browser and one provider of a Collaboration Server to implement and define the protocol together ----> this implementation work will need a test case. For this test case I would rebase the SMUOS Framework from SMUOS A (old network sensor) to SMUOS B (MNS) and I would keep the SMUOS B within the repository of SP-ARK. SrrTrains could be used as test application above the SMUOS B.

4) If then the SMUOS B is used by an acceptable number of applications, SMUOS Extensions and MIDAS Objects (all have to be declared "experimental"), we could define an X3D Component from the SMUOS B (i.e. SMUOS C)

5) Then the SP-ARK project has done its duty and can be deleted.

6) SrrTrains v1.0 will use SMUOS C.

Sorry, I have not explained this earlier, my fault.

All the best
Christoph

P.S.: I have not considered how to get the terrain data from a virtual globe, tbd.

________________________________
From: Valentin Christoph
Sent: 04 February 2018 13:17
To: Sven-Erik Tiberg (Sven-Erik.Tiberg at ltu.se)
Cc: Onic Roman; brutzman at nps.edu; Roiger Angela
Subject: RE: The SP-ARK project

Hi Sven-Erik,

I would be even pleased, if you forked the http://github.com/christoph-v/spark project and if you used it for the good of mankind.

I will be available as consultant, anytime.

Have a nice week
Christoph
________________________________
From: Valentin Christoph
Sent: 03 February 2018 18:25
To: Sven-Erik Tiberg (Sven-Erik.Tiberg at ltu.se)
Cc: Onic Roman
Subject: The SP-ARK project

Hi Sven-Erik,

I remember my first steps of the SrrTrains project (it had not even the name SrrTrains those early times), when I looked for implementations of the network sensor and when I found some interesting entries at the Octaga Community fora, where some Mr. Tiberg was looking for information about the network sensor, too.

Later you told me about your project of defining the networking mechanisms (and protocols) for the network sensor using some JavaScript libraries. Even later I understood your concepts were about W3C Browsers hosting JavaScript Based Web3D Browsers (X3DOM, X_ITE). Right?

However, my own project went another direction. I did not care about the networking protocols, because I bound my project to the Bitmanagement Ges.m.b.H. and to the classical Web3D Browser products BS Contact / BS Collaborate, which already used some protocol - this protocol being proprietary, though.

I focussed on the "client-side calculations" and on the "meta-structure" of the scene, which I thought would be important for the definition of the protocol in a later stage.

Now I come back and have defined the "SP-ARK" project - I have granted the output of the SrrTrains v0.01 project as an input to the SP-ARK project - licensing the papers (.odt) by a proper GPL.

The first goal of the SP-ARK project is the support of a proper definition of the X3D Network Sensor (including the network protocol, e.g. as IETF RFC).

Do you think, you or someone else from LTU could feel well, when supporting or even joining the SP-ARK project? I will start this project only, when it gets some supporters.

http://areasharpa.wordpress.com/spark

@Roman: this e-mail is about my private SP-ARK project, but it is not about anything that can be foreseen for the use at Kapsch CarrierCom. However, the use cases are similar, therefore it might happen, that our current KCC concepts could be replaced in a later future (e.g. after my retirement) by that concepts, which this e-mail is about.

Looking forward to an answer
Yours Christoph

________________________________
From: x3d-public [x3d-public-bounces at web3d.org] on behalf of Valentin Christoph [Christoph.Valentin at kapsch.net]
Sent: 03 February 2018 12:35
To: x3d-public at web3d.org
Subject: [x3d-public] f.y.i.

https://areasharpa.wordpress.com/2018/02/03/spark7-construction-work-starts/

The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180205/d283abba/attachment.html>