Welcome to the RAIPH website!

Take a look at our group at Yahoo. This website is primarily our resource center for information, coordination, and where we will explore all the topics of the RAIPH project.

Of serious note: Do not look at this website while at work because we might then lose the rights to our project by using the property of an employer. This is explored a bit here.

At this website, we will be addressing the real content of our work. Here are areas of interest so far:

Understanding the viability of RAIPH (not yet made)- Here we explore the options for getting RAIPH off the ground. This is where we will discuss and link ideas like the burden for proving prior art and how this affects our effort.
RAIPH resources (not yet made)- This includes a host of links, that will be useful when researching our ideas, and the feasibility discussed above.
The IDEA Heap - This is an organized area where our ideas are indexed by number, and categorized by area. Roughly, all idea files are stored in the <root>/ideaheap/<number> directory of the website as a flat list, with index.html in each server directory pointing to versions of documents, etc. as necessary. We also have a series of webpages that represent the hierarchical placement of each idea within category. The category structure webpages act like a view into the flat list of files, so that you can search by subject, or directly go to an idea by its number. This avoids the hassle of creating a lot of directories and managing them all. Take a look to see what I mean.

I will be periodically backing up this entire site (once a week), but please also keep an organized list of local files on your comp, to make sure we never lose any piece of work. This also helps to avoid problems if we both try to upload the same file to the webserver simultaneously, causing some loss of data. If anyone has a nice solution to this problem, please let me know. Maybe we should post on the groups website before we update a file?

Web Site Maintenance Issues (any comments on the following would be helpful):

• Password protecting the pages?
• Solving the multiple-updates-at-a-time problem? Essentially a way to ensure we can lock a page until it is updated and that everyone can know about these locks?
• How to schedule cron jobs for periodic backups?
• Adding frames/banners to make navigation much faster?

Last Updated: 9/19/03 (ash)
Last Backed Up: Not yet
Next Backup Scheduled:  9/26/03
Post your feedback