<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Challenges in SLA Translation</title>
	<atom:link href="http://sla-at-soi.eu/2009/12/challenges-in-sla-translation/feed/" rel="self" type="application/rss+xml" />
	<link>http://sla-at-soi.eu/2009/12/challenges-in-sla-translation/?utm_source=subscriber&amp;utm_medium=rss&amp;utm_campaign=rss</link>
	<description>Empowering the service industry with SLA-aware infrastructures</description>
	<lastBuildDate>Fri, 02 Jul 2010 10:00:26 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Wolfgang Theilmann</title>
		<link>http://sla-at-soi.eu/2009/12/challenges-in-sla-translation/comment-page-1/#comment-700</link>
		<dc:creator>Wolfgang Theilmann</dc:creator>
		<pubDate>Tue, 22 Dec 2009 16:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://sla-at-soi.eu/?p=829#comment-700</guid>
		<description>Dear Nick,
There is certainly a hierarchy... the one we display here is taken from OMG and its Model-Driven Architecture. For them the process layer is clearly on top.
On the other hand you could also give an even more service-oriened view on all these layers by considering that all or many of them expose their functionality as service and are managed accordingly.
Causality is definitly an important issue, which we subsumed so far in the model integration aspect.
Best regards, Wolfgang</description>
		<content:encoded><![CDATA[<p>Dear Nick,<br />
There is certainly a hierarchy&#8230; the one we display here is taken from OMG and its Model-Driven Architecture. For them the process layer is clearly on top.<br />
On the other hand you could also give an even more service-oriened view on all these layers by considering that all or many of them expose their functionality as service and are managed accordingly.<br />
Causality is definitly an important issue, which we subsumed so far in the model integration aspect.<br />
Best regards, Wolfgang</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Overwater</title>
		<link>http://sla-at-soi.eu/2009/12/challenges-in-sla-translation/comment-page-1/#comment-690</link>
		<dc:creator>Nick Overwater</dc:creator>
		<pubDate>Mon, 21 Dec 2009 21:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://sla-at-soi.eu/?p=829#comment-690</guid>
		<description>Good evening,
Is there some form of hierarchy between the layers? If so why is service not on top?
What I could not find in the challenges bullet list was the configuration of a transformation table in which causality between the layers is hard wired for a specific service. 

Regards Nick</description>
		<content:encoded><![CDATA[<p>Good evening,<br />
Is there some form of hierarchy between the layers? If so why is service not on top?<br />
What I could not find in the challenges bullet list was the configuration of a transformation table in which causality between the layers is hard wired for a specific service. </p>
<p>Regards Nick</p>
]]></content:encoded>
	</item>
</channel>
</rss>
