<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Hello Don,</div><div><br></div><div>The use of metadata is in my opinion very straightforward and your example is almost like I would do it, except I would use MetadataDouble for number values. Your example would then rather look like this:</div><div><br></div><div><Shape bboxDisplay='true'></div><div> <MetadataSet name='extension'></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><MetadataDouble name='bboxColor' value='0.7 0.8 0.9'/></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">MetadataDouble</span> name='bboxMargin' value='0.1' /></div><div> </MetadataSet></div><div> <Sphere/></div><div></Shape></div><div><br></div><div>With the different Metadata* nodes, every field can be type save represented.</div><div><br></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">There is already a good working concept there to access these values. </span></div><div><br></div><div>
<div>Holger Seelig</div><div>Leipzig, Germany</div><div>holger.seelig@yahoo.de</div><div><br></div><br class="Apple-interchange-newline">
</div>
<div><br><blockquote type="cite"><div>Am 01.04.2023 um 21:57 schrieb Brutzman, Donald (Don) (CIV) <brutzman@nps.edu>:</div><br class="Apple-interchange-newline"><div><div>Thanks for continuing news about this excellent progress.<br><br>Am thinking we might all agree to regularize addition of nonstandard fields in a way that still passes content validation.<br><br>For example, non-standard experimental example<br><br><Shape bboxDisplay='true' bboxColor='0.7 0.8 0.9' bboxMargin='0.1' ><br> <Sphere/><br></Shape><br><br>Might be equivalently and validly expressed as<br><br><Shape bboxDisplay='true'><br> <MetadataSet name='extension'><br><span class="Apple-tab-span" style="white-space:pre"> </span><MetadataString name='bboxColor' value='0.7 0.8 0.9'/><br><span class="Apple-tab-span" style="white-space:pre"> </span><MetadataString name='bboxMargin' value='0.1' /><br> </MetadataSet><br> <Sphere/><br></Shape><br><br>A little more verbose perhaps... However, note that not only is model content validatable, but metadata content might also be validated if we build a metadata vocabulary that lists experimental field names, types and default values. That way common extensions might be more sharable and model content remains confirmably correct.<br><br>Seems like a useful good practice that isn't complex, so we could easily build <MetadataSet name='extension'> capabilities into our browser parsers and authoring tools.<br><br>The X in X3D is Extensible... looking forward to continued innovation and practice/progress together.<br><br>v/r Don<br><br><br>-----Original Message-----<br>From: Andreas Plesch <andreasplesch@gmail.com> <br>Sent: Saturday, April 1, 2023 6:43 AM<br>To: X3D <x3d-public@web3d.org><br>Cc: x3dom mlist <x3dom-users@lists.sourceforge.net><br>Subject: Re: [x3dom-users] [x3d-public] bboxDisplay considerations<br><br>The bboxDisplay field is now available for bounded objects (grouping nodes and shapes) in the dev. version of x3dom.<br><br>The color of the displayed bounding box can be customized with the non-standard bboxColor field, and the size expanded with the bboxMargin field.<br><br>Enjoy ! Andreas<br><br>On Thu, Mar 30, 2023 at 2:19 PM Andreas Plesch <andreasplesch@gmail.com> wrote:<br><blockquote type="cite"><br>I think it will be very useful to allow different colors for different <br>sets of bounding boxes. Here are the rotating cubes with two sets of <br>bounding boxes. The yellow ones react to a TouchSensor, the orange <br>ones do not:<br>[...]<br></blockquote></div></div></blockquote></div><br></body></html>