[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-cppa] FW: Update on CPPA v 3 and ebMS 3
If you wish a broader picture, here is the link to updated examples for CPPA-ebMS-ebBP from Dale from mid-July 2007: http://lists.oasis-open.org/archives/ebxml-cppa/200707/msg00005.html. ----- Original Message ----- From: Moberg Dale <dmoberg@axway.com> Date: Tuesday, August 28, 2007 8:10 am Subject: [ebxml-cppa] FW: Update on CPPA v 3 and ebMS 3 To: ebxml-cppa <ebxml-cppa@lists.oasis-open.org> > > > Here is the mapping table for ebMS and version 3 that reflects the > current consensus. > > > > An updated schema is also attached. (There may be some more schema > refactoring around the Transport group) > > > > The next tasks this week are to: > > > > 1. update and recheck the WSDL 1.1 / 2.0 and WS-Policy extensions, and > create a chart/map. > > 2. create an EDIINT table showing how to use CPPA v 3 to set up EDIINT > collaborations. > > > > Then I will return to edits on the main body of the specification. > > > > Editorial Staff > > > > > > A. Correspondence Between CPPA and ebMS Version 3 Parameters > > ebMS Header or PMode Information Item > > CPPA v 3.0 Information Source > > > > > > AgreementRef Agreement > > /CollaborationProtocolAgreement/@cpaId > > PartyId,Initiator.Party, Responder.Party > > //PartyInfo/PartyId > > PartyId/@type > > //PartyInfo/PartyId/@type > > MEP > > //SenderProcessingMode/MEP | > > //ReceiverProcessingMode/MEP > > URI value such as > http://www.oasis-open.org/committees/ebxml-msg/one-way. > > > > MEPbinding > > //SenderProcessingMode/MEPBinding | > > //ReceiverProcessingMode/MEPBinding > > URI such as http://www.oasis-open.org/committees/ebxml-msg/push > > [Initiator|Responder].Authorization. > > username > > //SenderProcessingMode/AccessToken-/Username | > > //ReceiverProcessingMode/AccessToken-/Username > > [Can be found within //ProcessingMode/AccessToken-/EncryptedData also.] > > > > [Initiator|Responder].Authorization. > > password > > //SenderProcessingMode/AccessToken-/Password | > > //ReceiverProcessingMode/AccessToken-/Password > > [Can be found within //ProcessingMode/AccessToken/-EncryptedData also.] > > > > > > //SenderProcessingMode-/@conformanceLevel | > > //ReceiverProcessingMode-/@conformanceLevel > > > > > > > > ProtocolAddress > > > > //TransportSender/Endpoint/@uri > > //TransportReceiver/Endpoint/@uri > > Protocol.SOAPversion > > //SenderProcessingMode/SOAPVersion | > > //ReceiverProcessingMode/SOAPVersion > > > > > > > > BusinessInfo.Service > > //ServiceBinding/Service > > BusinessInfo.Action > > //ActionBinding@action (version 3) > > //ThisPartyActionBinding/@action (version 2) > > BusinessInfo.Role > > //CollaborationRole/Role/@name > > or when present, > > //ActionContext2/@role > > BusinessInfo.PayloadProfile.MimeMediaType > > //SimplePart/@mimetype > > BusinessInfo.PayloadProfile.namespaces > > //SimplePart/NamespaceSupported > > BusinessInfo.PayloadProfile.optional > > //Constitutent/@minOccurs equals 0 > > BusinessInfo.PayloadProfile.maxSize > > //Constituent/@maxSizeInKBytes > > BusinessInfo.MPC > > //SenderProcessingMode/MPC | > > //ReceiverProcessingMode/MPC > > > > BusinessInfo.Properties > > //SenderProcessingMode/ExtensionProperty | > > //ReceiverProcessingMode-/ExtensionProperty > > > > ErrorHandling.SenderErrorsTo > > //TransportReceiver/Endpoint/@uri when > //TransportReceiver/Endpoint/@type is "error" or "allPurpose" | > > Endpoint value associated with defaultMshChannelId| > > Endpoint/@uri value associated with OverrideMshActionBinding/@channelId > when OverrideMshActionBinding/@action value is the action for this > configuration. > > ErrorHandling.ReceiverErrorsTo > > //TransportSender/Endpoint/@uri when //TransportReceiver/Endpoint/@type > is "error" or "allPurpose" | > > Endpoint/@uri value associated with defaultMshChannelId | > > Endpoint/@uri value associated with OverrideMshActionBinding/@channelId > when OverrideMshActionBinding/@action value is the action for this > configuration. > > ErrorHandling.AsResponse > > //MessagingCharacteristics/-@syncReplyMode equals mshSignalsOnly, > signalsOnly, or signalsAndResponse. > > ErrorHandling.ProcessErrorNotifyConsumer > > //SenderProcessingMode/-@processErrorNotifyConsumer > > //SenderProcessingMode/-@processErrorNotifyConsumer > > ErrorHandling.ProcessErrorNotifyProducer > > //SenderProcessingMode/-@processErrorNotifyProducer > > //ReceiverProcessingMode/-@processErrorNotifyProducer > > ErrorHandling.DeliveryFailuresNotifyProducer > > //SenderProcessingMode/-@deliveryErrorNotifyProducer > > //ReceiverProcessingMode/-@deliveryErrorNotifyProducer > > > > > > atLeastOnce.Contract > > //MessagingCharacteristics.AckRequested > > atLeastOnce.AckOnDelivery > > //MessagingCharacteristics.AckRequested > > atLeastOnce.AcksTo > > //MessagingCharacteristics/-@syncReplyMode equals mshSignalsOnly, > signalsOnly, or signalsAndResponse imply that HTTPResponse is used for > Acks. > > Otherwise, Endpoint/@uri value associated with defaultMshChannelId or > > > Endpoint/@uri value associated with OverrideMshActionBinding/@channelId > when OverrideMshActionBinding/@action value is the action for this > configuration. > > atLeastOnce.AckResponse > > //MessagingCharacteristics.AckRequested (but for Response Action) > > atLeastOnce.ReplyPattern > > Endpoint/@uri value associated with defaultMshChannelId or > > Endpoint/@uri value associated with OverrideMshActionBinding/@channelId > when OverrideMshActionBinding/@action value is the action in this > configuration record. > > > > > > atMostOnce.Contract > > MessagingCharacteristics/@duplicateElimination contains the value, true. > > inOrder.Contract > > ReliableMessaging/MessageOrderSemantics contains the value "Guaranteed" > > StartGroup > > //ReliableMessaging/ReliabilityGroup/-@startGroup. > > Correlation > > //ReliableMessaging/ReliabilityGroup/-CorrelationPath > > TerminateGroup > > //ReliableMessaging/ReliabilityGroup/-@terminateGroup > > > > > > WSSVersion > > //SenderNonRepudiation/NonRepudiation-Protocol/@version where > //SenderNonRepudiation/NonRepudiation-Protocol identifies protocol value > as "WSS" or > "http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1" > > Signature.Element > > //Constituent/ElementRef/@signed contains value, "true" > > Signature.Attachment > > //Constituent/@excludedFromSignature contains the value, false. > > Signature.Certificate > > //SenderNonRepudiation/SigningCertificateRef points to certificate. > > Signature.HashFunction > > //SenderNonRepudiation/NonRepudiation-Protocol/HashFunction > > Signature.Algorithm > > //SenderNonRepudiation/SignatureAlgorithm/-@w3c > > Encryption.Element > > //Constituent/ElementRef/@encrypted contains value, "true" > > [When same element is both signed and encrypted, use the value of > //Constituent/ElementRef/@signBeforeEncrypt to decide order.] > > Encryption.Certificate > > //ReceiverDigitalEnvelope/-EncryptionCertificateRef > > Encryption.Algorithm > > //ReceiverDigitalEnvelope/EncryptionAlgorithm/@w3c > > //SenderDigitalEnvelope/EncryptionAlgorithm/@w3c > > Encryption.MinimumStrength > > //ReceiverDigitalEnvelope/EncryptionAlgorithm/@minimumStrength > > //SenderDigitalEnvelope/EncryptionAlgorithm/-@minimumStrength > > WSS.username > > //SenderProcessingMode/AccessToken-/Username | > > //ReceiverProcessingMode/AccessToken-/Username > > [Can be found within //ProcessingMode/AccessToken/EncryptedData also.] > > > > WSS.password > > //SenderProcessingMode/AccessToken-/Password | > > //ReceiverProcessingMode/AccessToken-/Password > > [Can be found within //ProcessingMode/AccessToken/EncryptedData also.] > > > > WSS.Token.digest > > //SenderProcessingMode/AccessToken/Digest | > > //ReceiverProcessingMode/AccessToken/Digest > > [Can be found within //ProcessingMode/AccessToken/-EncryptedData also.] > > > > WSS.Token.nonce > > //SenderProcessingMode/AccessToken/Nonce | > > //ReceiverProcessingMode/AccessToken/Nonce > > [Can be found within //ProcessingMode/AccessToken/-EncryptedData also.] > > > > WSS.Token.created > > //SenderProcessingMode/AccessToken/-CreatedTimestamp | > > //ReceiverProcessingMode/AccessToken/-CreatedTimestamp > > [Can be found within //ProcessingMode/AccessToken/-EncryptedData also.] > > > > WSS.PModeAuthorize > > //BusinessCharacteristics/@isAuthorizationRequired. > > SendReceipt > > MessagingCharacteristics/@signAck and > BusinessTransactions/@isNonReudiationofReceiptRequired > > SendReceipt.ReplyPattern > > MessagingChacteristics/@syncReplyMode is signalsOnly or > signalsAndResponse > > Or, signals can have a delivery channel configured within their own > ActionBinding. > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]