[x3d-public] Patched file, please review
John Carlson
yottzumm at gmail.com
Tue Apr 20 19:57:57 PDT 2021
Indeed, looking at X3Dv4 XML encoding, X3D Canonical Form (but I'm
confused over whether VRML also has a canonical form or not):
file:///home/coderextreme/X3D/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html#X3DCanonicalForm
retrieved via git clone.
Section 4.2.3:
"Double-quote and single-quote characters:
1. Individual MFString array values are bounded by "double-quote"
characters, each separated by a single space.
2. The overall MFString attribute is contained within 'single-quote'
characters.
EXAMPLE 1 |<NavigationInfo type='"WALK" "EXAMINE" "ANY"'/>|
3. Single-quote characters within an MFString value are replaced by the
|′| character entity.
4. Double-quote characters within an MFString value are replaced by the
|"| character entity (and escaped by a leading backslash
"\" character).
5. XML " character references that delimit individual strings in
an MFString array are converted to double-quote characters.
EXAMPLE 1 |<Text string=' "\"Hello, quotation marks\""
"Line 2 has no quotation marks" '/>| displays the following two lines:
“Hello, quotation marks”
Line 2 has no quotation marks"
6.
=========================================================================
I'm not seeing any ' It could appear in XML Canonicalization? I do
see 3), which appears to say ' is at least not preferred.
Also, I'm seeing in 2) that my way of handling FontStyle family is correct.
Read 'em and weep, or just send back a response rebutting.
Enjoying the lively banter about standards. Is this what you guys spend
time doing?
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.
Suggestion, we at least do XML -> JSON -> XML in 2 wildly different ways.
What should the new standard be?
In 5) I do not see why we have ""'s and also \" very confusing.
Oh, I get it, quotes within SFStrings.
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
Drop a little data file in the archives, and poof, it explodes.
I'm hearing a suggestion that I go through the standard using a fine
tooth comb, because we are generating it from X3DUOM?
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.
John
On 4/19/21 10:36 PM, John Carlson wrote:
>
> 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"'.
>
> So I reference:
>
> https://www.web3d.org/documents/specifications/19776-3/V3.3/Part03/concepts.html#X3DCanonicalForm
> which I believe is the latest XML encoding standard (reviewing, I see
> there's a 4.0 draft).
>
> "Double-quote and single-quote characters:
>
> 1. Individual MFString array values are bounded by "double-quote"
> characters, each separated by a single space.
> 2. The overall MFString attribute is contained within 'single-quote'
> characters.
>
> EXAMPLE 1 |<NavigationInfo type='"WALK" "EXAMINE" "ANY"'/>|
>
> 3. Single-quote characters within an MFString value are replaced by
> the |′| character entity.
> 4. Double-quote characters within an MFString value are replaced by
> the |"| character entity (and escaped by a leading backslash
> "\" character).
> 5. XML " character references that delimit individual strings in
> an MFString array are converted to double-quote characters.
>
> EXAMPLE 1 |<Text string=' "\"Hello, quotation marks\""
> "Line 2 has no quotation marks" '/>| displays the following two lines:
>
> “Hello, quotation marks”
> Line 2 has no quotation marks"
>
>
> 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.
>
> The above also indicates that ' is not a good encoding for
> single-quote characters, although it's OK XML.
>
>
> 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:
>
> https://raw.githubusercontent.com/Web3DConsortium/X3D/master/ISO-IEC19776/ISO-IEC19776-3/ISO-IEC19776-3v4.0/ISO-IEC19776-3v4.0-WD1/Part03/concepts.html
> (I did try to read this).
>
> Or:
>
> 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
> (not found).
>
> 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?
>
> Looking here:
>
> https://www.web3d.org/specifications/
>
> I do see the 3.3 XML encoding standard referenced as first link above.
>
>
> 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.).
>
> 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.
> https://www.web3d.org/about/documents
>
>
> 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.
>
> 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.
>
> Thanks!
>
> John
>
> On 4/19/21 8:43 AM, Don Brutzman wrote:
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> On 4/17/2021 11:54 PM, John Carlson wrote:
>>> NPS WARNING: *external sender* verify before acting.
>>>
>>>
>>> SplitChannels.x3d attached. (no guarantees on which material was chosen
>>> as backMaterial).
>>>
>>>
>>> x3d/content/examples/X3dForAdvancedModeling/AudioSpatialSound$ diff
>>> SplitChannels.x3d ~/X3DJSONLD/src/main/data/SplitChannels.x3d
>>> 20c20
>>> < <NavigationInfo DEF='NAV' headlight='true' type='NONE'/>
>>> ---
>>> > <NavigationInfo DEF='NAV' headlight='true' type='"NONE"'/>
>>> 44,45c44,45
>>> < <Material diffuseColor='0.345 0.345 0.882'
>>> transparency='0'/>
>>> < <Material ambientIntensity='0.0933' diffuseColor='1 1 1'
>>> emissiveColor='0 0 0' shininess='0.51' specularColor='0.46 0.46 0.46'/>
>>> ---
>>> > <Material diffuseColor='0.345 0.345 0.882'
>>> transparency='0' containerField="material"/>
>>> > <Material ambientIntensity='0.0933' diffuseColor='1 1 1'
>>> emissiveColor='0 0 0' shininess='0.51' specularColor='0.46 0.46 0.46'
>>> containerField="backMaterial"/>
>>> 47,48c47,48
>>> < <Text solid='false' string='Right Channel Volume'>
>>> < <FontStyle family=''Times'' horizontal='true'
>>> justify='BEGIN' leftToRight='true' size='1' spacing='1' style='BOLD'
>>> topToBottom='true'/>
>>> ---
>>> > <Text solid='false' string='"Right Channel Volume"'>
>>> > <FontStyle family='"Times"' horizontal='true'
>>> justify='"BEGIN"' leftToRight='true' size='1' spacing='1' style='BOLD'
>>> topToBottom='true'/>
>>> 74,75c74,75
>>> < <Material diffuseColor='0.345 0.345 0.882'
>>> transparency='0'/>
>>> < <Material ambientIntensity='0.0933' diffuseColor='1 1 1'
>>> emissiveColor='0 0 0' shininess='0.51' specularColor='0.46 0.46 0.46'/>
>>> ---
>>> > <Material diffuseColor='0.345 0.345 0.882'
>>> transparency='0' containerField="material"/>
>>> > <Material ambientIntensity='0.0933' diffuseColor='1 1 1'
>>> emissiveColor='0 0 0' shininess='0.51' specularColor='0.46 0.46 0.46'
>>> containerField="backMaterial"/>
>>> 77,78c77,78
>>> < <Text solid='false' string='Left Channel Volume'>
>>> < <FontStyle family=''Times'' horizontal='true'
>>> justify='BEGIN' leftToRight='true' size='1' spacing='1' style='BOLD'
>>> topToBottom='true'/>
>>> ---
>>> > <Text solid='false' string='"Left Channel Volume"'>
>>> > <FontStyle family='"Times"' horizontal='true'
>>> justify='"BEGIN"' leftToRight='true' size='1' spacing='1' style='BOLD'
>>> topToBottom='true'/>
>>> 107c107
>>> < </X3D>
>>> \ No newline at end of file
>>> ---
>>> > </X3D>
>>>
>>
>> all the best, Don
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210420/e2d425a5/attachment-0001.html>
More information about the x3d-public
mailing list