<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Data-Quality on jamesm.blog</title>
    <link>https://jamesm.blog/tags/data-quality/</link>
    <description>Recent content in Data-Quality on jamesm.blog</description>
    <image>
      <title>jamesm.blog</title>
      <url>https://jamesm.blog/papermod-cover.png</url>
      <link>https://jamesm.blog/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 04 Jun 2026 20:19:00 +0100</lastBuildDate>
    <atom:link href="https://jamesm.blog/tags/data-quality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ethical Data Use (EDU) in 2026: What Data Engineers Actually Need to Get Right</title>
      <link>https://jamesm.blog/data-engineering/ethical-data-use-2026/</link>
      <pubDate>Thu, 04 Jun 2026 20:19:00 +0100</pubDate>
      <guid>https://jamesm.blog/data-engineering/ethical-data-use-2026/</guid>
      <description>Ethical data use has moved from a policy memo to an engineering problem. This is a grounded, practitioner&amp;#39;s look at what data engineers actually need to get right in 2026 - consent and purpose limitation as schema-level concerns, the right to be forgotten meeting the immutable lakehouse, training-data provenance, privacy-preserving techniques, dataset documentation, and the regulatory backdrop that now has real deadlines.</description>
    </item>
  </channel>
</rss>
