<?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/5a4f6dda94754830a6eb3e86f31d63cf&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/5a4f6dda94754830a6eb3e86f31d63cf-0dc2ce6fd8e8b73f.gif</thumbnail_url><duration>85.881</duration><title>Fixing DGCore Content Negotiation Errors</title><description>This Loom explains how schema content negotiation should work when requesting dgCore. The presenter reports that requesting dgCore directly currently returns a 406 Not Acceptable or sometimes a 404, and that the correct approach is to ask for the title using Turtle content negotiation. With curl, including an appropriate Accept header like text/turtle returns the actual Turtle, while requesting a different year results in a not acceptable response as expected. The goal is to ensure the server responds with the right status codes rather than a rewrite.</description></oembed>