Menu ▾ ▴

#51 -acousticProperties should be a JSON object, not a JSON array in X3D JSON

X3D4
closed
Don Brutzman
seems simple (1)
2026-02-22
2025-08-16
John W Carlson
No

https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/shape.html#Appearance

Appearance : X3DAppearanceNode {
** SFNode [in,out] acousticProperties NULL [AcousticProperties]**
[ snip ]
}

https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/AudioSpatialSound/AllAudioGraphNodesTest.json

snippet:

{ "Shape":
{
"-geometry":
{ "Box":
{
}
},
"-appearance":
{ "Appearance":
{
** "-acousticProperties":[**
{ "AcousticProperties":
{
"@description":"Testing of X3D4 nodes demonstrating W3C Audio API in progress",
"@diffuse":0.25,
"@refraction":0.5,
"@specular":1
}
}
],
"-material":
{ "Material":
{
}
}
}
}
}
}

      -acousticProperties should be an SFNode, according to the standard, a JSON object, not an array.

      Here's the acousticProperties in X3DUOM:

      <ConcreteNode name="Appearance">

[snip]
<field name="acousticProperties" **="" type="SFNode" accesstype="inputOutput" default="NULL" acceptablenodetypes="AcousticProperties" description="Single contained acousticProperties node that can specify additional acoustic attributes applied to associated surface geometry.">
<componentinfo name="Shape" level="5">
</componentinfo></field>

Related

Tickets: #51

Discussion

  • John W Carlson

    John W Carlson - 2025-08-16
    • summary: -acousticsProperties should be a JSON object, not a JSON array in X3D JSON --> -acousticProperties should be a JSON object, not a JSON array in X3D JSON
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -39,9 +39,9 @@
             }
           }

-          -acousticsProperties should be an SFNode, according to the standard, a JSON object, not an array.
+          -acousticProperties should be an SFNode, according to the standard, a JSON object, not an array.

-          Here&#39;s the acousticsProperty in X3DUOM:
+          Here&#39;s the acousticProperties in X3DUOM:

           &lt;ConcreteNode name=&#34;Appearance&#34;&gt;
     

  • John W Carlson

    John W Carlson - 2026-02-19
    • labels: --> seems simple
     

  • John W Carlson

    John W Carlson - 2026-02-19

    Can we get this looked at sooner than later? This is delaying acceptance testing of x3dvalidate.

     

  • Don Brutzman

    Don Brutzman - 2026-02-19

    Since X3DUOM is correctly defined, and specification is correctly defined, exactly what is the problem you are referring to? Processing by X3dToJson.xslt stylesheet?

     

    • John W Carlson

      John W Carlson - 2026-02-20

      Sure, -acousticProperties is an SFNode (JSON object), but X3dToJson.xslt
      treats it as an MFNode (JSON array).

      If you look at the online JSON object (I saved a snippet before for you to
      look at--pardon the bolding), you will see that it;'s an MFNode. Please
      remove the [] around the property value for the property name
      "-acousticProperties", such that the property value becomes an object, and
      not an array.

      What it should look like:

      { "Shape":
      {
      "-geometry":
      { "Box":
      {
      }
      },
      "-appearance":
      { "Appearance":
      {
      "-acousticProperties":
      { "AcousticProperties":
      {
      "@description":"Testing of X3D4 nodes demonstrating W3C Audio API in
      progress",
      "@diffuse":0.25,
      "@refraction":0.5,
      "@specular":1
      }
      },
      "-material":
      { "Material":
      {
      }
      }
      }
      }
      }
      }

      On Thu, Feb 19, 2026 at 10:54 AM Don Brutzman brutzman@users.sourceforge.net wrote:

      Since X3DUOM is correctly defined, and specification is correctly defined,
      exactly what is the problem you are referring to? Processing by
      X3dToJson.xslt stylesheet?

      [tickets:#51] https://sourceforge.net/p/x3d/tickets/51/
      -acousticProperties should be a JSON object, not a JSON array in X3D JSON

      Status: open
      Milestone: X3D4
      Labels: seems simple
      Created: Sat Aug 16, 2025 09:48 AM UTC by John W Carlson
      Last Updated: Thu Feb 19, 2026 01:34 PM UTC
      Owner: Don Brutzman

      https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/shape.html#Appearance

      Appearance : X3DAppearanceNode {
      ** SFNode [in,out] acousticProperties NULL [AcousticProperties]**
      [ snip ]
      }

      https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/AudioSpatialSound/AllAudioGraphNodesTest.json

      snippet:

      { "Shape":
      {
      "-geometry":
      { "Box":
      {
      }
      },
      "-appearance":
      { "Appearance":
      {
      ** "-acousticProperties":[**
      { "AcousticProperties":
      {
      "@description":"Testing of X3D4 nodes demonstrating W3C Audio API in
      progress",
      "@diffuse":0.25,
      "@refraction":0.5,
      "@specular":1
      }
      }
      ]      ,
      "-material":
      { "Material":
      {
      }
      }
      }
      }
      }
      }

        -acousticProperties should be an SFNode, according to the standard, a JSON object, not an array.

  Here's the acousticProperties in X3DUOM:

  <ConcreteNode name="Appearance">

      [snip]
      <field name="acousticProperties" **="" type="SFNode" accesstype="inputOutput" default="NULL" acceptablenodetypes="AcousticProperties" description="Single contained acousticProperties node that can specify additional acoustic attributes applied to associated surface geometry.">
      <componentinfo name="Shape" level="5">
      </componentinfo></field>

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/x3d/tickets/51/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Tickets: #51

      alternate

  • Don Brutzman

    Don Brutzman - 2026-02-22
    • status: open --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB