The Java Community Process(SM) Program - JSRs: Java Specification Requests

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy

JSR #93
Java^TM API for XML Registries 1.0 (JAXR)
JSR Review Ballot
Ballot duration: 2001-01-09 to: 2001-01-22

These are the final results of the JSR Review Ballot for JSR #93. The Executive Committee for SE/EE has approved this ballot.

Votes

SE/EE

Accenture

Apache Software Foundation

Apple Computer, Inc.

BEA Systems

Borland Software Corporation

Caldera Systems

Cisco Systems

Compaq Computer Corporation

Fujitsu Limited

Hewlett-Packard

IBM

Lea, Doug

Oracle

Progress Software

Sun Microsystems, Inc.

WebGain

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2001-01-22 Fujitsu Limited voted Yes with the following comment:
The specifications will be developed by industry experts to ensure that JAXR clients can access business registries based on open standards such
as ebXML, OASIS, eCo framework as well as other industry consortium led registry specifications such as UDDI.

If this registries interface will be defined based on some open standards such as ebXML, OASIS, eCo framework, we hope this registries interface is freely available as well as open standard specifications.
------------------------------------------------------------------------------
On 2001-01-22 Progress Software voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-22 Apache Software Foundation voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-22 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-22 Borland Software Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-19 IBM voted Yes with the following comment:
It is very important that the JAXR API is designed so that it can be used to access a range of registries including UDDI, OASIS, and ebXML.  It must also be capable of accommodating evolutions of the functionality provided by these registries.  The specification should include examples of how different registries could be used, and the TCK must not require use of a specific registry.  We would also like the reference implementation to support more than one registry in order to demonstrate proof of concept that this is possible. We request that this requirement is addressed before the EC vote at the Community Review phase of this JSR.
------------------------------------------------------------------------------
On 2001-01-15 Cisco Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-15 Caldera Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-12 BEA Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2001-01-09 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------