{"id":3249,"date":"2026-05-12T22:37:02","date_gmt":"2026-05-12T14:37:02","guid":{"rendered":"https:\/\/www.dpriver.com\/blog\/?p=3249"},"modified":"2026-05-12T22:37:03","modified_gmt":"2026-05-12T14:37:03","slug":"why-ai-alone-cannot-replace-accurate-data-lineage-analysis","status":"publish","type":"post","link":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/","title":{"rendered":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis"},"content":{"rendered":"\n<p>In recent years, AI has rapidly transformed the data industry. From SQL generation to metadata summarization and natural language querying, Large Language Models (LLMs) are becoming deeply integrated into modern data platforms. As a result, many organizations are beginning to ask an important question:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote\">\n<p>\u201cCan AI fully replace traditional SQL parsing and data lineage analysis?\u201d<\/p>\n<\/blockquote>\n\n\n\n<p>At first glance, the answer may appear to be \u201cyes.\u201d AI models can already explain SQL, summarize transformations, and even generate lineage-like descriptions. However, when it comes to <strong>enterprise-grade data lineage analysis<\/strong>, relying solely on AI introduces serious technical limitations and risks.<\/p>\n\n\n\n<p>This article explains why accurate data lineage analysis still requires deterministic SQL parsing technologies like <strong>SQLFlow<\/strong>, and why AI should be treated as an enhancement layer\u2014not the core lineage engine.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">The Fundamental Problem: AI Is Probabilistic, Lineage Must Be Deterministic<\/h4>\n\n\n\n<p>Data lineage is not a \u201cbest guess\u201d problem.<\/p>\n\n\n\n<p>In enterprise environments, lineage is used for:<\/p>\n\n\n\n<ul>\n<li>Regulatory compliance<\/li>\n\n\n\n<li>Impact analysis<\/li>\n\n\n\n<li>Data governance<\/li>\n\n\n\n<li>Root cause investigation<\/li>\n\n\n\n<li>Audit trails<\/li>\n\n\n\n<li>Migration validation<\/li>\n\n\n\n<li>Security analysis<\/li>\n<\/ul>\n\n\n\n<p>In these scenarios, even a small mistake can create significant operational or legal risks.<\/p>\n\n\n\n<p>AI models are fundamentally probabilistic systems:<\/p>\n\n\n\n<ul>\n<li>They predict likely outputs<\/li>\n\n\n\n<li>They infer intent<\/li>\n\n\n\n<li>They approximate relationships<\/li>\n<\/ul>\n\n\n\n<p>But lineage requires deterministic precision:<\/p>\n\n\n\n<ul>\n<li>Exact source-to-target mappings<\/li>\n\n\n\n<li>Precise column dependencies<\/li>\n\n\n\n<li>Reliable transformation tracing<\/li>\n\n\n\n<li>Guaranteed reproducibility<\/li>\n<\/ul>\n\n\n\n<p>This difference is critical.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Example : Nested CTEs and Alias Resolution<\/h4>\n\n\n\n<p>Consider the following SQL:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>WITH sales_cte AS (\n    SELECT customer_id, amount\n    FROM sales\n),\nagg_cte AS (\n    SELECT customer_id, SUM(amount) AS total_sales\n    FROM sales_cte\n    GROUP BY customer_id\n)\nSELECT *\nFROM agg_cte;<\/code><\/pre>\n\n\n\n<p>A human can understand this easily.<\/p>\n\n\n\n<p>An AI model may also summarize it correctly most of the time.<\/p>\n\n\n\n<p>But enterprise lineage systems must answer questions such as:<\/p>\n\n\n\n<ul>\n<li>Does <code>total_sales<\/code> originate from <code>sales.amount<\/code>?<\/li>\n\n\n\n<li>Is <code>customer_id<\/code> preserved through all transformations?<\/li>\n\n\n\n<li>What happens if <code>sales.amount<\/code> changes datatype?<\/li>\n\n\n\n<li>Which downstream reports are impacted?<\/li>\n<\/ul>\n\n\n\n<p>These questions require:<\/p>\n\n\n\n<ul>\n<li>Namespace resolution<\/li>\n\n\n\n<li>CTE scope tracking<\/li>\n\n\n\n<li>Semantic dependency analysis<\/li>\n\n\n\n<li>Deterministic column tracing<\/li>\n<\/ul>\n\n\n\n<p>This is where traditional parser-based engines like SQLFlow outperform AI.<\/p>\n\n\n\n<p>SQLFlow builds an Abstract Syntax Tree (AST), resolves aliases, tracks namespaces, and computes exact lineage relationships step-by-step.<\/p>\n\n\n\n<p>AI does not truly execute semantic resolution\u2014it predicts likely meanings.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Hallucinations Are Acceptable for Chatbots \u2014 Not for Governance<\/h4>\n\n\n\n<p>One of the biggest hidden risks of AI-generated lineage is hallucination.<\/p>\n\n\n\n<p>An LLM may:<\/p>\n\n\n\n<ul>\n<li>Invent nonexistent dependencies<\/li>\n\n\n\n<li>Miss hidden transformations<\/li>\n\n\n\n<li>Misinterpret aliases<\/li>\n\n\n\n<li>Infer relationships that do not exist<\/li>\n<\/ul>\n\n\n\n<p>For casual analytics assistance, this may be acceptable.<\/p>\n\n\n\n<p>For governance systems, it is dangerous.<\/p>\n\n\n\n<p>Imagine:<\/p>\n\n\n\n<ul>\n<li>Incorrect compliance reporting<\/li>\n\n\n\n<li>False impact analysis<\/li>\n\n\n\n<li>Missing PII tracing<\/li>\n\n\n\n<li>Incomplete audit lineage<\/li>\n<\/ul>\n\n\n\n<p>These are not minor UX issues\u2014they are enterprise risks.<\/p>\n\n\n\n<p>Deterministic lineage systems exist precisely to eliminate ambiguity.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">AI Still Has Massive Value in Data Lineage<\/h4>\n\n\n\n<p>This does not mean AI is useless.<\/p>\n\n\n\n<p>In fact, AI can dramatically improve lineage workflows when combined with deterministic engines.<\/p>\n\n\n\n<p>For example, AI is excellent at:<\/p>\n\n\n\n<ul>\n<li>Natural language interaction<\/li>\n\n\n\n<li>Lineage summarization<\/li>\n\n\n\n<li>Root cause explanation<\/li>\n\n\n\n<li>Intelligent search<\/li>\n\n\n\n<li>Documentation generation<\/li>\n\n\n\n<li>Metadata enrichment<\/li>\n\n\n\n<li>User assistance<\/li>\n<\/ul>\n\n\n\n<p>This is exactly why modern systems should combine:<\/p>\n\n\n\n<ul>\n<li>Deterministic parsing engines (like SQLFlow)<\/li>\n\n\n\n<li>AI-powered interaction layers<\/li>\n<\/ul>\n\n\n\n<p>Instead of replacing SQL parsers, AI should sit on top of them.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">The Future: AI + Deterministic Parsing<\/h4>\n\n\n\n<p>The future of data lineage is not \u201cAI versus parsers.\u201d<\/p>\n\n\n\n<p>It is:<\/p>\n\n\n\n<ul>\n<li>AI for usability<\/li>\n\n\n\n<li>Parsers for correctness<\/li>\n<\/ul>\n\n\n\n<p>At SQLFlow, this is the direction we are actively building toward.<\/p>\n\n\n\n<p>Our upcoming SQLFlow Copilot combines:<\/p>\n\n\n\n<ul>\n<li>Natural language interaction<\/li>\n\n\n\n<li>Intelligent lineage exploration<\/li>\n\n\n\n<li>AI-assisted troubleshooting<\/li>\n<\/ul>\n\n\n\n<p>while still relying on SQLFlow\u2019s deterministic parsing and semantic resolution engine underneath.<\/p>\n\n\n\n<p>This hybrid architecture delivers both:<\/p>\n\n\n\n<ul>\n<li>Enterprise-grade accuracy<\/li>\n\n\n\n<li>Modern AI-driven usability<\/li>\n<\/ul>\n\n\n\n<p>without sacrificing reliability.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h4 class=\"wp-block-heading\">Final Thoughts<\/h4>\n\n\n\n<p>AI is transforming the data industry, but data lineage remains one of the domains where precision matters more than approximation.<\/p>\n\n\n\n<p>When organizations depend on lineage for governance, compliance, and operational decision-making, deterministic parsing engines are still essential.<\/p>\n\n\n\n<p>AI can enhance lineage systems.<br>AI can simplify lineage exploration.<br>AI can improve user experience.<\/p>\n\n\n\n<p>But AI alone cannot reliably replace accurate SQL parsing and semantic lineage analysis.<\/p>\n\n\n\n<p>That is why enterprise-grade platforms like SQLFlow continue to rely on deterministic SQL analysis as the foundation of trustworthy data lineage.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In recent years, AI has rapidly transformed the data industry. From SQL generation to metadata summarization and natural language querying, Large Language Models (LLMs) are becoming deeply integrated into modern data platforms. As a result, many organizations are beginning to ask an important question: \u201cCan AI fully replace traditional SQL parsing and data lineage analysis?\u201d At first glance, the answer may appear to be \u201cyes.\u201d AI models can already explain SQL, summarize transformations, and even generate lineage-like descriptions. However, when it comes to enterprise-grade data lineage analysis, relying solely on AI introduces serious technical limitations and risks. This article explains\u2026<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":5}},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v19.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Why AI Alone Cannot Replace Accurate Data Lineage Analysis<\/title>\n<meta name=\"description\" content=\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\" \/>\n<meta property=\"og:description\" content=\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\" \/>\n<meta property=\"og:site_name\" content=\"SQL and Data Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-12T14:37:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-12T14:37:03+00:00\" \/>\n<meta name=\"author\" content=\"leo gu\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"leo gu\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/#organization\",\"name\":\"SQL and Data Blog\",\"url\":\"https:\/\/www.dpriver.com\/blog\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.dpriver.com\/blog\/wp-content\/uploads\/2022\/07\/sqlpp-character.png\",\"contentUrl\":\"https:\/\/www.dpriver.com\/blog\/wp-content\/uploads\/2022\/07\/sqlpp-character.png\",\"width\":251,\"height\":72,\"caption\":\"SQL and Data Blog\"},\"image\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/#website\",\"url\":\"https:\/\/www.dpriver.com\/blog\/\",\"name\":\"SQL and Data Blog\",\"description\":\"SQL related blog for database professional\",\"publisher\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dpriver.com\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\",\"url\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\",\"name\":\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\",\"isPartOf\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/#website\"},\"datePublished\":\"2026-05-12T14:37:02+00:00\",\"dateModified\":\"2026-05-12T14:37:03+00:00\",\"description\":\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.dpriver.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\"},\"author\":{\"name\":\"leo gu\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/#\/schema\/person\/9e80d249b6da4e572bd8590b0789bc14\"},\"headline\":\"Why AI Alone Cannot Replace Accurate Data Lineage Analysis\",\"datePublished\":\"2026-05-12T14:37:02+00:00\",\"dateModified\":\"2026-05-12T14:37:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/\"},\"wordCount\":654,\"publisher\":{\"@id\":\"https:\/\/www.dpriver.com\/blog\/#organization\"},\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/#\/schema\/person\/9e80d249b6da4e572bd8590b0789bc14\",\"name\":\"leo gu\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dpriver.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/24976e2e4ca7dd476652bb26bd09392b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/24976e2e4ca7dd476652bb26bd09392b?s=96&d=mm&r=g\",\"caption\":\"leo gu\"},\"url\":\"https:\/\/www.dpriver.com\/blog\/author\/guyuanhao\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","description":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/","og_locale":"en_US","og_type":"article","og_title":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","og_description":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","og_url":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/","og_site_name":"SQL and Data Blog","article_published_time":"2026-05-12T14:37:02+00:00","article_modified_time":"2026-05-12T14:37:03+00:00","author":"leo gu","twitter_card":"summary_large_image","twitter_misc":{"Written by":"leo gu","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Organization","@id":"https:\/\/www.dpriver.com\/blog\/#organization","name":"SQL and Data Blog","url":"https:\/\/www.dpriver.com\/blog\/","sameAs":[],"logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dpriver.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dpriver.com\/blog\/wp-content\/uploads\/2022\/07\/sqlpp-character.png","contentUrl":"https:\/\/www.dpriver.com\/blog\/wp-content\/uploads\/2022\/07\/sqlpp-character.png","width":251,"height":72,"caption":"SQL and Data Blog"},"image":{"@id":"https:\/\/www.dpriver.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"WebSite","@id":"https:\/\/www.dpriver.com\/blog\/#website","url":"https:\/\/www.dpriver.com\/blog\/","name":"SQL and Data Blog","description":"SQL related blog for database professional","publisher":{"@id":"https:\/\/www.dpriver.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dpriver.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/","url":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/","name":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","isPartOf":{"@id":"https:\/\/www.dpriver.com\/blog\/#website"},"datePublished":"2026-05-12T14:37:02+00:00","dateModified":"2026-05-12T14:37:03+00:00","description":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","breadcrumb":{"@id":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dpriver.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis"}]},{"@type":"Article","@id":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/#article","isPartOf":{"@id":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/"},"author":{"name":"leo gu","@id":"https:\/\/www.dpriver.com\/blog\/#\/schema\/person\/9e80d249b6da4e572bd8590b0789bc14"},"headline":"Why AI Alone Cannot Replace Accurate Data Lineage Analysis","datePublished":"2026-05-12T14:37:02+00:00","dateModified":"2026-05-12T14:37:03+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dpriver.com\/blog\/why-ai-alone-cannot-replace-accurate-data-lineage-analysis\/"},"wordCount":654,"publisher":{"@id":"https:\/\/www.dpriver.com\/blog\/#organization"},"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dpriver.com\/blog\/#\/schema\/person\/9e80d249b6da4e572bd8590b0789bc14","name":"leo gu","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dpriver.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/24976e2e4ca7dd476652bb26bd09392b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/24976e2e4ca7dd476652bb26bd09392b?s=96&d=mm&r=g","caption":"leo gu"},"url":"https:\/\/www.dpriver.com\/blog\/author\/guyuanhao\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/posts\/3249"}],"collection":[{"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/comments?post=3249"}],"version-history":[{"count":1,"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/posts\/3249\/revisions"}],"predecessor-version":[{"id":3250,"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/posts\/3249\/revisions\/3250"}],"wp:attachment":[{"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/media?parent=3249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/categories?post=3249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dpriver.com\/blog\/wp-json\/wp\/v2\/tags?post=3249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}