{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/5a4f6dda94754830a6eb3e86f31d63cf\" 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/5a4f6dda94754830a6eb3e86f31d63cf-0dc2ce6fd8e8b73f.gif","duration":85.881,"title":"Fixing DGCore Content Negotiation Errors","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."}