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

[Andreas Plesch]

On Sat, Mar 8, 2025 at 12:07 AM Michalis Kamburelis <
michalis.kambi at gmail.com> wrote:

> 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.
>

Ah, yes, I recall that this was mentioned but then no changes to 4.3.2 were
made. Allowing specifically FontLibrary in 4.3.2 would emphasize that it
would be a very unique sort of root node.

WorldInfo is interesting in this respect because it is also really about
the whole scene but it implements the X3DChildNode interface and could be
part of any grouping node (although it probably never is).


> 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.
>

x3dom treats Scene as a X3DGroupingNode. I think in x3dom it would be
possible to add a Scene.fontLibray pseudo field.

Regards,
-Andreas


> Regards,
> Michalis
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250309/88c1f47b/attachment.html>