Area 1.0 (refrigerated)

Dear Friends of Realtime 3D Graphics,

While the MR Model Railroad project SrrTrains 1.0 is still being a vision, foreseen beyond the year 2035,

I am on the other hand already doing some considerations about possible next steps for the SrrTrains v0.01 hobby project.

You might remember, I was pursuing a hobby project for several years, but the CORE subject of the project was never met.

This core subject would be the synergies between DIY hobby MR model railroads and professional railway simulations, both using the same 3D models, so the models have to be created only once.

We counted – and we still count – on the X3D standard to do so (https://www.web3d.org).

Unfortunately, the project never made the step from experimental implementation to something serious.

This can change in the future.

Have a nice week

Yours Christoph

Links:

• Vision of SrrTrains 1.0: https://areasharpa.blog/schlussfolgerungen
• SrrTrains v0.01:
• https://areasharpa.blog/about
• https://letztersein.com/srrtrains-v0-01

Dear Friends of Realtime 3D Graphics

In the “Glossary of the SrrTrains Project” (https://simulrr.sourceforge.net/concepts/001_Glossary.pdf), in appendix A.2, I had published a few assumptions about SMUOS.

Here, in this Blog posting, I am feeling free to highlight those assumptions that COULD be relevant for relativistic software.

[…]A.2. Basic Assumptions about a Possibly Suggested X3D Component “SMUOS”
———————————————————————–
1. SMUOS will follow the enhanced model/module/frame paradigm (eMMF paradigm)
2. Basic assumptions about SMS models (*M*MF)
2.1. SMS models are represented using declarative 3D principles
2.2. Models can be rendered (they are visible, audible, sensible, …)
2.3. Models are rendered relative to a module
2.4. If models are not attached to a module, then they cannot be rendered
2.5. SMS models contain MIDAS objects to become multiuser capable
2.6. MIDAS objects depend on the SMUOS component. They are specialized to
distinct use cases (binary switch, carousel drive, …)
2.7. MIDAS objects cannot be rendered. They make only sense together with
a model or module
3. Basic assumptions about SMS modules (M*M*F)
3.1. An SMS module is NOT a tile
3.2. SMS modules are represented using declarative 3D principles
3.3. A module renders a (small) part of a virtual universe
3.4. A module spans a (pseudo) euclidean space time, where models and/or
avatars can meet
3.5. The relation of a module’s coordinate system to the world coordinate
system of the Web3D browser is “for further study” (ffs.)
3.6. Modules can contain “intrinsic” models. “Intrinsic” models are imple-
mented directly as a part of a module
3.7. Modules can contain “bound” models. “Bound” models are implemented
separately from modules, so that they can be used by many modules.
3.8. Modules can contain “unbound” models. “Unbound” models can be loaded
or unloaded independent of all modules. If created, an unbound model can
be “assigned” to a module. Changing the assignment from one module to
another is called “handover”
3.9. Each SMS module contains an instance of the “SMS module coordinator”.
The SMS module coordinator is a node defined by the SMUOS component.
The SMS module coordinator cannot be rendered, but it coordinates all
MIDAS objects of all models that are attached to its module
4. Basic assumptions about the SMS frame (MM*F*)
4.1. The frame integrates one or more SMS modules into a VR/AR platform
4.2. The frame is responsible to register, load or unload top level modules
4.3. SMS models cannot be contained directly in the frame. A module must be
in between
4.4. If the scene shall be multiuser capable, then the frame
4.4.1. is responsible to initialize the used MU system and to provide a
“sessionId” to the SMUOS component
4.4.2. must provide a network connection to the SMUOS component
4.5. The SMS frame contains an instance of the “Simple Scene Controller”,
which is a node defined by the SMUOS component.
The “Simple Scene Controller” cannot be rendered, but it controls the
SMS module coordinators of all SMS modules and hence it controls the
complete SMUOS component within a scene instance
5. Basic assumptions about “classic avatars”
5.1. Classic avatars have N instances, where one instance – the so-called
“pilot” – is part of the scene instance that is used by the user, who
is represented by the avatar, and the other N – 1 instances – the
so-called “drones” – just follow the pilot
5.2. With the help of the special MIDAS object “Avatar Container”, we can
5.2.1. assign avatars to the frame (world coordinate system)
5.2.2. assign avatars to some module (module coordinate system)
5.2.3. assign avatars to some model
5.3. Please be aware: SMS models can NOT be rendered relative to the world
coordinate system. SMS models can NOT be rendered relative to SMS models
5.4. Hence classical avatars are NOT SMS models
6. Basic assumptions about “UM avatars” (unbound model avatars)
6.1. UM avatars are unbound SMS models
6.2. UM avatars are models that represent a virtual identity
7. Basic assumptions about moving modules
7.1. There will be a special MIDAS object, let’s call it “Module Container”,
that will allow to instantiate SMS modules as parts of an SMS model
7.2. Hence the “basic MMF paradigm”
frame – 1:n – module – 1:n – model
will become the “enhanced MMF paradigm”
frame – 1:n – module – 1:n – model -1:n – module – 1:n – model ad. inf.[…]

Have a nice week

Yours CP/V

Dear Friends of Realtime 3D Graphics,

I guess, you all know the joke about how to ride a dead horse. Here’s one of the thousands of links that publish this old story, which has been happening in history all the time and again and again:

https://www.kenhomer.com/single-post/2018/08/03/modern-strategies-for-riding-a-dead-horse

However, before we will have sold the dead horse to the new owner – who shall then perform the preparation of the dead horse for another owner – we must hide the fact that the horse is already dead (de facto).

Hence we shouldn’t talk too much about Web3D graphics and relativity, at the time being, because relativity will kill the current horse and replace it by the next horse, but the current horse is not yet sold and shall not be “eaten” by the next horse.

Hidden Hints about 3D Graphics and Relativity

However, I brought a few points about 3D graphics and relativity – as far as I can grasp and understand it – as easter eggs into my narration about “The third child”:

The narration can be found HERE.

The first and second part of the narration do not publish any idea about relativity, but a subtle hint: One of Walter’s children is named “Lieserl”, which was the first name of Albert Einstein’s first daughter (it’s a short form for “Elisabeth”).

More Clarity in Part Three of the Narration

In the third part of the narration, in a side story the siblings Lieserl and Conrad Peter work on a Software Project about relativistic software. It’s nowhere explicitly mentioned that it is about 3D Graphics, but the third part will not be actively pursued anyway, until “the horse will have been sold”.

Following chapters of the narration are relevant:

[…]1.5.
Lieserl is attending a lecture on general relativity.
The lecturer: “And at the end of this year’s lecture I would like to draw your attention, dear colleagues, to the fact that there will be a competition next year.
There are only a few years left until the 400th anniversary of the principle of relativity and so we would like to consciously set incentives to develop software programs and software concepts that are only based on the theory of relativity and no longer on the approximations of classical physics. So, ladies and gentlemen, if you have a good idea about the summer, get in touch with me. Prize money and recognition from the academic senate beckon. “[…]

[…]1.6.
Lieserl and Conrad Peter are sitting in an ice cream parlor, it’s a sunny summer day.
C.P .: “Thank you for inviting me”
Lieserl: “You don’t pass the technnical college diploma every day. Do you already know how to continue? Are you going to study too?”
C.P .: “No, I’m looking for a job now, my freedom is more important to me.”
Lieserl: “Say, Conrad, you know your way around computers.”
C.P .: “Well, let’s put it this way: everything that has a CPU usually obeys me.”
Lieserl: “Yes, that’s what I mean. We have a competition for relativistic approaches in computer technology at our university.”
C.P .: “I’m sorry, I don’t understand anything about the theory of relativity.”
Lieserl: “I can explain that to you. Differential geometry is about always describing small parts of the universe with equations and then putting the large universe together from small parts. <E Minori ad maiorem>“.
C.P .: “That reminds me of our good old ‘My Reality’ computer game. There we also put the scenes together from partial scenes”.
Lieserl: “But it is important that none of the parts have a special position“
C.P. (pulls the air through between the teeth): “That will be difficult”
C.P. (thinks for a while): “But do you remember the railway line from Wiener Neustadt to Puchberg, which we had as children? It could represent part of the scene. If we now add the data for the main line from Wiener Neustadt to Mürzzuschlag then we could put the scene together from two parts and also program the handover “.
Lieserl: “Well, we’ll do that!”[…]

[…]1.10
Conrad Peter started thinking about Lieserl’s project. Now they sit together and discuss the details.
C.P .: “Well, roughly speaking, our software will consist of three parts”
Lieserl: “Nice number” (giggles)
CP: “First of all there is the” telecommunications infrastructure “. This is the basis of the whole thing, so we should be flexible and support every possible type of transport layer: http, https, TCP, UDP, SCTP, TLS, RTP, SRTP, XMPP, SIP, 3GPP IMS, 3GPP MCx and whatever they are called.”
Lieserl: “Yes, I understand that. This is where we will have to communicate most of the time with other projects. Is it OK for you if I take on this part?”
CP: “Yes, of course! The second part is the protocol in the application layer, on the one hand to connect the scenes with one another via a broker, and on the other hand to connect special “blind scenes” to the real objects via brokers. I would do the part gladly take over. I already have some ideas for an <Event / State Description Protocol> ESDP “.
Lieserl: “Yes, that suits me very well. But you mentioned three parts, where is the third one?”
C.P .: “Exactly the third part is the problem. It’s about the download of geospatial data through a distributed database. So far I have no plan how we could approach it”.
Lieserl: “Well, but it’s a start.” (hesitates briefly, has a flash of inspiration) “but can you remember the dealer who got us the Semmering Railway? He surely knows a lot about downloads, uploads and the combination of geodata.”
C.P .: “Could be, but we don’t have his name”.
Lieserl: “No, not that. But maybe you can still find his phone number. You know, I know how to hack phones”.
C.P .: “OK”[…]

[…]1.12
Lieserl and Conrad Peter have thought about their project and meet again in the ice cream parlor to forge further plans.
C.P .: “A few days ago I came across a good article about <Mixed Reality>”.
Lieserl: “Is that where you hide behind an avatar so you don’t have to come out?”
CP .: “No, that is <Virtual Reality>, but things have to do with each other. <Mixed Reality> is actually just the umbrella term for some very different technologies that are supposed to enable us to better cope with <real> reality come to <enlarge> them. “
Lieserl (looks uninterested): “Aha. And what does that have to do with our project?”
C.P .: “That has a lot to do with and with what you have achieved with our <dealer> of geodata” (says the word “dealer” in a disparaging tone)
Lieserl (ostentatiously rolls her eyes): “Oh, him! I’m not interested in him.”
C.P. looks a little confused, thinks: “Well, maybe the distributed database is not the most urgent of the three software components. So let’s start with the telecommunications infrastructure”
Lieserl: “Yes! Our project will require many services from the lower layers:
– Telephony (audio and video)
– telegraphy
– Position and status reports
– Geographic Infrastructure
So we will need a flexible hierarchy of networks in which all services are integrated – an <Integrated Services Digital Networks, Tree of> – ISDN / To, so to speak.[…]

[…]2.3.
Lieserl and Conrad Peter get together again to talk about their relativistic software project. You will see how multiuser scenes could “give the Virtual Globes a go” and why the Virtual Globes are dependent on a large number of users[…]

[…]2.5.
Lieserl and Conrad Peter are making progress with their project.
You find out what it has to do with the theory of relativity.
But unfortunately it is too late to compete.
Judgments are made[…]

[…]2.20.
After Thanksgiving – it’s raining and it’s “typically Irish autumnal” – Lieserl and her fellow student sit at the window for a long time and talk.
He asks her why she came to Ireland from Austria, but she gives an evasive answer. They talk – also – about astrophysics and the software project.
You have a realization: if the multiuser scenes and the virtual globes do not cooperate, nothing can come of the whole thing.[…]

Closing Remarks

The vision is also explained in short words here: Conclusions of SrrTrains v0.01

a.m.D.g.

Dear Friends of Open Metaverse,

You might have noticed: I have renamed this Blog from “Area #A, the 10th state of Austria” into “Area 1.0, the 10th state of Austria”.

What is the reason? Well, I want to avoid a possible misconception.

Which misconception?

Hmmm. I talked a lot about some “Plan A”, “Plan B” and “Plan C”, and how I want to behave in connection with the ideas that have emerged from the project SrrTrains v0.01 (see https://areasharpa.blog/schlussfolgerungen/ and https://areasharpa.blog/2022/12/03/the-great-achievement-of-2022/).

Now, this Blog is NOT specifically about “Plan A”, so I try to avoid the “A” in the name, furthermore I want to focus on version 1.0 of the SrrTrains project in future, hence I thought “Area 1.0” would be a valid name.

Btw.: I do NOT change the domain name “areasharpa.blog”, to avoid broken links and generally a mess with the links.

Have a nice week

Yours Christoph

Dear All,

Following New Year’s Resolutions apply to my (non-)activity with respect to the 3D Web:

1. Stick to Plan C
2. If “Something like Plan A” is started
   • Start Project Fiat A as a “Lighthouse Project”
   • Try to found “Society for Lifelong Collaborating”
   • Try to pursue “Plan B”

About the Details:

1. Stick to Plan C

Plan A, Plan B and Plan C are explained at the posting Spark#41-Clarifications. Plan C means basically: I will not actively pursue the idea of “Integrated 3D Collaboration” at my employer’s.

2.a. Start Fiat A Project

The Fiat-A project will be started, if and only if I encounter positive evidence for some “Integrated 3D Collaboration” project at the industry (may I be involved in that project or not).

Explicitly the non-starting of the Fiat-A project will NOT be an evidence for such “Integrated 3D Collaboration” project has not been NOT started at all.

The Fiat-A project will not have a deadline. It will be “done, when it’s done”.

2.b. The Society

In a first step, I will be looking in the DACH region for participants of “The Society” (DACH = Germany, Austria, Switzerland) – see (German language): digits#88 Kopf gesucht.

2.c. Try to Pursue “Plan B”

This cannot be described in a more detailed way, currently.

Happy New Year

Yours Christoph

Liebe Familie, Freunde und Kollegen

Diesmal, mit Newsletter Nr. 88, möchte ich einen Aufruf machen.

Wie Ihr wisst, geht es mir um Nachhaltigkeit im besten Sinne, und eine der wichtigsten Strategien, um nachhaltig zu leben, ist es m.E. den Frieden zu halten.

Den inneren Frieden mit uns selbst und Gott, sowie den äußeren Frieden mit den “lieben” Mitmenschen.

Wir betreiben einen Krieg gegen die nächste Generation. Abgetrieben zu werden, ist mittlerweile eine der häufigsten Todesursachen, häufiger noch, als bei einem Verkehrsunfall ums Leben zu kommen.

Obwohl ja manche Menschen versuchen, Abtreibungen als eine Art “Verkehrsunfall” abzutun 😮

Mein geplanter Verein, die “Society for lifelong collaborating”, ist nun ein Friedensprojekt, ein Platz im Web, an dem sich die “ganze Welt treffen kann”, und ich meine wirklich die GANZE Welt, inklusive China, Rußland und Afrika.

Es ist noch nicht klar, welche technischen Hilfsmittel wir verwenden werden, seien es VPNs oder gar TOR Browser, jedenfalls werden in der Anfangszeit des Vereins Leute mit IT Background dringend benötigt werden.

Meldet Euch doch. Am dringendsten brauchen wir einen Vereinsobmann, den Kassier und den Schriftführer kann ich selber geben.

Die geplanten Statuten findet man hier: https://areasharpa.blog/2022/02/23/statutes-for-the-society/

Weitere Info: https://areasharpa.blog/2022/02/27/the-time-has-not-yet-come/

Vereins-Impressum
https://lc-soc-lc.or.at/addendum.htm

Lg,
Christoph

…is for sure the following fact:

I actually started the DIGITS/S&P-ARK/ALPES project:

https://areasharpa.blog/2022/05/14/spark37-project-really-started/

and the second achievement is:

I have decided for “Plan C”:

https://areasharpa.blog/2022/09/04/spark41-clarifications/

Unfortunately, there are also two drawbacks:

1. The “Society for Lifelong Collaboration” was not founded: https://areasharpa.blog/2022/02/27/the-time-has-not-yet-come/
2. The ALPES project did not make progress in 2022

Have a nice week

Yours Christoph

I think I should pass this on now:

in 2000 I learned two sentences from 2 “angels” that I only understood a few weeks ago:

1. Time does not matter
2. Never alone

I now think that this has something to do with the tandem operation of RADAR stations.

Dear Friends of Realtime 3D Graphics, 3D Web, Enternet, Metaverses and similar topics!

I am not sure, whether it is important, but during the last weeks and months I have sent some signals via this Blog that could eventually lead to serious misconceptions.

First, and most important: the statements given in following blog posting are still valid!!!

That is, in detail:

• I have prepared for “Plan A” (meanwhile abandoned): convince my employer to start projects about what-I-call “Integrated 3D Collaboration” (integrated with NGN, integrated with MCN, 3GPP/ETSI based)
• I have prepared for “Plan B”: support “Integrated 3D Collaboration” on my own, based on IETF/W3C/Web3D (still desired during my spare time)
• I have prepared for “Plan C”: abandon any professional support of “Integrated 3D Collaboration” (finally selected)

This “Decision for Plan C” was made public on my Facebook account.

Anyway: if I stumble over some reliable indication that tells me something equivalent to my “Plan A” has been started somewhere within the industry, then I will “officially start” my project “Fiat-A” as an “encoded hint bit” for the Web3D community. This statement is still true, although I have officially abandoned my “personal Plan A”.

The above statement about the project “Fiat-A” is independent of an optional foundation of a “Society for Lifelong Collaborating”, which might happen any time without any implication, and it is independent of the S&P-ARK project, which has been started in spring 2022 without any reason.

I think, I could have caused some confusion with those two initiatives.

The following blog posting indicated the start of the DIGITS/S&P-ARK/ALPES project. I am still not sure, and I will have to define, whether this project is still a “template” project (i.e. not a REAL project, but a project, which I use to report my opinion about projects that *should* be started by the community) or not.

The following blog posting should be completely ignored, discussion is not yet closed.

Have a nice week

Yours Christoph