<?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>Comments on: What constitutes a version change?</title>
	<atom:link href="http://depts.washington.edu/ontheroa/?feed=rss2&#038;p=161" rel="self" type="application/rss+xml" />
	<link>http://depts.washington.edu/ontheroa/?p=161</link>
	<description>The UW blog for all things Resource Oriented Architecture &#38; web services - email appdev@u.washington.edu</description>
	<lastBuildDate>Tue, 07 Feb 2012 00:23:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Scott Bush</title>
		<link>http://depts.washington.edu/ontheroa/?p=161&#038;cpage=1#comment-12</link>
		<dc:creator>Scott Bush</dc:creator>
		<pubDate>Fri, 29 May 2009 16:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://depts.washington.edu/ontheroa/?p=161#comment-12</guid>
		<description>I agree with Rupert in that version integers shouldn&#039;t change unless something major occurs. Certainly, any update that would break existing apps (due to an API change or something along those lines) deserves a new version.
As for incremental additions, the service code version should be adequate--with an up-to-date reference--to inform developers what data they can access. Incrementing the version integer based on additions to the web services should only happen when those additions are sufficient enough to warrant it. What constitutes &quot;sufficient&quot; is another question...</description>
		<content:encoded><![CDATA[<p>I agree with Rupert in that version integers shouldn&#8217;t change unless something major occurs. Certainly, any update that would break existing apps (due to an API change or something along those lines) deserves a new version.<br />
As for incremental additions, the service code version should be adequate&#8211;with an up-to-date reference&#8211;to inform developers what data they can access. Incrementing the version integer based on additions to the web services should only happen when those additions are sufficient enough to warrant it. What constitutes &#8220;sufficient&#8221; is another question&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Architecture Blogs</title>
		<link>http://depts.washington.edu/ontheroa/?p=161&#038;cpage=1#comment-11</link>
		<dc:creator>Architecture Blogs</dc:creator>
		<pubDate>Thu, 28 May 2009 23:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://depts.washington.edu/ontheroa/?p=161#comment-11</guid>
		<description>&lt;strong&gt;Architecture Blogs...&lt;/strong&gt;

[...] The UW blog for all things Resource Oriented Architecture &amp; web services - email appdev@u.washington.edu. On the ROA · Home. « Student Web Services V3 Release. What constitutes a version change? Recently, in the ROA technical group, ... [...]...</description>
		<content:encoded><![CDATA[<p><strong>Architecture Blogs&#8230;</strong></p>
<p>[...] The UW blog for all things Resource Oriented Architecture &amp; web services &#8211; email <a href="mailto:appdev@u.washington.edu">appdev@u.washington.edu</a>. On the ROA · Home. « Student Web Services V3 Release. What constitutes a version change? Recently, in the ROA technical group, &#8230; [...]&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
