From a4b852224e2b5e2928953145f8eeec4ea5291590 Mon Sep 17 00:00:00 2001 From: Leon van Kammen Date: Sun, 22 Feb 2026 11:35:46 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=83=20master:=20update=20documentation?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- index.html | 99 +++++++++++++++++++++++++++++++++++------------------- 1 file changed, 64 insertions(+), 35 deletions(-) diff --git a/index.html b/index.html index f4d9a07..a5f3e62 100644 --- a/index.html +++ b/index.html @@ -264,6 +264,23 @@
+
+
+
+
+ +

XR Hypermedia criteria

+ + +
+
@@ -388,6 +405,7 @@
+

Supporter of Open XR Hypermedia stacks

@@ -424,7 +442,7 @@ A: Indirectly funding/promoting proprietary engines with public money is tough (public money public code).
- + Q: Which Open XR engines are preferred?
A: Preferred are Fully Opensource XR Browserengines like: @@ -451,26 +469,30 @@
- Q: Regarding hyperlinking, is linking to a webpage enough?
- A: Most games or WebXR-sites are shallow-linked disjointed XR experiences via appstores (not hypermedia), basically: +
+ Q: Regarding hyperlinking, is linking to a webpage enough?
+ A: Most games or WebXR-sites are shallow-linked disjointed XR experiences via appstores (not hypermedia), basically: -
- - "We don't want customers to leave our premise" - -
+
+ + "We don't want customers to leave our premise" + +
- A much more interesting is seamless XR hypermedia surfing: by interlinking 3D files immersively via (XR Fragment) URLs or JanusWeb.
See the difference below:

- + A much more interesting is seamless XR hypermedia surfing: by interlinking 3D files immersively via (XR Fragment) URLs or JanusWeb.
See the difference below:

+ -
- Rule of thumb: if the XR content can be selfhosted by users separately from the XR viewer, you're on the right track. -
+
+ Rule of thumb: if the XR content can be selfhosted by users separately from the XR viewer, you're on the right track. +
+
- Q: How important is security?
- A: It depends, The value of a digital common lies in its liquidity. If you wrap public-domain content in restrictive security layers (like heavy DRM or complex access controls), you destroy the "common" aspect. Since the content is meant to be seen and shared, there is no "secret" to protect. Attempts to ensure it isn't maliciously altered are saluted. +
+ Q: How important is security?
+ A: It depends, The value of a digital common lies in its liquidity. If you wrap public-domain content in restrictive security layers (like heavy DRM or complex access controls), you destroy the "common" aspect. Since the content is meant to be seen and shared, there is no "secret" to protect. Attempts to ensure it isn't maliciously altered are saluted. +
@@ -489,31 +511,38 @@
- Q: How do you identify "XR interoperability-washing"?
- A: "XR interoperability-washing" is akin to greenwashing; it occurs when companies aggressively market a commitment to open standards while their top-down corporate structures make true interoperability technically impossible. It also partially explains why XR interop historically creates top-down talkshops, instead of actual bottom-up interop (like JanusXR).
- Characteristics: -
    -
  • Top-down B2B-interop (instead of bottom-up)
    • -
  • complex SDKs and proprietary integrations
    • -
  • proprietary servers as essential component
    • -
  • designed to "lock in" their user base
    • -
  • no credible exit (run content elsewhere e.g.)
    • -
+
+ Q: How do you identify "XR interoperability-washing"?
+ A: "XR interoperability-washing" is akin to greenwashing; it occurs when companies aggressively market a commitment to open standards while their top-down corporate structures make true interoperability technically impossible. It also partially explains why XR interop historically creates top-down talkshops, instead of actual bottom-up interop (like JanusXR).
+ Characteristics: +
    +
  • Top-down B2B-interop (instead of bottom-up)
    • +
  • complex SDKs and proprietary integrations
    • +
  • proprietary servers as essential component
    • +
  • designed to "lock in" their user base
    • +
  • no credible exit (run content elsewhere e.g.)
    • +
- While these methods may offer limited connectivity, they fall short of providing a sustainable, seamless "world-to-world" browsing experience (XR hypermedia).
-In contrast, (bottom-up) XR hypermedia offers a more cost-efficient path.
- By removing the need to protect stakeholders, centralized user bases, or specific crypto-wallets, it flips the traditional power structure.
In this model, the user—not the corporate stakeholder—is the starting point and operator of the network. + While these methods may offer limited connectivity, they fall short of providing a sustainable, seamless "world-to-world" browsing experience (XR hypermedia).
+ In contrast, (bottom-up) XR hypermedia offers a more cost-efficient path.
+ By removing the need to protect stakeholders, centralized user bases, or specific crypto-wallets, it flips the traditional power structure.
In this model, the user—not the corporate stakeholder—is the starting point and operator of the network. - NOTE: XRHF is not anti-business, it's just that many online businesses don't have the 90s internet-mindset like DNS-companies (the network is the market, not the users). -

+ NOTE: XRHF is not anti-business, it's just that many online businesses don't have the 90s internet-mindset like DNS-companies (the network is the market, not the users). +
- Q: What is the 'XR at rest' criteria?
- A: Basically that XR experiences should be cheap to archive and reproduce: the 'XR at rest' criteria dictates that immersive experiences should ideally exist as persistent, static files rather than being dependent on active, power-hungry server processes.
By decoupling the XR space from continuous compute requirements, these experiences remain accessible even when the original hosting infrastructure or company servers are powered down.
This approach leverages a 'cacheable' hypermedia architecture, allowing virtual environments to be served and cached much like standard web pages.
Ultimately, this ensures the long-term preservation and interoperability of the spatial web, preventing "digital decay" common in traditional live-service gaming models. -
+
- Q: What is the 'credible exit' criteria?
- A: A credible exit ensures that users are never trapped within a single ecosystem, allowing their digital identity, assets, and progress to remain functional even if they switch platforms.
By prioritizing data portability and interoperable file standards, developers protect the user's long-term investment and prevent the loss of personal data if a service is discontinued.
Ultimately, providing a clear path to move data elsewhere fosters trust and is a fundamental requirement for building a truly open and decentralized XR landscape.
+
+ Q: What is the 'XR at rest' criteria?
+ A: Basically that XR experiences should be cheap to archive and reproduce: the 'XR at rest' criteria dictates that immersive experiences should ideally exist as persistent, static files rather than being dependent on active, power-hungry server processes.
By decoupling the XR space from continuous compute requirements, these experiences remain accessible even when the original hosting infrastructure or company servers are powered down.
This approach leverages a 'cacheable' hypermedia architecture, allowing virtual environments to be served and cached much like standard web pages.
Ultimately, this ensures the long-term preservation and interoperability of the spatial web, preventing "digital decay" common in traditional live-service gaming models. +
+
+ +
+ Q: What is the 'credible exit' criteria?
+ A: A credible exit ensures that users are never trapped within a single ecosystem, allowing their digital identity, assets, and progress to remain functional even if they switch platforms.
By prioritizing data portability and interoperable file standards, developers protect the user's long-term investment and prevent the loss of personal data if a service is discontinued.
Ultimately, providing a clear path to move data elsewhere fosters trust and is a fundamental requirement for building a truly open and decentralized XR landscape. +
Jump to: