<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="">Ok, I misspoke, or was very imprecise to the point of being incorrect.<div class=""><br class=""></div><div class="">The 'more complex features' I was thinking of was XML namespaces; the XML encoding of X3D does not define an x3d namespace, and taken rigourously, the standard does not allow for including XML elements from other namespaces.</div><div class="">And, the XML encoding does not use the type system from XML Schema -- <a href="https://www.w3.org/TR/xmlschema-2/" class="">https://www.w3.org/TR/xmlschema-2/</a> -- but uses the types as defined in the X3D Specification.</div><div class=""><br class=""></div><div class="">But, the XML encoding of X3D respects all the syntax rules in XML and the XML toolset is available for using with *.x3d files; XSLT is an important part of my kit for creating X3D files.</div><div class=""><br class=""></div><div class="">Vince</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 16, 2019, at 7:58 PM, Joseph D Williams <<a href="mailto:joedwil@earthlink.net" class="">joedwil@earthlink.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Monaco; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><ul type="disc" style="margin-bottom: 0in; margin-top: 0in;" class=""><li class="MsoListParagraph" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The XML encoding of X3D does not use the more complex features of XML.<o:p class=""></o:p></li></ul><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The web3d x3d xml encoding uses all practical features of xml/xhtml encoding and xml schema authoring and validation toolset(s) to their limits and beyond. I don’t think we are beyond any authortime limits at this time, but probably still maybe some sai/dom runtime problematics. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Joe</div></div></div></blockquote></div><br class=""></div></body></html>