[x3d-public] Note to browser vendors.

Michalis Kamburelis michalis.kambi at gmail.com
Mon Jul 17 15:52:43 PDT 2023


I just improved Castle Game Engine / view3dscene reporting to properly
warn when node names are not unique (in both VRML and X3D).

Regards,
Michalis

czw., 13 lip 2023 o 17:16 Michalis Kamburelis
<michalis.kambi at gmail.com> napisał(a):
>
> AD 2 - Agreed, though note that VRML 97 and X3D (all encodings) differ here.
>
> VRML 97: ( https://tecfa.unige.ch/guides/vrml/vrml97/spec/part1/concepts.html#4.6.2
> )
>
> """
> If multiple nodes are given the same name, each USE statement refers
> to the closest node with the given name preceding it in either the
> VRML file or prototype definition.
> """
>
> X3D: ( https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/concepts.html#DEFL_USESemantics
> )
>
> """
> Node names shall be unique in the context within which the associated
> DEF keyword occurs.
> """
>
> To be clear, I think X3D (stricter) is saner. But still, a browser
> that wants to handle all valid VRML (like view3dscene) can warn in
> VRML with at most something like "Duplicate identifier specified for a
> name. This is not portable to the X3D (VRML successor) so we recommend
> to make it unique". Only in X3D the warning can be stronger
> ("Duplicate identifier, not allowed in X3D.").
>
> Regards,
> Michalis
>
> czw., 13 lip 2023 o 01:11 John Carlson <yottzumm at gmail.com> napisał(a):
> >
> > 1) Warn for DEF value after USE value.   Some browsers do.  Some browsers choke.
> > 2) Warn for repeated DEF values.  Probably unintended by author.
> >
> > That's all for now.
> > _______________________________________________
> > x3d-public mailing list
> > x3d-public at web3d.org
> > http://web3d.org/mailman/listinfo/x3d-public_web3d.org



More information about the x3d-public mailing list