coderofsalvation/xrhf
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

🔧 master: work in progress [might break]

Browse source
This commit is contained in:
Leon van Kammen 2026-02-21 09:56:16 +01:00
parent 12d7e91d4d
commit 8069944ebb
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
index.html
View file

@ -487,6 +487,25 @@
<br/>
</center>
<hr/>
<b>Q: How do you identify "XR interoperability-washing"?</b><br/>
<b>A:</b> <i>"XR interoperability-washing"</i> is akin to greenwashing; it occurs when companies aggressively <b>market a commitment to open standards</b> while their top-down corporate structures make true interoperability technically impossible.<br>These entities often promote:<br>
<ul>
<li>Top-down business2business-interop (instead of bottom-up)</li>
<li>complex SDKs and proprietary integrations
<li>proprietary servers as essential component</li>
<li>designed to "lock in" their user base</li>
<li>no credible exit (run content elsewhere e.g.)</li>
</ul>
<blockquote>
<b>Metaphor:</b> XR interoperability-washing is similar to a DNS-company (which allows you to register a domain) disables the 'transfer a domain'-feature.
</blockquote>
While these methods may offer limited connectivity, they fall short of providing a sustainable, seamless "world-to-world" browsing experience (XR hypermedia).<br>
In contrast, <b>(bottom-up) XR hypermedia</b> offers a more cost-efficient path.<br>By removing the need to protect stakeholders, centralized user bases, or specific crypto-wallets, it flips the traditional power structure. <br>In this model, the user—not the corporate stakeholder—is the starting point and operator of the network.
<div class="footer">
<small>Jump to:</small>