<p dir="ltr">At this point, I just have basic setters, getters, add children, remove children (no implementation for children) and possible constructors (needs work for abstract base classes). So I have Python which generates SAI-like stuff. I also have JavaScript which takes XML DOM encoding and produces Python for a document. I do need to look over the Object Model or model schema to see if I'm missing something obvious. Statements come to mind.</p>
<p dir="ltr">John</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Nov 16, 2016 2:57 AM, "Don Brutzman" <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(belated response) Joe, thanks for this offer.<br>
<br>
We will get to SAI specification improvements in the coming year. It has been a looong time since the last review. For the next few months, effort will focus on X3D Object Model and implementations such as this.<br>
<br>
Am hoping that our next revision of SAI will also align with HTML5/DOM. Plenty more discussion, implementation and evaluation lies ahead of us to get there. It is pretty cool that John Carlson has a Python draft, and also that any architectural changes in X3D v4 will be directly implementable in autogenerated codebases.<br>
<br>
Meanwhile first of 2 H-Anim spec editors meetings is tomorrow. 8)<br>
<br>
Onward we go. Looking forward to future diligence that updates reviews like the one you posted - again thanks.<br>
<br>
v/r Don<br>
<br>
<br>
On 10/26/2016 6:57 AM, Joe D Williams wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How about we look at abstract SAI, EcmaScript SAI Language Binding and Java SAI Language Binding together on a working-group call (ensuring that Dick is present) and decide on similar/common structure for each specification?<br>
</blockquote>
<br>
Will these help. Out of data but I am willing to update if it will help.<br>
<br>
<a href="http://www.hypermultimedia.com/x3d/Quick/SAIABSDEFS.htm" rel="noreferrer" target="_blank">http://www.hypermultimedia.com<wbr>/x3d/Quick/SAIABSDEFS.htm</a><br>
<br>
<a href="http://www.hypermultimedia.com/x3d/Quick/SAIDEFS.htm" rel="noreferrer" target="_blank">http://www.hypermultimedia.com<wbr>/x3d/Quick/SAIDEFS.htm</a><br>
<br>
Thanks,<br>
Joe<br>
<br>
<br>
<br>
<br>
----- Original Message ----- From: "Don Brutzman" <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br>
To: "Roy Walmsley" <<a href="mailto:roy.walmsley@ntlworld.com" target="_blank">roy.walmsley@ntlworld.com</a>>; "'X3D Graphics public mailinglist'" <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
Sent: Saturday, October 22, 2016 4:24 PM<br>
Subject: Re: [x3d-public] announce: X3D Java Scene Authoring Interface (SAI) open source, initial review release<br>
<br>
<br>
On 7/2/2016 8:31 AM, Roy Walmsley wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Don,<br>
<br>
This is great work done. Well done.<br>
</blockquote>
<br>
thank you Roy.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You know me - can't help but be picky!<br>
</blockquote>
<br>
um, if the details weren't important, they wouldn't be the details. 8)<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I looked at the draft Annex B for the 19777-2 Java language binding. I looked at the title of the annex, B.1.1 Introduction, and then Table B.1 Topics. As you can see there is a mismatch.<br>
</blockquote>
<br>
OK... here are links to compare autogenerated annex with original specification annex.<br>
<br>
Autogenerated: draft Annex B Node type interfaces<br>
<a href="http://www.web3d.org/specifications/java/draftJavaLanguageBindingAnnexes/Part2/nodeTypeInterfaces.html" rel="noreferrer" target="_blank">http://www.web3d.org/specifica<wbr>tions/java/draftJavaLanguageBi<wbr>ndingAnnexes/Part2/<wbr>nodeTypeInterfaces.html</a><br>
<br>
(former original Abstract node interfaces)<br>
<a href="http://www.web3d.org/documents/specifications/19777-2/V3.0/Part2/abstracts.html" rel="noreferrer" target="_blank">http://www.web3d.org/documents<wbr>/specifications/19777-2/V3.0/<wbr>Part2/abstracts.html</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I see two alternatives to resolve this:<br>
<br>
1) Change the title and the introduction to reflect the contents.<br>
<br>
2) Separate the contents into smaller annexes. For example, “Abstract type interfaces”,<br>
<br>
Now look at B.3 Auxiliary node type interfaces. And then the topics within it. These are not node types. They would be better titled ‘Auxiliary type interfaces’.<br>
<br>
I also think that field interfaces need to be first. Look at 19775, 19776 series standards. Fields are derived before nodes, because all nodes need fields, and only some fields need nodes.<br>
</blockquote>
<br>
These seem like reasonable improvements. Usage of the terms nodes, interfaces and fields can be slippery - there is already a rename in the annex title pending.<br>
<br>
However, since options (1) and (2) above each relate to specification document structure, am hesitating to make piecemeal improvements that might lead to other inconsistencies elsewhere/later. Don't want to chase a problem by possibly pushing inconsistencies around.<br>
<br>
How about we look at abstract SAI, EcmaScript SAI Language Binding and Java SAI Language Binding together on a working-group call (ensuring that Dick is present) and decide on similar/common structure for each specification?<br>
<br>
Given the importance of getting this right, getting the specification organizations reconciled and documented in Mantis will help. I can then easily change the original-spec titles in the autogenerated annexes to match.<br>
</blockquote>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA <a href="tel:%2B1.831.656.2149" value="+18316562149" target="_blank">+1.831.656.2149</a><br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzma<wbr>n</a><br>
<br>
______________________________<wbr>_________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listi<wbr>nfo/x3d-public_web3d.org</a><br>
</blockquote></div></div>