Openwings Data Specification Request
Openwings Specification Request (OSR)
Title:
Openwings Data Services (OSR_008)
Summary:
The charter for the Data Services Expert team is to define an
abstraction for database services. The data server provides a three-tier architecture,
which allows database independence across relational and object oriented databases. It also provides the publication of databases as
services in an object-oriented manner.
Section 1. Identification
| |
Submitting
Member
|
Specification
Lead
|
|
Name of Contact
|
Guy Bieber
|
TBD
|
|
Telephone
Number
|
1-480-441-7692
|
TBD
|
|
Fax
Number
|
1-480-441-2304
|
TBD
|
Expert Nominee
Qualifications:
Candidate for this expert team should have the following
qualifications:
- Experienced with the Java2 platform (mandatory requirement).
- Experience with issues in implementing Object and Relational Databases.
- Familiarity with ODBC and JDBC database connection technology.
- Familiarity with Object-Relational mapping tools and issues.
Section 2: Request
2.1 Please describe the
proposed Specification:
The charter for the Data Services Expert team is to define an
abstraction for database services. The data server provides a three-tier architecture,
which allows database independence across relational and object oriented databases. It also provides the publication of databases as
services in an object-oriented manner. This
technology includes techniques to make relational databases look object oriented, such as
Object Relational mapping of database tables to objects.
This technology will allow large databases to be easily distributed.
The Data Services Expert team will be responsible for developing the
following:
- Data Services specification
- Data Services Reference Implementation
- Data Services Compatibility Test Suite.
2.2 What is the target Java
platform? (i.e., desktop, server, personal, embedded, card, etc.)
This specification is target towards the J2SE and J2EE platforms. It is anticipated that a J2ME platform will be
able to use these services, but not necessarily host them.
2.3 What need of the Openwings
community will be addressed by the proposed specification?
The need to access database services is covered by this
specification.
2.4 Why isn't this need met by
existing specifications?
No.
2.5 Please give a short
description of the underlying technology or technologies:
This specification will utilize the following technologies: Java Database Connectivity (JDBC), Object
Relational Mapping Tools, Relational Databases, and Object Databases.
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.data.
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?
No.
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 |
Openwings Specification Request Approved |
12/1/2000 |
Form Expert Group |
3/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/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)
- Openwings Data Services Specification (Alpha version 0.7)
In addition to the specifications
an Alpha implementation of the existing data service specification is being provided for
this effort.
3.2 Explanation of how these items might be used as a
starting point for the work.
The existing specification and reference implementation serve as a
working model of the data services that can be used to further refine the specification.
Section 4: Additional Information (Optional)
4.1 This section contains any additional information that
the submitting Member wishes to include in the OSR.
None.
|