 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 214: Micro BPSS for J2ME Devices.
Reason: This JSR was not approved by the ME Executive Committee in the JSR Approval Ballot. JCP version in use: 2.5 Java Specification Participation Agreement version in use: 2.0 Description: This JSR is to provide a standard set of APIs for J2ME Devices 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
This JSR has been Rejected
Identification |
Request |
Contributions |
Additional Information
Section 1. Identification Submitting Member: Iopsis Software, Inc. Name of Contact Person: Ash Parikh E-Mail Address: ash@iopsis.com Telephone Number: +1 650 358 2522 Fax Number: +1 650 358 0403 Specification Lead: Ash Parikh E-Mail Address: ash@iopsis.com Telephone Number: +1 650 358 2522 Fax Number: +1 650 358 0403 Initial Expert Group Membership:
Supporting this JSR: 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 on J2ME Devices. These APIs will define a way to construct and manipulate various profile information corresponding to the CPP/A. 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 enable J2ME Device 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.)THE JSR IS TARGETED TO BOTH CLDC/MID-P AND CDC/PERSONALJAVA STACKS. 2.3 What need of the Java community will be addressed by the proposed specification?This set of APIs will allow J2ME and J2ME Web services developers to build ebXML based e-business applications that will be include devices within the scope of the business collaborations. 2.4 Why isn't this need met by existing specifications?J2ME does not provide a standard set of APIs for representing and manipulating profile information described by the CPP/A documents. This includes the Process Specification (BPSS 1.05). 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.)To be determined. 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.HERE IS THE TENTATIVE SCHEDULE (WILL BE FORMALIZED LATER): 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.The expert group members will determine the nature of the working model. It is anticipated that a mixture of email discussion, feedback on regular drafts and face to face meetings will work well. 2.13 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.It is expected that the specification leader will have responsibilities associated with group leadership, including group communications, decision making, and agreeing to the business terms for the Reference Implementation (RI) and Technical Compatibility Kit (TCK). Exact details will be agreed on early in the life of this specification and communicated to expert group members. The RI and TCK will be managed by Iopsis Software. 2.14 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).Iopsis will deliver a standalone reference implementation (RI) and Technology Compatibility Kit (TCK) for Java Process Definition. 2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.Iopsis will license the specification, RI and TCK to all interested parties on a royalty free basis. 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.http://www.ebxml.org/specs/index.htm#technical_specifications 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 Section 4: Additional Information (Optional)
4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.N/A |
|||||||||||||||||||||||||||||||||||||
