<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 16, 2022, at 4:30 PM, John Carlson <<a href="mailto:yottzumm@gmail.com" class="">yottzumm@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><strong class=""><a href="https://sourceforge.net/p/x3d/tickets/10/" target="_blank" class="">[tickets:#10]</a> JSON schema errors that start to make sense. Need X3dToJson.xslt updates to create MFString arrays.</strong><br class=""></div><div class=""><p class=""><b class="">Discussion leading towards enlightenment whether MFStrings should be arrays or strings in JSON (or both?).</b></p><p class="">Vince, I added you here because I thought you would want to advocate for a single string MFString being a string and not an arrray.</p><div class=""><br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div>John</div><div><br class=""></div><div>Thank you for including me, but I would actually advocate for the opposite, that any value typed as MFString be encoded as an MFString of 0, 1, or N>1 elements, by whatever syntax is appropriate for that encoding.</div><div><br class=""></div><div>Vince</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class=""><p class="">John</p></div> <div class="">
<div class="">
</div>
</div></div></div>
</div></blockquote></div><br class=""></body></html>