Groups - P-Mode model (PMode-model-86.doc) uploaded

[jdurand@us.fujitsu.com]

in order to address comments from latest meeting:
- V0.86: makes more explicit in introduction that P-Mode model described
here does not intend to be detailed enough to determine the final content
of a representation so that it is interoperable. This is the role of a
P-Mode representation to do so. The stated objective of the PMode data
model in this spec is to articulate the semantics of the PMode parameters
w/r to the specification features, defining abstract controls for these
features, and a basis for communicating these via a PMode rpresentation. As
a consequence, PMode.Security section is updated to remove details of
parameter representations such as Certificates. Also, added one more
example of P-Mode representation and usage (example 3 on light device).

 -- Mr Jacques Durand

The document revision named P-Mode model (PMode-model-86.doc) has been
submitted by Mr Jacques Durand to the OASIS ebXML Messaging Services TC
document repository.  This document is revision #10 of PMode-model-2.doc.

Document Description:
Data Model proposal for P-Modes, for appendix.
Updated for improvement, corrections, and addressing i054, i073, partially
i059.
- V0.82: removes the recently added group "PMode.Exchange" , not needed.
The definition of the referred MEP (PMode.MEP) should provide all this
info. A few corrections, and emphasis on binding a vector of PMode
parameter values to each leg of the MEP, using leg "labels" to identify
these vectors.
- V0.83: remodeling of PMode.Security based on AxWay proposal, for
addressing Core issue 88. Plus consolidating other changes already proposed
on the list or in meeting (PayloadProfile.maxSize, generalization of the
indexed notation []).
- V0.84: updates based on meeting 1/17:Role parameter in businessInfo (not
in general parameters of initiator/responder), indication of cardinality
for intiator/responder, clearer treatment of the reliability scope
(starting, correlating and terminating a message group/sequence),
cardinality of error reporting destinations, ID of certificates X509
leveraging Security Policy.
- V0.85: Adds to the diffs from 0.84: better introduction on P-Modes and
examples illustrating how they are supposed to be used. Adding AgreementRef
as a parameter. Also clearer on the uniqueness of PMode.ID, and the
expectation that this ID be used in @pmode in message header. Updated the
Reliability "scoping"  parameters, renamed StartGroup, Correlation and
TerminateGroup, for clarity. Clarified their meaning, made it clear that
"Correlation" fields (somehow analogous to CorrelationSet in BPEL) will
lead to creation of a new group/sequence if they cannot correlate with an
existing group at run-time.
- V0.86: makes more explicit in introduction that P-Mode model described
here is does not intend to be detailed enough to determine the final
content of a representation so that it is interoperable. This is the role
of a P-Mode representation to do so. The stated objective of the PMode data
model in this spec is to articulate the semantics of the PMode parameters
w/r to the specification features. As a consequence, updated PMode.Security
section to remove details of parameter representations such as
Certificates. Also, added one more example of P-Mode representation and
usage (example 3 on light device).

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=22133

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/22133/PMode-model-86.doc

Revision:
This document is revision #10 of PMode-model-2.doc.  The document details
page referenced above will show the complete revision history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration