<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Tips for your public art proposal</title>
	<atom:link href="http://www.artbizblog.com/2007/09/tips-for-your-public-art-proposal.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.artbizblog.com/2007/09/tips-for-your-public-art-proposal.html</link>
	<description>for the Business of Being an Artist</description>
	<lastBuildDate>Fri, 10 Feb 2012 01:18:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Art Marketing Action: Plan for a fruitful meeting — Art Biz Blog</title>
		<link>http://www.artbizblog.com/2007/09/tips-for-your-public-art-proposal.html/comment-page-1#comment-13501</link>
		<dc:creator>Art Marketing Action: Plan for a fruitful meeting — Art Biz Blog</dc:creator>
		<pubDate>Mon, 28 Sep 2009 14:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.artbizblog.com/2007/09/tips-for-your-public-art-proposal.html#comment-13501</guid>
		<description>[...] action as a result of this meeting. Perhaps you want the secrets of another artist’s success with public art commissions. Or maybe you want to find out from your gallery dealer what you could be doing to drive more [...]</description>
		<content:encoded><![CDATA[<p>[...] action as a result of this meeting. Perhaps you want the secrets of another artist’s success with public art commissions. Or maybe you want to find out from your gallery dealer what you could be doing to drive more [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary Richmond</title>
		<link>http://www.artbizblog.com/2007/09/tips-for-your-public-art-proposal.html/comment-page-1#comment-4348</link>
		<dc:creator>Mary Richmond</dc:creator>
		<pubDate>Tue, 18 Sep 2007 13:08:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.artbizblog.com/2007/09/tips-for-your-public-art-proposal.html#comment-4348</guid>
		<description>Thanks for the links and the info about the publication. I have begun working with art consultants and it is a very interesting aspect of selling art. It&#039;s usually very site specific and much more collaborative than the average artist may be used to. I compare it to writing for publication. You have to be open to editing. Until I began to be published on a regular basis I had no idea how collaborative writing really is. Not that an editor or art consultant does your work but there are many parameters that doing &quot;our own thing&quot; often ignore. Size, scope, colors, theme....these sorts of things are agreed upon beforehand and the finished piece must look like the proposal. No artistic license in the process once it&#039;s been approved! Still, an interesting way of working. Thanks again for the info.
</description>
		<content:encoded><![CDATA[<p>Thanks for the links and the info about the publication. I have begun working with art consultants and it is a very interesting aspect of selling art. It&#8217;s usually very site specific and much more collaborative than the average artist may be used to. I compare it to writing for publication. You have to be open to editing. Until I began to be published on a regular basis I had no idea how collaborative writing really is. Not that an editor or art consultant does your work but there are many parameters that doing &#8220;our own thing&#8221; often ignore. Size, scope, colors, theme&#8230;.these sorts of things are agreed upon beforehand and the finished piece must look like the proposal. No artistic license in the process once it&#8217;s been approved! Still, an interesting way of working. Thanks again for the info.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

