<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Kommentare für Agentic Business Solutions	</title>
	<atom:link href="https://sol4biz.at/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://sol4biz.at</link>
	<description>AI-enabled Business Solutions, IAM, API Management &#38; System Integration</description>
	<lastBuildDate>Thu, 08 Oct 2026 11:32:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		Kommentar zu TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn&#8217;t) von The Agent Tool Facade: How to Design the Layer Between AI Agents and Your Enterprise Systems - Pragmatic Business Solutions		</title>
		<link>https://sol4biz.at/tmf-open-apis-and-ai-agents/#comment-6</link>

		<dc:creator><![CDATA[The Agent Tool Facade: How to Design the Layer Between AI Agents and Your Enterprise Systems - Pragmatic Business Solutions]]></dc:creator>
		<pubDate>Thu, 08 Oct 2026 11:32:00 +0000</pubDate>
		<guid isPermaLink="false">https://sol4biz.at/?p=1430#comment-6</guid>

					<description><![CDATA[[&#8230;] my previous article on TMF Open APIs and AI agents I recommended putting a “curated layer” between the agent and your TMF Open APIs, and called it [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] my previous article on TMF Open APIs and AI agents I recommended putting a “curated layer” between the agent and your TMF Open APIs, and called it [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Kommentar zu TMF Open APIs &#8211; Pragmatic Order Lifecycle Using TMF622 and TMF641 von TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions		</title>
		<link>https://sol4biz.at/pragmatic-order-lifecycle-using-tmf622-and-tmf641/#comment-5</link>

		<dc:creator><![CDATA[TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 21:06:49 +0000</pubDate>
		<guid isPermaLink="false">https://sol4biz.at/?p=510#comment-5</guid>

					<description><![CDATA[[&#8230;] is not conservatism for its own sake. It is the same principle as in pragmatic order lifecycle design: there must be exactly one place that owns order [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] is not conservatism for its own sake. It is the same principle as in pragmatic order lifecycle design: there must be exactly one place that owns order [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Kommentar zu TMF OpenAPIs &#8211; Customer Order Management von TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions		</title>
		<link>https://sol4biz.at/tmf-openapis-customer-order-management/#comment-4</link>

		<dc:creator><![CDATA[TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 20:58:53 +0000</pubDate>
		<guid isPermaLink="false">https://sol4biz.at/?p=561#comment-4</guid>

					<description><![CDATA[[&#8230;] orders (TMF641) are not for agents at all in most landscapes. They belong to the orchestration between Customer Order Management and Service Activation, not to a conversational layer. Let COM decompose the product order into service orders as it does [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] orders (TMF641) are not for agents at all in most landscapes. They belong to the orchestration between Customer Order Management and Service Activation, not to a conversational layer. Let COM decompose the product order into service orders as it does [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Kommentar zu TMF Open APIs – Service Qualification von TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions		</title>
		<link>https://sol4biz.at/tmf-open-apis-service-qualification/#comment-3</link>

		<dc:creator><![CDATA[TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 20:57:16 +0000</pubDate>
		<guid isPermaLink="false">https://sol4biz.at/?p=742#comment-3</guid>

					<description><![CDATA[[&#8230;] Qualification APIs are in my experience the best first &#8222;active&#8220; use case for agents: [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Qualification APIs are in my experience the best first &#8222;active&#8220; use case for agents: [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Kommentar zu TMF Open APIs Without the Complexity Trap von TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions		</title>
		<link>https://sol4biz.at/tm-forum-open-apis-without-the-complexity-trap/#comment-2</link>

		<dc:creator><![CDATA[TMF Open APIs and AI Agents: Why Your BSS/OSS Landscape Is Already Agent-Ready (and Where It Isn’t) - Pragmatic Business Solutions]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 20:56:56 +0000</pubDate>
		<guid isPermaLink="false">https://sol4biz.at/?p=495#comment-2</guid>

					<description><![CDATA[[&#8230;] have argued before that TMF Open APIs are best used as pragmatic integration contracts, not as an architecture framework. That same property makes them good agent [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] have argued before that TMF Open APIs are best used as pragmatic integration contracts, not as an architecture framework. That same property makes them good agent [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
