Prior-art comparison
The surveyed systems provide precedents for individual parts of authored interface interchange. This comparison records their relevance to NUIF’s proposed scope. It is not a product ranking or an exhaustive novelty claim. Each linked research record identifies the reviewed source and retrieval date.
| System and source record | Relevant mechanism | Boundary of the comparison |
|---|---|---|
| Penpot | Inspectable design documents and SVG mapping | A design-tool model does not by itself establish cross-runtime synchronization |
| OpenPencil | Programmable editor, Figma codec and automation interfaces | Editor capabilities and neutral specification governance are separate questions |
| Figma | Component and layout authoring semantics | Interoperability depends on the exposed vendor APIs and their versions |
| W3C UI Specification Schema Community Group | Proposed implementation-agnostic UI schema | The group closed in 2026; the cited record does not establish the cause |
| Open UI | Control anatomy, states and accessibility | The reviewed scope concerns web controls |
| SVG | Vector geometry and paint | NUIF component and authored-layout mappings require additional contracts |
| Lottie and Rive | Animation and state-machine runtimes | Runtime delivery and general authoring interchange have different requirements |
| DTCG | Design-token semantics | Tokens form one part of the proposed document model |
| OpenUSD | Layers, references and variants | UI composition requires a separately specified interpretation |
| glTF | Extension and capability declarations | The reviewed specification concerns runtime 3D assets |
| MaterialX | Typed renderer-independent graphs | Material graphs do not define UI document semantics |
| MLIR | Dialects and explicit lowering | Compiler infrastructure supplies a pattern, not a document interchange contract |
| CSS | Authored style and resolved formatting | Correspondence with non-web layout requires named profiles |
| IFC | Semantic interchange and domain profiles | NUIF has no measured adoption-cost comparison with this domain |
Repository interpretation
The architecture adopts established geometry, token and text specifications where their semantics match a declared profile. Composition, lowering, capability declarations and source correspondence require adaptation to UI editing. The cross-industry synthesis records those decisions individually.
The proposed contribution is the integration of authored and resolved state, stable semantic identity, opaque preservation, fidelity reporting and retentive source edits. Evidence for that integration comes from bounded experiments. Neither the number of surveyed systems nor the absence of an identical system in this comparison proves novelty, usefulness or adoption potential.