<div dir="ltr">Follow up after re-reading Mantis
700. The Mantis does not speak of NurbsCurve, a subtype node of X3DParametricGeometryNode. This is the biggest sticking point for me. To me, it's not a surface, but if you say so, I will concur! The language of the standards limits NurbsSet geometry to surfaces, if not the interfaces. Shucks!<div><br></div><div>I would love to add more parametric geometry that includes tesselationScale to the standard. Let me know when we can proceed. I realize that I cannot add it to NurbsSet.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 14, 2022 at 1:36 AM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Finally, my recommendation:<div><br></div><div>Change nothing unless we want curves and possibly extrusions (pseudo-surfaces) to be in NurbsSet. Otherwise, proceed.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 14, 2022 at 1:29 AM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><div>I apologize that this was not in a comment to the website. It's easier to follow a thread in email. Read the last paragraph if you want a conclusion.</div><div><br></div><div>The X3D4 CD <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/nurbs.html#NurbsSet" target="_blank">Extensible 3D (X3D), ISO/IEC 19775-1:2022, 27 NURBS Component (web3d.org)</a> says the tesselationScale affects Nurbs surface nodes: "<span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px">The </span><i style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px">tessellationScale</i><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px"> parameter is scaling the tessellation values in </span><span title="Mantis 428" style="background-color:orange;text-decoration-line:line-through;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px">lower level</span><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px"> </span><span title="Mantis 428" style="background-color:yellow;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px">contained</span><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:16px"> Nurbs surface nodes."</span><br></div><div><br></div><div><font color="#000000" face="Verdana, Arial, Helvetica, sans-serif"><span style="font-size:16px"><b>Note: If the contained Nurbs </b>curve <b>nodes now possible, but illegal in a NurbsSet are not scaled by the tessellationScale, things might get confusing! But I kind of understand why they aren't! If NurbsSet only contains surfaces, why not call it "NurbsSurfaceSet"?</b></span></font></div></div><div><font color="#000000" face="Verdana, Arial, Helvetica, sans-serif"><span style="font-size:16px"><b><br></b></span></font></div><div>I hope we have a good list of Nurbs surface nodes that people can add to NurbsSet geometry for instead of relying on interfaces.</div><div><br></div><div><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif">Full text of NurbsSet:</p><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif">The NurbsSet node groups a <b>set of Nurbs surface nodes</b> to a common group for rendering purposes only. This informs the <span title="Mantis 1076" style="background-color:yellow">X3D</span> browser that the set of Nurbs surfaces shall be treated as a unit during tessellation to enforce tessellation continuity along borders. The <i>tessellationScale</i> parameter is scaling the tessellation values in <span title="Mantis 428" style="background-color:orange;text-decoration-line:line-through">lower level</span> <span title="Mantis 428" style="background-color:yellow">contained</span> Nurbs surface nodes. A set of Nurbs surfaces that use a matching set of <i>controlPoint</i> along the borders shall result in a common tessellation stepping.</p><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif">The geometry represented in the children of this node shall not be directly rendered. It is an informational node only. Surfaces not represented elsewhere in the transformation hierarchy shall not be rendered.</p><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif">The bounds information is provided for optimization purposes only. A <span title="Mantis 1076" style="background-color:yellow">X3D</span> browser <i>may choose </i>[ Editor's note: Why Don is seeing non-smooth NURBS, likely--but I'm not too familiar with the standard] to use this information about when to apply trimming or smooth tessellation between patches based on the bounds information (<span style="font-size:13.6px">EXAMPLE only smooth when the viewer is within the bounds</span>). </p><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif"><br></p><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif">So:</p><p style="font-size:16px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif"><br></p><h2 style="font-size:20.8px;margin-top:18px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif">27.4.3 NurbsCurve</h2><pre style="color:rgb(0,0,0);font-size:11.05px;margin-left:25px">NurbsCurve : X3DParametricGeometryNode {
SFNode [in,out] controlPoint NULL [X3DCoordinateNode]
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFInt32 [in,out] tessellation 0 (-∞,∞)
MFDouble [in,out] weight [] (0,∞)
SFBool [] closed FALSE
MFDouble [] knot [] (-∞,∞)
SFInt32 [] order 3 [2,∞)</pre><pre style="color:rgb(0,0,0);font-size:11.05px;margin-left:25px"><br></pre><pre style="color:rgb(0,0,0);font-size:11.05px;margin-left:25px"><br></pre><pre style="color:rgb(0,0,0);margin-left:25px"><font face="arial, sans-serif">The above has controlPoint, has tessellation, but does not participate in tesselationScale?</font></pre><pre style="color:rgb(0,0,0);margin-left:25px"><font face="arial, sans-serif"><br></font></pre><pre style="color:rgb(0,0,0);margin-left:25px"><font face="arial, sans-serif">I'm trying to understand the impact of: X3DNurbsControlCurveNode to surfaces that use it. The surfaces appear visually to be extrusions, and I now know that NURBS includes extrusions (surprise to me!) from reading the CD standard.</font></pre><pre style="color:rgb(0,0,0);margin-left:25px"><font face="arial, sans-serif"><span style="color:rgb(34,34,34);white-space:normal">I guess there's a use case for adding NurbsSwungSurfaces and NurbsSweptSurface to NurbsSets? Like outlining a </span><span style="color:rgb(34,34,34);white-space:normal">X3DNurbsSurfaceGeometryNode? Sounds okay by me! It seems confusing that there are no controlPoints to smooth with! Or is it more like, what set of controlPoints? And no tessellation control!</span></font><span style="font-size:11.05px">
</span></pre><pre style="color:rgb(0,0,0);margin-left:25px"><pre style="font-size:11.05px;margin-left:25px"><h2 style="font-size:20.8px;margin-top:18px;font-family:Verdana,Arial,Helvetica,sans-serif;white-space:normal">NurbsCurve2D</h2></pre><pre style="margin-left:25px">can't be added to a NurbsSet, thank goodness!</pre><span style="font-size:11.05px">
</span></pre></div><div>Are we okay now? As far as I can tell, the specification will work, but implementers will have to deal with sticky problems smoothing controlPoint between surfaces and extrusion surfaces. They'll have to somehow delegate the controlPoint in the extrusions to a control curve (is this specified?). And also excluding NurbsCurve from NurbsSet seems rather arbitrary, which is a good reason to change the type of the geometry field in NurbsSet. When we change the geometry field type, we lose the ability to separate types of NURBS (curves, extrusions, surfaces) in the NurbsSet geometry interfaces.</div><div><br></div><div>Thanks,</div><div><br></div><div>John</div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 13, 2022 at 10:13 AM Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div><p class="MsoNormal">Looking at the Interface Hierarchy shows what implements those types, confirming that only Nurbs nodes are involved. This also clearly identifies why we shifted the interface involved.<u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">+- X3DParametricGeometryNode -+- NurbsCurve<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> +- NurbsSweptSurface<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> +- NurbsSwungSurface<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> |<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> +- X3DNurbsSurfaceGeometryNode -+- NurbsPatchSurface<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> +- NurbsTrimmedSurface<u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Dick points out that someday in (some wonderful) future we might allow other geometry nodes to get smoothly aligned next to Nurbs nodes. That will be nice – but we are OK for now.<u></u><u></u></p><div><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">all the best, Don<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">-- <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">X3D graphics, virtual worlds, Navy robotics https://</span> <span style="font-size:10pt;font-family:"Courier New""><a href="http://faculty.nps.edu/brutzman" target="_blank">faculty.nps.edu/brutzman</a><u></u><u></u></span></p></div><p class="MsoNormal"><u></u> <u></u></p><div><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><p class="MsoNormal"><b>From:</b> John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> <br><b>Sent:</b> Thursday, May 12, 2022 7:39 AM<br><b>To:</b> Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br><b>Cc:</b> X3D Public Mailing List (<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>) <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br><b>Subject:</b> Re: [x3d-public] Mantis 27.4.9 NurbSet - Change child geometry model to X3DParametricGeometryNode<u></u><u></u></p></div></div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">Understood, i am just trying to work through if there’s any parametric geometry which isn’t NURBS, and is thus now inclusive in this modified NurbsSet.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Thanks!<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">John <u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal">On Thu, May 12, 2022 at 8:58 AM Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<u></u><u></u></p></div><blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in"><div><div><p class="MsoNormal">Please be assured, no new semantics and no new functionality is being proposed. We are addressing a Mantis issue that noted the NurbsSet definition was unnecessarily restrictive. We adjusted the specification interface to match that inclusive rationale.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Changes to implementations are up to them. Since NurbsSet is a way for authors to communicate when various Nurbs nodes are coincident and potentially smoothable, it has no impact on functionality and might improve rendering appearance by enabling smoothed seams.<u></u><u></u></p><p class="MsoNormal"><br>Thanks for your review.<u></u><u></u></p></div></div><div><div><div><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">all the best, Don</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">-- </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a></span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">X3D graphics, virtual worlds, Navy robotics https://</span> <span style="font-size:10pt;font-family:"Courier New""><a href="http://faculty.nps.edu/brutzman" target="_blank">faculty.nps.edu/brutzman</a></span><u></u><u></u></p></div><p class="MsoNormal"> <u></u><u></u></p><div><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><p class="MsoNormal"><b>From:</b> John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> <br><b>Sent:</b> Wednesday, May 11, 2022 10:40 PM<br><b>To:</b> Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br><b>Cc:</b> X3D Public Mailing List (<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>) <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br><b>Subject:</b> Re: [x3d-public] Mantis 27.4.9 NurbSet - Change child geometry model to X3DParametricGeometryNode<u></u><u></u></p></div></div><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><div><div><p class="MsoNormal">Don, I'm a bit unsure of the new semantics for NurbsSet....it includes other parametric geometry nodes which aren't NURBS? <u></u><u></u></p><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">Would ParametricGeometrySet be a better name than NurbsSet, or a good addition to X3D4?<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">Is it counterintuitive to look for a "ParametricGeometrySet" inside NURBS sections?<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">How does this impact browser implementations?<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">I don't know if the standard includes parametric, implicit, etc. descriptions?<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">Are we planning on dropping X3DNurbsSurfaceGeometryNode in the future?<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">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.<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">I have no other issues that come to mind presently.<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">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 <span style="font-size:10pt;font-family:"Courier New";color:black;background:yellow">X3DParametricGeometryNode</span><u></u><u></u></p></div><div><p class="MsoNormal">and X3DNurbsSurfaceGeometryNode sub node types for geometry?<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">Thanks!<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">John<u></u><u></u></p></div></div><p class="MsoNormal"> <u></u><u></u></p><div><div><p class="MsoNormal">On Wed, May 11, 2022 at 8:06 PM Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<u></u><u></u></p></div><blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt"><div><div><p class="MsoNormal">NurbsSet should be inclusive about which nodes an author thinks can be rendered together as one smooth surface.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><ul type="disc"><li>Mantis 27.4.9 NurbSet - Change child geometry model to X3DParametricGeometryNode <u></u><u></u></li><li><a href="https://www.web3d.org/member-only/mantis/view.php?id=700" target="_blank">https://www.web3d.org/member-only/mantis/view.php?id=700</a><u></u><u></u></li></ul><p class="MsoNormal"> <u></u><u></u></p><ul type="disc"><li>X3D4 Architecture, NURBS component, 27.4.8 NurbsSet<u></u><u></u></li><li><a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/nurbs.html#NurbsSet" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/nurbs.html#NurbsSet</a><u></u><u></u></li></ul><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Since X3DParametricGeometryNode includes X3DNurbsSurfaceGeometryNode, changed all three NurbsSet geometry fields from X3DNurbsSurfaceGeometryNode to X3DParametricGeometryNode.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">NurbsSet : X3DChildNode, X3DBoundedObject {</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> MFNode [in] addGeometry [<span style="color:black;background:yellow">X3DParametricGeometryNode</span>]</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> MFNode [in] removeGeometry [<span style="color:black;background:yellow">X3DParametricGeometryNode</span>]</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> MFNode [in,out] geometry [] [<span style="color:black;background:yellow">X3DParametricGeometryNode</span>]</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> SFNode [in,out] metadata NULL [X3DMetadataObject]</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> SFFloat [in,out] tessellationScale 1.0 (0,∞)</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> SFVec3f [] bboxCenter 0 0 0 (-∞,∞)</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> SFVec3f [] bboxSize -1 -1 -1 [0,∞) or −1 −1 −1</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">}</span><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">This changes X3DUOM and possibly some implementations. Comments welcome.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">We current intend to accept this change as resolved once X3DUOM is updated.<u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New""> </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">all the best, Don</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">-- </span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a></span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</span><u></u><u></u></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">X3D graphics, virtual worlds, Navy robotics https://</span> <span style="font-size:10pt;font-family:"Courier New""><a href="http://faculty.nps.edu/brutzman" target="_blank">faculty.nps.edu/brutzman</a></span><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p></div></div><p class="MsoNormal">_______________________________________________<br>x3d-public mailing list<br><a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><u></u><u></u></p></blockquote></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div></div>
</blockquote></div>
</blockquote></div>