<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/3f7bd9edc333439ca1217a86c6e22023&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/3f7bd9edc333439ca1217a86c6e22023-63236edcd0d35500.gif</thumbnail_url><duration>301.363</duration><title>Importing Schemas and Relations Across Graphs</title><description>This Loom tests importing a cross-space relationship in Roam when the custom node schema is only published in the source graph. The creator imports a claim into the destination graph to bring in the MapTest type, then notes the relation type is initially missing until a published relation in the source graph triggers it. After publishing a relation from the source graph and refreshing the MapTest node, the destination shows a provisional relation that resolves to the indirectly imported MapTest type. They then add another relation and confirm the destination graph reuses the constructed triple without creating another version.</description></oembed>