<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I think I am fine with this decisions. I<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">n the next release </span>X_ITE will implement Appearance alphaMode, and alphaCutoff. Besides this, X3DShapeNode castShadow, X3DBoundedBox visible, and bboxDisplay is implemented.<div class=""><br class=""></div><div class="">Best regards,</div><div class="">Holger<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 23.11.2021 um 04:00 schrieb John Carlson <<a href="mailto:yottzumm@gmail.com" class="">yottzumm@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">Note: some synonyms have spotty coverage. X3DJSAIL has setBackTexture and not setBack. I’ve tried to support synonyms in the X3D JSON Schema.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">John</div><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 22, 2021 at 5:43 PM John Carlson <<a href="mailto:yottzumm@gmail.com" class="">yottzumm@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="auto" class="">It appears that X3D4 is moving towards synonyms for field names (see X3DUOM), but that’s likely not fully addressed in X3DJSAIL yet.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Whether different case is supported in synonyms, IDK. Kinda wonky.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">John </div><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 22, 2021 at 5:34 PM Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com" target="_blank" class="">michalis.kambi@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Nice catch.<br class="">
<br class="">
Yes, the spelling of "Appearance.alphaCutoff" with lowercase "o" was<br class="">
deliberate... to be consistent with glTF property with *exactly* the<br class="">
same name, "alphaCutoff" . We also have "Appearance.alphaMode"<br class="">
matching glTF "alphaMode" closely.<br class="">
<br class="">
See glTF spec: <a href="https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#reference-material" rel="noreferrer" target="_blank" class="">https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#reference-material</a><br class="">
<br class="">
I honestly blatantly didn't think to check the spelling of<br class="">
"SpotLight.cutOffAngle" . I missed the fact that we are, in effect,<br class="">
inconsistent with it.<br class="">
<br class="">
I do not have a strong opinion about the resolution. We can<br class="">
<br class="">
1. leave things as-is. So we remain consistent with glTF, but<br class="">
inconsistent with "SpotLight.cutOffAngle".<br class="">
<br class="">
2. rename the field to have uppercase "O", making<br class="">
"Appearance.alphaCutOff". So we remain consistent with<br class="">
"SpotLight.cutOffAngle", but inconsistent with glTF.<br class="">
<br class="">
Normally I'd say that AD 2 is better (better to be consistent with<br class="">
ourselves), but in this case "alphaMode" and "alphaCutoff" are both<br class="">
very directly from glTF, and the "SpotLight.cutOffAngle" seems<br class="">
"further away" in terms of concepts (the spot light cut-off angle<br class="">
talks about a very different thing, not related to alpha<br class="">
interpretation). So... I'm really on the fence, and can accept any<br class="">
resolution. Waiting for others' opinions!<br class="">
<br class="">
Regards,<br class="">
Michalis<br class="">
<br class="">
pon., 22 lis 2021 o 21:42 Holger Seelig <<a href="mailto:holger.seelig@yahoo.de" target="_blank" class="">holger.seelig@yahoo.de</a>> napisał(a):<br class="">
><br class="">
> I noticed that the new field alphaCutoff is written with a lowercase o in off, and not alphaCutOff. But the field SpotLight.cutOffAngle is written with an uppercase O in Off. Is both right or should there be a correction?<br class="">
><br class="">
> Appearance:<br class="">
> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/shape.html#Appearance" rel="noreferrer" target="_blank" class="">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/shape.html#Appearance</a><br class="">
><br class="">
> SpotLight<br class="">
> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/lighting.html#SpotLight" rel="noreferrer" target="_blank" class="">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/lighting.html#SpotLight</a><br class="">
><br class="">
> Holger<br class="">
><br class="">
> _______________________________________________<br class="">
> x3d-public mailing list<br class="">
> <a href="mailto:x3d-public@web3d.org" target="_blank" class="">x3d-public@web3d.org</a><br class="">
> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank" class="">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br class="">
<br class="">
_______________________________________________<br class="">
x3d-public mailing list<br class="">
<a href="mailto:x3d-public@web3d.org" target="_blank" class="">x3d-public@web3d.org</a><br class="">
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank" class="">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br class="">
</blockquote></div></div>
</blockquote></div></div>
</div></blockquote></div><br class=""></div></body></html>