<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1250">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2113741340;
mso-list-type:hybrid;
mso-list-template-ids:-1461011540 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Best way to confirm is to look at autogenerated documentation to see what occurred.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">https://www.web3d.org/specifications</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">https://www.web3d.org/specifications/X3dSchemaDocumentation4.0.html<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">https://www.web3d.org/specifications/X3dDoctypeDocumentation4.0.html<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The modifications to the schemas and DTDs were corrections to match the requirements defined in the X3D Architecture specification. Hopefully they are correct.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Work continues on an example scene that has tested this to some degree.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">https://x3dgraphics.com/examples/X3dForAdvancedModeling/TextureMapping/MultiTextureTeapotIndex.html<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hope this helps.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">all the best, Don<br>
<span style="font-size:10.0pt;font-family:"Courier New"">-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman">
http://faculty.nps.edu/brutzman</a></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:michalis.kambi@gmail.com">Michalis Kamburelis</a><br>
<b>Sent: </b>Monday, September 27, 2021 3:58 PM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br>
<b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Public</a><br>
<b>Subject: </b>Re: [x3d-public] X3D4 updates: MultiTexture validation, X3DUOM, Java, Python, Turtle</p>
</div>
<p class="MsoNormal"><br>
The texCoord field of X3DComposedGeometryNode should just allow any<br>
texture coordinate, i.e. anything descending from<br>
X3DTextureCoordinateNode .<br>
<br>
Indeed X3DTextureCoordinateNode means "X3DSingleTextureCoordinateNode<br>
or MultiTextureCoordinate" in practice.<br>
<br>
Reading the log, I am not sure -- what is the change you made? Was<br>
there an issue with "just" allowing texCoord to allow any<br>
X3DTextureCoordinateNode (and thus, implicitly. any<br>
X3DSingleTextureCoordinateNode or MultiTextureCoordinate)?<br>
<br>
Regards,<br>
Michalis<br>
<br>
pon., 27 wrz 2021 o 23:09 Brutzman, Donald (Don) (CIV)<br>
<brutzman@nps.edu> napisał(a):<br>
<br>
><br>
> Extensible 3D (X3D) Graphics is the royalty-free open standard for publishing, viewing, printing and archiving interactive 3D models on the Web.<br>
><br>
><br>
><br>
> Here are recent updates. Had some good refinements related to MultiTexture, now rippled out through all of the open-source autogenerated software builds.<br>
><br>
><br>
><br>
> X3D XML Schema update activity, addressing some scene validation issues:<br>
><br>
> <a href="https://www.web3d.org/specifications/x3d-schema-changelog.txt">https://www.web3d.org/specifications/x3d-schema-changelog.txt</a><br>
><br>
><br>
><br>
> 25 SEP 2021, brutzman<br>
><br>
> - (v3.1-v4.0) MultiTexture texture field has type X3DSingleTextureNode and can include<br>
><br>
> ComposedCubeMapTexture, GeneratedCubeMapTexture, ImageCubeMapTexture,<br>
><br>
> ComposedTexture3D, ImageTexture3D, PixelTexture3D<br>
><br>
> - (v3.1-v4.0) MultiTextureCoordinate is part of ComposedGeometryContentModel<br>
><br>
> - (v4.0) allow X3DComposedGeometryNode texCoord field to include<br>
><br>
> X3DSingleTextureCoordinateNode|MultiTextureCoordinate<br>
><br>
> - (v4.0) allow watchlist containerField for backwards compatibility of X3D models in<br>
><br>
> containerFieldChoicesAudioClip<br>
><br>
><br>
><br>
> Corresponding changes added to X3D XML DOCTYPE as appropriate. All details found at<br>
><br>
><br>
><br>
> X3D Specifications: Schema and DOCTYPE Validation<br>
> <a href="https://www.web3d.org/specifications">https://www.web3d.org/specifications</a><br>
><br>
><br>
><br>
> X3D XML Schema changes are applied to the X3DUOM, which then in turn is applied via XSLT conversion stylesheets to create multiple coding projects.<br>
><br>
><br>
><br>
> X3D Unified Object Model (X3DUOM)<br>
> <a href="https://www.web3d.org/specifications/X3DUOM.html">https://www.web3d.org/specifications/X3DUOM.html</a><br>
> <a href="https://www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml">https://www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml</a><br>
><br>
><br>
><br>
> “The X3D Unified Object Model (X3DUOM) is a full set of object-oriented interfaces for all nodes, fields and statements in the X3D Architecture Specification.”<br>
><br>
><br>
><br>
> Each of the following codebase updates passed respective sets of unit tests and conversions using the test scenes (nearly 4000 total).<br>
><br>
><br>
><br>
> X3D Resources, Examples: Scene Archives for X3D<br>
> <a href="https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples">
https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples</a><br>
><br>
><br>
><br>
> JAVA X3DJSAIL API<br>
><br>
><br>
><br>
> X3D Java Scene Access Interface Library (X3DJSAIL)<br>
> <a href="http://www.web3d.org/specifications/java/X3DJSAIL.html">http://www.web3d.org/specifications/java/X3DJSAIL.html</a><br>
><br>
><br>
><br>
> “X3D Java Scene Access Interface Library (X3DJSAIL) supports programmers with standards-based X3D Java interfaces and objects, all as open source.”<br>
><br>
><br>
><br>
> Python X3DPSAIL API<br>
><br>
><br>
><br>
> X3D Python Scene Access Interface Library (X3DPSAIL)<br>
> <a href="https://www.web3d.org/x3d/stylesheets/python/python.html">https://www.web3d.org/x3d/stylesheets/python/python.html</a><br>
><br>
><br>
><br>
> Python x3d.py package<br>
> <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fx3d&data=04%7C01%7Cbrutzman%40nps.edu%7C8fabf046665e4cf38c7e08d9820a45f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637683802917537795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HX%2BALPxSai48frPhw8jcdLWioprvKYjwHXzFYRu5zOE%3D&reserved=0">
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fx3d&data=04%7C01%7Cbrutzman%40nps.edu%7C8fabf046665e4cf38c7e08d9820a45f5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637683802917537795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HX%2BALPxSai48frPhw8jcdLWioprvKYjwHXzFYRu5zOE%3D&reserved=0</a><br>
><br>
><br>
><br>
> “The x3d.py Python X3D Package supports programmers with Python interfaces and objects for standards-based X3D programming, all as open source.”<br>
><br>
><br>
><br>
> Design Features<br>
><br>
><br>
><br>
> The current implementation strives to follow first principles of python package design, being as "pythonic" as possible. Creating a native-Python implementation for X3D data structures appears to provide the greatest possible portability.<br>
> Python is exceedingly rigorous regarding design and implementation, demands crisp readability, and often leads to a single best approach for each programming task. These are valuable features that lead to ease of programming and greatly reduced debugging.
A single well-constructed open-source Python X3D implementation has the potential to serve all Python distributions and programmers well.<br>
><br>
><br>
><br>
> X3D Ontology<br>
><br>
><br>
><br>
> X3D Ontology for Semantic Web<br>
> <a href="https://www.web3d.org/x3d/content/semantics">https://www.web3d.org/x3d/content/semantics</a><br>
><br>
><br>
><br>
> “The X3D Ontology for Semantic Web provides terms of reference for semantic query of X3D models.”<br>
><br>
><br>
><br>
> Steady work continues. All feedback welcome. Have fun with X3D4! 8)<br>
><br>
><br>
><br>
> all the best, Don<br>
> --<br>
> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<br>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
> X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman">
http://faculty.nps.edu/brutzman</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> x3d-public mailing list<br>
> x3d-public@web3d.org<br>
> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>