<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Andreas,<br>
<br>
I like this kind of solution. It does bring up a procedural
question. It may be better answered by Dick (CCed)<br>
<br>
Shadow DOM is a working draft (2017-02-13)
<a class="moz-txt-link-freetext" href="https://www.w3.org/TR/shadow-dom/">https://www.w3.org/TR/shadow-dom/</a>. It is also being moved to other
standards (DOM, HTML, CSS, etc. -- see pink box in above link)<br>
<br>
Web Components are browser implementations necessary to support
Shadow DOM and other features. This is also a standard in
development at <a class="moz-txt-link-freetext" href="https://github.com/w3c/webcomponents">https://github.com/w3c/webcomponents</a>.<br>
<br>
I know that an ISO standard cannot normatively reference a working
draft standard. Is the purpose of a standard to make explicit
standard practices and procedures throughout an industry? Is it
possible to codify standard practices and procedures when they
don't exist because the underlying technology is too new?<br>
<br>
The danger I see here is that something is standardized before it
is really ready to be standardized. The penalty for waiting is
that everything will pass you by and there will always be
something new coming down the line.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAKdk67unvvRoRpRK1yTkycRv+RQ4XDjV8ME_A2Tob4YZViM6Ag@mail.gmail.com">
<div dir="ltr">
<div><a
href="https://glitch.com/edit/#%21/juniper-wool?path=index.html:40:7"
moz-do-not-send="true">https://glitch.com/edit/#!/juniper-wool?path=index.html:40:7</a><br>
</div>
<div><br>
</div>
<div>is an investigation of how HTML Imports and ShadowDOM may
be used to substitute for X3D Inline nodes. HTML Imports makes
it straightforward to load an external fragment of HTML into a
document: <a
href="https://www.webcomponents.org/community/articles/introduction-to-html-imports"
moz-do-not-send="true">https://www.webcomponents.org/community/articles/introduction-to-html-imports</a>. And
the stated purpose of ShadowDOM is encapsulation. </div>
<div><br>
</div>
<div>Here are some observations:</div>
<div><br>
</div>
<div>HTML imports work as intended with x3dom.</div>
<div>It is likely one could use a generic 'include'
webcomponent.</div>
<div>DEF nodes in the imported x3d are exported/imported, so
they can be USEd. There is no separate namescope.</div>
<div>HTML imports can also be attached as shadow tree to a host
node. But x3dom does not recognize the shadow tree and it is
not rendered. Native X3D in HTML or an improved x3dom would
likely render those.</div>
<div>Attached shadow tree content cannot be selected/found with
regular DOM methods. However, shadow trees still can be
selected with the host.shadowroot property. </div>
<div><br>
</div>
<div>It is likely that one could use en existing webcomponent
such as</div>
<div><a
href="https://www.webcomponents.org/element/github/include-fragment-element"
moz-do-not-send="true">https://www.webcomponents.org/element/github/include-fragment-element</a></div>
<div>for inline purposes as well.</div>
<div><br>
</div>
<div>Overall, it looks like that Inline would duplicate native
webcomponent capability.</div>
<div><br>
</div>
<div>It could also be fruitful to investigate how custom
elements with templates compare with protos in detail. There
seems to be match in purpose and ability.</div>
<div><br>
</div>
<div>-Andreas</div>
<div><br>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Andreas Plesch<br>
39 Barbara Rd.<br>
Waltham, MA 02453</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>