This essay does not describe an existing computer program, just one that should exist. This essay is about a suggested student project in Java programming. This essay gives a rough overview of how it might work. I have no source, object, specifications, file layouts or anything else useful to implementing this project. Everything I have prepared to help you is right here.
This project outline is not like the artificial, tidy little problems you are spoon-fed in school, when all the facts you need are included, nothing extraneous is mentioned, the answer is fully specified, along with hints to nudge you toward a single expected canonical solution. This project is much more like the real world of messy problems where it is up to you to fully the define the end point, or a series of ever more difficult versions of this project and research the information yourself to solve them.
Everything I have to say to help you with this project is written below. I am not prepared to help you implement it; or give you any additional materials. I have too many other projects of my own.
Though I am a programmer by profession, I don’t do people’s homework for them. That just robs them of an education.
You have my full permission to implement this project in any way you please and to keep all the profits from your endeavour.
Please do not email me about this project without reading the disclaimer above.
To convert these documents properly to HTML you need to:
Ideally you will get the RFCs into an SQL (Standard Query Language) database so you can do clever searches. You would manually add keywords to each entry. You might be able to detect the changes in standards.
You can make money with this by posting the formatted RFCs on a website with a Google Adsense ad discretely off to the side. Last time I looked there were 4938 RFCs. Last revised/verified: 2007-07-05 It is within reason you could at least quickly proofread them all for gross formatting problems. Thousands of programmers reference these every day. If yours are the most convenient, the word will get out that yours is the best site to browse them. Google does the rest with ads cleverly matched to the content of each RFC. You could also offer the set to read offline, indexed with Google Desktop, via the Replicator.
Since I wrote this, I discovered the rfc-editor.org search engine. It has an SQL search engine. It tracks obsoletes, deletes, is-deleted by etc. It provides the RFCs in text form and in a PDF (Portable Document Format) version that exactly matches the text version. However, it does not provide an internally cross-referenced HTML version, which is what you really need as a web reference.
You can find out which RFCs are obsolete and which RFC obsoletes what at faqs.org.
For a more ambitious project you might like to partially gray out any text that has been obsoleted and provide clickable links to the replacing text, going directly to it, not via a chain.
This page is posted
Optional Replicator mirror
Your face IP:[184.108.40.206]
You are visitor number|