[x3d-public] draft X3D 4.1 prose for font files and libraries

[Michalis Kamburelis]

Andreas wrote:

> In fact, it appears that X3DChildNodes can be root nodes while on the
contrary most other X3DNodes cannot - unless something changed. See
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD//Part01/concepts.html#Rootnodes
> This is why X3D browsers tend to treat Scene as a Grouping node.
>  If that is the case FontLibray would need to derive from X3DChildNode,
not X3DNode.
> Perhaps I am missing something about root nodes,

My understanding so far was that Don wants to change that piece of
specification, "4.3.2 Root nodes", to explicitly allow FontLibrary as a
root node.

And yes, this is another complication for implementations. For CGE, our
"root node" is actually a descendant of Group node, with special code for
handling top-level metadata node. For every "special rule" in that section
"4.3.2 Root nodes", the implementation gets complicated.

Regards,
Michalis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250308/7bb54a13/attachment-0001.html>