[x3d-public] Replacing USE with DEF

[Don Brutzman]

It is not possible to avoid USE, it is fully integrated functionality in
the specification.  No need to reengineer the specification.

Again recommend working on one very simple case at a time, to narrow down
each problem and fix it.  Complexity obscures diagnosis.

all the best, Don
-- 
X3D Graphics, Maritime Robotics, Distributed Simulation
Relative Motion Consulting  https://RelativeMotion.info


On Fri, Mar 27, 2026 at 6:08 PM John Carlson via x3d-public <
x3d-public at web3d.org> wrote:

> Replacing USE with DEF would massively improve the JSON schema.   I vote
> for that!   It would massively improve the error reporting as well.
>
> What does FreeWRL think?
>
> No need for two attributes for the same meaning.
>
> USE and DEF code be used interchangeably, and container fields could
> specify parents.
>
> The only problem I see is when USE and DEF are used together, but that’s
> already an issue.
>
> John
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20260327/cc01356b/attachment-0001.html>