Release: Merlin

Problem:
   This API is the product of JSR006, Unified Printing API, and will allow
   client applications to provide rich access to the capablities of print services available such as printer browsing and selection,
   and discovery of the capablities of those printers, selection of printers for a printer job, specification of a printer job such as paper sizes, etc.
   Availability of specific capabalities is necessarily dependent on the underlying print service.

   Since all capabilities will be exposed though API server applications become first class citizens of this API.

   Server applications may be beneficiaries of the capabilities for spooling documents to print services, whereas previously only graphics calls
   could be used to generate printer jobs from Java applications.

Requesters:
   Java2D, Xerox, JINI Printing Group, JustSystems

Proposed API change:
   Please look at:
      http://java.sun.com/aboutJava/communityprocess/review/jsr006/index.html

API reviewed and approved by:
   JSR006 expert group, JINI Printing Working Group, Sun internal
   printing review, Java2D

Implementation:
  - Engineer who made (or will make) the changes: Alan Kaminsky, Phil Race
  - Date at which changes will be complete: Sept 1, 2000
  - Number of lines of new or modified code:
+ Java: 23000 (includes extensive comments)
+ Native:
  - Code reviewed (or will be reviewed) by: Phil Race, Jennifer Godinez

Risk assessment: Low

SQE (product testing) impact; contact ###@###.###:

   - Name of person who approved change and committed to add/modify
     tests: Mukund Madhugiri (mukundm@eng)

JCK (compatibility testing) impact; contact jck-ccc@eng: (JCK would
like hard copy submittals instead of URL pointers)

   - Name of person who approved change and committed to write JCK
     tests: dkrishna@eng

Doc impact (contact Alan Sommerer if you don't know your contact):

   - Name of person committed to add/modify documents: Jennifer Ball (jenball@eng)

Localization impact: No

   - If yes, describe:

Internationalization impact: No

   - If yes, describe:

Security impact: No

   - If yes, describe:

Compatibility impact: No

   - If yes, describe:

Legal impact: No

   - If yes, describe:

For feature changes, Product Marketing approval: