ifcx schema vs JSON-schema

ifcx schema definitions are very similar to JSON Schema but seem to differ in small but important ways. With the goal of IFC5 in mind to reuse existing best practices instead of redefining them, this surprised me.

There are probably very good reasons for these differences, but to me, it feels like it makes ifcx harder to adopt because it cannot be validated with out-of-the box validators without special schema mappings? Can anyone please explain this choice or point me in the right direction?

This would for example to directly reuse schema's like glTF:
https://github.com/KhronosGroup/glTF/blob/main/specification/2.0/schema/material.schema.json

@atomczak @tomvandig @aothms

>
> @janbrouwer post an issue or propose a PR, as this has already been merged.
>
> _Originally posted by @atomczak in https://github.com/buildingSMART/IFC5-development/issues/71#issuecomment-3028661899_
>