JSRs: Java Specification Requests
JSR 86: Enterprise Media Beans
Section 1. Identification
Submitting Member: Donna Dillenberger
Name of Contact Person: Donna Dillenberger
E-Mail Address: email@example.com
Telephone Number: 914-784-7108
Specification Lead: Sascha Baumeister
E-Mail Address: firstname.lastname@example.org,
Telephone Number: +49-7031-163067
Fax Number: +49-7031-163545
Initial Expert Group Membership:
Section 2: Request
2.1 Please describe the proposed Specification:EMB provides a framework to integrate rich media data such as audio, video or image into applications based on EJBTM Entity Beans within the J2EETM application development model. It provides a common view on rich media from an application model point of view. EMB abstracts over underlying transport and rendering mechanisms (e.g. the various stream server implementations), caching and replication throughout the network. It ensures referential integrity and hides the underlying persistency method for rich media (file, binary large object, user defined data types, etc.) from the application model. EMB enforces a common security model for rich media, and ensure transactional behavior for operations like media insertion, remove or move. It standardizes the integration of en-de-transcoding mechanisms into the application model.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)Server
2.3 What need of the Java community will be addressed by the proposed specification?There is currently no framework for applications to easily tie their business logic with rich media assets. What is missing is a lightweight, component based way to seamlessly integrate rich media data into business applications, from the backend throughout the enterprises' intelligent infrastructure. EMB addresses all main issues such as persistence with referential integrity, ingesting, updating, rendering, caching, etc., all in a transactional context imbedded into the security concept of the customer's existing IT infrastructure. EMB deliver a uniform view on rich media data, that means rich media is treated as as just another data type within the J2EETM application model. As an example, an insurance application can relate an emergency call recording (audio asset), a loss claim (EJBTM) and a customer (EJBTM). Subsequently, the insurance company can easily query and replay the emergency call recording if neccessary, query and replay all emergency call recordings for a given customer, find out easily who the participants in a given emergency call were, etc. This offering would result in another segment (multimedia) where EJBsTM could be used.
2.4 Why isn't this need met by existing specifications?There are Java frameworks that help application writers develop video players (Java Media Framework). But there are no standards in the Java and NonJava World that enable business programs to easily embed digital assets as a type into their business logic.
2.5 Please give a short description of the underlying technology or technologies:The underlying technology is Enterprise JavaBeansTM.
2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)javax.emb
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.1. Creation of expert group [10/2000]
2. Submission of the IBM initial API specification and first reference implementation [12/2000]
3. Community review of the initial specification [01/2000]
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.- We have a detailed set of APIs that we can start off with.
3.2 Explanation of how these items might be used as a starting point for the workThe Javadoc and EMB interfaces can be shipped as part of the core J2EETM. We can make an overview document available on the Web and a reference implementation can be made available through the Open Source process. It's important that this JSR be part of the J2EETM to ensure ubiquity to all new media data applications and programmers.