- Rating
- 1
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper studies interoperability failures in serialized 3D Gaussian Splatting assets. Its central observation is that serialized Gaussian parameters do not by themselves uniquely determine a rendered scene: heterogeneous consumers may complete the representation using different assumptions about schema, record extent, rotations, coordinate systems, radiance/color conventions, and resource commitments. The paper formalizes this as consumer-completed semantics and distinguishes bounded admission from semantic portability. It proposes root-adjudicated differential semantics for reducing cross-implementation disagreements to causally validated mechanisms.
Critical strengths
- The paper is unusually careful about distinguishing disagreement from a causal mechanism. Starting from 582 provisional signatures but retaining only four mechanisms after invariant reduction, source localization, stable replay, and causal analysis avoids the common failure mode of equating parser discrepancies with independent bugs.
- The contract connects safety and semantics rather than treating them independently. Requiring structural/extent proof before size-dependent allocation and then imposing a canonical typed representation provides a coherent boundary between untrusted serialized assets and downstream rendering.
- The paper includes both visual and resource consequences, rather than demonstrating only acceptance/rejection differences between parsers.
Critical weaknesses
- The formal noninterference result depends on a strong contract-conformance assumption. Proposition 1 states that if a deterministic downstream adapter factors its asset-dependent behavior entirely through the canonical handoff, then two encodings mapped to the same BGIR cannot produce different observations. This is correct, but the central guarantee follows strongly from the assumption that the downstream consumer no longer has any source-byte-dependent behavior. I therefore view the proposition primarily as an interface-level guarantee rather than a proof that heterogeneous real-world pipelines are automatically semantically portable. The practically difficult question is how conformance/non-bypassability is verified for complex importers, plugins, or engines.
- External validity is limited by the small source-native public corpus. The headline compatibility number of 7,998/8,000 is based on the sealed generated corpus. The source-native public corpus contains only fourteen files from six scenes and four captured objects, while some additional routes are correlated conversions of those assets. This is sufficient to demonstrate concrete mechanisms, but less convincing as evidence that the canonical profile captures the diversity of the broader deployed 3DGS ecosystem.
- Preventing all four discovered mechanisms is not equivalent to completeness of the semantic profile. The paper convincingly handles the four adjudicated mechanisms in the evaluated system surface. However, candidate generation, selected formats, revisions, and the chosen semantic invariants define the search space. The authors appropriately acknowledge that the empirical conclusions are limited to the pinned formats, implementations, revisions, and assets.
Questions for authors
How can one practically verify that a real downstream consumer is contract-conforming and cannot reintroduce source-byte authority through metadata, plugins, cached state, or extension-specific code?
How representative is the 8,000-asset generated test corpus of source-native assets in practice? Could the authors clarify which compatibility conclusions they believe generalize beyond this generated distribution?
Is the intended claim that SplatContract eliminates the four observed/adjudicated mechanisms, or that the current semantic profile is complete with respect to portability failures? I believe the former is well supported, while the latter would require substantially stronger evidence.