{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/50d2f0c2f7f24c6189572f91030abbf0\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/50d2f0c2f7f24c6189572f91030abbf0-9bb2925b09b25a0c.gif","duration":72.398,"title":"Proposal for Cross App Schema Contract","description":"This Loom proposes a cross-app contract for Schemas, specifically how node schemas and cross-app relation types should be defined. The author creates a new base to ensure metadata tied to the literal content in the concept table is always available, and notes that making the same metadata available in the node is a separate PR. They describe a node schema with a label and a template, and a unique Obsidian cross-app relation type with a label and compliment. For triples, they explain that the Obsidian case uses a reference to the relation, while the Roam case differs, though the details are cut off in the transcript."}