[x3d-public] X3D in and of the MetaVerse

[joedwil at earthlink.net]

So, I have been participating in the MSF, Metaverse Standards Forum, 
in areas related to X3D, X3D HAnim, and especially HAnim.
One item I am convinced of is that  
MetaVerse should be CamelCase.
There will be many Verses and so this One particular,  
although having properties of waves,
virtualization deserves extra special distinction. 
because it alone will be free and open, 
and defined by free and open standards. 

However, this name of this asset could be controversial.  
If only to me? Because, well, is there a real possibility 
there can be only one Meta when even that  common name
of a common self-defining thing can be owned? 
Is a meta really only a meta when it completely describes itself 
in logically related pairs both locally and by remote proxy?
Does the runtime need live access to meta?   
     
But seriously, there is some naming I would like to see. 
We have some existing web standardizable interfaces to assist
in specialized communications and interactions that are
considered as Accessibility features.  
For this unique versal effort, let's put these  
within the broad category of Conveniences.  
A Convenience is just an asset that gives the Avatar,
your HAnim Humanoid Twin,  
for instance, and thus the user, You, for instance,  
access to some  standard or enriched feature  
of the host environment.  
In the immersive experience there are at least two  
levels of convenience.
First the Avatar must be able to navigate and interact
in the current scene of the container provided by the host, 
Second, the User must be able to reliably control
navigation and interactions of the Avatar
in the environment the Avatar finds itself. 
The user can be immersed only to the extent
that the Avatar can be immersed. 
Each asset of the Avatar that can transact with a
feature or collection of features of the scene are shared
with the Avatar and thus with the User as a Convenience.   
       
Overall, MSF id a chance to discuss targets for implementations
and at least give an evolving metaverse an idea of what
we, by consensus, consider best standard practices at this time.
Videos here:

https://www.youtube.com/@metaversestandardsforum

Thanks for All,
Joe 
    


. 


 .