<?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 zu: TMF OpenAPIs &#8211; Customer Order Management	</title>
	<atom:link href="https://sol4biz.at/tmf-openapis-customer-order-management/feed/" rel="self" type="application/rss+xml" />
	<link>https://sol4biz.at/tmf-openapis-customer-order-management/</link>
	<description>AI-enabled Business Solutions, IAM, API Management &#38; System Integration</description>
	<lastBuildDate>Sat, 03 Oct 2026 20:58:53 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		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>
	</channel>
</rss>
