[x3d-public] Mantis 27.4.9 NurbSet - Change child geometry model to X3DParametricGeometryNode

[John Carlson]

Don, I'm a bit unsure of the new semantics for NurbsSet....it includes
other parametric geometry nodes which aren't NURBS?

Would ParametricGeometrySet be a better name than NurbsSet, or a good
addition to X3D4?

Is it counterintuitive to look for a "ParametricGeometrySet" inside NURBS
sections?

How does this impact browser implementations?

I don't know if the standard includes parametric, implicit, etc.
descriptions?

Are we planning on dropping X3DNurbsSurfaceGeometryNode  in the future?

NURBS seems a bit specialized, but at least I know I'm looking for NURBS.
Parametric seems *way* general, and should probably remain at the abstract
level.

I have no other issues that come to mind presently.

I'm a bit leery of Mantis, so I will now review your next email.    My
summary:  Can one include more than one abstract type in the allowable
types?  That is, allow both X3DParametricGeometryNode
and X3DNurbsSurfaceGeometryNode sub node types for geometry?

Thanks!

John

On Wed, May 11, 2022 at 8:06 PM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

> NurbsSet should be inclusive about which nodes an author thinks can be
> rendered together as one smooth surface.
>
>
>
>    - Mantis 27.4.9 NurbSet - Change child geometry model to
>    X3DParametricGeometryNode
>    - https://www.web3d.org/member-only/mantis/view.php?id=700
>
>
>
>    - X3D4 Architecture, NURBS component, 27.4.8 NurbsSet
>    -
>    https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/nurbs.html#NurbsSet
>
>
>
> Since X3DParametricGeometryNode includes X3DNurbsSurfaceGeometryNode,
> changed all three NurbsSet geometry fields from X3DNurbsSurfaceGeometryNode
> to X3DParametricGeometryNode.
>
>
>
> NurbsSet : X3DChildNode, X3DBoundedObject {
>
>   MFNode  [in]     addGeometry                [X3DParametricGeometryNode]
>
>   MFNode  [in]     removeGeometry             [X3DParametricGeometryNode]
>
>   MFNode  [in,out] geometry          []       [X3DParametricGeometryNode]
>
>   SFNode  [in,out] metadata          NULL     [X3DMetadataObject]
>
>   SFFloat [in,out] tessellationScale 1.0      (0,∞)
>
>   SFVec3f []       bboxCenter        0 0 0    (-∞,∞)
>
>   SFVec3f []       bboxSize          -1 -1 -1 [0,∞) or −1 −1 −1
>
> }
>
>
>
> This changes X3DUOM and possibly some implementations.  Comments welcome.
>
>
>
> We current intend to accept this change as resolved once X3DUOM is updated.
>
>
>
> all the best, Don
>
> --
>
> Don Brutzman  Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
>
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149
>
> X3D graphics, virtual worlds, Navy robotics https://
> faculty.nps.edu/brutzman
>
>
> _______________________________________________
> 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/20220512/83aebea8/attachment.html>