The Final Notes for the First Chapter of the Early Draft of MVC 1.0 (Ozark)

Team. For those who are interested, Ozarks issue tracking system for the first release is located at https://java.net/jira/browse/MVC_SPEC, the API documentation is at https://mvc-spec.java.net, and one can find the reference implementation at https://ozark.java.net. After reading through part or most of the documentation, you can provide the expert group with any inputs which  are valuable by mailingusers@mvc-spec.java.net.

For those who actual read through the early draft, they should be aware that most of the terminology used comes from the JAX-RS and Context and Dependency Injection (CDI) specifications. The following pairs of terms: per-request and request-scoped plus per-application and application-scoped, are synonymous. Also, the following terms should be interpreted as they are described in RFC 2119, http://www.ietf.org/rfc/rfc2119.txt, "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may", and "optional". Plus, all assertions are formatted using a descriptive name plus a label and can be found in Appendix A of the Early Draft. Also, all JAVA code fragments use a courier font and line numbering. Uniform Resource Identifiers (URIs)n of the general form "http://www.example.org" and "http://www.example.com" are application or context-dependent URIs.

A summary of the second chapter will likely come during the beginning of next week.

Enjoy a week of Enlightenment, Endeavor, and Success,

The CABOOSE Team