[x3d-public] MFString type in JSON. Both string and array?

[John Carlson]

I, too, like a JSON array for MFString.  That's how it is currently, and
I'm reluctant to make changes.

On Tue, Oct 14, 2025 at 8:24 PM Vincent Marchetti via x3d-public <
x3d-public at web3d.org> wrote:

> I disagree with including  "string" as an allowed type in this case.
>
> I think that a X3D field which is declared as type MFString in the X3D
> Spec should be encoded as a json array, each item of which (if it is
> non-empty) is a string under the rules for json formatted data.
>
> > On Oct 12, 2025, at 8:26 PM, John Carlson via x3d-public <
> x3d-public at web3d.org> wrote:
> >
> > I just found out that the type of an MFString in JSON could be either an
> array or a string—the value of “type” in JSON schema could be an array,
> like:
> >
> >  “type” : [ “string”, “array” ]
> >
> > I am open making this a reality in X3D JSON schema, but what do people
> think?
> >
> > John
> > _______________________________________________
> > x3d-public mailing list
> > x3d-public at web3d.org
> > http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20251015/39ebd35d/attachment.html>