The scope of a subject area will be expressed as a Table of Contents , more like a book than a library. Herein lies the greatest challenge. JOMA intends to distinguish between areas for faculty and developers. This should not imply that these two categories of people have an empty intersection. I believe that the best results might be achieved when the faculty, as a source of insights, gets directly involved in the development process.
Web come alive.
It's not that difficult at all. The development effort should not be restricted to a specific programming language or programming environment. On the other hand, I believe that to be good, a book must be coherent in style and expressive means. And as we have to start somewhere, Java is as good a choice as any other. From the time it became public some 4 years ago, Java underwent several transformations.