coderofsalvation
/
xrfragment
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
xrfragment/doc/RFC_XR_Fragments.txt

393 lines
15 KiB
Plaintext
Raw Normal View History

update documentation
2023-09-01 14:20:02 +02:00
Internet Engineering Task Force L.R. van Kammen
update documentation
2023-09-02 21:44:57 +02:00
Internet-Draft 1 September 2023
update documentation
2023-09-01 14:20:02 +02:00
Intended status: Informational
update documentation
2023-09-02 21:44:57 +02:00
Expires: 4 March 2024
update documentation
2023-09-01 14:20:02 +02:00
XR Fragments
draft-XRFRAGMENTS-leonvankammen-00
Abstract
This draft offers a specification for 4D URLs & navigation, to link
3D scenes and text together with- or without a network-connection.
The specification promotes spatial addressibility, sharing,
navigation, query-ing and interactive text across for (XR) Browsers.
XR Fragments allows us to enrich existing dataformats, by recursive
use of existing technologies like URI Fragments
(https://en.wikipedia.org/wiki/URI_fragment) & visual-meta
(https://visual-meta.info).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
update documentation
2023-09-02 21:44:57 +02:00
This Internet-Draft will expire on 4 March 2024.
update documentation
2023-09-01 14:20:02 +02:00
Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.
update documentation
2023-09-02 21:44:57 +02:00
van Kammen Expires 4 March 2024 [Page 1]
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
Internet-Draft XR Fragments September 2023
update documentation
2023-09-01 14:20:02 +02:00
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 2
3. Navigating 3D . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Navigating text . . . . . . . . . . . . . . . . . . . . . . . 3
update documentation
2023-09-02 21:44:57 +02:00
4.1. Default Data URI mimetype . . . . . . . . . . . . . . . . 4
4.1.1. URL and Data URI . . . . . . . . . . . . . . . . . . 4
4.2. omnidirectional XR annotations . . . . . . . . . . . . . 5
5. HYPER copy/paste . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Plain Text (with optional visual-meta) . . . . . . . . . 6
6. Embedding 3D content . . . . . . . . . . . . . . . . . . . . 6
7. List of XR URI Fragments . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
update documentation
2023-09-01 14:20:02 +02:00
1. Introduction
How can we add more features to existing text & 3D scenes, without
introducing new dataformats? Historically, there's many attempts to
create the ultimate markuplanguage or 3D fileformat. However, thru
update documentation
2023-09-02 21:44:57 +02:00
the lens of authoring their lowest common denominator is still: plain
text. XR Fragments allows us to enrich existing dataformats, by
recursive use of existing technologies:
update documentation
2023-09-01 14:20:02 +02:00
* addressibility & navigation of 3D objects: URI Fragments
(https://en.wikipedia.org/wiki/URI_fragment) + (src/href) metadata
* addressibility & navigation of text objects: visual-meta
(https://visual-meta.info)
2. Conventions and Definitions
* scene: a (local/remote) 3D scene or 3D file (index.gltf e.g.)
* 3D object: an object inside a scene characterized by vertex-,
face- and customproperty data.
* metadata: custom properties defined in 3D Scene or Object(nodes)
* XR fragment: URI Fragment with spatial hints (#pos=0,0,0&t=1,100
e.g.)
update documentation
2023-09-02 21:44:57 +02:00
van Kammen Expires 4 March 2024 [Page 2]
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
Internet-Draft XR Fragments September 2023
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
* src: a (HTML-piggybacked) metadata-attribute of a 3D object which
instances content
* href: a (HTML-piggybacked) metadata-attribute of a 3D object which
links to content
update documentation
2023-09-01 14:20:02 +02:00
* query: an URI Fragment-operator which queries object(s) from a
scene (#q=cube)
update documentation
2023-09-02 21:44:57 +02:00
* visual-meta (https://visual.meta.info): metadata appended to text
which is only indirectly visible/editable in XR.
update documentation
2023-09-01 14:20:02 +02:00
{::boilerplate bcp14-tagged}
3. Navigating 3D
Here's an ascii representation of a 3D scene-graph which contains 3D
objects (◻) and their metadata:
update documentation
2023-09-02 21:44:57 +02:00
+--------------------------------------------------------+
| |
| index.gltf |
| │ |
| ├── ◻ buttonA |
| │ └ href: #pos=1,0,1&t=100,200 |
| │ |
| └── ◻ buttonB |
| └ href: other.fbx |
| |
+--------------------------------------------------------+
update documentation
2023-09-01 14:20:02 +02:00
An XR Fragment-compatible browser viewing this scene, allows the end-
user to interact with the buttonA and buttonB. In case of buttonA
the end-user will be teleported to another location and time in the
*current loaded scene*, but buttonB will *replace the current scene*
with a new one (other.fbx).
4. Navigating text
update documentation
2023-09-02 21:44:57 +02:00
Text in XR has to be unobtrusive, for readers as well as authors. We
think and speak in simple text, and given the new paradigm of XR
interfaces, logically (spoken) text must be enriched _afterwards_
(lazy metadata). Therefore, XR Fragment-compliant text will just be
plain text, and *not yet-another-markuplanguage*. In contrast to
markup languages, this means humans need to be always served first,
and machines later.
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
| Basically, a direct feedbackloop between unobtrusive text and
| human eye.
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
van Kammen Expires 4 March 2024 [Page 3]
Internet-Draft XR Fragments September 2023
Reality has shown that outsourcing rich textmanipulation to
commercial formats or mono-markup browsers (HTML) have there
usecases, but also introduce barriers to thought-translation (which
uses simple words). As Marshall MCluhan said: we have become
irrevocably involved with, and responsible for, each other.
In order enjoy hasslefree batteries-included programmable text
(glossaries, flexible views, drag-drop e.g.), XR Fragment supports
visual-meta (https://visual.meta.info)(data).
4.1. Default Data URI mimetype
The XR Fragment specification bumps the traditional default browser-
mimetype
text/plain;charset=US-ASCII
into:
text/plain;charset=utf-8;visual-meta=1
This means that visual-meta (https://visual.meta.info)(data) can be
appended to plain text without being displayed.
4.1.1. URL and Data URI
+--------------------------------------------------------------+ +------------------------+
| | | author.com/article.txt |
| index.gltf | +------------------------+
| │ | | |
| ├── ◻ article_canvas | | Hello friends. |
| │ └ src: ://author.com/article.txt | | |
| │ | | @{visual-meta-start} |
| └── ◻ note_canvas | | ... |
| └ src:`data:welcome human @{visual-meta-start}...` | +------------------------+
| |
| |
+--------------------------------------------------------------+
The difference is that text (+visual-meta data) in Data URI is saved
into the scene, which also promotes rich copy-paste. In both cases
will the text get rendered immediately (onto a plane geometry, hence
the name '_canvas'). The enduser can access visual-meta(data)-fields
only after interacting with the object.
| NOTE: this is not to say that XR Browsers should not load
| HTML/PDF/etc-URLs thru src-metadata, it is just that text/
| plain;charset=utf-8;visual-meta=1 is the minimum requirement.
van Kammen Expires 4 March 2024 [Page 4]
Internet-Draft XR Fragments September 2023
4.2. omnidirectional XR annotations
+---------------------------------------------------------------+
| |
| index.gltf |
| │ |
| ├── ◻ todo |
| │ └ src:`data:learn about ARC @{visual-meta-start}...`|
| │ |
| └── ◻ ARC |
| └── ◻ plane |
| └ src: `data:ARC was revolutionary |
| @{visual-meta-start} |
| @{glossary-start} |
| @entry{ |
| name = {ARC}, |
| description = {Engelbart Concept: |
| Augmentation Research Center, |
| The name of Doug's lab at SRI. |
| }, |
| }` |
| |
+---------------------------------------------------------------+
Here we can see an 3D object of ARC, to which the enduser added a
textnote (basically a plane geometry with src). The enduser can
view/edit visual-meta(data)-fields only after interacting with the
object. This allows the 3D scene to perform omnidirectional features
for free, by omni-connecting the word 'ARC':
* the ARC object can draw a line to the 'ARC was revolutionary'-note
* the 'ARC was revolutionary'-note can draw line to the 'learn about
ARC'-note
* the 'learn about ARC'-note can draw a line to the ARC 3D object
5. HYPER copy/paste
The previous example, offers something exciting compared to simple
textual copy-paste. , XR Fragment offers 4D- and HYPER- copy/paste:
time, space and text interlinked. Therefore, the enduser in an XR
Fragment-compatible browser can copy/paste/share data in these ways:
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
* copy ARC 3D object (incl. animation) & paste elsewhere including
visual-meta(data)
* select the word ARC in any text, and paste a bundle of anything
ARC-related
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
van Kammen Expires 4 March 2024 [Page 5]
Internet-Draft XR Fragments September 2023
5.1. Plain Text (with optional visual-meta)
In contrast to markuplanguage, the (dictated/written) text needs no
parsing, stays intact, by postponing metadata to the appendix.
This allows for a very economic XR way to:
* directly write, dictate, render text (=fast, without markup-
parser-overhead)
* add/load metadata later (if provided)
* enduser interactions with text (annotations,mutations) can be
reflected back into the visual-meta(data) Data URI
* copy/pasting of text will automatically cite the (mutated) source
* allows annotating 3D objects as if they were textual
representations (convert 3D document to text)
| NOTE: visualmeta never breaks the original intended text (in
| contrast to forgetting a html closing-tag e.g.)
6. Embedding 3D content
Here's an ascii representation of a 3D scene-graph with 3D objects
(◻) which embeds remote & local 3D objects (◻) (without)
using queries:
+--------------------------------------------------------+ +-------------------------+
| | | |
| index.gltf | | ocean.com/aquarium.fbx |
| │ | | │ |
| ├── ◻ canvas | | └── ◻ fishbowl |
| │ └ src: painting.png | | ├─ ◻ bass |
| │ | | └─ ◻ tuna |
| ├── ◻ aquariumcube | | |
| │ └ src: ://rescue.com/fish.gltf#q=bass%20tuna | +-------------------------+
| │ |
| ├── ◻ bedroom |
| │ └ src: #q=canvas |
| │ |
| └── ◻ livingroom |
| └ src: #q=canvas |
| |
+--------------------------------------------------------+
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
van Kammen Expires 4 March 2024 [Page 6]
update documentation
2023-09-01 14:20:02 +02:00
update documentation
2023-09-02 21:44:57 +02:00
Internet-Draft XR Fragments September 2023
update documentation
2023-09-01 14:20:02 +02:00
An XR Fragment-compatible browser viewing this scene, lazy-loads and
projects painting.png onto the (plane) object called canvas (which is
copy-instanced in the bed and livingroom). Also, after lazy-loading
update documentation
2023-09-02 21:44:57 +02:00
ocean.com/aquarium.gltf, only the queried objects bass and tuna will
be instanced inside aquariumcube. Resizing will be happen
update documentation
2023-09-01 14:20:02 +02:00
accordingly to its placeholder object (aquariumcube), see chapter
Scaling.
7. List of XR URI Fragments
8. Security Considerations
TODO Security
9. IANA Considerations
This document has no IANA actions.
10. Acknowledgments
TODO acknowledge.
update documentation
2023-09-02 21:44:57 +02:00
van Kammen Expires 4 March 2024 [Page 7]