<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">This update refers to item 4.f of the agenda and minutes for the Jan 31 X3D WG meeting, available from x3d-public at <a href="http://web3d.org/pipermail/x3d-public_web3d.org/2020-January/011744.html" class="">http://web3d.org/pipermail/x3d-public_web3d.org/2020-January/011744.html</a><div class=""><br class=""></div><div class="">Recent email to X3D WG list ( <a href="http://web3d.org/mailman/private/x3d_web3d.org/2020-February/007810.html" class="">http://web3d.org/mailman/private/x3d_web3d.org/2020-February/007810.html</a> ) proposes setting default value of xml attribute 'containerField' to 'metadata' for the MetadataSet node only, and set default value of 'containerField' to 'value' for the other X3D Metadata nodes. This would reduce need for explicit values of the attribute in X3D files for the common use case of metadata organized into data records grouped into MetadataSet nodes.</div><div class=""><br class=""></div><div class="">Reported by Vince Marchetti</div><div class=""><br class=""><div class=""><br class=""></div><div class=""><br class=""></div></div></body></html>