Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 157: ebXML CPP/A APIs for Java

Stage Access Start Finish
Withdrawn   30 Jul, 2010  
Expert Group Formation   06 Nov, 2001  
JSR Review Ballot View results 23 Oct, 2001 05 Nov, 2001
Status: Withdrawn
Reason: Withdrawn at the request of the Spec Lead.
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0


Description:
This JSR is to provide a standard set of APIs for representing and manipulating Collaboration Profile and Agreement information described by ebXML CPP/A (Collaboration Protocol Profile/Agreement)documents.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Himagiri Mukkamala Sybase
Expert Group
  Kanumury, Nagesh Progress Software SAP AG
  Sterling Commerce Sybase Tell, Anders W.

This JSR has been Withdrawn
Reason: Withdrawn at the request of the Spec Lead.

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Sybase Inc.

Name of Contact Person: Himagiri (Hima) Mukkamala

E-Mail Address: himagiri@sybase.com

Telephone Number: +1 510 922 5477

Fax Number: +1 510 922 5340


Co-Specification Lead: Dale Moberg

E-Mail Address: dmoberg@cyclonecommerce.com

Telephone Number: +1 480 627 1846

Fax Number: +1 480 627 1801

Co-Specification Lead: Himagiri (Hima) Mukkamala

E-Mail Address: himagiri@sybase.com

Telephone Number: +1 510 922 5477

Fax Number: +1 510 922 5340


Initial Expert Group Membership:

1) Michael Ho
hom@sybase.com
Sybase Inc

2) Jeff Turpin
jturpin@cyclonecommerce.com
Cyclone Commerce

Supporting this JSR:

Sybase Inc.
Cyclone Commerce.



Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to provide a standard set of APIs for representing and manipulating Collaboration Profile and Agreement information described by ebXML CPPA (Collaboration Protocol Profile/Agreement)documents. These APIs will define a way to construct and manipulate various profile information corresponding to the CPP/A. In addition, these APIs will provide a way to negotiate CPAs between two partners enabling them to conduct e-business. The profile information can be derived from a CPP document or constructed through the API provided or constructed by accessing a ebXML Registriy/Repository using JAXR. The APIs would also assist users in creating a CPA document from merging to CPP documents by doing a selective merge of the profile information or by providing infrastructure to negotiate between the partners. The APIs would also enable users to create a base profile by taking information from a Business Process Specification document.

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

Java 2 SDK, Standard Edition v. 1.3 and above

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

This set of APIs will allow developers to build ebXML based e-business applications without directly having to access the CPP/A documents. These will also let users of the APIs create CPA documents for taking part in collaborations.

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

The Java 2 SDK Standard Edition does not provide a standard set of APIs for representing and manipulating profile information described by the CPP/A documents.

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

By design, this proposed specification depends on the ebXML CPP/A specification. ebXML CPP/A is an XML format for describing profile and agreement information for partners agreeing to collaborate based on ebXML as the underlying architecture. In addition, since the ebXML CPP/A specification is bound to the ebXML MSH specification and ebXML BPSS specification, this specification is dependent on these.

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

javax.ebxml.cpp

javax.ebxml.cpa

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.

We should have API documentation and a preliminary specification ready by 3/1/2002 (approximately 24 weeks).

Further revisions of the specifications will include support for negotiation etc.

Schedule for the specification is tied to the schedules of ebXML CPP/A TC.

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

Mostly by conference calls and F2F meetings once every quarter.





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.

ebXML CPP/A http://www.oasis-open.org/committees/ebxml-cppa

ebXML MSG http://www.oasis-open.org/committees/ebxml-msh

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

The ebXML CPP/A 1.1 specification defines the schema for the elements in the profile