Skip to content

Illustrating the Open Siddur

17-Jan-10

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 drew one up.

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.

The data flow starts in the upper right hand corner, with traditional Jewish source texts available in print and which are in the Public Domain due to their age. Some of these texts are already digitized and free. Compatible free culture and open source licensing enables these digitized texts to be  used in other open source projects, as well as included within the Open Siddur Project’s free digital library.

For texts that are not yet digitized, the Open Siddur Project is engaged in a process of transcription, proofreading, and encoding. Through this process, the material in our digital library will be interlinked with each other and organized as a public database. 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.

Open Siddur Users with common interests can join collaboration groups to advance the development of specific texts. Users engaged in transcribing, proofreading, and encoding texts comprise an important collaboration group 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 Mission Statement. We envision other collaboration groups coalescing around translating, authoring, and/or transcribing texts that will be shared with free culture licensing.

Free culture licensing 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 (CC0, CC-BY, and CC-BY-SA).

We recognize that davvening (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 a user-private database, 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.

Once texts from the database are edited, ordered and remixed, our rendering technology will compile them into digital or custom printed formats suitable for reading, printing with on-demand printers, or further offline crafting.

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 book artists, book binders, and other consultants 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.

The project of Jewish spirituality is a matter of common interest and private engagement. When Jewish individuals and collectives engage and share in the legacy of their common cultural heritage what results is a more vibrant and vital Jewish culture.

The colors and shapes on the flowchart below are not self-explanatory, so here’s a key:

  • Rectangles are Processes.
  • Rhomboids represent Data.
  • Curve-cut rectangles are Documents.
  • Concave/convex-ended rectangles are Databases.
  • Orange identifies work deriving from the Public Domain.
  • Yellow identifies work licensed with permissive copyright (free culture) licensing.
  • Blue identifies public resources maintained by the Open Siddur Project team. (Light blue identifies user/private resources within Open Siddur.)
  • Green 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.)

Welcome Jewish Week Readers!

13-Jan-10

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 the siddur — 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.

For more about our mission, click here. To see some early technology demos, click here. To learn move about how you can get involved in helping to build the Open Siddur, read on.

By “open,” we mean that our code and our texts are free to take under permissive copyright licenses. 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.

If you’d like to help us, take a look at the following opportunities to contribute (below), fill out our survey, or just contact us. (Donations, if you like, can be made to this project via our fiscal sponsor the Center for Jewish Culture and Creativity. )

If you … then …
can type in Hebrew with vowels try transcribing a line or a page from a historic siddur.
can proofread English text… try proofreading a page from an automatically transcribed English translation of the Tanach.
have already written liturgy-related material… contribute it to us.
have access to public domain books and a high speed book scanner… try finding copies of or scanning from our list of wanted books.
code or document XML… proofread, debug, and/or provide examples for the JLPTEI XML specification, improve validators using TEI ODD or Schematron.
code in any language… help us write one-time transformations to convert contributed material into JLPTEI.
code in CSS … help us write rendering instructions for web browsers.
code in Javascript… help us build our web application.
code in Java… help us build the compiler application and/or choose and improve existing rendering engines.
code in XSLT 2.0… help us write transforms.
code in XQuery… help us write the toolkit API.

For more details on our development and to get status updates, please fill out our survey. If you’d like to follow our developments closely and participate, then please join our discussion list, friend us on Facebook, follow us on Twitter, and check out our development wiki (our current storehouse for documentation and texts).

Architecture of the Open Siddur

18-Dec-09

Lead developer, Efraim Feinstein, recently contributed this helpful diagram of Open Siddur’s architecture.

Kaddish by Rabbi Daniel Brenner

10-Dec-09

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, this holy name.

The name is beyond any song, poem, or comforting words we could ever speak.

Eveybody say: That’s the truth!

May a big peace descend from the heavens, a life-giving peace for all
of us, for our beloved people,

Let everybody say: May it be true!

Make that peace in the heavens, great peacemaker, great One who brings
wholeness to our people.

Stop.

Everybody pray:

May it be true.

rabbi daniel brennerRabbi 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!

Rabbi Brenner submitted this with the CC-BY-SA license by including the following text.

Creative Commons license
Creative Commons Attribution Creative Commons Share Alike

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 ‘Contributors to the Jewish Liturgy Project/Open Siddur’, with the author’s name(s) Rabbi Daniel Brenner included in the contributors list.

Take it, use, add to it, and remix it. Just make certain to abide by the requirements of CC-BY-SA.

If you would like to contribute a translation, commentary, transcription, meditation, or any other content to the Open Siddur, please see our helpful guide to doing this. (Once we have the Open Siddur web application fully built, submitting and sharing content should be even easier.)

Welcome Tablet Readers

02-Dec-09

What a great morning! We’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 — 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.

By “open,” we mean that our code and our texts are free to take under permissive copyright licenses. 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.

If you’d like to help us, take a look at the following opportunities to contribute (below), fill out our questionnaire, or just straight out contact us. (Donations, if you like, can be made to this project via our fiscal sponsor the Center for Jewish Culture and Creativity. )

If you … then …
can type in Hebrew with vowels try transcribing a line or a page from a historic siddur.
have already written liturgy-related material… contribute it to us.
have access to public domain books and a high speed book scanner… try scanning from our list of wanted books.
code or document XML… proofread, debug, and/or provide examples for the JLPTEI XML specification, improve validators using TEI ODD or Schematron.
code in any language… help us write one-time transformations to convert contributed material into JLPTEI.
code in CSS … help us write rendering instructions for web browsers.
code in Javascript… help us build our web application.
code in Java… help us build the compiler application and/or choose and improve existing rendering engines.
code in XSLT 2.0… help us write transforms.
code in XQuery… help us write the toolkit API.

For more details on our development and to get status updates, fill out our questionnaire and you’ll be added to our mailing list. If you’d like to follow our developments closely and participate, then please join our discussion list, friend us on Facebook, follow us on Twitter, and check out our development wiki (our current storehouse for documentation and texts).

Update 12/3/09: Broken links in the table have been corrected.

Jewish Content, Free Culture and “Content Compatibility”

19-Nov-09

This post is primarily directed at Jewish content providers  and anyone thinking about becoming one.

If you’re in the Jewish content world, it’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 “content compatibility,” 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.

Disclaimer: I am not a lawyer and this is not legal advice.

Issues of content compatibility arise out of copyright law.  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’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 “fair use,” 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.

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 “implied license” 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.

Aside from relying on an implied license, some websites attempt to use “parasitic” 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’s accidental.  Some sites’ 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:

Limited Right to Use.
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).

Editing, Deleting and Modification.
We reserve the right in our sole discretion to edit or delete any documents, information or other content appearing on the Site.

and the rather dangerous (and dubious, emphasis added):

Use of Information.
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. All remarks, suggestions, ideas, graphics, or other information communicated by you to us through the Site (collectively, the “Submission”) will forever be the property of SITE NAME. SITE NAME 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 SITE NAME products, services or operations. Without limitation, SITE NAME will have exclusive ownership of all present and future existing rights to the Submission of every kind and nature everywhere. SITE NAME 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 SITE NAME, have full responsibility for the message, including its legality, reliability, appropriateness, originality, and copyright.

These broad claims of ownership(!) 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.

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:

  • 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’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.
  • 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).
  • 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 “intellectual property.”  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 orphan works problem .

The free culture community has developed mechanisms to make sharing and collaborative development easier.  The principles that define works of free culture are:
1. the freedom to use the work and enjoy the benefits of using it
2. the freedom to study the work and to apply knowledge acquired from it
3. the freedom to make and redistribute copies, in whole or in part, of the information or expression
4. the freedom to make changes and improvements, and to distribute derivative works
Note that these freedoms do not discriminate on the basis of endeavor, and all free culture works allow creation of derivative works and commercial use.

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 “all rights reserved” copyright).

A major organization responsible for maintaining the legal framework of the free culture community is Creative Commons.  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.):

  • Creative Commons Zero – “no rights reserved” – essentially, an internationally-applicable public domain declaration, indicating that the author surrenders all rights to the work.
  • Creative Commons Attribution – The work may be copied, modified, and distributed, as long as attribution is maintained and reference is made to the license.
  • Creative Commons Attribution-ShareAlike – 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.

Creative Commons also offers some licenses with *non free culture* terms (in combination with the Attribution and/or ShareAlike terms):

  • NonCommercial – No commercial use.  Use of this term will also place severe limits on the work’s use in the future, both by you and your users.
  • NoDerivs – The work may not be changed from its original version.  Use of this term will completely curtail communal development to the same degree as “all rights reserved” copyright.

Wikipedia and Wikimedia Commons, the largest free culture projects, have chosen the Creative Commons Attribution-ShareAlike 3.0 license for their material.

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.

In many cases, the Open Siddur Project’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.

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 “all rights reserved” copyrights.

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.

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.

We hope to begin a conversation about content compatibility with the world of online Jewish content providers. If you’re interested in joining it, talk to us.

Development Status (11/11/2009)

11-Nov-09

Open Siddur Project Development Status as of 11/11/2009

Our third development status covers progress on the Open Siddur made since our last update 9/22/09. Email aharon@opensiddur.net if you want to include something we haven’t covered. For now we’ll be sending these out once a month but if you’d like to get news of Open Siddur as it happens, make sure to follow @opensiddur at Twitter.

Contributions

Aharon read through Reb Zalman’s weekday and shabbat evening siddur and prepared the document for sharing as a PDF as well as in the ODT (open document) format. Folks can now use this to help make their own siddurim offline while we continue to work on creating our online open siddur web application. Want to craft your own siddur using material from Reb Zalman’s siddur? Check it out here.

We need a *print* copy of Siddur Torah Ohr (pre-1923) to correct and proof a digital transcription of the siddur already available CC-BY-SA at wikisource. Do you have one we could use? Please let us know. With this text vetted and proofed, we could use it to help folk begin making their own siddurim as well as for comparing it with our transcription of Siddur Avodat Israel.

Manual transcription of Seligman Baer’s Siddur Avodat Israel slowed over the last few months, but this is the easiest place someone with little technical capability can make a big difference. Every line of text transcribed is digitally liberated for use in future siddurim. If you haven’t yet, register on the wiki and start transcribing here.

Software Development

Efraim completed an implementation of XPointer to be used in our XSLT transforms and XQuery.  In the process, he developed a generic parser generator for XSLT (http://wiki.jewishliturgy.org/XSLT_Grammar_Parser).  This is a prerequisite to the continued development of (1) toolkit APIs that grab ordered text segments from JLPTEI documents and (2) transforms to convert JLPTEI to other forms. The code is complete and committed to subversion.  The code has had some minimal testing.
Efraim explains in more detail in a posting on our listserve: http://groups.google.com/group/jewishliturgy-discuss/browse_thread/thread/61285fef05e1846f

Efraim also finished a first pass of XSLT code to combine multiple overlapping hierarchies as described on our wiki.  Finishing this take us one step closer to processing JLPTEI.  Help wanted!

Azriel’s OSNAT (Open Siddur Network Application for Transcription) is still pre-alpha, but includes a fly in-browser Hebrew Unicode 5.0 standard keyboard. Interested and familiar with Javascript and jQuery?

We are always looking for more software developers! Please contact us with your skills.

Documentation

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.

Organization/Structure

w00t! The Open Siddur now has a mission statement. see http://wiki.jewishliturgy.org/Mission_Statement

How can we better track progress now that we have a list of milestones (http://wiki.jewishliturgy.org/Milestones)? Aharon is thinking of a fractal tree showing milestone markers and child dependencies.

Communication and Promotion

We had our third Open Siddur Open Chat at irc://irc.freenode.net/jewisliturgy on October 16th. The logs of the chat are available on our wiki at http://wiki.jewishliturgy.org/IRC_Conference

Our next Open Chat is scheduled for November 22nd, 11am EST.

Team Member Updates

At Yeshivat Hadar, Aharon is studying with R. Elie Kaunfer the evolution of Jewish spiritual practice in prayer and meditation and where Jewish liturgy supports this practice in the evolution of nusaḥ.

Why all the software?

02-Nov-09

One question I’ve been asked a number of times about the Open Siddur Project is: why are you developing all that software?  It’s a fair question.  After all, the siddur is just text.  There are other do-it-yourself siddur kits out there.  They sell you (or, more accurately, license you) a text.  You open the text in a word processor, make a few stylistic changes, and voila, you have your own custom siddur.  The “advanced” ones may even hand you one copy of a “nusah Ashkenaz” siddur, one copy of a “nusah Sefard” siddur, and one copy of a “nusah Edot Hamizrah” siddur, giving you some choices.  All good, right?  So, once again, why does the Open Siddur need so much software?

In actuality, there is no such thing as a single text called _the_ Ashkenazic siddur, _the_ Hasidic siddur, or _the_ Sephardic siddur, etc.  A nusah is a major division which uniquely specifies a common denominator of customs within a group of customs.  Within Ashkenaz, there are differences between the Polish and German customs.  The Iraqi custom is not the same as the Yemenite custom, and the Lubavitch custom is not the same as the Breslov custom.  There are also divisions within each rite along major the philosophical boundaries that have developed in recent centuries, which lead to differences in custom and text.  The traditional-egalitarian rite (usually a variant of the Ashkenazic rite), for example, is still undergoing major evolution.

Now, let’s say that we provided a single text for each sub-rite within the major rites, and simply copy-pasted the common text between them.  The amount of replication of very similar material between the texts would be huge.  If a mistake were found in one copy, it would have to be corrected separately in all copies.  Further, there would be no real connection between the copies other than their content.  If we were tracking some data (say, grammatical or historical data about the text), it too would have to have each change copied to all copies of the texts.  This would quickly result in an unmaintainable mess.

The Open Siddur’s current approach is different.  It involves (1) minimizing the amount of stored text, (2) storing the differences between the texts and (3) sets of conditions that specify when each variant is selected.  If a typo is corrected in one variant, it is corrected for all variants.  Any stored metadata is also automatically consistent between all texts.  An additional advantage of this approach is that a community with a custom that differs from the “base” custom of the rite only has to make a different choice of variants.  No change is required in the text in order to support a slightly differing custom.

The disadvantage of this approach is that each user likely only wants one variant of the text.  Something has to (1) convert human-typed text into the unified format used in the archive and (2) splice the archival text into a unified “printable” text that can be used as a siddur.  And that is one answer to why we need to develop software.

Reb Zalman’s Open Siddur Tehillat Hashem

19-Oct-09

The Open Siddur is pleased to announce the first contribution of a contemporary translation of the siddur. Reb Zalman Schachter-Shalomi contributed his Weekday Siddur and Sabbath Supplement: Siddur Tehillat HaShem. Siddur Tehillat HaShem presents Reb Zalman’s creative translation in English of Psalms, blessings, the Amidah, liturgical poetry, meditations, and other prayers read daily and on Friday evening. Reb Zalman contributed his siddur soon after being contacted by the Open Siddur Project having grokked the potential of free culture and shared resources to renew Jewish culture and spirituality. Thank you Reb Zalman!

Reb Zalman Schachter-ShalomiThe Open Siddur Project will be formatting the text of Siddur Tehillat Hashem siddur in XML according to our JLPTEI specification. In that way the modular components of the siddur will be added to our growing archive of siddur content that can be accessed as a whole or as sections as part of our Open Siddur web application. Until that work is completed, Reb Zalman’s siddur can be accessed as ODT and PDF documents in the links below.

ODT | PDF Siddur Tehillat HaShem Weekdays

ODT | PDF Siddur Tehillat HaShem Sabbath Evening Supplement

The Open Siddur Project is non-denominational and welcomes contributions of siddur content in any language spoken by Jews: translations, prayers, commentaries, instructional text and meditations, as well as the text of historical nusḥaot and their contemporary adaptations. Our goal is to prepare an archive of the texts of the siddur showing the entire history of the siddur in its respective nusḥaot and a web application to present these texts for inclusion in personally customized Jewish prayer books. For more information on how to contribute your siddur, translation, commentary, or other works to the Open Siddur Project, please read our submission guide.

Reb Zalman released this Siddur with a CC-BY-SA license by including the following text.

Creative Commons license
Creative Commons Attribution Creative Commons Share Alike

I am the original author of the attached Siddur and I am licensing the following attachments under the Creative Commons Attribution-ShareAlike 3.0 Unported License. Attribution may be given as ‘Contributors to the Jewish Liturgy Project/Open Siddur’, with the author’s name, Reb Zalman Schachter-Shalomi, included in the contributors list.

Free as in Freedom

18-Oct-09

Often we are asked here at the Open Siddur Project why we cannot simply use the digitized texts of the siddur that are available from Davka Corporation. Our instinct was that Davka only granted permission for individuals to use their digitized Hebrew texts under fair use doctrine. To be certain, we sought to find the the text of Davka Corporation’s End User License Agreement (EULA) and failing to locate this information online, friends of the project provided us with the EULA included with the packaging and software installer for a Davka software product: DavkaWriter Dimensions II.

From the language of these license agreements, it is clear that the text Davka is providing is not free for end-users to distribute or to create derivative  works. Section 4(a) of the EULA reads: “You may not use the texts in the software to publish materials for sale without express written permission from Davka Corporation. Preparation of these texts has entailed considerable effort and expense. They are not shareware, and should be used by no one other than the purchaser.”

In stark contrast, the texts that the Open Siddur is sharing may be distributed and re-distributed without our express written permission, for commercial and non-commercial, for educational and non-educational use. In short, our texts are FREE. We are making these texts free because we believe that these texts are the cultural legacy and inheritance of the Jewish people to create and innovate with in the publishing of new siddurim customized to an individual or groups spiritual practice. We have so much to share with each other, why should we  limit our culture vitality by shackling it to copyright?

There are other reasons why we would not use the digitized texts of contemporary siddurim. The most important reason besides their not being free, is that they do not clearly attribute the source of their digitized texts to the historical siddurim that they were presumably derived from. The Open Siddur Project aims to provide the text of all the nusḥaot of the siddur and their variations with full attribution of the sources for these texts.

The following is the text of the License Agreement (pdf) included in the packaging of the DavkaWriter Dimensions II CD:

Licensing Agreement

The files on this program are licensed to the purchaser on an “as-is” basis. While the publishers have made every effort to avoid errors, they will not be held responsible for any loss or damage, incidental or consequential, resulting directly or indirectly from the use of this program. In any case, the sole and total liability of the publishers shall not exceed the sum paid for the program by the purchaser. The texts on this CD may be used by the purchaser for personal or family use. If the purchaser is an institution, the texts may be used by that institution for its own needs. However, any use of the texts in the publication of materials for sale requires written permission from the Davka Corporation. Preparation of DavkaWriter Dimensions has entailed considerable effort and expense. It is not shareware, and therefore should not be used other than by the purchaser.

The following is the EULA included with the software installer and must be agreed to (via click-through) before the software allows itself to be installed.

END-USER LICENSE AGREEMENT FOR DAVKAWRITER DIMENSIONS

IMPORTANT-READ CAREFULLY: This End-User License Agreement (the “Agreement”) is a legal agreement between you, either an individual or a single entity, (the “Licensee”) and the Institute for Computers in Jewish Life, Davka Corporation, and David Kantrowitz (the “Publishers”) for the DavkaWriter Dimensions software product, which includes computer software, truetype font files, textual documents, associated media and printed materials, and “online” or electronic documentation (the “SOFTWARE”).

By installing, copying, or otherwise using the SOFTWARE, you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, promptly return the unused SOFTWARE to the place from which you obtained it for a full refund.

The SOFTWARE is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE is licensed, not sold.

1. GRANT OF LICENSE. This Agreement grants you the right to use one copy of the SOFTWARE on a single computer.

The SOFTWARE is in “use” on a computer when it is loaded into temporary memory (i.e., RAM) or installed into permanent memory (e.g., hard disk, CD-ROM, or other storage device) of that computer. However, installation on a network server for the sole purpose of internal distribution to one or more other computer(s) shall not constitute “use” for which a separate Agreement is required, provided you have a separate Agreement for each computer to which the SOFTWARE is distributed.

THE LICENSE IS LIMITED TO THE PROVISIONS OF THE REST OF THIS AGREEMENT, ESPECIALLY THOSE IN ITEM 4 BELOW.

2. UPGRADES. The SOFTWARE includes an upgrade to the DavkaWriter Platinum program, produced by Davka Corporation. This upgrade may be used ONLY by a licensed user of the DavkaWriter Platinum program. The DavkaWriter Platinum upgrade may NOT be separated from this SOFTWARE for use by another individual or entity. It may be used only in accordance with this Agreement.

3. COPYRIGHT. All title and copyrights in and to the SOFTWARE (including but not limited to any images, photographs, animations, video, audio, music, text, and “applets” incorporated into the SOFTWARE), the accompanying printed materials, and any copies of the SOFTWARE are owned by Davka Corporation or its suppliers.

The SOFTWARE is protected by copyright laws and international treaty provisions. Therefore, you must treat the SOFTWARE like any other copyrighted material except that you may either (a) make one copy of the SOFTWARE solely for backup or archival purposes or (b) install the SOFTWARE on a single computer provided you keep the original solely for backup or archival purposes. You may not copy the printed materials accompanying the SOFTWARE.

4. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

a. YOU MAY NOT USE THE TEXTS IN THE SOFTWARE TO PUBLISH MATERIALS FOR SALE WITHOUT EXPRESS WRITTEN PERMISSION FROM DAVKA CORPORATION. PREPARATION OF THESE TEXTS HAS ENTAILED CONSIDERABLE EFFORT AND EXPENSE. THEY ARE NOT SHAREWARE, AND SHOULD BE USED BY NO ONE OTHER THAN THE PURCHASER.

b. Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

c. No Separation of Components. The SOFTWARE is licensed as a single product and neither the software SOFTWAREs comprising the SOFTWARE or any UPDATE may be separated for use by more than one user at a time.

d. Rental. You may not rent, lease, or lend the SOFTWARE.

e. Software Transfer. You may permanently transfer all of your rights under this Agreement, provided that you retain no copies, you transfer all of the SOFTWARE (including all component parts, the media and printed materials, any upgrades, and this Agreement), and the recipient agrees to the terms of this Agreement. If the SOFTWARE is an upgrade, any transfer must include all prior versions of the SOFTWARE.
The SOFTWARE must be completely removed from your computer before transfering it to the recipient.

f. Termination. Without prejudice to any other rights, the Publishers may terminate this Agreement if you fail to comply with the terms and conditions of this Agreement. In such event, you must destroy all copies of the SOFTWARE.

5. EXCLUSION OF WARRANTIES.

The Publishers offer the SOFTWARE and the Licensee accepts it “AS IS”. The Publishers do not warrant the SOFTWARE will meet the Licensee’s requirements or will operate uninterrupted or error-free.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE PUBLISHERS AND THEIR SUPPLIERS DISCLAIM ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.

CUSTOMER REMEDIES. The Publishers’ and their suppliers’ entire liability and the Licensee’s exclusive remedy shall be, at the Publishers’ option, either (a) return of the price paid by the Licensee, or (b) repair or replacement of SOFTWARE or hardware that is defective and which is returned to Davka Corporation with a copy of the Licensee’s receipt.
All Warranties are void if failure of the SOFTWARE or hardware has resulted from accident, abuse, or misapplication. Outside the United States, neither these remedies nor any product support services offered by Davka Corporation are available without proof of purchase from an authorized international source.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE PUBLISHERS OR THEIR SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF THE PUBLISHERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Some states and jurisdictions do not allow the exclusion or limitation of certain implied warranties or the exclusion or limitation of liability for incidental or consequential damages, in which case and to the extent such exclusion or limitation is not allowed, some of the foregoing limitations and exclusions may not apply to the Licensee.
To the extent allowed by applicable law, implied warranties on the SOFTWARE and hardware, if any, are limited to ninety (90) days and one year, respectively.