<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Open Siddur Project &#187; open source</title>
	<atom:link href="http://opensiddur.org/tag/open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://opensiddur.org</link>
	<description>sharing the ingredients of Jewish spiritual practice for the craft and design of new siddurim</description>
	<lastBuildDate>Mon, 21 May 2012 21:55:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Just say NO to NC — choose a *free* Creative Commons license</title>
		<link>http://opensiddur.org/2011/03/why-to-choose-a-free-creative-commons-license-or-say-no-to-nc/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-to-choose-a-free-creative-commons-license-or-say-no-to-nc</link>
		<comments>http://opensiddur.org/2011/03/why-to-choose-a-free-creative-commons-license-or-say-no-to-nc/#comments</comments>
		<pubDate>Thu, 10 Mar 2011 19:15:23 +0000</pubDate>
		<dc:creator>Efraim Feinstein</dc:creator>
				<category><![CDATA[Free/Libre Jewish Culture]]></category>
		<category><![CDATA[copyleft]]></category>
		<category><![CDATA[creative commons]]></category>
		<category><![CDATA[free culture]]></category>
		<category><![CDATA[licensing]]></category>
		<category><![CDATA[nc]]></category>
		<category><![CDATA[non-commercial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[sharealike]]></category>
		<category><![CDATA[what is free]]></category>

		<guid isPermaLink="false">http://opensiddur.org/?p=2707</guid>
		<description><![CDATA[<em>This post continues the series of advocacy posts directed at Jewish content creators and aggregators. Other parts of the series discussed the <a href="http://opensiddur.org/2010/02/an-economic-argument-for-free-primary-data/">global communal benefit of free primary data resources</a> and <a href="http://opensiddur.org/2009/11/jewish-content-free-culture-and-content-compatibility/">issues of copyright license compatibility</a> and <a href="http://opensiddur.org/2010/11/openness-remixability-and-free-culture/">the connection between copyright licensing and remixability</a>. While <a href="http://opensiddur.org/2009/11/jewish-content-free-culture-and-content-compatibility/">my previous post</a> briefly mentioned the non-free <a href="http://creativecommons.org">Creative Commons</a> licenses, this post details why you should choose a free culture license. In particular, it urges you to avoid the licenses with the non-commercial-use only (NC) terms.</em> <span style="color:#777"> . . . &#8594; Read More: <a href="http://opensiddur.org/2011/03/why-to-choose-a-free-creative-commons-license-or-say-no-to-nc/">Just say NO to NC — choose a *free* Creative Commons license</a></span>]]></description>
			<content:encoded><![CDATA[<p><div id="attachment_2730" class="wp-caption alignright" style="width: 310px"><a href="http://opensiddur.org/wp-content/uploads/2011/03/cc-by-nc-sa.svg_-300x120.png"><img src="http://opensiddur.org/wp-content/uploads/2011/03/cc-by-nc-sa.svg_-300x120.png" alt="" title="Non-Commercial Copyleft is not a Free License" width="300" height="120" class="size-medium wp-image-2730" /></a><p class="wp-caption-text">Which of the above Creative Commons licensing option conflicts with the entire copyleft and free/libre license ecosystem? (Image by Aharon Varady, licensed CC-BY-SA 3.0 Unported)</p></div><em>This post continues the series of advocacy posts directed at Jewish content creators and aggregators. Other parts of the series discussed the <a href="http://opensiddur.org/2010/02/an-economic-argument-for-free-primary-data/">global  communal benefit of free primary data resources</a> and <a href="http://opensiddur.org/2009/11/jewish-content-free-culture-and-content-compatibility/">issues of copyright license compatibility</a> and <a href="http://opensiddur.org/2010/11/openness-remixability-and-free-culture/">the connection between copyright licensing and remixability</a>. While <a href="http://opensiddur.org/2009/11/jewish-content-free-culture-and-content-compatibility/">my previous post</a> briefly mentioned the non-free <a href="http://creativecommons.org">Creative Commons</a> licenses, this post details why you should choose a free culture license. In particular, it urges you to avoid the licenses with the non-commercial-use only (NC) terms. The author, Efraim Feinstein, is lead developer of the Open Siddur Project.</em></p>
<p>The Jewish digital media community is young. Welcome to it! Those of you who are posting and innovating now are the trend-setters for the near-term. In addition, as long as the material you and your &#8220;students&#8221; produce remains relevant, the length of the copyright term will ensure that licensing restrictions placed on your data now last well beyond your lifetime,  The community will learn, and I hope to convince you that the non-commercial (NC) term of use sets a dangerous precedent going forward.</p>
<p>The community is currently undergoing a transition from resources that are simply &#8220;free as in beer&#8221; (do not cost money to download and use) but place restrictions on what can be done with their content (<a href="http://opensiddur.org/2009/11/jewish-content-free-culture-and-content-compatibility/">examples here</a>) to resources that recognize the educational and cultural value of remixing. The <a href="http://ejewishphilanthropy.com/the-jewish-futures-conference-the-conversation-continues/">educational arguments in favor</a> of remixability are remarkably similar to the philosophy of free culture, although they differ in focus. Our community, however, has not yet fully embraced the values of user freedom, and is subject to the confusion created by the choice offered in the spectrum of rights that Creative Commons licenses offer. The Creative Commons brand is recognized, but the differences in terms between the various licenses are not, leading to unhelpful suggestions like &#8220;use a Creative Commons license,&#8221; without specification of which one. While Creative Commons uses <a href="https://creativecommons.org/weblog/entry/8051">a logo</a> to distinguish its free licenses from its non-free licenses, the brand name itself is still more recognizable than this logo.</p>
<p>One argument that I have heard promoting the use of the non-commercial term is the fear of a larger <em>bogeyman</em>. The identity of this bogeyman differs depending on who is making the argument. For content developers, the bogeyman is often a large publishing house. The new media entrepreneur worries that a larger publishing house will either take their free data and undercut their price or sell their free data without returning anything to its source. </p>
<p>This argument does not distinguish between two types of relationships with commercial entities: simple &#8220;commercial use&#8221; and &#8220;exploitation.&#8221; The free culture community answers the exploitation argument by proposing <a href="http://en.wikipedia.org/wiki/Copyleft">copyleft</a>, also known as <a href="http://en.wikipedia.org/wiki/Share-alike">ShareAlike</a>. Under copyleft licenses, any derived works of the original work must be released under the same terms as the original. What was once free remains free. The large publishing house bogeyman who publishes a copylefted work must allow the person who received the work to copy, modify, sell, and create derivative works of your work, just like any other user. Their intellectual improvements to the work can therefore be reincorporated into the original, diluting any advantage of the large publishing house&#8217;s version aside from the unique value added by their version (such as the fact that it&#8217;s a physical bound copy). In addition to the optional copyleft, all Creative Commons licenses except for the &#8220;Creative Commons Zero&#8221; (CC0) public domain declaration have anti-<a href="http://en.wikipedia.org/wiki/Digital_rights_management">DRM</a> clauses that prohibit adding digital rights/restrictions management that disallow users from exercising their rights under the license, so a third party is prevented from <a href="http://en.wikipedia.org/wiki/Tivoization">Tivo-izing</a> your material.</p>
<p>Further, publishing houses that make use of your data can become your supporters. If your project provides them with useful data now, you will likely be able to provide them with useful data in the future, forming symbiotic relationships between publishers and content creators and aggregators.</p>
<p>Non-commercial use restrictions are particularly dangerous in combination with the ShareAlike term, as is the case in the Creative Commons Attribution-NonCommercial-ShareAlike (<a href="http://creativecommons.org/licenses/by-nc-sa/3.0/">CC-BY-NC-SA</a>) license. The reason is that the ShareAlike term ensures that derivative works are released under the same terms as the original. Overuse of the CC-BY-NC-SA license will result in two copyleft ghettos that cannot be mixed with each other: one that allows commercial use and one that does not. The existence of the non-commercial partially-free ghetto can only lead to duplication of effort and waste, both by commercial and non-commercial entities.</p>
<p><div id="attachment_2745" class="wp-caption alignright" style="width: 308px"><a href="http://opensiddur.org/wp-content/uploads/2011/03/anti-non-commercial.png"><img src="http://opensiddur.org/wp-content/uploads/2011/03/anti-non-commercial-298x300.png" alt="" title="Just say no to non-commercial terms of use" width="298" height="300" class="size-medium wp-image-2745" /></a><p class="wp-caption-text">Don&#039;t make your copyleft, copywrong. License with a CC-BY-SA license instead of the CC-BY-NC-SA (Image by Aharon Varady, licensed CC-BY-SA 3.0 Unported.)</p></div> The interpretation of Creative Commons&#8217; NC term has been the subject of misunderstanding and debate. In 2009, Creative Commons issued a <a href="https://creativecommons.org/weblog/entry/17127">report</a> on the variant interpretations of the NC term between content creators and user/remixers. The study found that users tend to be more conservative in their interpretation of NC than creators, leading to failed sharing. </p>
<p>One proposed resolution to the varying interpretations of the NC term is for the creator to spell out what is expected. <a href="http://ocw.mit.edu/terms/#noncomm">MIT OpenCourseWare</a> is one such example of a well thought out model. However, even this liberal interpretation of the NC term blocks innovation and remixability by a large class of users for purposes which provide for the social good but involve an exchange of money beyond at-cost. </p>
<p>The real difference between MIT&#8217;s model and the model of many free resources in the Jewish community is that, it seems to me, MIT intends not to limit commercial use, but to reserve rights to commercial use. MIT is acting as a distributor for a collective of a relatively small number of copyright holders (the faculty) who themselves may have outside commercial interests in the material. Because only a few are involved and they are easily found, the NC license invites commercial users to obtain a separate licensing agreement for commercial publication. The NC term is creating a permission culture for commercial use of the work that is separate from the (semi-)free culture of its non-commercial use. Many content creators and aggregators in the Jewish community have no commercial interest in the work, which requires a different thought process from an entity that wants to reserve commercial rights.</p>
<p>A community-driven project that uses an NC term is in an even harder position. Not only is it content-incompatible with truly free resources, including Wikipedia, but it is also limited in what it in itself can do with derivative works of its own creation, once it has accepted a contribution from an outside contributor under the NC terms. For community-created works, there is no single author with whom to negotiate.</p>
<p>Further confusion is generated by the equation in many previous &#8220;free&#8221; resources of &#8220;non-profit&#8221; with &#8220;non-commercial.&#8221; With the advent of <a href="http://ejewishphilanthropy.com/legal-structure-as-a-tool-for-accomplishing-your-goals/">new business models</a>, the lines between various entities with social purpose are increasingly blurred. This is the era of the &#8220;social enterprise.&#8221; While traditional non-profits rely on grants and donations to ensure their continued functioning, many social enterprises prefer to ensure their future sustainability by offering products on the market that help their social mission. A no-commercial use copyright term prevents these enterprises from transacting business with your data unless they negotiate separate terms as described above.</p>
<p>Whatever your form of legal incorporation (if any), it is hard to argue that you have envisioned 100% of the uses of your data from now until 70 years after your death. By blocking commercial use of materials, an entire group of social enterprises has been cut off from any use of your data, no matter how innovative.</p>
<p>For the reasons outlined above, I urge you to avoid licenses that restrict commercial use. If you are worried about exploitation, choose a license with a copyleft (ShareAlike) term.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.org/2011/03/why-to-choose-a-free-creative-commons-license-or-say-no-to-nc/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Siddur Builder (pre-alpha, v.0.4.4.1 demo)</title>
		<link>http://opensiddur.org/2010/12/siddur-builder-alpha/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=siddur-builder-alpha</link>
		<comments>http://opensiddur.org/2010/12/siddur-builder-alpha/#comments</comments>
		<pubDate>Sun, 26 Dec 2010 22:12:29 +0000</pubDate>
		<dc:creator>Efraim Feinstein</dc:creator>
				<category><![CDATA[Howto]]></category>
		<category><![CDATA[Project Development]]></category>
		<category><![CDATA[JLPTEI]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://opensiddur.org/?p=1989</guid>
		<description><![CDATA[<p>Development of the Open Siddur Project &#8220;Siddur Builder&#8221; application has now reached the 0.4.4.1 milestone, a pre-alpha, feature-limited demonstration of the technology we&#8217;ve developed to compile textual content from our public database. (Barring any serious bugs, with current resources, we anticipate reaching an alpha-quality milestone at v.0.6.4 by the end of 2012.) The user interface <span style="color:#777"> . . . &#8594; Read More: <a href="http://opensiddur.org/2010/12/siddur-builder-alpha/">Siddur Builder (pre-alpha, v.0.4.4.1 demo)</a></span>]]></description>
			<content:encoded><![CDATA[<p>Development of the Open Siddur Project &#8220;Siddur Builder&#8221; application has now reached the 0.4.4.1 milestone, a pre-alpha, feature-limited demonstration of the technology we&#8217;ve developed to compile textual content from our public database. (Barring any serious bugs, with current resources, we anticipate reaching an alpha-quality milestone at v.0.6.4 by the end of 2012.) The user interface is still fairly primitive but the underlying technology and API are fairly advanced. Our 0.4.4.1 &#8220;Siddur Builder&#8221; functionally demonstrates how we can select XML formatted texts from our public, open source database and compile them into a single web viewable text. This XSL application serves up the <a href="http://opensiddur.org/2010/11/%d7%aa%d7%a0%d7%b3%d7%9a-the-westminster-leningrad-codex/">Westminster Leningrad Codex</a> (WLC), a digital edition of the earliest complete Masoretic edition of the TaNaKh. The texts are stored in XML and encoded in <a href="http://wiki.jewishliturgy.org/JLPTEI">JLPTEI</a>, our extension to the standard schema for formatting XML texts developed by the Text Encoding Initiative, or TEI The applet converts these XML formatted texts into XHTML for viewing in a web browser. </p>
<p>The code for this demo is open source. For more information on hacking this code, see our <a href="http://wiki.jewishliturgy.org/TaNaKh_XML_to_XHTML_Conversion_Demonstration">wiki</a></p>
<p><iframe src="http://shell.jewishliturgy.org:8080/code/apps/builder/welcome.xql" width="99%" height="400" frameborder="1" marginheight="0" marginwidth="20" scrolling="auto">Loading&#8230;</iframe></p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.org/2010/12/siddur-builder-alpha/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>An Economic Argument for Free Primary Data</title>
		<link>http://opensiddur.org/2010/02/an-economic-argument-for-free-primary-data/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=an-economic-argument-for-free-primary-data</link>
		<comments>http://opensiddur.org/2010/02/an-economic-argument-for-free-primary-data/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 20:10:05 +0000</pubDate>
		<dc:creator>Efraim Feinstein</dc:creator>
				<category><![CDATA[Free/Libre Jewish Culture]]></category>
		<category><![CDATA[economics]]></category>
		<category><![CDATA[free culture]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[semantic data]]></category>
		<category><![CDATA[what is free]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=359</guid>
		<description><![CDATA[<p>There are two principles on which the success of data on the contemporary web rests: the web makes content available, and it adds value to that content by linking it to other related information.</p> <p>When considering bringing old content online, both of these aspects are important. A first level of digitization involves simply making data <span style="color:#777"> . . . &#8594; Read More: <a href="http://opensiddur.org/2010/02/an-economic-argument-for-free-primary-data/">An Economic Argument for Free Primary Data</a></span>]]></description>
			<content:encoded><![CDATA[<p>There are two principles on which the success of data on the contemporary web rests: the web makes content available, and it adds value to that content by linking it to other related information.</p>
<p>When considering bringing old content online, both of these aspects are important.  A first level of digitization involves simply making data available.  <a href="http://books.google.com">Google Books</a> and <a href="http://hebrewbooks.org">Hebrewbooks.org</a> work at this level, providing PDFs and/or OCR-ed transcriptions of the material.  A second level of digitization involves semantic linkage of the data, both internal to the site and external to the site.  The <a href="http://opensiddur.org">Open Siddur Project</a>, <a href="http://www.taggedtanakh.org/">Tagged Tanakh</a> and <a href="http://openscriptures.org">Open Scriptures</a> digitize at the semantic level.  This second-level digitization is required to do all of the cool things we expect to be able to do with online texts: click on a word and find its definition or grammatical form, find the source of a passage in one text in another text, find how the text has evolved historically, etc.  Even the simplest form of a link: a reference from another site, requires some kind of internal division.</p>
<p>Digitization that takes advantage of the web therefore requires a number of steps: (1) getting the basic text online, (2) getting it in an addressable form (to make it more like typed text, instead of a picture of a page), (3) assuring the text&#8217;s accuracy, and (4) marking it up for semantic linkage.  Some of these steps, or parts of them can be done automatically, but, overall, they require some degree of intelligent input.  Even step 1, which is primarily mechanical in nature, requires design of the procedures.</p>
<p>I hope that this outline of the required steps to getting a text online suggests that the most expensive part of making content available is human labor &#8212; it takes time to do it, and it takes even more time to do it right.</p>
<p>And now for the rhetorical questions:</p>
<ul>
<li>How many times has the Tanach been digitized?</li>
<li>&#8230; the siddur?</li>
<li>&#8230; the Talmud?</li>
<li>&#8230; major commentaries on the siddur, Torah, Talmud (Rashi, Tosefot)?</li>
<li>&#8230; full codes of Jewish law (Mishneh Torah, Tur, Shulchan Aruch, Aruch Hashulchan)?</li>
<li>&#8230; uncommon piyyutim (liturgical poems)?</li>
</ul>
<p>In some cases, the answer is: it&#8217;s been done many times.  In other cases, the answer is: it&#8217;s never been done.  And, both answers lead the all-important question: why?  Why are there so many digitizations of the Tanach and no full digitizations of Shulchan Aruch online?  Why isn&#8217;t the siddur already hyperlinked to its Talmudic sources?</p>
<p>I would propose that we have been wasteful with our resources.  Earlier, I pointed out that the primary resources that go into these advanced digitizations are time and human labor.  In some cases, these resources equate directly to money, in others, the linkage is more indirect.</p>
<p>The core material of all of the above-mentioned works comes from the public domain.  It is ownerless, and free for anyone to copy for any purpose.  Every time we encounter a basic text that we have to digitize again because of &#8220;new copyright&#8221; claims or EULA-style contractual constraints, that is an indication of a failure somewhere in the system. This is particularly true if the claims are being made by non-profits, &#8220;social&#8221; businesses, or academic institutions. In the Jewish world, even for-profit published books are sometimes donation-supported.  Each common text that has to be digitized a second, third, or hundreth time equates to another less common text that is not being digitized.  Redoing basic OCR work and transcription takes resources away from establishing semantic linkages.</p>
<p>Some people and organizations get it.  As of now, we only need one digitization of the Leningrad Codex (Masoretic Bible). That&#8217;s because Christopher Kimball and the J. Alan Groves Center for Advanced Biblical Research digitized it, transcribed it, and released it as free data.  The <a href="http://www.tanach.us">Westminster Leningrad Codex</a> is now perhaps the most built-off version of the Hebrew Bible online.  The base texts (which may be used &#8220;without restriction&#8221;) are present in both commercial and non-commercial products.  The Open Siddur Project is using it both for its <a href="http://wiki.jewishliturgy.org/Demos">technology demonstrations</a> and as the basis of all biblical texts in the siddur.</p>
<p>There are precious few examples of free data in the Jewish community, even on the Internet.  There are copious examples of donation-funded organizations presenting primarily public domain data with new copyright claims.</p>
<p>Free data prevents the necessity of duplication of effort, which, in turn, prevents the community as a whole from unnecessarily wasteful spending.  Particularly for organizations with a social mission, its use is a win for everyone.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.org/2010/02/an-economic-argument-for-free-primary-data/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Invitation to Young Technologists</title>
		<link>http://opensiddur.org/2009/08/invitation-to-young-technologists/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=invitation-to-young-technologists</link>
		<comments>http://opensiddur.org/2009/08/invitation-to-young-technologists/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 18:26:13 +0000</pubDate>
		<dc:creator>Efraim Feinstein</dc:creator>
				<category><![CDATA[Project Development]]></category>
		<category><![CDATA[education]]></category>
		<category><![CDATA[open source]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=184</guid>
		<description><![CDATA[<p>The Open Siddur Project is a free and open source software project founded around a community of folk passionate about the siddur. We are developing an online collaborative publishing platform for crafting custom siddurim, for preserving the diversity of Jewish prayer traditions, and for sharing translations, commentary, t&#8217;fillot, meditations, and art in the siddur.</p> <p>The <span style="color:#777"> . . . &#8594; Read More: <a href="http://opensiddur.org/2009/08/invitation-to-young-technologists/">Invitation to Young Technologists</a></span>]]></description>
			<content:encoded><![CDATA[<p>The Open Siddur Project is a free and open source software project founded around a community of folk passionate about the siddur. We are developing an online collaborative publishing platform for crafting custom siddurim, for preserving the diversity of Jewish prayer traditions, and for sharing translations, commentary, t&#8217;fillot, meditations, and art in the siddur.</p>
<p>The Jewish Day School systems are filled with many talented students, and we would like to reach out to those interested in technology and computer science, particularly in high schools.  The Open Siddur Project offers an opportunity for these students to participate in a real free software and open source project that is also relevant to the entire Jewish community. We invite them to participate in development discussions, provide original research, learn and write programs in a number of computer languages, edit, proofread, and correct texts, and work with others of many different backgrounds, in a pluralistic Jewish context.</p>
<div>Students who participate will be treated like adults and will be expected to interact with the same level of <em>dereḥ</em><em> eretz </em>(common courtesy) as all the other participants in the Open Siddur.</p>
<p>If you are a teacher or school administrator interested in this project for your students, we would just like to ask that participation in the project never be compulsory, for example, that it never be used as a homework assignment or classroom exercise.</p></div>
<p>We will be happy to recognize the participation of your school or project represented by its volunteer programmers. To participate, please invite your students to fill out our survey form available at <a href="../join-us/">http://opensiddur.org/contribute/join-us/</a>.* To browse our websites please visit, <a href="../">http://opensiddur.org</a> and <a href="http://wiki.jewishliturgy.org/">http://wiki.jewishliturgy.org</a>. To join our discussion list directly, please visit <a href="http://groups.google.com/group/opensiddur-talk/">http://groups.google.com/group/opensiddur-talk/</a>. Please feel free to <a href="http://opensiddur.org/contact/" target="_self">contact us</a> via our contact form or via email for more information.</p>
<p>(*) While we are not a commercial entity, in case we ever do fall under the Children&#8217;s Online Privacy Protection Act of 1998, we avoid collecting personal information from students under the age of 13.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.org/2009/08/invitation-to-young-technologists/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

