<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>openusd composition on Matias Codesal</title>
    <link>https://matiascodesal.com/tags/openusd-composition/</link>
    <description>Recent content in openusd composition on Matias Codesal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Matias Codesal</copyright>
    <lastBuildDate>Wed, 11 Nov 2026 01:00:00 -0500</lastBuildDate><atom:link href="https://matiascodesal.com/tags/openusd-composition/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LIVERPS Composition Arcs, Prioritized: Master These 4 First</title>
      <link>https://matiascodesal.com/posts/liverps-composition-arcs-prioritized/</link>
      <pubDate>Wed, 11 Nov 2026 01:00:00 -0500</pubDate>
      
      <guid>https://matiascodesal.com/posts/liverps-composition-arcs-prioritized/</guid>
      <description>Introduction Any team that works in parallel has to decide what happens when two people edit the same document. Software teams use Git. Everyone works freely and conflicts get handled when the work is merged. Even a shared Word doc follows the same pattern. You either break the work into pieces that don&amp;rsquo;t overlap, or someone reconciles the edits at the end.
OpenUSD takes a different approach: you decide all of that up front.</description>
    </item>
    
  </channel>
</rss>
