[X3D-Ecosystem] [x3d-public] Hierarchy of Object Models

[John Carlson]

Very good, Joe!

I might consider one more thing, working offline temporarily , with a queue
of updates being kept on the client and server, in “local-first” worlds.
And resolution between updates when eventually connected.   Often this will
mean running a database in the browser, with indexdb, SQLite or Postgres
compiled into WASM.   So both a local database in the browser and one on
the server, with two-way sync, which extends into multiway sync.

Having a local database means that even DOM may be stored for long term use
on the client, and not continually loaded in the browser when you bring up
a world—it’s stored in the browser for immediate viewing without rebuilding
from XML or HTML each time.   Yes, one may have to build from records in a
local database, or one can store JSON (glTF), which is already compatible
with tables, except UUIDs and versions (with dates) are needed for syncing
clients with servers.

One may also reconsider object-based databases, like storing RAM structures
directly in an SSD, which should mean loading and saving can be extremely
efficient.  So don’t store files and folders long term, but objects and
arrays directly on SSD.  Some might consider this a relational file system
as previously proposed by Microsoft, but never released.

Yes, ultimately, things need to be stored in an external format, either for
transmission, updates, archiving or migrations.

John

On Tue, Apr 29, 2025 at 3:07 PM Joe D Williams via x3d-public <
x3d-public at web3d.org> wrote:

>
> https://metaverse-standards.org/news/blog/linked-spatial-experiences-the-web-of-worlds/
>
> Hierarchy of Object Models
>
> WWW Our World Wide Web
> .DOM Document Object Model
> ..WMVOM WebiMetaVerse Object Model
> ...FSOM FreeSpace Object Model
> ....SOM Scene Object Model (X3D SAI)
> ...WOM World Object Model
> ....SOM Scene Object Model (X3D SAI)
> ....HOM Humanoid Object Model
> ...AOM Action Object Model
> ....Dynamics Library
> ...Other Standards-Track Content Models
> ..Domain-Specific AI
>
> An advanced object model at any level will implement
> a Domain-Specific AI for realtime validation of
> certain structure and function parameters.
>
> So, in the general case our WWW information/experience
> system is hosted by a form of web browser that can
> implement the DOM. This provides the basic WWW
> object model to host certain XML-based
> interactive content.
> Immersion functionality is added as a component
> to the DOM by the WMVOM, which defines the
> standards-track content and event system
> for the WebiMetaVerse.
>
> The Immersive standards-track is produced by
> the WOM, describing allowed and required content of the World.
> This WOM contains the SOM, which is currently
> implemented by X3D SAI.
>
> The Humanoid Object Model is a component of
> the SOM that documents the standards-track
> Humanoid that can represent the user simulating
> operations in the active Scene of the host World.
>
> The FreeSpace Object Model defines operations
> that provide an immersion experience using
> extensions and augmentations that
> are not necessarily embedded in a World.
>
> The WMV can exist freestanding, without the
> DOM host, and may implement the DOM to interact
> with the WWW.
>
> Thanks for thinking about this hierarchy of content documentation,
> Joe
>
> _______________________________________________
> x3d-public mailing list
> 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-ecosystem_web3d.org/attachments/20250429/8333946f/attachment.html>