Clarification needed: why a separate format instead of an extension to glTF?

It's not clear from the docs why a separate file format is a good idea here.

I think it would have been perfectly viable to design a regular glTF extension that allows for composition of assets and addition of interactive behaviours (in fact, we're using vendor-specific extensions that way already). A separate file format seems to overcomplicate this, but would be great to read more about the reasoning for that.

Additionally, this imposes a weird restriction: glXF files can't be self-contained anymore since they can only reference other assets and not contain any buffers etc. Not sure why this would be desired; in most cases for last-mile delivery a self-contained file is a good thing, not a bad thing. It means there always must be multiple requests to even build the simplest of experiences.

Start by reviewing the project documentation that explains why glXF is separate from glTF and why glXF files reference external assets rather than containing buffers. Use the issue's questions and existing comment discussion to identify the agreed rationale; done means the documentation records that rationale and addresses self-contained delivery concerns.