[x3d-public] [create3000/x3d-tidy] Possible issue with moving IS to bottom of Transform children. (Issue #14)

[John Carlson]

Understood, but I am translating JSON to XML/DOM with X3DJSONLD, and then I
am validating the XML/DOM with XML Schema, which does have extrinsic
order.  Since JSON schema may never be standardized, we may be dependent on
XML Schema for JSON validation.

I fully realize that my X3DJSONLD should “do the right thing” and reorder
the children, but also realize that my X3DJSONLD also has an installed base.

We don’t want to “break the web” if we don’t have to.

I realize that x3d-tidy already repairs these things when converting JSON
back to XML, and I will likely look at the source to see what has been
done, I am kind of curious at this point.  I will probably have to examine
XML Schema and X3DUOM to find these specialized orderings.  I am pretty
sure they are not in X3DUOM, since I’ve had a lot of experience with X3DUOM.

The solution is probably to fix both X3DJSOLD and x3d-tidy.

cc:ed to x3d-public as FYI

John

On Fri, Dec 22, 2023 at 5:23 PM Holger Seelig <notifications at github.com>
wrote:

> As it turns out, there is not an intrinsic order of properties in a JSON
> schema object.
>
> See also
> https://stackoverflow.com/questions/31691247/how-can-i-define-the-sequence-of-properties-in-json-schema/31693656#31693656
> .
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/create3000/x3d-tidy/issues/14#issuecomment-1868126861>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAFMJ5427C3NJ2BHBEQJ5XDYKYJANAVCNFSM6AAAAABAVIGC6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGEZDMOBWGE>
> .
> You are receiving this because you authored the thread.Message ID:
> <create3000/x3d-tidy/issues/14/1868126861 at github.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231222/86fe1be2/attachment.html>