<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenUSD Foundations and Workflows Certification on Matias Codesal</title>
    <link>https://matiascodesal.com/series/openusd-foundations-and-workflows-certification/</link>
    <description>Recent content in OpenUSD Foundations and Workflows Certification 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/series/openusd-foundations-and-workflows-certification/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>
    
    <item>
      <title>Speaking OpenUSD: Stages, Layers, Prims, and the Words Around Them</title>
      <link>https://matiascodesal.com/posts/speaking-openusd-stages-layers-prims/</link>
      <pubDate>Tue, 03 Nov 2026 08:00:00 -0500</pubDate>
      
      <guid>https://matiascodesal.com/posts/speaking-openusd-stages-layers-prims/</guid>
      <description>Introduction I&amp;rsquo;ve been in far more meetings than I care to admit where I was talking about a USD assembly thinking that everyone was following along, but in reality they had a different understanding of what an assembly was because of their industry background or technologies they&amp;rsquo;ve used. To a mechanical engineer, an assembly is a collection of parts joined together. In OpenUSD, it&amp;rsquo;s a specific kind of group with its own rules.</description>
    </item>
    
    <item>
      <title>The Case for OpenUSD: What It Solves for Your Teams</title>
      <link>https://matiascodesal.com/posts/case-for-openusd-what-it-solves/</link>
      <pubDate>Tue, 20 Oct 2026 08:00:00 -0700</pubDate>
      
      <guid>https://matiascodesal.com/posts/case-for-openusd-what-it-solves/</guid>
      <description>I remember sitting in my cubicle at DreamWorks Animation in 2016 when Pixar open-sourced Universal Scene Description. I was poring over the documentation website trying to understand what value OpenUSD could provide for my team. We had recently started using Alembic for interchange, and we were pleased with the results. DreamWorks also already had a proprietary scene description with a concept similar to OpenUSD layers, though it was starting to show its age.</description>
    </item>
    
  </channel>
</rss>
