<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">catching up....<br>
<br>
</div>
<blockquote cite="mid:6c5073e2-7718-eb6a-a860-b0469f245463@nps.edu"
type="cite">Thanks for your continuing efforts. Feedback:
<br>
<br>
a. Not clear what your motivation is. What functionality does a
Macro node provide that isn't already available using Script and
Prototype definitions? Getting clear about differences helps
getting clear about goals.
<br>
</blockquote>
<br>
X3D Script is not available in HTML as it is already being used.
After repeated requests to X3D and X3D-Public mailing lists, no one
could supply an example of a trivial PROTO (one without a Script
node) that was not convenience definition. I felt that the ability
to define a set of nodes at initialization (parse-type) was useful.
I added the ability to vary the parameters from one instance to the
next as important to provide variability in the scene. <br>
<br>
The Macro node definition (linked in the OP) is part of a much
larger document that includes the section "Author's Notes"
(<a class="moz-txt-link-freetext" href="http://tools.realism.com/specification/x3d-v40/authors-notes">http://tools.realism.com/specification/x3d-v40/authors-notes</a>) where
the motivation and domain of operation are described. There is also
a link to the "Author's Notes" section in the sidebar.<br>
<br>
<br>
<blockquote cite="mid:6c5073e2-7718-eb6a-a860-b0469f245463@nps.edu"
type="cite">
<br>
b. Usage examples are often helpful for illustrating goals at this
stage of design.
<br>
</blockquote>
<br>
Each node comes with at least one test case. Andreas has collected
the test scenes and provide me information as to how that can be
made part of the Github pages. I will be working on that.<br>
<br>
<br>
<blockquote cite="mid:6c5073e2-7718-eb6a-a860-b0469f245463@nps.edu"
type="cite">
<br>
c. Previous efforts on NetworkSensor node, and the difficulties
encountered, may be worth considering:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/x3d/content/examples/Basic/Networking/">http://www.web3d.org/x3d/content/examples/Basic/Networking/</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/x3d/content/examples/Basic/Networking/NetworkSensorConnectionPrototypes.x3d">http://www.web3d.org/x3d/content/examples/Basic/Networking/NetworkSensorConnectionPrototypes.x3d</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/x3d/content/examples/Basic/Networking/NetworkSensorConnectionPrototypes.html">http://www.web3d.org/x3d/content/examples/Basic/Networking/NetworkSensorConnectionPrototypes.html</a>
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/x3d/content/examples/Basic/Networking/NetworkSensorConnectionNodes.html">http://www.web3d.org/x3d/content/examples/Basic/Networking/NetworkSensorConnectionNodes.html</a>
<br>
</blockquote>
<br>
Communication between users (networking) is a useful area to
investigate. I was involved in the previous attempt and remember
many of the difficulties and different approaches that the WG had.
In the end we were unable to define anything for the specification
because the problem scope was not sufficiently well-defined and
agreed-upon. Things in the HTML world have changed considerably
since then and it would probably be useful to try to get that kind
of communication going again. I do not know if it is appropriate to
put that in X3D or better to handle external of X3D in (e.g.)
WebRTC.<br>
<br>
I do not understand why it was brought up here. It is not a topic I
brought up.<br>
<br>
<br>
<br>
<blockquote cite="mid:6c5073e2-7718-eb6a-a860-b0469f245463@nps.edu"
type="cite">
<br>
d. Then noticed that you have applied a (CC BY-ND) No Derivatives
license, which specifically forbids any adaptation.
<br>
<br>
<a class="moz-txt-link-freetext" href="https://creativecommons.org/licenses/by-nd/3.0/us/">https://creativecommons.org/licenses/by-nd/3.0/us/</a>
<br>
<br>
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Creative_Commons_license">https://en.wikipedia.org/wiki/Creative_Commons_license</a>
<br>
"No Derivative Works (ND)"
<br>
"Licensees may copy, distribute, display and perform only
verbatim copies of the work, not derivative works and remixes
based on it."
<br>
<br>
Unfortunately that discourages further consideration.
<br>
</blockquote>
<br>
At this time I am not submitting this for consideration for V4. I
did not want multiple versions of the document existing. That would
make it hard to determine the differences between the different
documents. I am aware of the requirements for consideration and the
document will comply with those requirements when it is submitted.
The CC BY-ND license does not discourage consideration as changes
can be sent to me for incorporation. If there are several people
interested in working on the document, I will supply other
mechanisms for editing/updating.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
<blockquote cite="mid:6c5073e2-7718-eb6a-a860-b0469f245463@nps.edu"
type="cite">
<br>
<br>
On 8/26/2016 7:39 PM, Leonard Daly wrote:
<br>
<blockquote type="cite">For the last year I have been working on
advancing X3D to be standardized in HTML5/DOM environment and
support mobile and VR. I have just completed alpha work on the
Macro node. This node provides the static definition
capabilities of PROTO in an HTML5 environment. It can perform
string substitution (name/value pairs) on X3D code stored
externally. The node documentation is at
<a class="moz-txt-link-freetext" href="http://tools.realism.com/specification/x3d-v40/abstract-specification/changes-additions-x3d-v33/macro">http://tools.realism.com/specification/x3d-v40/abstract-specification/changes-additions-x3d-v33/macro</a>.<br>
<br>
I will continue to get to at least alpha stage (basic functional
implemented and working) for all nodes I discussed during my
presentations at Web3D2016 & SIGGRAPH. The presentation is
online at
<a class="moz-txt-link-freetext" href="http://realism.com/presentations/188?title=Extending-X3DOM-to-Mobile">http://realism.com/presentations/188?title=Extending-X3DOM-to-Mobile</a>.
<br>
<br>
All of the code is up on Github at
<a class="moz-txt-link-freetext" href="https://github.com/DrX3D/x3dv4">https://github.com/DrX3D/x3dv4</a> with testing code.
<br>
<br>
I am interested in any bugs that are found or new/revised
direction for the nodes. I am completely open to anyone who
would like to help code.
<br>
<br>
<br>
--
<br>
*Leonard Daly*
<br>
3D Systems Architect
<br>
Cloud Consultant
<br>
President, Daly Realism - /Creating the Future/
<br>
<br>
<br>
_______________________________________________
<br>
x3d-public mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<br>
<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>
<br>
<br>
</blockquote>
<br>
<br>
all the best, Don
<br>
</blockquote>
<br>
<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>
X3D Co-Chair<br>
Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>