<?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: Classical got its own way &#8211; Classical:NEXT&#8230; and many voices.</title>
	<atom:link href="http://www.sequenza21.com/2012/06/classical-got-its-own-way-classicalnext-and-many-voices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sequenza21.com/2012/06/classical-got-its-own-way-classicalnext-and-many-voices/</link>
	<description>The Contemporary Classical Music Community</description>
	<lastBuildDate>Sun, 19 May 2013 04:27:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Ilona Oltuski</title>
		<link>http://www.sequenza21.com/2012/06/classical-got-its-own-way-classicalnext-and-many-voices/comment-page-1/#comment-26902</link>
		<dc:creator>Ilona Oltuski</dc:creator>
		<pubDate>Sat, 09 Jun 2012 00:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.sequenza21.com/?p=7758#comment-26902</guid>
		<description><![CDATA[To the editor : I have a correction for my article - is it possible to mention it within the article?? Here it is!  perhaps point it out as a correction within the article?



Correction!!!
Thanks to a conversation with Klaus Heymann in response to my article &#039;s mention of the Naxos hosted party at Classical:NEXT, it has been clarified that both the Naxos party and subsequnt Naxos-sponsored concert were open to the public. Their minimal publicity was simply an administrative oversight on the part of the event&#039;s organizers.
&quot;Not publicising the party and the concert was one of the issues we had with the organisers...We could have had more people at our party and the subsequent concert.We will probably back next year&#039;s event again, provided they make improvements,&quot; Heymann said.

Ilona Oltuski]]></description>
		<content:encoded><![CDATA[<p>To the editor : I have a correction for my article &#8211; is it possible to mention it within the article?? Here it is!  perhaps point it out as a correction within the article?</p>
<p>Correction!!!<br />
Thanks to a conversation with Klaus Heymann in response to my article &#8216;s mention of the Naxos hosted party at Classical:NEXT, it has been clarified that both the Naxos party and subsequnt Naxos-sponsored concert were open to the public. Their minimal publicity was simply an administrative oversight on the part of the event&#8217;s organizers.<br />
&#8220;Not publicising the party and the concert was one of the issues we had with the organisers&#8230;We could have had more people at our party and the subsequent concert.We will probably back next year&#8217;s event again, provided they make improvements,&#8221; Heymann said.</p>
<p>Ilona Oltuski</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Hickey</title>
		<link>http://www.sequenza21.com/2012/06/classical-got-its-own-way-classicalnext-and-many-voices/comment-page-1/#comment-26898</link>
		<dc:creator>Sean Hickey</dc:creator>
		<pubDate>Thu, 07 Jun 2012 21:26:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sequenza21.com/?p=7758#comment-26898</guid>
		<description><![CDATA[Great recap, Ilona. I&#039;m sad that I couldn&#039;t be there. We had some 80 meetings there and no time to attend a single event, even missing some Naxos ones apparently. All in all, it sounded a bit less chaotic than most of us expected, and good to have so many friends together.]]></description>
		<content:encoded><![CDATA[<p>Great recap, Ilona. I&#8217;m sad that I couldn&#8217;t be there. We had some 80 meetings there and no time to attend a single event, even missing some Naxos ones apparently. All in all, it sounded a bit less chaotic than most of us expected, and good to have so many friends together.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
