2.1 Please describe the proposed Specification:

The JAIN^TM User Interaction 1.0 specification will provide Java APIs for use in a Parlay client environment.

These APIs are functionally compatible with the Parlay Generic User Interaction 3.0 APIs.

State-of-the-art design patterns will be used hiding some details of the underlying communication model between Parlay client and server.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

The JAIN^TM User Interaction 1.0 specification is targeted for the Java 2 Standard Edition (J2SE) and Java 2 Enterprise Edition (J2EE) platforms.

2.3 What need of the Java community will be addressed by the proposed specification?

The JAIN^TM User Interaction 1.0 API will be part of a Java technology instantiation of Parlay, which enables external enterprises to rapidly build and deploy applications that exploit capabilities of the underlying telco's network. By adopting Parlay, the Java community can leverage on the huge investment made by Parlay members into the specification and associated adoption across the IT & telecom industry.

This specification is required to ensure continued standardization across the computing industry with regard to public open APIs.

2.4 Why isn't this need met by existing specifications?

There exists no JAIN^TM (or Java^TM) API to represent a Java^TM specification of the Parlay Generic User Interaction API at present.

2.5 Please give a short description of the underlying technology or technologies:

The JAIN^TM User Interaction 1.0 specification abstracts underlying network capabilities.

It is anticipated that the proposed API would be implemented on a Parlay client, using an arbitrary communication protocol to a Parlay Server, to access Generic User Interaction services in a controlled and secure telecoms environment.

It is highly desired that the API seamlessly interoperates with other JAIN^TM APIs including but not limited to:

• JAIN^TM SPA TSM, SD and SAM
• JAIN^TM SPA IM and EN
• JAIN^TM SLEE
• JAIN^TM Call Control

  2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

  The Specification will be provided directly in, and in subpackages of
  javax.jain.services.gui

  It will contribute common classes and interfaces to javax.jain and javax.jain.services, as defined in the JAIN^TM Common API.

  2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

  No

  2.8 Are there any security issues that cannot be addressed by the current security model?

  No

  2.9 Are there any internationalization or localization issues?

  No

  2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

  No

  2.11 Please describe the anticipated schedule for the development of this specification.

  Initial Expert meeting: 10th December 2001
  Regular expert group sessions during JAIN meetings Conference calls when required

  Community Review: late Q1 2002
  Public Review: Q2 2002
  Proposed Final Draft: early Q3 2002
  RI & TCK: early Q4 2002
  Final Release: late Q4 2002
  

  
  
  
  
  

  Section 3: Contributions

  3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

  Documents describing JAIN^TM can be found at:
  http://java.sun.com/products/jain/index.html

  Documents describing Parlay can be found at:
  http://www.parlay.org/specs/index.asp

  3.2 Explanation of how these items might be used as a starting point for the work.

  The Parlay GUI would form the basis of the JAIN^TM GUI API.