Profiles rationale

[mark.reinhold at oracle.com]

Attached below is some text that could be added after the "Content"
subsection of the "Profiles" section (§8) of the EDR draft.

Comments?

- Mark

----

**Rationale** The contents of the various Profiles are motivated as
follows:

  - The `compact1` Profile contains the smallest set of packages that is
    feasible without omitting any classes or methods.  The logging
    (`java.util.logging`) and SSL/TLS (`javax.net.ssl`) packages are
    additionally included because it is expected that many applications
    running on even the smallest Profile will require these facilities.

    The `compact1` Profile is a suitable migration target for
    applications that currently target CDC 1.1 (JSR 218) and Foundation
    Profile 1.1 (JSR 219).  It includes every package specified in those
    JSRs, including the "Security Optional Packages" in JSR 219, except
    for `java.security.acl` (a legacy API which nobody uses) and the
    `javax.microedition.io` and `javax.microedition.pki` packages (which
    are Java ME-specific).

  - The `compact2` Profile adds packages for remote method invocation
    (RMI), database access (JDBC), and XML processing.  This Profile is a
    suitable migration target for applications that currently target CDC
    1.1 and Foundation Profile 1.1 and, additionally, one or more of the
    following Specifications:

      - RMI Optional Package Specification 1.0 (JSR 66)
      - JDBC Optional Package for CDC/Foundation Profile (JSR 169)
      - XML API for Java ME (JSR 280)

  - The `compact3` Profile adds packages for instrumentation, management,
    naming, scripting, and compilation as well as further packages for
    database access, security, and cryptography.  This Profile is
    intended for applications that require most of the full Platform
    except for the desktop user-interface packages (AWT, Swing, etc.),
    web services (JAX-WS, JAXB, and SAAJ), and CORBA.