<?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 Development Blog</title>
	<atom:link href="http://opensiddur.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://opensiddur.net</link>
	<description>craft your own Jewish prayer book</description>
	<lastBuildDate>Wed, 17 Feb 2010 04:32:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Development Status (02/15/2010)</title>
		<link>http://opensiddur.net/2010/02/development-status-15022010/</link>
		<comments>http://opensiddur.net/2010/02/development-status-15022010/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 01:39:30 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[status update]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=463</guid>
		<description><![CDATA[Open Siddur Project Development Status as of   February 2010/Adar 5770
Friends,
The communal project  of Jewish spirituality can only be improved through cooperation and  collaboration. The creative work used in our traditional liturgies is  the common  cultural heritage of the Jewish people. Most of this work resides in the  public domain. [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Open Siddur Project Development Status as of   February 2010/Adar 5770</strong></p>
<p>Friends,</p>
<p>The communal project  of Jewish spirituality can only be improved through cooperation and  collaboration. The creative work used in our traditional liturgies is  the common  cultural heritage of the Jewish people. Most of this work resides in the  public domain. The Open Siddur is your Siddur. Join the Open Siddur  Project  today and begin crafting and sharing the siddur you&#8217;ve always wanted.</p>
<p>This  development status update chronicles progress on the Open Siddur made  since our last update 11/11/2009. If you’d like to get news of Open  Siddur Project development as it occurs, make sure to follow <a href="http://twitter.com/opensiddur" target="_blank">@opensiddur</a> at Twitter, or join  the <a href="http://groups.google.com/group/opensiddur-announce" target="_blank">opensiddur-announce</a> email list.</p>
<p><em>Contributions </em>(Aharon, Anonymous, Gabriel,  Efraim, Eve, Daniel, John)</p>
<div style="padding-left: 30px;">Following  the contribution of Reb Zalman&#8217;s <a href="../../../2009/10/reb-zalmans-open-siddur-tehillat-hashem/">Siddur  Tehillat HaShem</a>, R. Daniel Brenner, executive director of  Birthright Israel Next, contributed a <a href="../../../2009/12/kaddish-by-rabbi-daniel-brenner/">Kaddish  prayer</a> that he composed in English. Check it out <a href="../../../2009/12/kaddish-by-rabbi-daniel-brenner/">here</a>.  Feel free to adapt and modify these works for yourself. They are  distributed with a <a href="http://www.creativecommons.org/licenses/by-sa/3.0" target="_blank">Creative  Commons 3.0 Share Alike By Attribution</a> license. (All derivative  works must show attribution to the original authors and must also be  distributed under the CC-BY-SA 3.0 license.)</p>
<p>John B. Hare of the <a href="http://www.sacred-texts.com/" target="_blank">Internet Sacred Text Archive</a> contributed the scans and auto-transcribed text of the 1917 JPS English  Translation of the TaNaKh. We are currently helping John release the  first ever free licensed digital text of the 1917 JPS TaNaKh translation  and have proofread the Book of Neḥemia and nearly 70% of Psalms. Please  help us complete this task by <a href="http://wiki.jewishliturgy.org/Transcribing_the_1917_JPS" target="_blank">proofreading  a few pages</a> &#8212; it&#8217;s a relatively easy way to begin working on the  Open Siddur Project.</p>
<p>John Hare also scanned and transcribed a  1915 edition of the <a href="http://www.sacred-texts.com/jud/spb/index.htm" target="_blank">Singer Siddur</a>,  an English translation based on Seligman Baer&#8217;s Seder Avodat Yisrael.  Thank you, John!</p>
<p><a href="http://wiki.jewishliturgy.org/Transcription" target="_blank">Transcription of  Seder Avodat Yisrael </a>has picked up since our last update. We have  transcribed 33 pages of the liturgy from Baer&#8217;s critical edition. Every  line of text transcribed is digitally liberated with the <a href="http://www.creativecommons.org/publicdomain/zero/1.0" target="_blank">Creative Commons Zero</a> (CC0) license for  free use in future siddurim. If you haven’t yet, register on the wiki  and start transcribing today. This is a great way to become fluent  typing Hebrew with <em>nikkudot</em> (vowels) &#8212; a real skill!</p>
<p>Gabriel   Wasserman contributed his transcription of many sections of the Seder  Avodat Yisrael that he had incorporated into his Maḥzor for Shabbat  Ḥanukkah. Thank you, Gabriel!</p>
<p>Efraim Feinstein acquired and  scanned a work of the Siddur Torah Ohr  (Nusaḥ HaAri/Lubavitch) an important siddur based on the text edited by  R. Shneur Zalman of Liadi. A partial digital transcription of the siddur  is already available on <a href="http://he.wikisource.org/wiki/%D7%A1%D7%99%D7%93%D7%95%D7%A8_%D7%AA%D7%95%D7%A8%D7%94_%D7%90%D7%95%D7%A8" target="_blank">Wikisource</a> and this scan will help us complete  that transcription and provide a source for proofreading it. Thanks  Efraim!</p>
<p>An anonymous contributor provided a text of the  Spanish-Portuguese  Nusaḥ. The text is currently formatted in the proprietary format of  DavkaWriter Platinum. Please let us know if you have a copy of this  software and if you can help us convert this document to an open  standard Unicode format.</p>
<p>If you have digitized any text of the  siddur or prepared a siddur that you&#8217;d like to share, please consider  contributing your work to the Open Siddur Project.</p>
</div>
<p><em>Software  Development </em>(Efraim, Ze&#8217;ev, Ilan, Raphael)</p>
<div style="padding-left: 30px;">We have now a functioning demonstration of  how we can display text encoded in JLPTEI XML on a webpage. Click <a href="http://wiki.jewishliturgy.org/Demos" target="_blank">here</a> for examples of  working Open Siddur technology.</p>
<p>An update to our demo is  forthcoming this week. License statements and contributor credits lists  are now being generated by the code, and both are mostly functional.   These should be incorporated in demo release 0.3.1 Generating a  bibliography correctly is a bit harder, and may have to wait for 0.4. We  are in the process of moving our Tanach to get its data directly from  the Westminster Leningrad Codex.  The process is almost complete, and  the new code will likely be in demo release 0.4.</p>
<p>Since our last  update, we&#8217;ve passed a few milestones, especially in our work on data  transforms. The major improvements we&#8217;ve made are the following:</p>
<ul>
<li>JLPTEI&#8217;s  <a href="http://wiki.jewishliturgy.org/Conditionals" target="_blank">conditional  inclusion feature</a></li>
<li>Parallel text alignment for <a href="http://wiki.jewishliturgy.org/Translations" target="_blank">translations</a></li>
<li>Generic  standoff <a href="http://wiki.jewishliturgy.org/Instructions_and_Notes" target="_blank">annotations</a>,  the basis for instructions, commentary, linkages, historical notation</li>
</ul>
<p>With  a lot of help from Ze&#8217;ev Clementson, cross platform build procedures  and instructions were tested; many build errors and documentation errors  were <a href="http://wiki.jewishliturgy.org/Intro_to_hacking" target="_blank">fixed</a>.</p>
<p>Ze&#8217;ev  has been checking in code to converting the STML formatted text of the  Singer Siddur provided by John B. Hare (see above) into a more easily  parsed XML representation. He&#8217;s now working on encoding this into JLPTEI  XML formatted text for integration into the Open Siddur&#8217;s database.  Ze&#8217;ev has also committed code for converting Strong&#8217;s Hebrew Dictionary  into JLPTEI XML for integration into the Open Siddur. (It&#8217;s currently  formatted in OSIS.) Ze&#8217;ev is currently working on the conversion of  David Troidl&#8217;s digitization of the Strong&#8217;s Biblical Hebrew dictionary  from OSIS to JLPTEI for integration into the Open Siddur.</p>
<p>Ilan Cohen committed an outline of the jQuery port of the transcription  interface. Thanks Ilan!</p>
<p>Some of the work we&#8217;re doing requires  expertise in the rules of Hebrew grammar and its effect on vowel  markings. Jonah Rank provided Joshua Jacobson&#8217;s rules written in  Chanting the Hebrew Bible for determining qamats qatan. Raphael Finkel  completed the first-pass qamats qatan/sheva na detection code.   That  code (currently written in Perl) needs to be integrated into our  infrastructure (mostly XQuery/XSLT; might be able to work in Java). The  transliteration engine used in Efraim&#8217;s early proof-of-concept Haggadah  is now incorporated into the code again.  It will need some tweaking  again once we integrate a system for indicating a definite sheva na in  the encoding, and it does not work properly unless the qamats qatan is  properly encoded).</p>
</div>
<p><em>Documentation</em> (Efraim,  Aharon, Ze&#8217;ev)</p>
<div style="padding-left: 30px;">We are still  looking for volunteers to just look over our documentation and help us  know how it reads and where we can make improvements. Anyone can freely  register to edit on our wiki.</p>
<p>Much thanks are due to Ze&#8217;ev  Clementson whose many questions posed on our discussion list helped us  clarify our documentation and fix bugs in our build processes.</p>
<p>Aharon  and Efraim, besides blogging on opensiddur.net,  they are also <a href="http://groups.google.com/group/jewish-tech/msg/b97320225bb29bc0" target="_blank">contributing</a> to the new <a href="http://groups.google.com/group/jewish-tech/" target="_blank">J-Tech</a> list set up by Dan Sieradski. If you&#8217;re a Jewish technologist, we  recommend this list as a useful space for sharing knowledge and ideas.</p>
</div>
<p><em>Organizational  Structure</em> (Aharon, Efraim)</p>
<div style="padding-left: 30px;">After  some feedback, we&#8217;ve made an effort to merge all project resources  under the Open Siddur Project banner. If you look closely, you&#8217;ll still  see the Jewish Liturgy Project. Hint: take a look at our XML encoding  documentation :)</p>
<p>Efraim and Aharon are looking into economic  models to keep this project  both free and sustainable in the long term.  One of these models is a  cooperative of contributors.  We are certainly looking for more input  here.</p>
<p>We are now <a href="http://www.razoo.com/story/The-Open-Siddur-Project-2" target="_blank">capable of  receiving tax deductible donations</a> via Razoo through a fiscal  sponsorship agreement with the United States 501(c)3 registered  non-profit, <a href="http://jewishcreativity.org" target="_blank">Center for Jewish Culture &amp; Creativity</a>. Money raised  this way can help us pay for our major operational expenses (server  costs, domain registration fees).</p>
</div>
<p><em>Communications and  Promotion</em> (Aharon)</p>
<div style="padding-left: 30px;">Aharon  gave a presentation at this year&#8217;s Limmud NY and pitched the Open Siddur  Project. Answering his question, what&#8217;s the siddur you&#8217;ve always  wanted, 11 year old Leora answered: &#8220;I&#8217;ve grown a lot since I was given  my first siddur in second grade, but I&#8217;m still using the same blue Shiloh siddur. I&#8217;d like to make a siddur that I can draw in, write my  own prayers, and share them with my friends.&#8221; Help the Open Siddur  Project bring Leora&#8217;s vision to fruition, there are <a href="../contribute/">many ways to contribute</a>.</p>
<p>We  now have two discussion email lists and an announcement email list.  Much of the volume on our old jewishliturgy-discuss list was focused on  software development. To avoid having our non-developer list members  tune out of the discussion, we thought it better to divide the list into  <a href="http://groups.google.com/group/opensiddur-talk" target="_blank">opensiddur-talk</a> and <a href="http://groups.google.com/group/opensiddur-tech" target="_blank">opensiddur-tech</a>.</p>
<p>The  <a href="http://groups.google.com/group/opensiddur-announce" target="_blank">opensiddur-announcement</a> list will be used mainly for sending out regular updates like this one.  Announcements will also be shared via twitter (149 followers) and our  facebook group (nearly 300 users).</p>
<p>Since last November we have  had 3 Open Siddur Open Chats at irc://irc.freenode.net/jewisliturgy .  During these chats we&#8217;ve talked shop with all sorts of curious folks,  software developers, liturgy researchers, and Jewish educators. The  format and medium of the communication (Internet Relay Chat) is proving  difficult for a number of participants and we&#8217;re investigating  alternatives. So far we&#8217;ve looked at DimDim and came away unimpressed.  Any suggestions for cross-platform group chat technology accessible to  users at no cost?</p>
<p>Thanks to quick action on the part of Azriel,  the Open Siddur Project now owns the opensiddur.org domain. Good work,  Azriel! :)</p>
<p>The logs of the chat are available on our wiki, <a href="http://wiki.jewishliturgy.org/IRC_Conference" target="_blank">here</a>.</p>
<p>Our  next Open Chat is scheduled for February 21st, 1pm EST/10am PST/8pm  Israel.</p>
<p>Aharon will be speaking on the Open Siddur at the <a href="http://www.ajrsem.org" target="_blank">Academy for Jewish  Religion</a> in Riverdale, March 15th.</p>
</div>
<p><em>Press</em> (Aharon, Efraim)</p>
<div style="padding-left: 30px;">Since our last  update in November, two major articles appeared in Jewish media  concerning the Open Siddur Project. Hadara Graubart&#8217;s &#8220;<a href="http://www.tabletmag.com/life-and-religion/21498/prayer-unbound/" target="_blank">Prayer  Unbound</a>&#8220;, in Tablet Magazine and Steve Lipman&#8217;s &#8220;<a href="http://www.thejewishweek.com/viewArticle/c36_a17662/News/New_York.html" target="_blank">Taking  Prayer Into Their Own Hands</a>&#8220;, in Jewish Week. Sociologist Dr.  Steven M. Cohen may have also been thinking of us when he wrote  concerning the use of New media by young Jewish innovators in an article  for the JPR Newsletter, &#8220;<a href="http://www.jpr.org.uk/news/detail.php?id=141" target="_blank">From Jewish people  to Jewish purpose: The new age of social innovation in American Jewish  life, and its implications for British Jewry</a>&#8220;:</p>
<div style="padding-left: 30px;">&#8220;The growth of Jewish culture may partly be  attributed to the expansion of the Internet and the decline in  production costs.  The Internet has allowed new music, videos and films  to be produced and distributed at almost no cost.  Much of the recent  Jewish innovation focuses on building websites, which typically empower  Jews to create their own Jewish lives on their own terms.  As the  Internet has become a two-way communications device, online innovations  often allow users to participate in interesting Jewish activities that  are free of any controlling authority.  Examples include online  facilities that allow people to create their own siddurim (prayer books)  or access midrashim  (Biblical commentaries) in ways that enable Jews  to discover traditional texts.&#8221;</div>
</div>
<p><em>Team Member  Updates</em> (Azriel, Aharon)</p>
<div style="padding-left: 30px;">Azriel  writes that this semester has kept him super busy and so hasn&#8217;t been  able to give as much as he&#8217;d like to the Open Siddur this semester.  Everyone here misses him.</p>
<p>Most of our developers are either  working full time or studying full time. Aharon&#8217;s fellowship at Yeshivat  Hadar is coming to a close in May and he&#8217;s been busy thinking about  where he can go next to help improve awareness, increase compassion, and  inspire creativity through Jewish spiritual techniques and  technologies. If you&#8217;re looking for someone <a href="http://aharon.varady.net/" target="_blank">multi-talented, capable, and visionary</a> all at once, reach out to him while he&#8217;s still available. Your Jewish  institution could hardly do better and you&#8217;d be supporting the Open  Siddur Project at the same time.</p>
</div>
<p>Wishing you a happy  and warm Adar,<br />
Aharon Varady<br />
Founder &amp; Co-director<br />
The Open Siddur Project<br />
<a href="../../../join-us">http://opensiddur.net/join-us/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2010/02/development-status-15022010/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Access, sharing, and innovation through digitization</title>
		<link>http://opensiddur.net/2010/02/access-sharing-and-innovation-through-digitization/</link>
		<comments>http://opensiddur.net/2010/02/access-sharing-and-innovation-through-digitization/#comments</comments>
		<pubDate>Sun, 14 Feb 2010 06:00:00 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Advocacy]]></category>
		<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[darim online]]></category>
		<category><![CDATA[empowerment]]></category>
		<category><![CDATA[free culture]]></category>
		<category><![CDATA[licensing]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=420</guid>
		<description><![CDATA[Over at Darim Online&#8217;s blog, Phillip Brodsky reflects on Apple&#8217;s release of the iPad and asks some leading questions concerning the future of the book with the &#8220;People of the Book&#8221;, similar to J.T. Waldman&#8217;s posts on JPS&#8217; blog last June and July last year. Considering e-readers and e-book formats, Brodsky asks,


How might the Jewish [...]]]></description>
			<content:encoded><![CDATA[<p>Over at <a href="http://jewpoint0.org/2010/02/10-for-2010-3-people-of-the-e-book" target="_blank">Darim Online</a>&#8217;s blog, Phillip Brodsky reflects on Apple&#8217;s release of the iPad and asks some leading questions concerning the future of the book with the &#8220;People of the Book&#8221;, similar to J.T. Waldman&#8217;s posts on JPS&#8217; blog last <a href="http://jpsblog.org/2009/06/the-book-vs-e-book-smackdown-are-you-ready-to-rumble/" target="_blank">June</a> and <a href="http://jpsblog.org/2009/07/traditional-book-vs-ebook-smackdown-round-two-ding" target="_blank">July</a> last year. Considering e-readers and e-book formats, Brodsky asks,</p>
<blockquote>
<ul>
<li>How might the Jewish community increase Jewish literacy as more  religious and educational resources become digitized in e-formats, and  thus become more easily disseminated and accessed?</li>
<li>Will prayer become more individualized as siddurs (prayer books)  become available to everyone and can be carried without adding any extra  bulk to a briefcase or book bag?</li>
<li>Will learning of Jewish texts attract new students as Torah and  Talmud become <a href="http://jpsinteractive.org/projects/tagged_tanakh" target="_blank">available in new formats</a>?</li>
<li>Will Jewish life become less expensive by saving on the purchase of  books at religious schools and day schools?</li>
<li>How might synagogues and JCCs build relationships beyond their walls  as sermons, newsletters and blog entries are sent to the palm of  constituents’ hands?</li>
<li>Will all Jews need a handheld device, like new students at <a href="http://www.nytimes.com/2008/08/21/technology/21iphone.html" target="_blank">some universities</a>, in order to fully participate in  all the community has to offer?</li>
</ul>
<p>How else might the Jewish world change as  it enters the digital realm? What’s your organization or community doing  to interact in the digital world?</p></blockquote>
<p>Here at the Open Siddur Project, we see the platform we&#8217;re developing as, yes, a means for improved dissemination and access &#8212; especially for illuminating the historical diversity of Judaism&#8217;s spiritual traditions enshrined in Jewish liturgy. But this is not our <em>raison d&#8217;etre</em>. There are already many who are sharing texts of the siddur online. <strong>What is novel for us is the opportunity for individuals and groups to collaborate with one another</strong>: creating, remixing, and sharing art and text, each a seed-like contribution grown in the fecund mulch of our common cultural and spiritual heritage. Speaking for myself, the question of whether Jews will be <em>davvening</em> (praying) from e-books in the future is thus something of a distraction from what is much more interesting &#8212; how digitization of the ingredients of the siddur and collaborative publishing platforms like the Open Siddur might empower a sense of personal ownership in the craft and creation of useful and beautiful tools for engaging in spiritual relationships.</p>
<p>Need it be argued that print media will ever be made entirely obsolete  for the <em>Am haSefer</em>,  or People of the Book? We are, after all, a  people who have enshrined in our laws the careful reproduction of our  seminal texts by a capable scribe using quill and ink on animal skin  parchment. I love Star  Trek and hate paper goods derived from felled trees, so I&#8217;m hopeful that in the  future we will at least be davvening from siddurim made from 100%  recycled bamboo and hemp based sustainable paper goods. iPhone possessing Jews, serious about the fulfillment of their thrice daily <em>t&#8217;fillah</em> obligations, are already davvening from siddur apps. Yet, I caution against any premise that assumes  digital media supplanting print media, in a sort of self-justifying march of technological progress.   Considering that conventions for sabbath  observance are well fixed in  the Jewish tradition, one could hardly  expect print formats to  disappear so long as there are Jews observing  traditional sabbath laws.  Saying this, I am certain that digitization  will improve print  resources used by Jews at any point during the week,  let alone Internet  or cloud-based resources — with one important caveat.  We need to think  seriously about how this material is licensed.</p>
<p>Efraim provided an insight into this issue with his <a href="./an-economic-argument-for-free-primary-data/" target="_self">economic argument for free primary data</a>. I&#8217;d like to add to what Efraim and I began to advocate publicly on the Jewish Tech list, <a href="http://groups.google.com/group/jewish-tech/msg/b97320225bb29bc0" target="_blank">here</a> in a criticism of Bar Ilan&#8217;s Responsa Project&#8217;s licensing of newly digitized historic works that are otherwise free and in the Public Domain.</p>
<p>The question of what formats improve access and dissemination is pressing. As cultural workers we should be interested in making access as inexpensive as possible to the source texts of Jewish culture. If we’re serious about this we will be mindful to use open standards and free culture licensing that allows others to build on top of and improve our work.</p>
<p>Digitization and networks provide the foundation for easy dissemination of cultural works. So much of the legacy of our cultural inheritance is already in the Public Domain, and thus, free, but bottled up in print media. The tragedy is that in the conversion from print to digital media, cultural workers are using closed standards and terms-of-use agreements which limit access to other cultural innovators. It is a real travesty when amazing and ambitious projects assume ownership of our common cultural heritage through onerous terms-of-use agreements. (See for example, Bar-Ilan&#8217;s Responsa Project or <a href="http://opensiddur.net/2009/10/free-as-in-freedom/" target="_blank">Davka Corp&#8217;s</a> license for using public domain texts they&#8217;ve digitized).</p>
<p>Cultures, including our own, breathe creativity and exhale innovation. We rely on the creative works bequeathed to us by earlier generations to remain rooted in our cultural identity. Synagogue members and kids in day schools, summer camps, youth orgs, and creative Jews working on their own can all benefit from our educational, cultural, and spiritual institutions cooperating with one another in sharing the bounty of our cultural heritage. As Jews, are we not all collaborating on a grand project of Torah learning, spiritual improvement, and tikkun olam? It’s time our cultural licensing choices reflect these profound intentions.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2010/02/access-sharing-and-innovation-through-digitization/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An Economic Argument for Free Primary Data</title>
		<link>http://opensiddur.net/2010/02/an-economic-argument-for-free-primary-data/</link>
		<comments>http://opensiddur.net/2010/02/an-economic-argument-for-free-primary-data/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 20:10:05 +0000</pubDate>
		<dc:creator>Efraim</dc:creator>
				<category><![CDATA[Advocacy]]></category>
		<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[economics]]></category>
		<category><![CDATA[free culture]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[semantic data]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=359</guid>
		<description><![CDATA[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.
When considering bringing old content online, both of these aspects are important.  A first level of digitization involves simply making data [...]]]></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.net/2010/02/an-economic-argument-for-free-primary-data/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Email list changes</title>
		<link>http://opensiddur.net/2010/02/email-list-changes/</link>
		<comments>http://opensiddur.net/2010/02/email-list-changes/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 01:39:38 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[communications]]></category>
		<category><![CDATA[email]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=353</guid>
		<description><![CDATA[In order to separate technical and non-technical discussion, the Open Siddur Project has changed the names and addresses of its discussion lists.  The new lists are:

opensiddur-announce: A read only list for project announcement postings
opensiddur-talk: General discussion list (replaces jewishliturgy-discuss)
opensiddur-tech: Technical discussion list
opensiddur-dev: Commit messages and issue reports (replaces jewishliturgy-devel)

The jewishliturgy-discuss and jewishliturgy-devel lists are [...]]]></description>
			<content:encoded><![CDATA[<p>In order to separate technical and non-technical discussion, the Open Siddur Project has changed the names and addresses of its discussion lists.  The new lists are:</p>
<ul>
<li><a href="http://groups.google.com/group/opensiddur-announce">opensiddur-announce</a>: A read only list for project announcement postings</li>
<li><a href="http://groups.google.com/group/opensiddur-talk">opensiddur-talk</a>: General discussion list (replaces jewishliturgy-discuss)</li>
<li><a href="http://groups.google.com/group/opensiddur-tech">opensiddur-tech</a>: Technical discussion list</li>
<li><a href="http://groups.google.com/group/opensiddur-dev">opensiddur-dev</a>: Commit messages and issue reports (replaces jewishliturgy-devel)</li>
</ul>
<p>The jewishliturgy-discuss and jewishliturgy-devel lists are no longer functional.  All old messages are archived on the new lists.  Members of jewishliturgy-discuss are now members of opensiddur-talk.  All committers should become members of opensiddur-tech.  Please update your bookmarks, mail filters, etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2010/02/email-list-changes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Illustrating the Open Siddur</title>
		<link>http://opensiddur.net/2010/01/illustrating-the-open-siddur/</link>
		<comments>http://opensiddur.net/2010/01/illustrating-the-open-siddur/#comments</comments>
		<pubDate>Sun, 17 Jan 2010 07:10:41 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[data flow]]></category>
		<category><![CDATA[flowchart]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=338</guid>
		<description><![CDATA[Since Lead Developer Efraim Feinstein drew up a helpful flowchart describing the technical architecture for the Open Siddur Project, I felt another flowchart might still be useful in illustrating how data flows between end users, collaboration groups, Jewish source texts, other free culture projects, and the goal of a more vibrant Jewish culture. So I [...]]]></description>
			<content:encoded><![CDATA[<p>Since Lead Developer Efraim Feinstein drew up a helpful flowchart describing the <a href="http://wiki.jewishliturgy.org/Architecture" target="_blank">technical architecture</a> for the Open Siddur Project, I felt another flowchart might still be useful in illustrating how data flows between end users, collaboration groups, Jewish source texts, other free culture projects, and the goal of a more vibrant Jewish culture. So I drew one up.</p>
<p>The following chart shows the flow of data within the project between end users, collaboration groups, Jewish source texts, other free culture projects, and the goal of a more vibrant Jewish culture.</p>
<p>The data flow starts in the upper right hand corner, with traditional<strong> Jewish source texts</strong> available in print and which are in the Public Domain due to their age. Some of these texts are already <strong>digitized</strong> and <strong>free</strong>. Compatible free culture and open source licensing enables these digitized texts to be  used in other <strong>open source projects</strong>, as well as included within the <strong>Open Siddur Project&#8217;s free digital library</strong>.</p>
<p>For texts that are not yet digitized, the Open Siddur Project is engaged in a process of <strong>transcription</strong>, <strong>proofreading</strong>, and <strong>encoding</strong>.  Through this process, the material in our digital library will be interlinked with each other and organized as a <strong>public database</strong>. Our use of a well documented open standard for encoding this material permits it to be efficiently served to our users and other open source projects over the Internet.</p>
<p><strong>Open Siddur Users</strong> with common interests can join <strong>collaboration groups</strong> to  advance the development of specific texts. Users engaged in transcribing, proofreading, and encoding texts comprise an important <strong>collaboration group</strong> within the Open Siddur Project, as they are contributing core material to this public database. Any user of the Open Siddur can join this group which operates consistent with our <a href="http://wiki.jewishliturgy.org/Mission_Statement" target="_blank">Mission Statement</a>. We envision other collaboration groups coalescing around <strong>translating</strong>, authoring, and/or transcribing texts that will be shared with free culture licensing. <strong> </strong></p>
<p><strong>Free culture licensing</strong> provides the legal framework for this  type of sharing to flourish. Material in our library  (texts, graphics, audio, and video) is open for editing and  remixing  by our users. Modifications, adaptations, and newly authored works can be shared  with other users or groups. An act of sharing requires acceptance of one  of the free culture licenses our project relies on (<a href="http://www.creativecommons.org/publicdomain/zero/1.0" target="_blank">CC0</a>, <a href="http://www.creativecommons.org/licenses/by/3.0" target="_blank">CC-BY</a>, and  <a href="http://www.creativecommons.org/licenses/by-sa/3.0" target="_blank">CC-BY-SA</a>).</p>
<p>We recognize that <em>davvening</em> (Jewish prayer) is as much a private experience as it is often enough (although not necessarily) framed within a communal setting.  For that  reason, the Open Siddur platform will support <strong>a user-private database</strong>,  offering users (and private collaboration groups) opportunities to limit  the sharing of their work in the public library. Privacy is what distinguishes the Open Siddur Project from a wiki devoted to collective work on the Siddur.</p>
<p>Once texts from the database are edited, ordered and remixed, our <strong>rendering technology</strong> will compile them into <strong>digital</strong> or <strong>custom printed</strong> formats suitable for reading, printing with on-demand printers, or further offline crafting.</p>
<p>Crafting a siddur is not only a matter of selecting, arranging, and modifying text.  A siddur also reflects the aesthetic of its maker.  Besides offering a selection of open source fonts and a rudimentary layout editor, we welcome the opportunity for <strong>book artists</strong>, <strong>book binders, and other consultants</strong> to get involved in the production process of siddurim. Our selection of licenses was considered carefully so that individuals producing or helping to produce siddurim using the Open Siddur can derive revenue through their efforts.</p>
<p>The project of Jewish spirituality is a matter of common interest and  private engagement. When Jewish individuals and collectives <strong>engage and share</strong> in the <strong>legacy  of their common cultural heritage</strong> what results is a more <strong>vibrant and vital Jewish culture</strong>.</p>
<p>The colors and shapes on the flowchart below are not self-explanatory, so here&#8217;s a key:</p>
<ul>
<li>Rectangles are <strong>Processes</strong>.</li>
<li>Rhomboids represent <strong>Data</strong>.</li>
<li>Curve-cut rectangles are <strong>Documents.</strong></li>
<li>Concave/convex-ended  rectangles are <strong>Databases.</strong></li>
<li><strong><span style="color: #ff6600;">Orange</span></strong> identifies work deriving from the Public Domain.</li>
<li> <strong><span style="color: #c8eb13;">Yellow</span> </strong>identifies work licensed with permissive copyright (free culture)  licensing.</li>
<li> <strong><span style="color: #0000ff;">Blue</span></strong> identifies public resources maintained by the Open Siddur Project  team. (Light blue identifies user/private resources within Open Siddur.)</li>
<li> <strong><span style="color: #339966;">Green</span></strong> represents external processes. (Dark green is other projects using  our public resources; light green are external resources for users; bright green represents a more vibrant Jewish culture.)</li>
</ul>
<p><a href="http://opensiddur.net/wp-content/uploads/2010/01/Aharons-Open-Siddur-Flowchart.png"><img class="alignnone size-full wp-image-333" title="Aharon's Open Siddur Flowchart" src="http://opensiddur.net/wp-content/uploads/2010/01/Aharons-Open-Siddur-Flowchart.png" alt="" width="757" height="685" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2010/01/illustrating-the-open-siddur/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome Jewish Week Readers!</title>
		<link>http://opensiddur.net/2010/01/welcome-jewish-week-readers/</link>
		<comments>http://opensiddur.net/2010/01/welcome-jewish-week-readers/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 21:25:15 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[Press]]></category>
		<category><![CDATA[Jewish Week]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=318</guid>
		<description><![CDATA[Once again, the Open Siddur Project has been mentioned in the press, this time by Steve Lipman in the Jewish Week.
The Open Siddur is a volunteer driven project to create a free resource for folks crafting their own siddur (Jewish prayer book). We intend to collaboratively build an archive of material that makes up  [...]]]></description>
			<content:encoded><![CDATA[<p>Once again, the Open Siddur Project has been mentioned in the press, this time by <a href="http://www.thejewishweek.com/viewArticle/c36_a17662/News/New_York.html" target="_blank">Steve Lipman in the Jewish Week</a>.</p>
<p>The Open Siddur is a volunteer driven project to create a <a href="http://freedomdefined.org/Definition" target="_blank">free</a> resource for folks crafting their own siddur (Jewish prayer book). We intend to collaboratively build an archive of material that makes up  the siddur &#8212; texts, translations, instructional material, commentaries,  essays, and other associated media.  Along with the archive, we are  building the software that can be used to put together the building blocks to customize and personalize the siddur. Ultimately, siddurim prepared from this content may be printed on your home printer, by on-demand print shop, or in cooperation with a book artist.</p>
<p>For more about our mission, <a href="http://opensiddur.net/about/">click here</a>.  To see some early technology <a href="http://wiki.jewishliturgy.org/Demos">demos, click here</a>. To learn move about how you can get involved in helping to build the Open Siddur, read on.</p>
<p>By &#8220;open,&#8221; we mean that our code and our texts are <a href="http://freedomdefined.org/Definition" target="_blank">free</a> to take under <a href="http://wiki.jewishliturgy.org/JewishLiturgyProject:Copyrights" target="_blank">permissive copyright licenses</a>. We are creating a community of folks passionate about the siddur and who express their passion by contributing material that can be used by others in the preparation of their own siddurim. This material could be historic or new, familiar or obscure. We seek to design a tool that will provide a resource to help those who  take Jewish spirituality seriously engage in their own spiritual  practice.</p>
<p>If you&#8217;d like to help us, take a look at the following opportunities to contribute (below), fill out our <a href="../../join-us/" target="_self">survey</a>, or just <a href="http://opensiddur.net/contact/" target="_self">contact us</a>. (Donations, if you like, <a href="http://www.razoo.com/story/The-Open-Siddur-Project-2" target="_blank">can be made</a> to this project via our fiscal sponsor the <a href="http://jewishcreativity.org" target="_blank">Center for Jewish Culture and Creativity</a>. )</p>
<table style="height: 535px;" border="1" width="547" rules="all">
<tbody>
<tr style="text-align: left;">
<th> If you &#8230;</th>
<th> then &#8230;</th>
</tr>
<tr style="padding-left: 30px;">
<td style="padding-left: 30px;">can <a title="Keyboard Setup/Hebrew" href="http://wiki.jewishliturgy.org/Keyboard_Setup/Hebrew">type in Hebrew with vowels</a>&#8230;</td>
<td style="padding-left: 30px;">try <a title="Transcription" href="http://wiki.jewishliturgy.org/Transcription">transcribing a line or a page from a historic siddur.</a></td>
</tr>
<tr style="padding-left: 30px;">
<td style="padding-left: 30px;">can proofread English text&#8230;</td>
<td style="padding-left: 30px;">try <a title="Transcription" href="http://wiki.jewishliturgy.org/Transcribing_the_1917_JPS">proofreading a page from an automatically transcribed English translation of the Tanach.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">have already written liturgy-related material&#8230;</td>
<td style="padding-left: 30px;"><a title="Submissions HOWTO" href="http://wiki.jewishliturgy.org/Submissions_HOWTO">contribute it to us.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">have access to public domain books and a high speed book scanner&#8230;</td>
<td style="padding-left: 30px;">try finding copies of or <a title="Scanning Guidelines" href="http://wiki.jewishliturgy.org/Scanning">scanning</a> from our <a title="Scans" href="http://wiki.jewishliturgy.org/Scans">list of wanted books.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code or document XML&#8230;</td>
<td style="padding-left: 30px;">proofread, debug, and/or provide examples for the <a title="JLPTEI" href="http://wiki.jewishliturgy.org/JLPTEI">JLPTEI</a> XML specification, improve validators using <a class="external text" title="http://en.wikipedia.org/wiki/ODD_%28One_Document_Does_it_all%29" rel="nofollow" href="http://en.wikipedia.org/wiki/ODD_%28One_Document_Does_it_all%29">TEI ODD</a> or <a class="external text" title="http://www.schematron.com" rel="nofollow" href="http://www.schematron.com">Schematron.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code in any language&#8230;</td>
<td style="padding-left: 30px;">help us write one-time transformations to convert contributed material into <a title="JLPTEI" href="http://wiki.jewishliturgy.org/JLPTEI">JLPTEI</a>.</td>
</tr>
<tr>
<td style="padding-left: 30px;">code in CSS &#8230;</td>
<td style="padding-left: 30px;">help us write rendering instructions for web browsers.</td>
</tr>
<tr>
<td style="padding-left: 30px;">code in Javascript&#8230;</td>
<td style="padding-left: 30px;">help us build our <a title="Architecture" href="http://wiki.jewishliturgy.org/Architecture">web application.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code in Java&#8230;</td>
<td style="padding-left: 30px;">help us build the <a title="Architecture" href="http://wiki.jewishliturgy.org/Architecture">compiler application</a> and/or choose and <a title="Target Survey" href="http://wiki.jewishliturgy.org/Target_Survey">improve existing rendering engines.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code in XSLT 2.0&#8230;</td>
<td style="padding-left: 30px;">help us write <a class="external text" title="http://shell.jewishliturgy.org/doc/code" rel="nofollow" href="http://shell.jewishliturgy.org/doc/code">transforms</a>.</td>
</tr>
<tr>
<td style="padding-left: 30px;">code in XQuery&#8230;</td>
<td style="padding-left: 30px;">help us write the toolkit API.</td>
</tr>
</tbody>
</table>
<p>For more details on our <a href="http://wiki.jewishliturgy.org/Milestones" target="_blank">development</a> and to get <a href="http://opensiddur.net/?s=development+status" target="_self">status updates</a>, please fill out our <a href="../../join-us/" target="_self">survey</a>. If you&#8217;d like to follow our developments closely and participate, then please join our <a href="http://groups.google.com/group/opensiddur-talk/" target="_blank">discussion list</a>, friend us on <a href="http://www.facebook.com/group.php?gid=107922647745" target="_blank">Facebook</a>, follow us on <a href="http://twitter.com/opensiddur" target="_blank">Twitter</a>, and check out our <a href="http://wiki.jewishliturgy.org" target="_blank">development wiki </a>(our current storehouse for documentation and texts).</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2010/01/welcome-jewish-week-readers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Architecture of the Open Siddur</title>
		<link>http://opensiddur.net/2009/12/architecture-of-the-open-siddur/</link>
		<comments>http://opensiddur.net/2009/12/architecture-of-the-open-siddur/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 18:02:17 +0000</pubDate>
		<dc:creator>Efraim</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[data flow]]></category>
		<category><![CDATA[flowchart]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=272</guid>
		<description><![CDATA[Lead developer, Efraim Feinstein, recently contributed this helpful diagram of Open Siddur&#8217;s architecture.

]]></description>
			<content:encoded><![CDATA[<p>Lead developer, Efraim Feinstein, recently contributed this helpful diagram of Open Siddur&#8217;s architecture.</p>
<p><a href="http://wiki.jewishliturgy.org/Architecture"><img src="http://wiki.jewishliturgy.org/w/images/2/2c/IODiagram.png" alt="" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2009/12/architecture-of-the-open-siddur/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kaddish by Rabbi Daniel Brenner</title>
		<link>http://opensiddur.net/2009/12/kaddish-by-rabbi-daniel-brenner/</link>
		<comments>http://opensiddur.net/2009/12/kaddish-by-rabbi-daniel-brenner/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 18:58:53 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Contributions]]></category>
		<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[Birthright Israel Next]]></category>
		<category><![CDATA[Daniel Brenner]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=261</guid>
		<description><![CDATA[A Kaddish
Make the God-name big.
Big and holy.
Do it in this world,
This creation sprung from consciousness,
And bring some order to this.
Do it fast, soon, in our lives, in the days ahead, in the life of the
people we call home.
Everybody join with me: May the name be blessed forever and ever!
Yes, blessed.
Blessed, whispered, sung out, shouted, honored, [...]]]></description>
			<content:encoded><![CDATA[<p>A Kaddish</p>
<p>Make the God-name big.</p>
<p>Big and holy.</p>
<p>Do it in this world,</p>
<p>This creation sprung from consciousness,</p>
<p>And bring some order to this.</p>
<p>Do it fast, soon, in our lives, in the days ahead, in the life of the<br />
people we call home.</p>
<p>Everybody join with me: May the name be blessed forever and ever!</p>
<p>Yes, blessed.</p>
<p>Blessed, whispered, sung out, shouted, honored, this holy name.</p>
<p>The name is beyond any song, poem, or comforting words we could ever  speak.</p>
<p>Eveybody say: That&#8217;s the truth!</p>
<p>May a big peace descend from the heavens, a life-giving peace for all<br />
of us, for our beloved people,</p>
<p>Let everybody say: May it be true!</p>
<p>Make that peace in the heavens, great peacemaker, great One who brings<br />
wholeness to our people.</p>
<p>Stop.</p>
<p>Everybody pray:</p>
<p>May it be true.</p>
<p><a href="http://www.auburnsem.org/about/RabbiDanielBrenner.htm" target="_blank"></a><a href="http://opensiddur.net/wp-content/uploads/2009/12/rabbi-daniel-brenner.jpg"><img class="alignleft size-full wp-image-263" title="rabbi daniel brenner" src="http://opensiddur.net/wp-content/uploads/2009/12/rabbi-daniel-brenner.jpg" border="10" alt="rabbi daniel brenner" width="180" height="269" border="10" /></a>Rabbi Daniel Brenner, executive director of Birthright Israel Next, contributed a Kaddish to the Open Siddur Project. It is now part of the cultural commons of the Jewish people by virtue of this text being contributed with a CC-BY-SA license. Thank you, Rabbi Brenner!</p>
<p>Rabbi Brenner submitted this with the CC-BY-SA license by including the following text.</p>
<table border="0">
<tbody>
<tr style="text-align: center;">
<td style="width: 90px;"><img src="http://upload.wikimedia.org/wikipedia/commons/thumb/7/79/CC_some_rights_reserved.svg/90px-CC_some_rights_reserved.svg.png" border="0" alt="Creative Commons license" width="90" height="36" /><br />
<img src="http://upload.wikimedia.org/wikipedia/commons/thumb/1/11/Cc-by_new_white.svg/24px-Cc-by_new_white.svg.png" border="0" alt="Creative Commons Attribution" width="24" height="24" /> <img src="http://upload.wikimedia.org/wikipedia/commons/thumb/2/29/Cc-sa.svg/24px-Cc-sa.svg.png" border="0" alt="Creative Commons Share Alike" width="24" height="24" /></td>
<td>
<blockquote><p>I am the original author of the attached Kaddish and I am licensing the following attachments  under the Creative Commons Attribution-ShareAlike 3.0 Unported License. Attribution may be given as &#8216;Contributors to the Jewish Liturgy Project/Open Siddur&#8217;, with the author&#8217;s name(s) Rabbi Daniel Brenner included in the contributors list.</p></blockquote>
</td>
</tr>
</tbody>
</table>
<p>Take it, use, add to it, and remix it. Just make certain to <a href="http://www.creativecommons.org/licenses/by-sa/3.0" target="_blank">abide by the  requirements</a> of CC-BY-SA.</p>
<p>If you would like to contribute a translation, commentary, <a href="http://wiki.jewishliturgy.org/Transcription:Main_Page" target="_blank">transcription</a>, meditation, or any other content to the Open Siddur, please see our <a href="http://wiki.jewishliturgy.org/Submissions_HOWTO" target="_blank">helpful guide</a> to doing this. (Once we have the Open Siddur web application fully built, submitting and sharing content should be even easier.)</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2009/12/kaddish-by-rabbi-daniel-brenner/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome Tablet Readers</title>
		<link>http://opensiddur.net/2009/12/how-you-can-help-us/</link>
		<comments>http://opensiddur.net/2009/12/how-you-can-help-us/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 02:24:40 +0000</pubDate>
		<dc:creator>Aharon</dc:creator>
				<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[Press]]></category>
		<category><![CDATA[volunteering]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=235</guid>
		<description><![CDATA[What a great morning! We&#8217;re honored to have our project the focus of an article in Tablet.
The Open Siddur is a volunteer driven project to create a free resource for folks crafting their own siddur (Jewish prayer book). We intend to collaboratively build an archive of material that makes up  the siddur &#8212; texts, [...]]]></description>
			<content:encoded><![CDATA[<p>What a great morning! We&#8217;re honored to have our project the focus of an <a href="http://www.tabletmag.com/life-and-religion/21498/prayer-unbound/" target="_blank">article in Tablet</a>.</p>
<p>The Open Siddur is a volunteer driven project to create a <a href="http://freedomdefined.org/Definition" target="_blank">free</a> resource for folks crafting their own siddur (Jewish prayer book). We intend to collaboratively build an archive of material that makes up  the siddur &#8212; texts, translations, instructional material, commentaries,  essays, and other associated media.  Along with the archive, we are  building the software that can be used to put together the building  blocks to customize and personalize the siddur. Ultimately, siddurim prepared from this content will be printed with either an on-demand printer or else in cooperation with a book artist.</p>
<p>By &#8220;open,&#8221; we mean that our code and our texts are <a href="http://freedomdefined.org/Definition" target="_blank">free</a> to take under <a href="http://wiki.jewishliturgy.org/JewishLiturgyProject:Copyrights" target="_blank">permissive copyright licenses</a>. We are creating a community of folks passionate about the siddur and who express their passion by contributing material that can be used by others in the preparation of their own siddurim. This material could be historic or new, familiar or obscure. We seek to design a tool that will provide a resource to help those who  take Jewish spirituality seriously engage in their own spiritual  practice.</p>
<p>If you&#8217;d like to help us, take a look at the following opportunities to contribute (below), fill out our <a href="../../join-us/" target="_self">questionnaire</a>, or just straight out <a href="http://opensiddur.net/contact/" target="_self">contact us</a>. (Donations, if you like, <a href="http://www.razoo.com/story/The-Open-Siddur-Project-2" target="_blank">can be made</a> to this project via our fiscal sponsor the <a href="http://jewishcreativity.org" target="_blank">Center for Jewish Culture and Creativity</a>. )</p>
<table style="height: 535px;" border="1" width="547" rules="all">
<tbody>
<tr style="text-align: left;">
<th> If you &#8230;</th>
<th> then &#8230;</th>
</tr>
<tr style="padding-left: 30px;">
<td style="padding-left: 30px;">can <a title="Keyboard Setup/Hebrew" href="http://wiki.jewishliturgy.org/Keyboard_Setup/Hebrew">type in Hebrew with vowels</a>&#8230;</td>
<td style="padding-left: 30px;">try <a title="Transcription:Main Page" href="http://wiki.jewishliturgy.org/Transcription:Main_Page">transcribing a line or a page from a historic siddur.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">have already written liturgy-related material&#8230;</td>
<td style="padding-left: 30px;"><a title="Submissions HOWTO" href="http://wiki.jewishliturgy.org/Submissions_HOWTO">contribute it to us.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">have access to public domain books and a high speed book scanner&#8230;</td>
<td style="padding-left: 30px;">try <a title="Transcription:Scanning Guidelines" href="http://wiki.jewishliturgy.org/Transcription:Scanning_Guidelines">scanning</a> from our <a title="Brainstorm session" href="http://wiki.jewishliturgy.org/Brainstorm_session#Siddurim_to_transcribe">list of wanted books.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code or document XML&#8230;</td>
<td style="padding-left: 30px;">proofread, debug, and/or provide examples for the <a title="JLPTEI" href="http://wiki.jewishliturgy.org/JLPTEI">JLPTEI</a> XML specification, improve validators using <a class="external text" title="http://en.wikipedia.org/wiki/ODD_%28One_Document_Does_it_all%29" rel="nofollow" href="http://en.wikipedia.org/wiki/ODD_%28One_Document_Does_it_all%29">TEI ODD</a> or <a class="external text" title="http://www.schematron.com" rel="nofollow" href="http://www.schematron.com">Schematron.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code in any language&#8230;</td>
<td style="padding-left: 30px;">help us write one-time transformations to convert contributed material into <a title="JLPTEI" href="http://wiki.jewishliturgy.org/JLPTEI">JLPTEI</a>.</td>
</tr>
<tr>
<td style="padding-left: 30px;">code in CSS &#8230;</td>
<td style="padding-left: 30px;">help us write rendering instructions for web browsers.</td>
</tr>
<tr>
<td style="padding-left: 30px;">code in Javascript&#8230;</td>
<td style="padding-left: 30px;">help us build our <a title="Architecture" href="http://wiki.jewishliturgy.org/Architecture">web application.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code in Java&#8230;</td>
<td style="padding-left: 30px;">help us build the <a title="Architecture" href="http://wiki.jewishliturgy.org/Architecture">compiler application</a> and/or choose and <a title="Target Survey" href="http://wiki.jewishliturgy.org/Target_Survey">improve existing rendering engines.</a></td>
</tr>
<tr>
<td style="padding-left: 30px;">code in XSLT 2.0&#8230;</td>
<td style="padding-left: 30px;">help us write <a class="external text" title="http://shell.jewishliturgy.org/doc/code" rel="nofollow" href="http://shell.jewishliturgy.org/doc/code">transforms</a>.</td>
</tr>
<tr>
<td style="padding-left: 30px;">code in XQuery&#8230;</td>
<td style="padding-left: 30px;">help us write the toolkit API.</td>
</tr>
</tbody>
</table>
<p>For more details on our <a href="http://wiki.jewishliturgy.org/Milestones" target="_blank">development</a> and to get <a href="http://opensiddur.net/?s=development+status" target="_self">status updates</a>, fill out our <a href="../../join-us/" target="_self">questionnaire</a> and you&#8217;ll be added to our mailing list. If you&#8217;d like to follow our developments closely and participate, then please join our <a href="http://groups.google.com/group/opensiddur-talk/" target="_blank">discussion list</a>, friend us on <a href="http://www.facebook.com/group.php?gid=107922647745" target="_blank">Facebook</a>, follow us on <a href="http://twitter.com/opensiddur" target="_blank">Twitter</a>, and check out our <a href="http://wiki.jewishliturgy.org" target="_blank">development wiki </a>(our current storehouse for documentation and texts).</p>
<p><strong>Update 12/3/09</strong>: Broken links in the table have been corrected.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2009/12/how-you-can-help-us/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Jewish Content, Free Culture and &#8220;Content Compatibility&#8221;</title>
		<link>http://opensiddur.net/2009/11/jewish-content-free-culture-and-content-compatibility/</link>
		<comments>http://opensiddur.net/2009/11/jewish-content-free-culture-and-content-compatibility/#comments</comments>
		<pubDate>Thu, 19 Nov 2009 14:22:52 +0000</pubDate>
		<dc:creator>Efraim</dc:creator>
				<category><![CDATA[Advocacy]]></category>
		<category><![CDATA[Open Siddur]]></category>
		<category><![CDATA[free culture]]></category>
		<category><![CDATA[licensing]]></category>

		<guid isPermaLink="false">http://opensiddur.net/?p=231</guid>
		<description><![CDATA[This post is primarily directed at Jewish content providers  and anyone thinking about becoming one.
If you&#8217;re in the Jewish content world, it&#8217;s quite possible that some day, you will develop  content that is relevant not only to you and your users directly, but to the wider Jewish community.  Because the siddur is so wide [...]]]></description>
			<content:encoded><![CDATA[<p><i>This post is primarily directed at Jewish content providers  and anyone thinking about becoming one.</i></p>
<p>If you&#8217;re in the Jewish content world, it&#8217;s quite possible that some day, you will develop  content that is relevant not only to you and your users directly, but to the wider Jewish community.  Because the siddur is so wide ranging in scope, it may even be relevant to the Open  Siddur Project in particular.  Conversely, I hope that some of the essays  contributed to the Open Siddur Project would be relevant to your site(s).  By &#8220;content compatibility,&#8221; I  mean the ability to post content generated for one site onto the other  and then further develop it.  It is possible for content to be one-way  compatible or bidirectionally compatible.</p>
<p>Disclaimer: I am not a lawyer and this is not legal advice.</p>
<p>Issues of content compatibility arise out of <a title="copyright law" href="http://en.wikipedia.org/wiki/Copyright" target="_blank">copyright law</a>.  All  literary or creative works fixed in a tangible form (including  electronic texts on the web) are covered under copyright law.  Copyright  law reserves certain rights to authors or owners of works.  These rights  include the rights to copy a document, to share it with others, to make  changes to it, and to distribute the changed document.  For a work  written by an individual in the US today, these rights are exclusive to  the copyright owner until 70 years after the author&#8217;s death.  Permission  must be obtained from the copyright owner in order to do any of the  activities covered under copyright law with his or her work.  There are  certain exceptions to copyright, including &#8220;<a title="fair use" href="http://en.wikipedia.org/wiki/Fair_use"  target="_blank">fair use</a>,&#8221; which allows  reprinting short excerpts of works under copyright for purposes such as  academic discussion.  Fair use will likely cover most of your everyday  uses of copyrighted works.  There are many useful online and offline  resources that go into more detail.</p>
<p>Content compatibility becomes a major issue when a text is developed  collaboratively.  If all contributing authors do not agree to a  framework for sharing their contributions, the site relies on an  &#8220;<a href="http://en.wikipedia.org/wiki/Implied_license" target="_blank">implied license</a>&#8221; from  the contributors to the site owner.  The implied license covers normal  operation of the site, and little else.  It most likely does not include  copying from one site and placing the content in another.</p>
<p>Aside from relying on an implied license, some websites attempt to use  &#8220;parasitic&#8221; licenses hidden in their terms of use.  These licenses  attempt to claim maximum rights from the contributor, while giving a  bare minimum back to the community.  Sometimes, this is intentional.  Sometimes, it&#8217;s accidental.  Some sites&#8217; operators blindly copy fill-in-the-blanks terms of use templates that assume that the content is to be kept proprietary.  One example from a popular site that provides source sheets and other learning material is presented here:</p>
<blockquote>
<p>
<b>Limited Right to Use. </b><br />
The viewing, printing or downloading of any content, graphic, form or  document from the Site grants you only a limited, nonexclusive license  for use solely by you for your own personal use and not for  republication, distribution, assignment, sublicense, sale, preparation  of derivative works or other use. No part of any content, form or  document may be reproduced in any form or incorporated into any  information retrieval system, electronic or mechanical, other than for  your personal use (but not for resale or redistribution).
</p>
<p>
<b>Editing, Deleting and Modification.</b><br />
We reserve the right in our sole discretion to edit or delete any  documents, information or other content appearing on the Site.
</p>
</blockquote>
<p>and the rather dangerous (and dubious, emphasis added):</p>
<blockquote>
<p>
<b>Use of Information.</b><br />
We reserve the right, and you authorize us, to the use and assignment of  all information regarding Site uses by you and all information provided  by you in any manner consistent with our Privacy Policy. <em>All  remarks, suggestions, ideas, graphics, or other information communicated  by you to us through the Site (collectively, the &#8220;Submission&#8221;) will  forever be the property of <b>SITE NAME</b>.</em> <b>SITE NAME</b> will not be  required to treat any Submission as confidential, and will not be liable  for any ideas for its business (including without limitation, product,  service or advertising ideas) and will not incur any liability as a  result of any similarities that may appear in future <b>SITE NAME</b>  products, services or operations. <em>Without limitation, <b>SITE NAME</b> will have exclusive ownership of all present and future existing  rights to the Submission of every kind and nature everywhere.</em>  <b>SITE NAME</b> will be entitled to use the Submission for any commercial  or other purpose whatsoever, without compensation to you or any other  person sending the Submission. You acknowledge that you are responsible  for whatever material you submit, and you, not <b>SITE NAME</b>, have  full responsibility for the message, including its legality,  reliability, appropriateness, originality, and copyright.
</p>
</blockquote>
<p>These broad claims of <strong>ownership(!)</strong> rights over submitted content work  entirely to the benefit of the contract author, and against the benefit  of the remainder of the community.  One also may question whether a site  which serves source sheets and audio recordings of prayer texts is  compromising its own potential by limiting reproduction of its materials  to personal use.  A copyright-conscious contributor (such as myself)  would refuse to submit to such a site, fearing that his or her own  future use of his or her own material would be threatened by the  (legally questionable) claim of transfer of ownership.</p>
<p>For an existing forum, if the operator simply removes draconian terms of use and returns the site to an implied license structure or the terms are kept in place, the following scenarios are still possible:</p>
<ul>
<li>Material from the project is relevant in its entirety to a  free culture project (defined below) such as The Open Siddur Project.   It is not covered by fair use.  We take terms of use at their word.  We  can&#8217;t use it without asking permission for all required rights from the  copyright owner(s).  We either need to answer the legal question as to  whether a transfer of ownership can be extracted by a terms of use  agreement or track down every contributor.</li>
<li>Material from another free culture project (such as The Open Siddur  Project, Wikipedia, or Wikisource) is relevant in its entirety to the  project.  The material cannot be copied wholesale and  further developed without playing by the rules of free culture (see below).</li>
<li>Fifty years from now, everyone who wrote for the project has moved on to other stages in life and other projects.  The site or project as an institution may not exist anymore, and nobody knows who are the  heirs of its &#8220;intellectual property.&#8221;  Some of the material is still  circulating, still relevant, and still under copyright.  Even if the  original intent of the authors were never to sue anyone for use of the  material, the future researcher does not know that because either no  policy was written down or the written policy indicates that his or her  usage rights are limited.  The material may become unpublishable and  lost forever.  This problem is known as the <a href="http://en.wikipedia.org/wiki/Orphan_works">orphan works</a> problem  .</li>
</ul>
<p>The free culture community has developed mechanisms to make sharing and  collaborative development easier.  The <a href="http://freedomdefined.org/Definition" target="_blank">principles that define works of  free culture</a> are:<br />
1. the freedom to use the work and enjoy the benefits of using it<br />
2. the freedom to study the work and to apply knowledge acquired from it<br />
3. the freedom to make and redistribute copies, in whole or in part, of  the information or expression<br />
4. the freedom to make changes and improvements, and to distribute  derivative works<br />
Note that these freedoms do not discriminate on the <a href="http://www.opensource.org/docs/definition.php" target="_blank">basis of endeavor</a>, and all free culture  works allow creation of derivative works and commercial use.</p>
<p>The free culture community is a group of individuals who believe that  culturally-relevant works of their creation should have minimal legal  impediments to their dissemination and further development.  The  mechanism involves use of copyright licenses, which work by having each  contributor agree to release his or her work under a given set of terms  at the time of submission.  All collaborating authors may then use,  share and build on the work using the rights given by the original  author.  Users may share, modify, publish, and distribute the work on  their own without asking for permission, as long as they comply with the  liberal terms of the license.  None of the free culture licenses  transfer ownership of the work.  An author may later decide to release  his or her own work in another forum under a different set of terms  (including &#8220;all rights reserved&#8221; copyright).</p>
<p>A major organization responsible for maintaining the legal framework of  the free culture community is <a href="http://creativecommons.org/" target="_blank">Creative Commons</a>.  Because some authors want to retain  different sets of rights over their works, Creative Commons has  developed a set of copyright licenses that are widespread, well known,  and well understood.  Their licenses are divided by sets of terms (note:  this is just a summary of the most important features.  Read the full  legal code before making a decision.):</p>
<ul>
<li>Creative Commons Zero &#8211; &#8220;no rights reserved&#8221; &#8211; essentially, an  internationally-applicable public domain declaration, indicating that  the author surrenders all rights to the work.</li>
<li>Creative Commons Attribution &#8211; The work may be copied, modified, and  distributed, as long as attribution is maintained and reference is made  to the license.</li>
<li>Creative Commons Attribution-ShareAlike &#8211; The work may be copied,  modified, and distributed, as long as attribution is maintained and  reference is made to the license, and all derivatives of the work are  also released under the same terms.</li>
</ul>
<p>Creative Commons also offers some licenses with <strong><span>*</span>non free culture<span>*</span></strong> terms  (in combination with the Attribution and/or ShareAlike terms):</p>
<ul>
<li>NonCommercial &#8211; No commercial use.  Use of this term will also place  severe limits on the work&#8217;s use in the future, both by you and your users.</li>
<li>NoDerivs &#8211; The work may not be changed from its original version.  Use  of this term will completely curtail communal development to the same  degree as &#8220;all rights reserved&#8221; copyright.</li>
</ul>
<p>Wikipedia and Wikimedia Commons, the largest free culture projects, have  chosen the Creative Commons Attribution-ShareAlike 3.0 license for their  material.</p>
<p>The Open Siddur Project has a somewhat more complex licensing structure,  in which works that originally derive from the public domain are  released with no rights reserved (Creative Commons Zero); other original  works (such as translations and commentaries) may also be released under  either Creative Commons Attribution 3.0 or Attribution-ShareAlike 3.0,  at the discretion of the author.  A combined work retains the licensing  properties of the most restrictive of the set of the licensing terms of  its included components.</p>
<p>In many cases, the Open Siddur Project&#8217;s use of Creative Commons  licenses makes one-way compatibility from the Open Siddur Project to most other projects a given.  In most cases, attribution must be  maintained; if the essay of interest has a ShareAlike licensing term,  the derivative essay would also have to be released under the same terms.</p>
<p>In the other direction, the Open Siddur Project cannot currently copy  and distribute works derived from sites with no explicit policy (or an explicit proprietary policy) because of their &#8220;all rights reserved&#8221; copyrights.</p>
<p>Because securing rights requires the consent of all contributing  authors, it is best to approach these issues at the start of a project  before accepting contributions from large numbers of authors.</p>
<p>Joining the free culture community involves surrendering some control  over submitted works.  In exchange, the entire community benefits from  more widespread dissemination of knowledge.  In addition to simple  propagation of ideas, free culture also allows works to develop in novel  ways that the authors could not have imagined.  I hope that you will  consider joining the Free Culture community in building enduring, truly  collaborative resources for the Jewish community.</p>
<p>We hope to begin a conversation about content compatibility with the world of online Jewish content providers.  If you&#8217;re interested in joining it, talk to us.</p>
]]></content:encoded>
			<wfw:commentRss>http://opensiddur.net/2009/11/jewish-content-free-culture-and-content-compatibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
