[x3d-public] Do modern browsers DO VRML??

[vmarchetti at kshell.com]

Ok, I misspoke, or was very imprecise to the point of being incorrect.

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.
And, the XML encoding does not use the type system from XML Schema -- https://www.w3.org/TR/xmlschema-2/ <https://www.w3.org/TR/xmlschema-2/> -- but uses the types as defined in the X3D Specification.

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.

Vince


> On Feb 16, 2019, at 7:58 PM, Joseph D Williams <joedwil at earthlink.net> wrote:
> 
> The XML encoding of X3D does not use the more complex features of XML.
>  
> 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.  
> Joe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190217/a1e76e84/attachment-0001.html>