<?xml version="1.0"?>
<rss version="2.0">

<channel>
	<title>The SOA Magazine Contributions by Paul S Prueitt</title>
	<link>http://www.soamag.com</link>
	<description>
The SOA Magazine is a monthly online publication provided by SOA Systems Inc. and Prentice Hall/PearsonPTR and is officially associated with the "Prentice Hall Service-Oriented Computing Series from Thomas Erl."
	</description>
	<category>SOA</category>
	<language>en-us</language>
	<copyright>Copyright 2006-2009, SOA Systems Inc.</copyright> 

	
	<item>
		<title>Articulating SOA in the Cloud</title>
		<link>http://www.soamag.com/I34/1109-4.php</link>
		<description>
Double articulated SOA service specification, use, reuse and orchestration will simplify best practices used in all Web services, service contracts and service discovery/orchestration in a platform agnostic fashion. In many cases, cloud computing bypasses the hardware platforms through a process similar to single processor program compilation. However, the process starts with mature design and this mature design is guided by SOA design principles and standards. A service is first articulated using SOA design principles, contracts and concepts. If all services within an infrastructure share a common second articulation, an inner articulation, then we have double articulated SOA infrastructure... 
		</description>
		<category>SOA</category>
		<guid>http://www.soamag.com/I34/1109-4.php#When:03.12.09</guid>
	</item>	
	
	<item>
		<title>The Service Engine: Structured Communication using Modern Service Technologies </title>
		<link>http://www.soamag.com/I30/0709-1.asp</link>
		<description>
A simple stand-alone fixed finite state machine may be used as an engine that determines all triggers for a particular set of web services. Such an engine requires a uniform design regime over all service contracts. This type of machine may exist as a URI/URL web service provider. The community of such providers defines a network infrastructure for social networks engaged in common tasks. Within this infrastructure, services may be offered and fulfilled using a structured method for machine specification (SMMS). Data persistence is distributed in a peer-to-peer architecture, again very simple in nature. XML files with very simple XML schema are all that is necessary and may be passed around the web using HTTP requests. The files may be manufactured in AJAX, SOAP or REST architectures. XML/XML-schema may also be manufactured using a hash table. Persistence may then be in the cloud with a minimal repository.
		</description>
		<category>SOA</category>
		<guid>http://www.soamag.com/I30/0709-1.asp#When:30.07.09</guid>
	</item>

</channel>
</rss>
