 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 123: JAINTM Presence and Availability Management (PAM) API
Reason: Withdrawn when no one was found to take over Specification Lead role. In addition, the differences between the OSA PAM and JAIN PAM specs are sufficiently small that it's not clear that the industry benefits from two specifications. JCP version in use: 2.1 Java Specification Participation Agreement version in use: 1.0 Description: JAINTM SPA Presence and Availability Management API will provide Java APIs to disseminate and manage presence information securely across heterogeneous networks and applications. Please direct comments on this JSR to the Spec Lead(s) Team
This JSR has been Withdrawn
Identification |
Request |
Contributions |
Additional Information
Section 1. Identification Submitting Member: Teltier Technologies Name of Contact Person: Guda Venkatesh E-Mail Address: venk@teltier.com Telephone Number: +1 908 598 4781 Fax Number: +1 908 273 5935 Specification Lead: Guda Venkatesh E-Mail Address: venk@teltier.com Telephone Number: +1 908 598 4781 Fax Number: +1 908 273 5935 Initial Expert Group Membership: NexTone Communications Sun Microsystems Section 2: Request
2.1 Please describe the proposed Specification:JAINTM SPA Presence and Availability Management API will provide Java APIs to disseminate and manage presence information securely across heterogeneous networks and applications. The APIs allow user preferences and enterprise policies to control the dissemination of presence information to address privacy and security concerns. The API will be based on the PAMforum v1.0 specifications and its adoption in Parlay 3.0. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)Java 2 Standard and Enterprise Edition 2.3 What need of the Java community will be addressed by the proposed specification?The Java community needs a Java API to be able to access the Presence and Availability Management services in Parlay implementations and stand alone PAM servers. This specification will complement the JAIN SPA APIs that provide Java APIs to equivalent Parlay Service Specifications. Java software developers can create presence based application independent of the underlying network technologies including both wired and wireless networks. 2.4 Why isn't this need met by existing specifications?None of the existing JAIN APIs address the management of presence in a network and application independent manner. As an independent Parlay service, Presence and Availability Management is not covered by any other JAIN SPA APIs. 2.5 Please give a short description of the underlying technology or technologies:The JAIN Presence and Availability Management specification abstracts presence information from the underlying networks. It serves as part of the SPA client interface to Parlay implementations and as the client interface to stand-alone PAM servers. It is expected that the API will seamlessly interoperate with other JAIN APIs including but not limited to: JAIN SLEE 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 sub-packages of
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 group meeting planned as a Joint Parlay/PAMforum/JAIN session in the third week of May in San Diego.? Followed by regular SPA-PAM sessions during JAIN meetings and conference calls when required. Community Review by end of? July 2001 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.The Expert Group will develop guidelines for the mapping between the Parlay UML and the Java specifications via an e-mail exploder/web message board. The Java interfaces developed under these guidelines will be iterated via comments solicited in conference calls and web discussion boards. 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.The PAM forum specifications and information is available from The current PAM forum specification document is accessible as PAM Specification v1.0 draft 3 3.2 Explanation of how these items might be used as a starting point for the work.The PAM forum specification will be adopted into and made consistent with Parlay 3.0 specs. The JAIN SPA APIs for PAM will be consistent with the Parlay 3.0 specs by providing guidelines to map the UML descriptions in Parlay into Java interfaces. Section 4: Additional Information (Optional)
4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.The Submitting member and spec lead is the Chair of the Technical Committee in PAMforum and Chair of the PAM WG in Parlay. |
||||||||||||||||||||||||||||||||||||||||||||||||||
