Openwings Component Specification Request

Openwings Specification Request (OSR)

Title:

Openwings Component Services

Summary:

The Component Services provide a simple model for Service Oriented Programming that allows services to be provided and used independent of protocols for transport, discovery mechanisms, and deployment environments.

Section 1. Identification

Submitting Member and Specification Lead:

	Submitting Member	Specification Lead
Name of Contact	Guy Bieber	Jeffrey Carpenter
Telephone Number	1-480-441-7692	1-480-441-6957
Fax Number	1-480-441-2304	1-480-441-2304

Expert Nominee Qualifications:

Candidate for this expert team should have the following qualifications:

Experience with the Java2 platform (mandatory requirement)
Experience with ad-hoc networking technologies (i.e. Jini, Chai, UPnP, Ninja)
Understanding of Component and Service Models.
Understanding of Java RMI

Section 2: Request

2.1 Please describe the proposed Specification:

The charter for the Component Services Expert team is to develop a component framework that will provide the ability to provide, locate and use services, without being dependent on any specific service location/lookup mechanisms. Initial implementations will be based on Sun’s Jini technology, but will be flexible enough to move to other lookup/discovery services (i.e. HP Chai or Universal Plug-n-Play).

The Component Services Expert team will be responsible for developing the following:

Component Services specification
Component Services Reference Implementation
Component Services Compatibility Test Suite

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

J2SE is largely targeted towards desktop and webtop applications on the front end. J2EE is largely targeted towards E-Commerce and back end servers. J2ME is targeted towards the device market. This specification has a system focus on networked components, which includes the front end, back end, and devices; hence this specification targets all three Java platforms. The J2ME configurations to be considered should go down to the CDLC configuration.

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

A specification that implements the Service-Oriented Programming concept of a component does not exist.

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

No other specification covers components in Openwings.

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

The reference implementation of Component Services leverages Jini technology (www.jini.org) and the ServiceUI project. In addition, Java 1.3 Dynamic Proxy Classes are used.

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

The proposed package for this specification is net.openwings.component.

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 Openwings security model?

Component services will be involved in the integration of service security in the Openwings framework as it is developed.

2.9 Are there any internationalization or localization issues?

This OSR is targeted towards systems that may be internationally deployed and hence use the internationalization features of Java. It is anticipated that the existing internationalization infrastructure will be sufficient for this OSR.

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.

Currently a draft specification exists as a contribution and starting point. The following schedule applies:

Milestone	Date
OSR Approved	12/1/2000
Form Expert Group	2/16/2001
Participant Draft	TBD
Participant Review	TBD – 2Q 2001
Public Review	TBD – 2Q 2001
Beta Release	TBD – 3Q 2001
Maintenance	TBD

Once the expert team is formed, the finalized schedule will be made available.

Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology.

The Motorola IISG (now General Dynamics C4 Systems)/Sun Openwings team has previously-generated work that is being contributed as a basis for this OSR. In particular the following contributions available at http://www.openwings.org/download.cfm#specs are relevant.

Openwings White Paper
Openwings Naming Specification (Alpha version 0.7)
Openwings Architecture Specification (Alpha version 0.7)
Openwings Interface Specification (Alpha version 0.7)
Openwings Component Services Specification (Alpha version 0.7)
Openwings Connector Services Specification (Alpha version 0.7)
Openwings Management Specification (Alpha version 0.7)
Openwings Policy Specification (Alpha version 0.7)

In addition to these draft specifications an alpha reference implementation of connector services, component services, management services, and polices are being contributed.

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

The existing specifications will serve as the starting draft for the specifications produced under this effort.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the OSR.

None.