<?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"
	>
<channel>
	<title>Comments on: Writing iPhoto Exif Data</title>
	<atom:link href="http://highearthorbit.com/289/feed/" rel="self" type="application/rss+xml" />
	<link>http://highearthorbit.com/289/</link>
	<description>Transmitting ideas, observations, and images from 42,000 km.</description>
	<pubDate>Sat, 11 Oct 2008 02:19:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: BaroqueW and his sidekick nikkitaa &#187; iPhoto et tags EXIF</title>
		<link>http://highearthorbit.com/289/#comment-198688</link>
		<dc:creator>BaroqueW and his sidekick nikkitaa &#187; iPhoto et tags EXIF</dc:creator>
		<pubDate>Sun, 17 Aug 2008 11:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-198688</guid>
		<description>[...] et tags EXIF Posted in August 17th, 2008  by BaroqueW in Tech &#62;&#62; Computer Adapté d&#8217;un script par Andrew Turner, ce script Applescript permet d&#8217;ajouter des tags Exif (commentaires, titre, [...]</description>
		<content:encoded><![CDATA[<p>[...] et tags EXIF Posted in August 17th, 2008  by BaroqueW in Tech &gt;&gt; Computer Adapté d&#8217;un script par Andrew Turner, ce script Applescript permet d&#8217;ajouter des tags Exif (commentaires, titre, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Banks</title>
		<link>http://highearthorbit.com/289/#comment-184119</link>
		<dc:creator>Roger Banks</dc:creator>
		<pubDate>Mon, 02 Jun 2008 21:08:58 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-184119</guid>
		<description>exiftool has an -overwrite_original option that you could use instead of deleting the *._original files after the fact.</description>
		<content:encoded><![CDATA[<p>exiftool has an -overwrite_original option that you could use instead of deleting the *._original files after the fact.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dayna</title>
		<link>http://highearthorbit.com/289/#comment-168536</link>
		<dc:creator>dayna</dc:creator>
		<pubDate>Sat, 19 Apr 2008 23:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-168536</guid>
		<description>thank you for replying.. i think i'm going to have to spend a bit more time on this (not played with programming much..)... or i'll find a friend to help me. *grin*</description>
		<content:encoded><![CDATA[<p>thank you for replying.. i think i&#8217;m going to have to spend a bit more time on this (not played with programming much..)&#8230; or i&#8217;ll find a friend to help me. *grin*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ville</title>
		<link>http://highearthorbit.com/289/#comment-163592</link>
		<dc:creator>Ville</dc:creator>
		<pubDate>Mon, 31 Mar 2008 11:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-163592</guid>
		<description>More on the apostrophe issue, this is a quick hack:

Of course, you can also quote the string with the parenthesis character, then it would probably look like this:

'exiftool -title="' &#38; image_title &#38; ¬
'" ' &#38; keywordslist...

That way, you can use the apostrophe within the title (but not the parenthesis).


The better solution (that will allow all characters) will probably need to be based on exiftool's argfile option:

From the exiftool documentation:

"-@ ARGFILE

Read command-line arguments from the specified file. The file contains one argument per line (NOT one option per line -- some options require additional arguments which must be placed on separate lines). Blank lines and lines beginning with # and are ignored. Normal shell processing of arguments is not performed, which among other things means that arguments should not be quoted. ARGFILE may exist relative to either the current directory or the exiftool directory unless an absolute pathname is given. 
For example, the following ARGFILE will set the value of Copyright to ``Copyright YYYY, Phil Harvey'', where ``YYYY'' is the year of CreateDate:

    -d
    %Y
    -copyright&#60;Copyright $createdate, Phil Harvey"</description>
		<content:encoded><![CDATA[<p>More on the apostrophe issue, this is a quick hack:</p>
<p>Of course, you can also quote the string with the parenthesis character, then it would probably look like this:</p>
<p>&#8216;exiftool -title=&#8221;&#8216; &amp; image_title &amp; ¬<br />
&#8216;&#8221; &#8216; &amp; keywordslist&#8230;</p>
<p>That way, you can use the apostrophe within the title (but not the parenthesis).</p>
<p>The better solution (that will allow all characters) will probably need to be based on exiftool&#8217;s argfile option:</p>
<p>From the exiftool documentation:</p>
<p>&#8220;-@ ARGFILE</p>
<p>Read command-line arguments from the specified file. The file contains one argument per line (NOT one option per line &#8212; some options require additional arguments which must be placed on separate lines). Blank lines and lines beginning with # and are ignored. Normal shell processing of arguments is not performed, which among other things means that arguments should not be quoted. ARGFILE may exist relative to either the current directory or the exiftool directory unless an absolute pathname is given.<br />
For example, the following ARGFILE will set the value of Copyright to &#8220;Copyright YYYY, Phil Harvey&#8221;, where &#8220;YYYY&#8221; is the year of CreateDate:</p>
<p>    -d<br />
    %Y<br />
    -copyright&lt;Copyright $createdate, Phil Harvey&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ville</title>
		<link>http://highearthorbit.com/289/#comment-163584</link>
		<dc:creator>Ville</dc:creator>
		<pubDate>Mon, 31 Mar 2008 10:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-163584</guid>
		<description>About the apostrophe problem:

Your guess is probably correct. Seems a more generic solution would be needed.

One idea would be to write the tag/content as tab-separated pairs to a temporary file and then let exiftool read that file.

That file could probably be also stdin, leading to something like this (note that this is a coarse example from memory without any syntax check):

do shell script "echo Keywords \t" item j of assigned_keywords &#124; exiftool -t ...

(Note the piping character. I hope you are a bit familiar with unix scripting.)


(BTW, regarding my previous comment about the rating info: for reading, that seems to be available only via the plist iPhoto archive file, for writing, UI scripting would be needed. Of course it is also not very difficult to generate rating-based tags like R0, R1, R2..R5.)</description>
		<content:encoded><![CDATA[<p>About the apostrophe problem:</p>
<p>Your guess is probably correct. Seems a more generic solution would be needed.</p>
<p>One idea would be to write the tag/content as tab-separated pairs to a temporary file and then let exiftool read that file.</p>
<p>That file could probably be also stdin, leading to something like this (note that this is a coarse example from memory without any syntax check):</p>
<p>do shell script &#8220;echo Keywords \t&#8221; item j of assigned_keywords | exiftool -t &#8230;</p>
<p>(Note the piping character. I hope you are a bit familiar with unix scripting.)</p>
<p>(BTW, regarding my previous comment about the rating info: for reading, that seems to be available only via the plist iPhoto archive file, for writing, UI scripting would be needed. Of course it is also not very difficult to generate rating-based tags like R0, R1, R2..R5.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dayna</title>
		<link>http://highearthorbit.com/289/#comment-162002</link>
		<dc:creator>dayna</dc:creator>
		<pubDate>Mon, 24 Mar 2008 20:58:17 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-162002</guid>
		<description>just found this today.. am i right in thinking that any comment with an apostrophe will cause trouble? That's what I'm seeing so far...</description>
		<content:encoded><![CDATA[<p>just found this today.. am i right in thinking that any comment with an apostrophe will cause trouble? That&#8217;s what I&#8217;m seeing so far&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ville</title>
		<link>http://highearthorbit.com/289/#comment-154029</link>
		<dc:creator>Ville</dc:creator>
		<pubDate>Tue, 26 Feb 2008 13:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-154029</guid>
		<description>Regarding the multi-word keyword issue:

This can easily be fixed by modifying the script by adding single quotes around each keyword, as it is already done for the other tags (have a look at the code above).

I.e. change this part to:

repeat with j from 1 to the count of assigned_keywords
	set the keywordslist to keywordslist &#38; " -keywords+='" ¬
		&#38; item j of assigned_keywords  &#38; "'"
end repeat

Note that it might be also more practical to change the += to =, as somebody already commented.

What could be also added is storing the rating information, I think it should be available via Applescript as well.</description>
		<content:encoded><![CDATA[<p>Regarding the multi-word keyword issue:</p>
<p>This can easily be fixed by modifying the script by adding single quotes around each keyword, as it is already done for the other tags (have a look at the code above).</p>
<p>I.e. change this part to:</p>
<p>repeat with j from 1 to the count of assigned_keywords<br />
	set the keywordslist to keywordslist &amp; &#8221; -keywords+=&#8217;&#8221; ¬<br />
		&amp; item j of assigned_keywords  &amp; &#8220;&#8216;&#8221;<br />
end repeat</p>
<p>Note that it might be also more practical to change the += to =, as somebody already commented.</p>
<p>What could be also added is storing the rating information, I think it should be available via Applescript as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Comment on Writing iPhoto Exif Data by Robert</title>
		<link>http://highearthorbit.com/289/#comment-130776</link>
		<dc:creator>Comment on Writing iPhoto Exif Data by Robert</dc:creator>
		<pubDate>Wed, 05 Dec 2007 21:11:58 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-130776</guid>
		<description>[...] life, Technology, Photography)    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;   Comment on Writing iPhoto Exif Data by Robert  Great script! I'm using the most recent EXIFtool. Keywords do not seem to be written to the JPG. [...]</description>
		<content:encoded><![CDATA[<p>[...] life, Technology, Photography)    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Comment on Writing iPhoto Exif Data by Robert  Great script! I&#8217;m using the most recent EXIFtool. Keywords do not seem to be written to the JPG. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://highearthorbit.com/289/#comment-126079</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Mon, 19 Nov 2007 22:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-126079</guid>
		<description>Does anyone have a solution to Matias' problem when using two word keywords?  For a two word keyword, I'd rather not have to use two separate tags "Los" and "Angeles", but rather just "Los Angeles."  

Is there an easy way to modify the script so that two word keywords are functional? 

Thanks so much for the awesome script!</description>
		<content:encoded><![CDATA[<p>Does anyone have a solution to Matias&#8217; problem when using two word keywords?  For a two word keyword, I&#8217;d rather not have to use two separate tags &#8220;Los&#8221; and &#8220;Angeles&#8221;, but rather just &#8220;Los Angeles.&#8221;  </p>
<p>Is there an easy way to modify the script so that two word keywords are functional? </p>
<p>Thanks so much for the awesome script!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://highearthorbit.com/289/#comment-114738</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sat, 13 Oct 2007 05:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-114738</guid>
		<description>Great script! I'm using the most recent EXIFtool. Keywords do not seem to be written to the JPG. Does anyone experience similar problems and have a solution to this? Thx in advance!</description>
		<content:encoded><![CDATA[<p>Great script! I&#8217;m using the most recent EXIFtool. Keywords do not seem to be written to the JPG. Does anyone experience similar problems and have a solution to this? Thx in advance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the loPEZ dispenser &#187; Blog Archive &#187; iPhoto IPTC/EXIF/XMP Tags</title>
		<link>http://highearthorbit.com/289/#comment-99711</link>
		<dc:creator>the loPEZ dispenser &#187; Blog Archive &#187; iPhoto IPTC/EXIF/XMP Tags</dc:creator>
		<pubDate>Tue, 07 Aug 2007 06:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-99711</guid>
		<description>[...] I was disappointed to find iPhoto didn&#8217;t &#8220;do&#8221; IPTC tags when I started using it to organise photos, and export them to Gallery2. Luckily I found an AppleScript that uses the excellent ExifTool. I&#8217;ve modified it a bit, to work better with Gallery 2, and fixed it so comments and tags are escaped properly. [...]</description>
		<content:encoded><![CDATA[<p>[...] I was disappointed to find iPhoto didn&#8217;t &#8220;do&#8221; IPTC tags when I started using it to organise photos, and export them to Gallery2. Luckily I found an AppleScript that uses the excellent ExifTool. I&#8217;ve modified it a bit, to work better with Gallery 2, and fixed it so comments and tags are escaped properly. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://highearthorbit.com/289/#comment-92666</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 28 Jun 2007 04:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-92666</guid>
		<description>Thank you very much for this script.. Apple tricks people into thinking they are doing things "the right way", when in reality it's "Apple's way" (iPhoto metadata as a prime example)



Just a mental note to anyone viewing this:

Think anyone could build in a versioning comment system that lets a commenter mark up (any) code, hide the revised full version behind css (or something) while showing the markups? (It would have to roll into a blog/new commenting system)

Would be great for a page like this, where there would have been at least 3 different versions so far, and encourage more.</description>
		<content:encoded><![CDATA[<p>Thank you very much for this script.. Apple tricks people into thinking they are doing things &#8220;the right way&#8221;, when in reality it&#8217;s &#8220;Apple&#8217;s way&#8221; (iPhoto metadata as a prime example)</p>
<p>Just a mental note to anyone viewing this:</p>
<p>Think anyone could build in a versioning comment system that lets a commenter mark up (any) code, hide the revised full version behind css (or something) while showing the markups? (It would have to roll into a blog/new commenting system)</p>
<p>Would be great for a page like this, where there would have been at least 3 different versions so far, and encourage more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://highearthorbit.com/289/#comment-88719</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 13 Jun 2007 06:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-88719</guid>
		<description>Thanks Ryan, that's exactly what I was looking for.

Will give it a go later tonight, I have hundreds of scanned images which I need to export with the correct (iPhoto) date.</description>
		<content:encoded><![CDATA[<p>Thanks Ryan, that&#8217;s exactly what I was looking for.</p>
<p>Will give it a go later tonight, I have hundreds of scanned images which I need to export with the correct (iPhoto) date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://highearthorbit.com/289/#comment-84306</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Sun, 13 May 2007 23:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-84306</guid>
		<description>Well, this is to answer my question above. I now got a modified version of the script to simply add the iPhoto date as the Original Date in the EXIF header within my iPhoto library... which also applies to any exported versions, etc. (NOTE: it works, but I have no clue about applescript, so this may not be 100% correct, it's just based on my trial-and-error).

Basically in the "tell this_photo" part I added:
set the image_date to the date

and then changed the exiftool shell script call to simply be:
"exiftool -DateTimeOriginal='" &#38; image_date &#38; "' " &#38; "'" &#38; image_file &#38; "'"

Dunno if that's useful to anyone, but this result saves me hours and hours of trouble in terms of getting my (properly dated) photos from iPhoto to Gallery 2.2 (http://gallery.menalto.com/)

Cheers!
Ryan</description>
		<content:encoded><![CDATA[<p>Well, this is to answer my question above. I now got a modified version of the script to simply add the iPhoto date as the Original Date in the EXIF header within my iPhoto library&#8230; which also applies to any exported versions, etc. (NOTE: it works, but I have no clue about applescript, so this may not be 100% correct, it&#8217;s just based on my trial-and-error).</p>
<p>Basically in the &#8220;tell this_photo&#8221; part I added:<br />
set the image_date to the date</p>
<p>and then changed the exiftool shell script call to simply be:<br />
&#8220;exiftool -DateTimeOriginal=&#8217;&#8221; &amp; image_date &amp; &#8220;&#8216; &#8221; &amp; &#8220;&#8216;&#8221; &amp; image_file &amp; &#8220;&#8216;&#8221;</p>
<p>Dunno if that&#8217;s useful to anyone, but this result saves me hours and hours of trouble in terms of getting my (properly dated) photos from iPhoto to Gallery 2.2 (http://gallery.menalto.com/)</p>
<p>Cheers!<br />
Ryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://highearthorbit.com/289/#comment-84020</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 11 May 2007 19:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-84020</guid>
		<description>This looks very very useful. I have been looking for a way to take the iPhoto date and somehow embed/attach it when exporting to external web galleries that need this date inf). I have to manually enter the dates in iPhoto because the originals are scans, and thus have no EXIF data.

Does anyone know how one would modify this script to also copy the iPhoto date within an EXIF capture date header?

Cheers,
Ryan</description>
		<content:encoded><![CDATA[<p>This looks very very useful. I have been looking for a way to take the iPhoto date and somehow embed/attach it when exporting to external web galleries that need this date inf). I have to manually enter the dates in iPhoto because the originals are scans, and thus have no EXIF data.</p>
<p>Does anyone know how one would modify this script to also copy the iPhoto date within an EXIF capture date header?</p>
<p>Cheers,<br />
Ryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matias</title>
		<link>http://highearthorbit.com/289/#comment-80824</link>
		<dc:creator>Matias</dc:creator>
		<pubDate>Thu, 12 Apr 2007 05:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-80824</guid>
		<description>The script works great, is just what I was looking for. But I have 2 error popups:
    The first one is when I have a two words keyword like "Los Angeles". I get this popup:

 Error: Error opening file - Angeles

And the second is this popup:

 Error: [minor] Bad NikonPreview directory pointer for tag 0x2 - Users/Saraza/Pictures/2004/040928-11.JPG

I couldn' t understand why this one appears.

Thanks!</description>
		<content:encoded><![CDATA[<p>The script works great, is just what I was looking for. But I have 2 error popups:<br />
    The first one is when I have a two words keyword like &#8220;Los Angeles&#8221;. I get this popup:</p>
<p> Error: Error opening file - Angeles</p>
<p>And the second is this popup:</p>
<p> Error: [minor] Bad NikonPreview directory pointer for tag 0&#215;2 - Users/Saraza/Pictures/2004/040928-11.JPG</p>
<p>I couldn&#8217; t understand why this one appears.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://highearthorbit.com/289/#comment-72621</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 19 Jan 2007 13:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-72621</guid>
		<description>@Tom - thanks for pointing out the fix

@Heather - you need to first install &lt;a href="http://www.sno.phy.queensu.ca/~phil/exiftool/" rel="nofollow"&gt;ExifTool&lt;/a&gt; onto your Mac. 

@Marty - you just need to select the photos you want to geocode and shouldn't depend on the name of the roll - I will have to test more to check this out. </description>
		<content:encoded><![CDATA[<p>@Tom - thanks for pointing out the fix</p>
<p>@Heather - you need to first install <a href="http://www.sno.phy.queensu.ca/~phil/exiftool/" rel="nofollow">ExifTool</a> onto your Mac. </p>
<p>@Marty - you just need to select the photos you want to geocode and shouldn&#8217;t depend on the name of the roll - I will have to test more to check this out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heather</title>
		<link>http://highearthorbit.com/289/#comment-72570</link>
		<dc:creator>Heather</dc:creator>
		<pubDate>Fri, 19 Jan 2007 00:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-72570</guid>
		<description>Thanks for the script, it's a great idea!  Any idea why I might be getting an error along the lines of "sh: line 1: exiftool: command not found"?</description>
		<content:encoded><![CDATA[<p>Thanks for the script, it&#8217;s a great idea!  Any idea why I might be getting an error along the lines of &#8220;sh: line 1: exiftool: command not found&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marty</title>
		<link>http://highearthorbit.com/289/#comment-71566</link>
		<dc:creator>Marty</dc:creator>
		<pubDate>Mon, 15 Jan 2007 20:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-71566</guid>
		<description>This script doesn't seem to work when the roll name for the photos has more than one space. Does it assume the roll/enclosing folder will always be named "Roll ####" ?</description>
		<content:encoded><![CDATA[<p>This script doesn&#8217;t seem to work when the roll name for the photos has more than one space. Does it assume the roll/enclosing folder will always be named &#8220;Roll ####&#8221; ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Kerswill</title>
		<link>http://highearthorbit.com/289/#comment-69231</link>
		<dc:creator>Tom Kerswill</dc:creator>
		<pubDate>Mon, 08 Jan 2007 02:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/289/#comment-69231</guid>
		<description>Ah yeah, so to alter this behaviour in the script just change:

set the keywordslist to keywordslist &#38; " -keywords+=" &#38; item j of assigned_keywords

to:

set the keywordslist to keywordslist &#38; " -keywords=" &#38; item j of assigned_keywords

This will just clear the keywords before setting the new ones,

Thanks!</description>
		<content:encoded><![CDATA[<p>Ah yeah, so to alter this behaviour in the script just change:</p>
<p>set the keywordslist to keywordslist &amp; &#8221; -keywords+=&#8221; &amp; item j of assigned_keywords</p>
<p>to:</p>
<p>set the keywordslist to keywordslist &amp; &#8221; -keywords=&#8221; &amp; item j of assigned_keywords</p>
<p>This will just clear the keywords before setting the new ones,</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
