[x3d-public] [x3d:tickets] #10 JSON schema errors that start to make sense. Need X3dToJson.xslt updates to create MFString arrays.

[John Carlson]

That’s basically the whole discussion, Vince.   What types do we use in
JSON for MF fields?  Particularly MFStrings.   We have two approaches, one
we use for url field and one we use for Navigation.type field.   You may
look at many online examples .  I’m hoping we can clearly express this in
the JSON encoding online materials.   Right now, our documents diverge,
possibly within a document.   We need to clearly describe this divergence,
if we choose to take that route.

There seems to be some confusion when I say string?

John

On Sun, Jan 16, 2022 at 6:19 PM vmarchetti at kshell.com <vmarchetti at kshell.com>
wrote:

>
>
> On Jan 16, 2022, at 4:30 PM, John Carlson <yottzumm at gmail.com> wrote:
>
> *[tickets:#10] <https://sourceforge.net/p/x3d/tickets/10/> JSON schema
> errors that start to make sense. Need X3dToJson.xslt updates to create
> MFString arrays.*
>
> *Discussion leading towards enlightenment whether MFStrings should be
> arrays or strings in JSON (or both?).*
>
> 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.
>
>
> John
>
> 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.
>
> Vince
>
>
> John
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220116/72c592aa/attachment.html>