OASIS ebXML Messaging Services TC

Back to discussions
Expand all | Collapse all

Groups - ebMS v3.0: Part 2, Advanced Features (v51) (ebMS3-part2-V51.odt) uploaded

Pim van der Eijk

Pim van der Eijk01-31-2010 20:42

Pim van der Eijk

Pim van der Eijk02-10-2010 00:28

Pim van der Eijk

Pim van der Eijk02-10-2010 01:06

Pim van der Eijk

Pim van der Eijk03-02-2010 20:17

  • 1.  Groups - ebMS v3.0: Part 2, Advanced Features (v51) (ebMS3-part2-V51.odt) uploaded

    Posted 01-31-2010 20:35 
    Changes in v50 and v51

Updated based on TC meeting of January 27th.   (Line numbers as in "Show
Changes" in OpenOffice).

Section 1:
Changed wording that might suggest this spec defines support for
WS-SecureConversation fully.

Section 1.3:
There is a more recented WSRSP draft.

Section 2.1, 2.2:
Minor textual edits.

Section 2.4.3:
Improved WSIRSP reference.

Section 2.4.5:
As discussed, the "next" role value is on wsa:To and ebint:RoutingInput. 
Not on wsa:Action.  PMode parameter determines presence on eb3:Messaging.

Section 2.5.4
Formatting.

Section 2.5.5:
@role attribute

Section 2.5.6.
Expiration in WS-Security added to discussion of WS-Reliability

Section 2.6.1
The EPR PMode is now embedded in a new Adressing group.

Section 2.6.3.1
@role and formating.

Section 2.6.3.2
Changing recommended to default.

Section 2.7
New Addressing group.
Lots of textual changes due to this.

Section 2.8.2
Indication that this document is not a complete WS-SecureConversation
profile.

Section 3.
Lots of (mainly textual) improvements based on review.

Section 4.2
New Addressing level.

Section 4.4
Introducing errorhandling.Report.ReceiverErrors.ReplyPattern

Section 4.6.2
Disclaimer on WS-SecureConversation.

Appendix D, E, F:
Updated examples for @role attribute and wsa headers.
Also WS-Security improvements (signed timestamps in all examples).




 

 -- Mr. Pim van der Eijk

The document revision named ebMS v3.0: Part 2, Advanced Features (v51)
(ebMS3-part2-V51.odt) has been submitted by Mr. Pim van der Eijk to the
OASIS ebXML Messaging Services TC document repository.  This document is
revision #21 of ebMS3-part2-V32-JD.odt.

Document Description:


View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=36168

Download Document:  
http://www.oasis-open.org/committees/download.php/36168/ebMS3-part2-V51.odt

Revision:
This document is revision #21 of ebMS3-part2-V32-JD.odt.  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


  • 2.  Updated examples

    Posted 01-31-2010 20:42

    Attachment(s)

    xml
    B 4. Acknowledgment.xml   3 KB 1 version
    xml
    C 1. PullRequest.xml   1 KB 1 version
    xml
    B 1. CreateSequence.xml   9 KB 1 version
    xml
    B 3. UserMessage.xml   7 KB 1 version
    xml
    A 2. Receipt.xml   9 KB 1 version
    xml
    A 1. UserMessage.xml   5 KB 1 version
    xml
    E Error.xml   3 KB 1 version
    xml
    B 2. CreateSequenceResponse.xml   7 KB 1 version


  • 3.  Remaining work on Part 2

    Posted 01-31-2010 20:55 
    Hello,

The lists of things to do to finish part 2 includes at
least:
-  Some discussion on Pulling.  In Core spec, you could pull
submitted user messages (or get an EmptyMPCError).  In Part
2, you can Pull anything that has an ebint:RoutingInput to
it.  And some of those things were not "submitted" (to an
MSH by an application) but received (from another MSH) for
forwarding.  
-  Review all options for Pull requests (from edge
intermediary, end-to-end pulling, something in-between):
when do they need a reference parameter, when do they need a
nextmsh @role, verify that we can configure all options
using the current Pmodes.
-  The ebint:RoutingInput schema could reuse more from the
Core Spec if we had global elements other than just
eb3:Messaging. Is that an option?
-  Add some text on ConversationId in RoutingInput (Not set
via Pmode, do we leave this to implementations or recommend
some approaches ?)
-  General editorial work (language, references, formatting,
style etc.).
-  Thorough review ..

Other than this we are almost there ..

Pim




    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 4.  Refactoring the ebMS schema

    Posted 02-10-2010 00:28

    Attachment(s)

    xml
    example_ebint.xml   1 KB 1 version
    xml
    example.xml   1 KB 1 version


  • 5.  RE: [ebxml-msg] Refactoring the ebMS schema

    Posted 02-10-2010 01:06
      |   view attached

    Attachment(s)

    xml
    example_ebint.xml   1 KB 1 version


  • 6.  Update to refactoring the ebMS schema

    Posted 03-02-2010 20:17

    Attachment(s)

    xml
    example_ebint_core.xml   1 KB 1 version
    xml
    example_ebms_core.xml   1 KB 1 version


Related Content