<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Don and others,<br>
<br>
This is great work in advance of the call. I have been mostly
staying out of the discussion, but actively reading the messages.
<br>
<br>
I've trimmed Don's latest post to get to a couple of questions I
have.<br>
<br>
<br>
<br>
</div>
<blockquote cite="mid:54FDBC31.40406@nps.edu" type="cite"><br>
<br>
Completely converted HelloWorld.json attached. Looks like a pair
of slightly different design patterns (first for header and then
for scene graph) are required and holding together OK so far.
Still passes jslint in its strictest mode. <a class="moz-txt-link-freetext" href="http://www.jslint.com">http://www.jslint.com</a>
<br>
</blockquote>
...<br>
<blockquote cite="mid:54FDBC31.40406@nps.edu" type="cite">
<br>
=======================================================================
<br>
7. Apparently not possible or not needed.
<br>
<br>
- Embedded JSON comments are specifically disallowed by JSON
specification
<br>
and so round-trippable inclusion must be a custom feature of
this encoding.
<br>
<a class="moz-txt-link-freetext" href="http://www.quora.com/How-do-I-write-comments-inside-a-JSON-document">http://www.quora.com/How-do-I-write-comments-inside-a-JSON-document</a>
<br>
- No JSON-unique header. Can optionally use X3D/head/meta
name=value pairs
<br>
(if capturing full document) or comments in a scene-graph
fragment
<br>
or even an X3D Metadata node. However for anything intended to
be
<br>
interoperable/reusable, consistency and repeatability is needed.
<br>
Leaving the output JSON as simple as possible avoids code
problems and
<br>
provides programmers with the greatest possible flexibility.
Further
<br>
analysis will show if a JSON header is needed, probably a
non-problem.
<br>
- DOCTYPE information is dropped. This is commonplace for XSLT
and does
<br>
not appear to be needed in the JSON encoding. If actually
needed by someone,
<br>
such information can be reconstructed simply by using the X3D
version number.
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Validation">http://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#Validation</a><br>
</blockquote>
<br>
Many languages (including PHP and Perl, I also presume Python, and
perhaps JavaScript) have libraries that will do a JSON -> XML
conversion. After conversion it would be necessary to write code to
convert the JSON embedded comments to true XML comments. Using one
of these may save some development time and effort.<br>
<br>
<br>
Is it possible to construct an extremely simple X3D scene (or
scene-let) that illustrates the issues with the various possible
JSON encodings? This would not be a test scene, but something that
is short (<20 lines) and has sufficient structure to illustrate
why certain encodings work or do not work.<br>
<br>
The attachment to the previous message is good as a test case, but
is long to easily grasp the issues. Perhaps multiple discussion
scenes are needed to address the various issues - something to
discuss the headers (but an empty scene), something to show node
array issues, something to use for ROUTE/IS/PROTOs, etc.<br>
<br>
<br>
<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>