<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Indeed, looking at X3Dv4 XML encoding, X3D Canonical Form (but
I'm confused over whether VRML also has a canonical form or not):</p>
<p><a class="moz-txt-link-freetext" href="file:///home/coderextreme/X3D/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html#X3DCanonicalForm">file:///home/coderextreme/X3D/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html#X3DCanonicalForm</a></p>
<p>retrieved via git clone.<br>
</p>
<div class="moz-cite-prefix">Section 4.2.3:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">"Double-quote and single-quote
characters:
<ol type="1">
<li>Individual MFString array values are bounded by
"double-quote" characters, each separated by a single space.</li>
<li>The overall MFString attribute is contained within
'single-quote' characters.</li>
</ol>
<blockquote>
<p class="Example">EXAMPLE 1 <code><NavigationInfo type='"WALK" "EXAMINE" "ANY"'/></code>
</p>
</blockquote>
<ol type="1" start="3">
<li>Single-quote characters within an MFString value are
replaced by the <code>′</code> character entity.</li>
<li>Double-quote characters within an MFString value are
replaced by the <code>"</code> character entity (and
escaped by a leading backslash "\" character).</li>
<li>XML " character references that delimit individual
strings in an MFString array are converted to double-quote
characters.
<p class="Example">EXAMPLE 1 <code><Text string='
"\"Hello, quotation marks\"" "Line 2 has
no quotation marks" '/></code> displays the following
two lines:</p>
<p class="Example"> “Hello, quotation marks”<br>
Line 2 has no quotation marks"</p>
</li>
<li>
<p class="Example">=========================================================================<br>
</p>
</li>
</ol>
<p>I'm not seeing any ' It could appear in XML
Canonicalization? I do see 3), which appears to say '
is at least not preferred.<br>
</p>
<p>Also, I'm seeing in 2) that my way of handling FontStyle family
is correct.</p>
<p>Read 'em and weep, or just send back a response rebutting.</p>
<p>Enjoying the lively banter about standards. Is this what you
guys spend time doing?</p>
<p>Remember, people are spending their lives on this stuff. No
need to jerk them around excessively. Getting close to right
was literally a struggle, and we're not quite there yet for JSON
parsing with X3DJSONLD.java (or whatever it's called now). I
was aching over pretty much everything in XML, which is why *I*
prefer JSON (despite not having comments). It is an ECMA
standard. It has a large body of people who know and love or
hate it.</p>
<p>Suggestion, we at least do XML -> JSON -> XML in 2 wildly
different ways.<br>
</p>
<p>What should the new standard be?</p>
<p>In 5) I do not see why we have ""'s and also \"
very confusing. Oh, I get it, quotes within SFStrings.<br>
</p>
<p>So maybe I am just the foil to discuss this. I have yet to
find a detail in V4 that wasn't in V3.3</p>
<p>Drop a little data file in the archives, and poof, it explodes.</p>
<p>I'm hearing a suggestion that I go through the standard using a
fine tooth comb, because we are generating it from X3DUOM?</p>
<p>There is room for building prototypes before specifications.
Just look at how X3DUOM was created. I know it's not your
favorite way of dealing with things.<br>
</p>
<p>John<br>
</p>
On 4/19/21 10:36 PM, John Carlson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:22586989-9886-c9f6-fbd7-114347588240@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I didn't realize that ' was acceptable. I knew
" used to be acceptable, and may still be. This is the
first time I've see ' and there were complaints, but I
can't recall which tool. I am also getting complaints about the
'"Times"'.<br>
</p>
<p>So I reference:</p>
<p><a class="moz-txt-link-freetext"
href="https://www.web3d.org/documents/specifications/19776-3/V3.3/Part03/concepts.html#X3DCanonicalForm"
moz-do-not-send="true">https://www.web3d.org/documents/specifications/19776-3/V3.3/Part03/concepts.html#X3DCanonicalForm</a>
which I believe is the latest XML encoding standard (reviewing,
I see there's a 4.0 draft).<br>
</p>
<p>"Double-quote and single-quote characters:</p>
<ol type="1">
<li>Individual MFString array values are bounded by
"double-quote" characters, each separated by a single space.</li>
<li>The overall MFString attribute is contained within
'single-quote' characters.</li>
</ol>
<blockquote>
<p class="Example">EXAMPLE 1 <code><NavigationInfo type='"WALK" "EXAMINE" "ANY"'/></code>
</p>
</blockquote>
<ol type="1" start="3">
<li>Single-quote characters within an MFString value are
replaced by the <code>′</code> character entity.</li>
<li>Double-quote characters within an MFString value are
replaced by the <code>"</code> character entity (and
escaped by a leading backslash "\" character).</li>
<li>XML " character references that delimit individual
strings in an MFString array are converted to double-quote
characters.
<p class="Example">EXAMPLE 1 <code><Text string='
"\"Hello, quotation marks\"" "Line 2 has
no quotation marks" '/></code> displays the following
two lines:</p>
<p class="Example"> “Hello, quotation marks”<br>
Line 2 has no quotation marks"</p>
</li>
</ol>
<p><br>
</p>
<p>Please read the above and tell me what I'm doing wrong. This
seems to indicate that newlines, tabs, etc. be are allow between
SFStrings in an MFString in XML, but I don't know about HAnim or
X3DV4.<br>
</p>
<p>The above also indicates that ' is not a good encoding
for single-quote characters, although it's OK XML.</p>
<p><br>
</p>
<p>I'm not really sure where else to look for X3D Canonical Form,
clicked the first link on Google, dang, that's 3.3. Okay, I see
version="4.0" X3DV4 in the audio X3D files. But X3DV4 doesn't
cover XML encoding that I know of? I will look through the
drafts. Okay, I see:</p>
<p><a class="moz-txt-link-freetext"
href="https://raw.githubusercontent.com/Web3DConsortium/X3D/master/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html"
moz-do-not-send="true">https://raw.githubusercontent.com/Web3DConsortium/X3D/master/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html</a>
(I did try to read this).<br>
</p>
<p>Or:</p>
<p><a class="moz-txt-link-freetext"
href="https://raw.githubusercontent.com/Web3DConsortium/X3D/master/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html#X3DCanonicalForm"
moz-do-not-send="true">https://raw.githubusercontent.com/Web3DConsortium/X3D/master/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html#X3DCanonicalForm</a>
(not found).</p>
<p>I don't see any way to show this except by downloading from the
github site. I have already seen the HTML--looks like
gobbledegook, as that's what's shown on github. Is there
another way to view github that will show the rendered file?<br>
</p>
<p>Looking here:</p>
<p><a class="moz-txt-link-freetext"
href="https://www.web3d.org/specifications/"
moz-do-not-send="true">https://www.web3d.org/specifications/</a></p>
<p>I do see the 3.3 XML encoding standard referenced as first link
above.</p>
<p><br>
I don't really want to spend time downloading the standard yet.
Is there someplace you can privately share the rendered X3DV4
Canonical Form on the web for me as a member of web3d
consortium? Seems like creating a member accessible version
would be very handy for collaboration, and then there would be
no disagreements (which version do you have, etc.).</p>
<p>This might be a good place on the web3d.org website to put
member documents? It's under "Documents" on the main web3d.org
site. <a class="moz-txt-link-freetext"
href="https://www.web3d.org/about/documents"
moz-do-not-send="true">https://www.web3d.org/about/documents</a></p>
<p><br>
</p>
<p>I'm not sure I can share the X3D 4.0 XML encoding standard on
the mailing list? Should I contact you directly once I've
viewed the 4.0 version? So far, I've just viewed it on github.
Yes, I realize I am not up on all the encoding standards at this
time, mostly I am focused on getting JSON/JavaScript working.
My second priority is HAnim. XML is way down the list of my
priorities.<br>
</p>
<p>I'm a bit nervous having proprietary info on my computer right
now. A virus scan did not go perfectly (100 false positives),
so I'm a bit nervous. What I'll do is download the snapshot,
render and send a picture to Don directly, then delete my
version.<br>
</p>
<p>Thanks!</p>
<p>John<br>
</p>
<div class="moz-cite-prefix">On 4/19/21 8:43 AM, Don Brutzman
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f0e43c09-738b-91db-0a83-649d09709ca1@nps.edu">I don't
think two-sided material was intended, recommend merging
Material nodes (watch out for duplicate diffuseColor) or else
simply remove one of them. <br>
<br>
Or better yet, refresh your version control later. I just
started adjusting these copies, found a lot of differences with
Efi's latest. Am using those differences to add & test some
new diagnostics. <br>
<br>
p.s. John you likely want to adjust your text output to match
X3D Canonical Form in order to avoid diffs when comparing
equivalent node definitions. <br>
<br>
On 4/17/2021 11:54 PM, John Carlson wrote: <br>
<blockquote type="cite">NPS WARNING: *external sender* verify
before acting. <br>
<br>
<br>
SplitChannels.x3d attached. (no guarantees on which material
was chosen <br>
as backMaterial). <br>
<br>
<br>
x3d/content/examples/X3dForAdvancedModeling/AudioSpatialSound$
diff <br>
SplitChannels.x3d ~/X3DJSONLD/src/main/data/SplitChannels.x3d
<br>
20c20 <br>
< <NavigationInfo DEF='NAV' headlight='true'
type='NONE'/> <br>
--- <br>
> <NavigationInfo DEF='NAV' headlight='true'
type='"NONE"'/> <br>
44,45c44,45 <br>
< <Material diffuseColor='0.345 0.345 0.882'
transparency='0'/> <br>
< <Material ambientIntensity='0.0933'
diffuseColor='1 1 1' <br>
emissiveColor='0 0 0' shininess='0.51' specularColor='0.46
0.46 0.46'/> <br>
--- <br>
> <Material diffuseColor='0.345 0.345
0.882' <br>
transparency='0' containerField="material"/> <br>
> <Material ambientIntensity='0.0933'
diffuseColor='1 1 1' <br>
emissiveColor='0 0 0' shininess='0.51' specularColor='0.46
0.46 0.46' <br>
containerField="backMaterial"/> <br>
47,48c47,48 <br>
< <Text solid='false' string='Right Channel
Volume'> <br>
< <FontStyle
family=''Times'' horizontal='true' <br>
justify='BEGIN' leftToRight='true' size='1' spacing='1'
style='BOLD' <br>
topToBottom='true'/> <br>
--- <br>
> <Text solid='false' string='"Right Channel
Volume"'> <br>
> <FontStyle family='"Times"'
horizontal='true' <br>
justify='"BEGIN"' leftToRight='true' size='1' spacing='1'
style='BOLD' <br>
topToBottom='true'/> <br>
74,75c74,75 <br>
< <Material diffuseColor='0.345 0.345 0.882'
transparency='0'/> <br>
< <Material ambientIntensity='0.0933'
diffuseColor='1 1 1' <br>
emissiveColor='0 0 0' shininess='0.51' specularColor='0.46
0.46 0.46'/> <br>
--- <br>
> <Material diffuseColor='0.345 0.345
0.882' <br>
transparency='0' containerField="material"/> <br>
> <Material ambientIntensity='0.0933'
diffuseColor='1 1 1' <br>
emissiveColor='0 0 0' shininess='0.51' specularColor='0.46
0.46 0.46' <br>
containerField="backMaterial"/> <br>
77,78c77,78 <br>
< <Text solid='false' string='Left Channel
Volume'> <br>
< <FontStyle
family=''Times'' horizontal='true' <br>
justify='BEGIN' leftToRight='true' size='1' spacing='1'
style='BOLD' <br>
topToBottom='true'/> <br>
--- <br>
> <Text solid='false' string='"Left Channel
Volume"'> <br>
> <FontStyle family='"Times"'
horizontal='true' <br>
justify='"BEGIN"' leftToRight='true' size='1' spacing='1'
style='BOLD' <br>
topToBottom='true'/> <br>
107c107 <br>
< </X3D> <br>
\ No newline at end of file <br>
--- <br>
> </X3D> <br>
<br>
</blockquote>
<br>
all the best, Don <br>
</blockquote>
</blockquote>
</body>
</html>