[x3d-public] [x3d] Web3D interop publish/subscribe

[John Carlson]

Thanks, Nicholas!

I have some thoughts related to JSONverse/Argonverse, a multiuser X3D
authoring/publishing system.  This is a think pad, and requires no
response.  Even though this is sent to Nicholas, anyone can contribute.  In
particular, I’m interested in old networking group members to chime in.

1)  I am currently planning on using socket.io on multiple servers for
multiple authors to publish scenes to multiple users or clients.  This is
the base profile and MVP.  I plan on modifying an old multiple user system
I have.

2) Might there be a way to publish Inlines and PROTOs individually?  Can
this be done with SAI or DIS?  Without knowing in advance which Inlines and
PROTOs will be updated?

3)  How might individual images/audio/video be updated within a scene for
all users?  SAI or DIS?

4) What might be a good publish/subscribe user interface?  Update changes
vs Update whole scene?  Receive changes vs Receive whole scene vs Live
update?

5) How might someone who joins the party late receive the whole scene?  Do
we need to store the whole scene on the server?  Is there a way to replay
updates?

6) My LIRCom does updates, but in some  cases, allows for a client to
SELECT data from other clients.  Is this really feasible unless one other
client is chosen, or there’s a “scene reference” to download scenes from?
What happens if the scene reference goes away?

7) I realize in the past multi-user editing was done with XMPP, and
probably updated individual characters in edit mode.

8) I’m looking for way to do this without polluting the scene with tons of
publish and update scripts, keeping update scripts external to the X3D
scene, so the scene author can use a simple publish/update button combo.

9) How might this be tied to Omniverse or the Metaverse?

I realize this is better for a networking group, but I’m not aware of a
networking group in Web3D.  Is there one for the MSF?  When there was a
networking group in Web3D, the discussion was about protocols, instead of
the above.

I am aware of DIS for multiple avatars scene updates, but I’m more worried
about publishing DIS scenes than communicating avatar position updates.

This is like a multiple user authoring system along with multiple user
browsing.

Thanks,

John
On Tue, Aug 13, 2024 at 10:59 PM Polys, Nicholas <npolys at vt.edu> wrote:

> Greetings all!
>
> Its been a very exciting year !
>
> As we take the SIGGRAPH energy and go forward, I looked to collect
>  a few from our working group over @ MSF !
> As you know our activities at
> https://metaverse-standards.org/domain-groups/3d-web-interoperability/
> <https://metaverse-standards.org/domain-groups/3d-web-interoperability/>
> 3D Web Interoperability
> <https://metaverse-standards.org/domain-groups/3d-web-interoperability/>
> The mission of the 3D Web Interoperability Working Group is to enable
> metaverse capabilities and content to be deployed on the web through
> informing and encouraging the web standards ecosystem to evolve to support
> metaverse use cases and for the web to support and leverage broader
> metaverse interoperability initiatives.
> metaverse-standards.org
> **
>
>
> We have been working 🙂
>
> https://www.youtube.com/playlist?list=PL9H8jJb7mpbkOXlo_PxEsRGNSAOyq4gxK
> <https://www.youtube.com/playlist?list=PL9H8jJb7mpbkOXlo_PxEsRGNSAOyq4gxK>
> 3D Web Interoperability
> <https://www.youtube.com/playlist?list=PL9H8jJb7mpbkOXlo_PxEsRGNSAOyq4gxK>
> 3D Web Interoperability Working Group at the Metaverse Standards Forum
> www.youtube.com
>
> ...
>  and
> There are some excellent angles for us!
>
> I look forward to talking with you about how such a web3dapi can work for
> all of us!
>
> with best regards,
>  _nicholas
>
>
>
>
> --
> Nicholas F. Polys, Ph.D.
>
> Director of Visual Computing
> Virginia Tech Research Computing
>
> Affiliate Professor
> Virginia Tech Department of Computer Science
> https://people.cs.vt.edu/~npolys/  <https://people.cs.vt.edu/~npolys/>
> _______________________________________________
> x3d mailing list
> x3d at web3d.org
> http://web3d.org/mailman/listinfo/x3d_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240814/0fb00261/attachment.html>