|
Technology
|
Description
|
Business Benefits
|
Status
|
| C Mapping Revision |
This RFP solicits proposals for an IDL-to-C mapping for CORBA that addresses these problems. |
The IDL-to-C mapping as currently published dates back to 1999 and does not provide a mapping for a number of important features of CORBA 2.4.2 . This RFP updates C Language Mappingto a more recent CORBA release. |
Revised Submission due at November 2002 meeting |
| CORBA Security V2.0 |
This
RFP seeks to standardize a set of CORBA interfaces that
instantiate a security model about authentication, privileges, and
delegation. The interfaces sought will handle
the complexity and govern the use of the
CSIv2 protocol. |
Will
provide standard CORBA interfaces for security, creating portable
CORBA security-aware applications. (The current CORBA security
specification does not yield portable
security-aware applications.) |
Drafting
stage; may issue RFP at November 2002 meeting |
| CORBA to
WSDL-SOAP Interworking |
This RFP solicits proposals for specification translation rules and interaction translation mechanisms that enable the following: To make existing OMG IDL-defined CORBA object interface instances accessible as WSDL-defined service ports bound to HTTP/SOAP. |
The innate qualities of CORBA’s architectural design can be deployed to extend CORBA’s reach to new domains, in this case Web Services. This RFP aims to: extend the sphere of CORBA object access to include SOAP/HTTP, by standardizing the fashion in which CORBA IDL may be expressed as
WSDL. |
Revised Submission due at November 2002 meeting |
| Data
Distribution |
This RFP solicits proposals for an MDA specification describing the application-visible interface and behavior of a Data-Distribution Service (DDS) that supports a Data-Centric Publish-Subscribe (DCPS) for real-time systems and offers optionally a Data Local Reconstruction Layer (DLRL). |
Support many real-time applications in which the communication pattern is often modeled as a pure data-centric exchange where applications publish (supply or stream) “data” which is then available to the remote applications that are interested in it. |
Revised Submission due at January 2003 meeting |
| Deployment and Configuration of Components |
This RFP solicits proposals for (meta)models, notations and facilities to realize a comprehensive automated deployment and configuration support for component-based distributed applications. |
At present, modeling of configuration properties and deployment requirements of component-based distributed applications as well as the modeling of elements and properties of software and hardware infrastructures onto which the applications are to be deployed is not yet well supported by existing OMG specifications. Moreover, only parts of the infrastructure elements necessary to automate the deployment and configuration process are already covered by existing or upcoming OMG specifications. This RFP seeks to resolve these issues. |
Revised Submission due at January 2003 meeting |
| Extensible
Frameworks |
The objective of this RFP is to establish a framework for plugging in transports with sufficient predictability, improving suitability for realtime systems. |
Standard IIOP is insufficient for most real-time domains. While GIOP is adequate for real-time systems, the use of GIOP coupled with TCP/IP (i.e., IIOP) is not sufficiently predictable for most real-time systems. This RFP seeks to resolve this issue. |
Revised Submission due at November 2002 meeting |
| GIOP / Stream Control Transmission Protocol
(SCTP) Protocol Mapping |
This RFP solicits proposals for a mapping of GIOP onto Stream Control Transmission Protocol (SCTP) as specified in the IETF RFC2960. Proposals may also specify an interoperability bridge between the IIOP and the proposed Inter-ORB Protocol (IOP). |
In the 3GPP (3rd Generation Partnership Project) specifications, ORB technology is adopted in the management plane. The 3GPP Working Group on Network Management has defined the management interfaces to be CORBA interfaces. In order to apply ORB also in the control plane, a GIOP mapping onto SCTP is needed. |
Revised Submission due at January 2003 meeting |
| Java Message Service (JMS) Notification |
This RFP solicits proposals to enable interworking between two asynchronous publish-subscribe communications: the OMG's Notification Service and the Java Message Service (JMS), contained within the Java 2 Enterprise Edition (J2EE) standards. |
Permits CORBA and Java objects (including EJB's) to communicate with each other asynchronously. |
Revised Submission due at November 2002 meeting |
| Load Balancing and Monitoring |
This RFP solicits proposals to extend CORBA functionality to conveniently and efficiently support load balancing and monitoring in CORBA-based environments and for CORBA-based applications. |
These extensions will bridge the gap between CORBA and other application methodologies for distributed and high performance computing that require these characteristics (load balancing and monitoring) and are currently not based on CORBA. |
Revised Submission due at November 2002 meeting |
| Mapping EDOC to J2EE |
This
RFP solicits proposals for codifying the
best practice of application architecture to middleware
design as a set of transformation rules alternatives for mapping
EDOC's Enterprise Collaboration Architecture (ECA) to J2EE. |
ECA
is a middleware platform independent representation of entities,
events, B2B collaborations and business process definitions, most,
if not all, of which can be implemented
using J2EE. This RFP will provide a normative
approach to deploying ECA models on a J2EE platform. |
Drafting
stage; may issue RFP at November 2002 meeting |
| Online Upgrade |
This RFP solicits proposals for standard OMG interfaces and mechanisms to provide online upgrade capabilities for CORBA object implementations. |
Many large complex systems and many small embedded systems are expected to provide a long lifetime of service. It must be possible to upgrade and evolve these systems by replacing individual software and hardware components without taking these systems out of service to perform an upgrade. |
ADOPTED;
in finalization |
| Reliable Ordered Multicast |
contact
MARS PTF |
contact
MARS PTF |
Drafting
stage; may issue RFP at November 2002 meeting |
| Security Protocol
(SECP) 1.1 |
This RFP solicits proposals for the following: Platform Independent Specification, which is a specification of the SECP protocol message formats and state machine that is independent of the underlying transport protocol. Platform Specific Specification, i.e. specification of GSS-API Mechanisms supported within the CORBA CSIv2 protocol. |
SECP is the current protocol used in SECIOP, which is a security protocol currently defined in the OMG security service[SEC]. The protocol is versatile in that it can multiplex security contexts over a single connection. Since SECP is a multiplexing protocol unto itself, it is desirable to separate it from the Security Specification into its own chapter with its own revision management. |
Initial Submission due at March 2003 meeting |
| UML Profile for CCM |
This RFP solicits proposals for a UML profile that facilitates representation of concepts that are needed to represent a CORBA Component PSM. |
This will result in significant benefits to the CCM user community and the users of MDA in general: The CCM is extended by graphical modeling support for the concepts defined in the CCM metamodel; MDA development environments can target different up-to-date component platforms; and interoperability between various analysis and design tools is facilitated. |
Initial Submission due at January 2003 meeting |
| WSDL-SOAP to CORBA Interworking |
This RFP solicits proposals for specification translation rules and interaction translation mechanisms which enable the following: To make WSDL-defined web-based services, with ports bound to HTTP/SOAP, accessible to CORBA clients, as OMG IDL-defined Object interface instance To use a WSDL to OMG IDL mapping for implementing a web service in terms of CORBA. |
The innate qualities of CORBA’s architectural design can be deployed to extend CORBA’s reach to new domains, in this case Web Services. This RFP aims to both: • Allow CORBA based clients (with all their language bindings already implemented by their Orbs) to gain access to Web Services defined using WSDL. • Allow Web Services defined using WSDL to be implemented on a CORBA based server. |
Revised Submission due at January 2003 meeting |
| Web Services for Enterprise Collaboration
(WSEC) |
This RFP provides for a two-way mapping between the Component Collaboration Architecture (CCA) portion of ECA and WSDL such that enterprise collaborations described in CCA can be implemented with WSDL, XML Schema and Soap. It also describes how existing WSDL services are represented in UML using CCA. |
Enables high-level and business focused collaborations to be automatically and deterministically mapped to web services infrastructures. Also allows existing services to be made part of new CCA collaborations. |
Initial Submission due at November 2002 meeting |
