addded override mention to spec
This commit is contained in:
parent
f73ddba0c0
commit
b288e0343d
4 changed files with 13 additions and 10 deletions
|
|
@ -318,7 +318,8 @@ This can be done via a JSON-pointers <a href="https://www.rfc-editor.org/rfc/rfc
|
||||||
<p>This would mean: hide object(s) with name or <code>tag</code>-value ‘penguin’ upon scene-load, and show it when the user clicks the chair</p>
|
<p>This would mean: hide object(s) with name or <code>tag</code>-value ‘penguin’ upon scene-load, and show it when the user clicks the chair</p>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
|
|
||||||
<p>So when loading <code>experience.glb</code> the existence of <code>experience.json</code> is detected, to apply the explicit metadata.<br></p>
|
<p>So after loading <code>experience.glb</code> the existence of <code>experience.json</code> is detected, to apply the explicit metadata.<br>
|
||||||
|
The sidecar will define (or <strong>override</strong> already existing) extras, which can be handy for multi-user platforms (offer 3D scene customization/personalization to users).</p>
|
||||||
|
|
||||||
<blockquote>
|
<blockquote>
|
||||||
<p>In THREE.js-code this would boil down to:</p>
|
<p>In THREE.js-code this would boil down to:</p>
|
||||||
|
|
|
||||||
|
|
@ -244,7 +244,8 @@ This can be done via a JSON-pointers [RFC6901](https://www.rfc-editor.org/rfc/rf
|
||||||
|
|
||||||
> This would mean: hide object(s) with name or `tag`-value 'penguin' upon scene-load, and show it when the user clicks the chair
|
> This would mean: hide object(s) with name or `tag`-value 'penguin' upon scene-load, and show it when the user clicks the chair
|
||||||
|
|
||||||
So when loading `experience.glb` the existence of `experience.json` is detected, to apply the explicit metadata.<br>
|
So after loading `experience.glb` the existence of `experience.json` is detected, to apply the explicit metadata.<br>
|
||||||
|
The sidecar will define (or **override** already existing) extras, which can be handy for multi-user platforms (offer 3D scene customization/personalization to users).
|
||||||
|
|
||||||
> In THREE.js-code this would boil down to:
|
> In THREE.js-code this would boil down to:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -407,8 +407,11 @@ Internet-Draft XR Fragments September 2024
|
||||||
| This would mean: hide object(s) with name or tag-value 'penguin'
|
| This would mean: hide object(s) with name or tag-value 'penguin'
|
||||||
| upon scene-load, and show it when the user clicks the chair
|
| upon scene-load, and show it when the user clicks the chair
|
||||||
|
|
||||||
So when loading experience.glb the existence of experience.json is
|
So after loading experience.glb the existence of experience.json is
|
||||||
detected, to apply the explicit metadata.
|
detected, to apply the explicit metadata.
|
||||||
|
The sidecar will define (or *override* already existing) extras,
|
||||||
|
which can be handy for multi-user platforms (offer 3D scene
|
||||||
|
customization/personalization to users).
|
||||||
|
|
||||||
| In THREE.js-code this would boil down to:
|
| In THREE.js-code this would boil down to:
|
||||||
|
|
||||||
|
|
@ -439,9 +442,6 @@ Internet-Draft XR Fragments September 2024
|
||||||
without using HTML).
|
without using HTML).
|
||||||
* allowing 3D assets/nodes to publish XR Fragments to themselves/
|
* allowing 3D assets/nodes to publish XR Fragments to themselves/
|
||||||
eachother using the xrf:// hashbus
|
eachother using the xrf:// hashbus
|
||||||
* collapsing the 3D scene to an wordgraph (for essential navigation
|
|
||||||
purposes) controllable thru a hash(tag)bus
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -450,6 +450,8 @@ van Kammen Expires 31 March 2025 [Page 8]
|
||||||
Internet-Draft XR Fragments September 2024
|
Internet-Draft XR Fragments September 2024
|
||||||
|
|
||||||
|
|
||||||
|
* collapsing the 3D scene to an wordgraph (for essential navigation
|
||||||
|
purposes) controllable thru a hash(tag)bus
|
||||||
* completely bypassing the security-trap of loading external scripts
|
* completely bypassing the security-trap of loading external scripts
|
||||||
(by loading 3D model-files, not HTML-javascriptable resources)
|
(by loading 3D model-files, not HTML-javascriptable resources)
|
||||||
|
|
||||||
|
|
@ -499,8 +501,6 @@ Internet-Draft XR Fragments September 2024
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
van Kammen Expires 31 March 2025 [Page 9]
|
van Kammen Expires 31 March 2025 [Page 9]
|
||||||
|
|
||||||
Internet-Draft XR Fragments September 2024
|
Internet-Draft XR Fragments September 2024
|
||||||
|
|
|
||||||
|
|
@ -233,8 +233,9 @@ This can be done via a JSON-pointers <eref target="https://www.rfc-editor.org/rf
|
||||||
]]>
|
]]>
|
||||||
</sourcecode>
|
</sourcecode>
|
||||||
<blockquote><t>This would mean: hide object(s) with name or <tt>tag</tt>-value 'penguin' upon scene-load, and show it when the user clicks the chair</t>
|
<blockquote><t>This would mean: hide object(s) with name or <tt>tag</tt>-value 'penguin' upon scene-load, and show it when the user clicks the chair</t>
|
||||||
</blockquote><t>So when loading <tt>experience.glb</tt> the existence of <tt>experience.json</tt> is detected, to apply the explicit metadata.<br />
|
</blockquote><t>So after loading <tt>experience.glb</tt> the existence of <tt>experience.json</tt> is detected, to apply the explicit metadata.<br />
|
||||||
</t>
|
|
||||||
|
The sidecar will define (or <strong>override</strong> already existing) extras, which can be handy for multi-user platforms (offer 3D scene customization/personalization to users).</t>
|
||||||
<blockquote><t>In THREE.js-code this would boil down to:</t>
|
<blockquote><t>In THREE.js-code this would boil down to:</t>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
<sourcecode type="javascript"><![CDATA[ scene.userData['#'] = "#chair&penguin"
|
<sourcecode type="javascript"><![CDATA[ scene.userData['#'] = "#chair&penguin"
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue