From the Open Siddur Project Development Wiki

This page is a list of ideas for new features or new uses of the Open Siddur data and software. There is no guarantee that anything listed here will ever be implemented, but it does give the development some ideas about what users (or other developers) want to see in the long term.

Contents 1 The ideas 1.1 Removal of geniza-names 1.2 Siddurim to transcribe 1.3 Triplet Annotations 1.4 Publishing 1.5 Viewing views

The ideas

• Enter ideas in this list or under their own headings.
• Client side computing: using an applet to create and compile the recipes instead of doing all of the hard work on the server.
• Server side computing: make all of the queries on the server side and keep the client as thin as possible.

Removal of geniza-names

Have an option to remove all geniza-requiring forms of God's name, see the feature request for a complete list.

Siddurim to transcribe

This section moved to Scans.

Triplet Annotations

The annotations represented by tei:note are usually textual.

Another type of annotation can be used to represent relationships using a limited vocabulary (see RDF triples], for example). These can easily be represented in TEI using feature structures. The triples could be of the form:

<item A> <relationship> <item B>

Such a limited vocabulary would make processing something like the historical siddur a lot easier.

eg:

<word> <is related to> <word>
<prayer> <was written by> <author>
<prayer> <dates from> <10th century>
<prayer> <added to siddur in> <11th century>

etc.

Publishing

• It would be nice if we can have a deal with self-publishing Print On Demand service, so that we can automatically have recipes printed, bound and shipped.
  • This might have issues of halacha, since who knows what the company might do with misprints ( sheimos ).

Viewing views

• It would be cool to have a JLPTEI viewer/editor that can view ( maybe in 3D, or on a slant ) all of the concurrent views of a document simultaniously.