<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>TheHub - LinkXG</title><description>Field notes from the network: what we are learning about supply chain data.</description><link>https://www.linkxg.com/</link><language>en-gb</language><item><title>Expected data sets: define and track partner data in one place</title><link>https://www.linkxg.com/thehub/2026-06-expected-data-sets/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-06-expected-data-sets/</guid><description>Expected data sets let you define the exact data you need from supply chain partners and track fulfilment across every connection in one place.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Evaluating your suppliers&apos; data infrastructure</title><link>https://www.linkxg.com/thehub/2026-04-evaluating-supplier-data-infrastructure/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-04-evaluating-supplier-data-infrastructure/</guid><description>Procurement rarely evaluates the data infrastructure behind supplier information. Six questions surface what a weak supplier data setup actually costs.</description><pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Keeping supplier product data current</title><link>https://www.linkxg.com/thehub/2026-04-keeping-supplier-product-data-current/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-04-keeping-supplier-product-data-current/</guid><description>Supplier product data falls out of date as soon as a static document is sent. A maintained record read at the point of use keeps the data current.</description><pubDate>Fri, 17 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Structured supplier data and AI adoption in supply chains</title><link>https://www.linkxg.com/thehub/2026-04-structured-supplier-data-ai-adoption/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-04-structured-supplier-data-ai-adoption/</guid><description>AI adoption in supply chain operations is limited by the shape of supplier data. Four properties describe the structure a model can actually read.</description><pubDate>Thu, 16 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Verifiable supplier data on demand</title><link>https://www.linkxg.com/thehub/2026-04-verifiable-supplier-data-on-demand/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-04-verifiable-supplier-data-on-demand/</guid><description>Only 18% of organisations are very confident in supplier-reported data. The cause is the exchange shape, which changes when data is published and retrieved.</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Upstream data in electronics manufacturing supply chains</title><link>https://www.linkxg.com/thehub/2026-04-electronics-manufacturing-upstream-data/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-04-electronics-manufacturing-upstream-data/</guid><description>Electronics contract manufacturers run a separate traceability workflow for every OEM customer. Shared upstream data removes the re-collection cycle.</description><pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Seven principles of supply chain data sharing</title><link>https://www.linkxg.com/thehub/2026-03-supply-chain-data-principles/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-03-supply-chain-data-principles/</guid><description>Seven principles describe what supply chain data sharing demands, and why existing infrastructure falls short of them.</description><pubDate>Sun, 01 Mar 2026 00:00:00 GMT</pubDate></item><item><title>Why we built LinkXG</title><link>https://www.linkxg.com/thehub/2026-02-why-we-built-linkxg/</link><guid isPermaLink="true">https://www.linkxg.com/thehub/2026-02-why-we-built-linkxg/</guid><description>Supply chain data sharing degrades with every exchange. LinkXG is infrastructure that lets companies share product data once, with every trading partner.</description><pubDate>Tue, 10 Feb 2026 00:00:00 GMT</pubDate></item></channel></rss>