diff --git a/doc/RFC_XR_Fragments.html b/doc/RFC_XR_Fragments.html index 301abae..9e5955f 100644 --- a/doc/RFC_XR_Fragments.html +++ b/doc/RFC_XR_Fragments.html @@ -148,8 +148,14 @@ Instead of combining them (in a game-editor e.g.), XR Fragments is opting for a
-XR Fragments does not look at XR (or the web) thru the lens of HTML.
+
But approaches things from a higherlevel browser- and feedbackloop perspective:XR Fragments does not look at XR (or the web) thru the lens of HTML.
But approaches things from a higherlevel feedbackloop/hypermedia browser-perspective:
+──────────────────────────────────────────────────────────────────────────────────────────────+
@@ -199,12 +199,12 @@ Instead of combining them (in a game-editor e.g.), XR Fragments is opting for a
Traditional webbrowsers can become 4D document-ready by:
-- loading 3D assets (gltf/fbx e.g.) natively (not thru HTML).
+- loading 3D assets (gltf/fbx e.g.) natively (with or without using HTML).
- allowing assets to publish hashtags to themselves (the scene) using the hashbus (like hashtags controlling the scrollbar).
- collapsing the 3D scene to an wordgraph (for essential navigation purposes) controllable thru a hash(tag)bus
-XR Fragments itself is HTML-agnostic, though pseudo-XR Fragment browsers can be implemented on top of HTML/Javascript.
+XR Fragments itself are HTML-agnostic, though pseudo-XR Fragment browsers can be implemented on top of HTML/Javascript.
Conventions and Definitions
diff --git a/doc/RFC_XR_Fragments.md b/doc/RFC_XR_Fragments.md
index 4fce8a3..00a097f 100644
--- a/doc/RFC_XR_Fragments.md
+++ b/doc/RFC_XR_Fragments.md
@@ -127,12 +127,12 @@ Instead of combining them (in a game-editor e.g.), XR Fragments is opting for a
| the hashbus | hashtags map to camera/scene-projections | hashtags map to document positions |
| spacetime hashtags | positions camera, triggers scene-preset/time | jumps/scrolls to chapter |
| src metadata | renders content and offers sourceportation | renders content |
-| href metadata | teleports to other position or XR document | jumps to other chapter or HTML document|
+| href metadata | teleports to other XR document | jumps to other HTML document |
+| href metadata | repositions camera or animation-range | jumps to camera |
| href metadata | draws visible connection(s) for XRWG 'tag' | |
| href metadata | triggers predefined view | Media fragments |
-| href metadata | repositions camera or animation-range | |
-> XR Fragments does not look at XR (or the web) thru the lens of HTML.
But approaches things from a higherlevel browser- and feedbackloop perspective:
+> XR Fragments does not look at XR (or the web) thru the lens of HTML.
But approaches things from a higherlevel feedbackloop/hypermedia browser-perspective:
```
+──────────────────────────────────────────────────────────────────────────────────────────────+
@@ -157,11 +157,11 @@ Instead of combining them (in a game-editor e.g.), XR Fragments is opting for a
Traditional webbrowsers can become 4D document-ready by:
-* loading 3D assets (gltf/fbx e.g.) natively (not thru HTML).
+* loading 3D assets (gltf/fbx e.g.) natively (with or without using HTML).
* allowing assets to publish hashtags to themselves (the scene) using the hashbus (like hashtags controlling the scrollbar).
* collapsing the 3D scene to an wordgraph (for essential navigation purposes) controllable thru a hash(tag)bus
-XR Fragments itself is HTML-agnostic, though pseudo-XR Fragment browsers **can** be implemented on top of HTML/Javascript.
+XR Fragments itself are HTML-agnostic, though pseudo-XR Fragment browsers **can** be implemented on top of HTML/Javascript.
# Conventions and Definitions
diff --git a/doc/RFC_XR_Fragments.txt b/doc/RFC_XR_Fragments.txt
index 09ffa62..e070ef4 100644
--- a/doc/RFC_XR_Fragments.txt
+++ b/doc/RFC_XR_Fragments.txt
@@ -170,40 +170,40 @@ van Kammen Expires 24 March 2024 [Page 3]
Internet-Draft XR Fragments September 2023
- +===========+=============================+========================+
- | principle | XR 4D URL | HTML 2D URL |
- +===========+=============================+========================+
- | the XRWG | wordgraph (collapses 3D | Ctrl-F (find) |
- | | scene to tags) | |
- +-----------+-----------------------------+------------------------+
- | the | hashtags map to camera/ | hashtags map to |
- | hashbus | scene-projections | document positions |
- +-----------+-----------------------------+------------------------+
- | spacetime | positions camera, triggers | jumps/scrolls to |
- | hashtags | scene-preset/time | chapter |
- +-----------+-----------------------------+------------------------+
- | src | renders content and offers | renders content |
- | metadata | sourceportation | |
- +-----------+-----------------------------+------------------------+
- | href | teleports to other position | jumps to other chapter |
- | metadata | or XR document | or HTML document |
- +-----------+-----------------------------+------------------------+
- | href | draws visible connection(s) | |
- | metadata | for XRWG 'tag' | |
- +-----------+-----------------------------+------------------------+
- | href | triggers predefined view | Media fragments |
- | metadata | | |
- +-----------+-----------------------------+------------------------+
- | href | repositions camera or | |
- | metadata | animation-range | |
- +-----------+-----------------------------+------------------------+
+ +===========+=============================+====================+
+ | principle | XR 4D URL | HTML 2D URL |
+ +===========+=============================+====================+
+ | the XRWG | wordgraph (collapses 3D | Ctrl-F (find) |
+ | | scene to tags) | |
+ +-----------+-----------------------------+--------------------+
+ | the | hashtags map to camera/ | hashtags map to |
+ | hashbus | scene-projections | document positions |
+ +-----------+-----------------------------+--------------------+
+ | spacetime | positions camera, triggers | jumps/scrolls to |
+ | hashtags | scene-preset/time | chapter |
+ +-----------+-----------------------------+--------------------+
+ | src | renders content and offers | renders content |
+ | metadata | sourceportation | |
+ +-----------+-----------------------------+--------------------+
+ | href | teleports to other XR | jumps to other |
+ | metadata | document | HTML document |
+ +-----------+-----------------------------+--------------------+
+ | href | repositions camera or | jumps to camera |
+ | metadata | animation-range | |
+ +-----------+-----------------------------+--------------------+
+ | href | draws visible connection(s) | |
+ | metadata | for XRWG 'tag' | |
+ +-----------+-----------------------------+--------------------+
+ | href | triggers predefined view | Media fragments |
+ | metadata | | |
+ +-----------+-----------------------------+--------------------+
Table 1
| XR Fragments does not look at XR (or the web) thru the lens of
| HTML.
- | But approaches things from a higherlevel browser- and feedbackloop
- | perspective:
+ | But approaches things from a higherlevel feedbackloop/hypermedia
+ | browser-perspective:
@@ -246,13 +246,14 @@ Internet-Draft XR Fragments September 2023
Traditional webbrowsers can become 4D document-ready by:
- * loading 3D assets (gltf/fbx e.g.) natively (not thru HTML).
+ * loading 3D assets (gltf/fbx e.g.) natively (with or without using
+ HTML).
* allowing assets to publish hashtags to themselves (the scene)
using the hashbus (like hashtags controlling the scrollbar).
* collapsing the 3D scene to an wordgraph (for essential navigation
purposes) controllable thru a hash(tag)bus
- XR Fragments itself is HTML-agnostic, though pseudo-XR Fragment
+ XR Fragments itself are HTML-agnostic, though pseudo-XR Fragment
browsers *can* be implemented on top of HTML/Javascript.
3. Conventions and Definitions
@@ -276,7 +277,6 @@ Internet-Draft XR Fragments September 2023
-
van Kammen Expires 24 March 2024 [Page 5]
Internet-Draft XR Fragments September 2023
diff --git a/doc/RFC_XR_Fragments.xml b/doc/RFC_XR_Fragments.xml
index be0de74..29c830a 100644
--- a/doc/RFC_XR_Fragments.xml
+++ b/doc/RFC_XR_Fragments.xml
@@ -85,8 +85,14 @@ Instead of combining them (in a game-editor e.g.), XR Fragments is opting for a
href metadata
-teleports to other position or XR document
-jumps to other chapter or HTML document
+teleports to other XR document
+jumps to other HTML document
+
+
+
+href metadata
+repositions camera or animation-range
+jumps to camera
@@ -100,15 +106,9 @@ Instead of combining them (in a game-editor e.g.), XR Fragments is opting for a
triggers predefined view
Media fragments
-
-
-href metadata
-repositions camera or animation-range
-
-
XR Fragments does not look at XR (or the web) thru the lens of HTML.
-But approaches things from a higherlevel browser- and feedbackloop perspective:
+But approaches things from a higherlevel feedbackloop/hypermedia browser-perspective:
+──────────────────────────────────────────────────────────────────────────────────────────────+
│ │
@@ -132,11 +132,11 @@ But approaches things from a higherlevel browser- and feedbackloop perspective:<
Traditional webbrowsers can become 4D document-ready by:
-- loading 3D assets (gltf/fbx e.g.) natively (not thru HTML).
+- loading 3D assets (gltf/fbx e.g.) natively (with or without using HTML).
- allowing assets to publish hashtags to themselves (the scene) using the hashbus (like hashtags controlling the scrollbar).
- collapsing the 3D scene to an wordgraph (for essential navigation purposes) controllable thru a hash(tag)bus
-XR Fragments itself is HTML-agnostic, though pseudo-XR Fragment browsers can be implemented on top of HTML/Javascript.
+XR Fragments itself are HTML-agnostic, though pseudo-XR Fragment browsers can be implemented on top of HTML/Javascript.
Conventions and Definitions