OASIS ebXML Messaging Services TC

 View Only

Re: [ebxml-msg] Oct 13th Agenda & Draft

  • 1.  Re: [ebxml-msg] Oct 13th Agenda & Draft

    Posted 10-27-2004 01:52
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ebxml-msg message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Re: [ebxml-msg] Oct 13th Agenda & Draft


    Matthew and Jeff,
    
    I may not be able to attend the call this week.
    However I am happy to provide some inputs
    for the function to Jeff and/or TC soon.
    Thanks,
    
    Iwasa
    
    > Iwasa,
    >
    > Thank you for taking some time to review for us.  We would be thrilled
    > if you were to write up a proposal / discussion paper on Pull.  Would
    > you be able to attend a meeting (by phone) to discuss your paper?
    >
    > Thanks,
    >
    > Matt
    >
    > On 22-Oct-04, at 3:09 AM, iwasa wrote:
    >
    > > Hi Matthew and all,
    > >
    > > The section 10.6 Reliable Messaging Module in the
    > > latest draft looks good so far. We may need to define
    > > a format of PullAcknowledgment Signal.
    > > I believe it is similer, if it is not exactly the same,
    > > with the Aknowledgment message of WS-Reliability.
    > >
    > > By the way, I have some questions.
    > > Is somebody working for section 10.5 Pull module?
    > > It looks like we need more texts for this section.
    > >
    > > I'm interested in this module to be written soon,
    > > since there is a strong demand from our customers
    > > for this function. And if we have this section
    > > written enough, it makes me easy to convince our
    > > customers to adopt ebMS 3.0.
    > >
    > > I personally can volunteer to draft a pull messaging
    > > specification to initiate a discussion, if it helps to
    > > speed up the process. I'm also fine if someone is
    > > going to write the text soon for review. I would
    > > like to know the current status for this section.
    > >
    > > Thanks,
    > >
    > > Iwasa
    > > Fujitsu Limited
    > >
    > >