OASIS ebXML Core (ebCore) TC

 View Only
Expand all | Collapse all

Meeting on Friday, Aug 7 for ebCORE?

  • 1.  Meeting on Friday, Aug 7 for ebCORE?

    Posted 08-05-2009 15:10
    Do we have agenda items for a telecon call for ebCORE on Friday? I know
    many people are on holiday or travel this month. Please advise if you
    are or are not available, and any agenda items.
    
    Thanks!
    Kathryn
    
    
    Kathryn Breininger
    Manager, Release & Delivery Services
    CIMS - Center for Information Management Services
    
    MC 62-LC
    425-965-0242 desk
    425-512-4281 cell
    425-237-4582 fax
    
    
    


  • 2.  RE: [ebcore] Meeting on Friday, Aug 7 for ebCORE?

    Posted 08-05-2009 15:56
    If we meet, and Pim can be on the call, I have a maintenance issue about
    party-id type values for version 3. It should not take a long time to
    discuss. (Issue raised on ebxml-dev recently.)
    
    I am available this Friday for a change!
    
    Dale Moberg
    
    
    
    


  • 3.  RE: [ebcore] Meeting on Friday, Aug 7 for ebCORE?

    Posted 08-05-2009 19:16
    Hello,
    
    I should be able to make it. I posted a follow-up to the ebXML-Dev posting.
    
    Pim
    
    


  • 4.  YES RE: [ebcore] Meeting on Friday, Aug 7 for ebCORE? Call in info and agenda below

    Posted 08-05-2009 19:21
    Great! It sounds like Pim, Ian, Dale and I will be available. We will
    plan to go ahead with the call. Agenda item will be the maintenance
    issues identified below, and any other items you would like to bring to
    the table.
    
    The telecon number and password:
    
    USA toll: 1-303-632-3052
    
    USA Toll free: 888-499-2539
    
    PARTICIPANT PASSCODE (same for all countries): 7627600
    
    NETHERLANDS Caller Paid 0-20-2061565 
    
    NETHERLANDS Toll-Free 0800-022-8641 
     
    Talk to you all then!
    Kathryn
    
    
    Kathryn Breininger
    Manager, Release & Delivery Services
    CIMS - Center for Information Management Services
    
    MC 62-LC
    425-965-0242 desk
    425-512-4281 cell
    425-237-4582 fax
    
    
    


  • 5.  Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 10:53
     Team,
    
    	are we having a call today?  One item of business has cropped up from the messaging TC to action work on CPPA spec for the new version of messaging due soon.
    
    	Sorry, I should have posted this yesterday - I thought call was next Friday!
    
    Ian


  • 6.  RE: [ebcore] Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 13:09
    Hello,
    
    Since I raised this in the messaging TC meeting, I indeed have some ideas to
    propose for CPA 3.0. As ebCore is a successor to the former CPA TC, we could
    use some time of the scheduled ebCore meetings to discuss this.  But as only
    a subset of ebCore members is interested in CPA, we should put it as last
    item on the agenda so those not interested can leave. Having said this, I
    think I should write up my input in an email to be sent some time in advance
    of a meeting so people have some time to review them. So today is too early
    for this and there being no other items I'm aware of we could cancel.  But
    if we schedule the CPA topic for the meeting of September 4th, I will commit
    to providing some input.
    
    Pim 
    
    


  • 7.  RE: [ebcore] Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 13:38
    All,
    
        I support cancelling as the other was from the last call and has not completed - e-mails started last week but just stopped.
    
    Ian 
    
    


  • 8.  RE: [ebcore] Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 13:46
    Hi Pim
    
    It would be good to have the issues sent to the list prior to the
    meeting.
    
    I think it would be a better use of time, and permit Kathryn to chair,
    if we ask her to put this on the agenda for Sept 4.
    
    Ian, should we then cancel the meeting today in that there is no new
    business quite ready for discussion?
    
    Thanks
    Dale Moberg
    
    
    


  • 9.  RE: [ebcore] Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 13:54
     Dale,
    
    	 I propose we cancel today's meeting and as co-chair you send a cancellation as 3 of the regulars support cancellation  and the other co-chair is absent.
    
    Ian
    
    


  • 10.  RE: [ebcore] Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 14:15
    Meeting today is cancelled. Next meeting will be Sept 4.
    
    
    


  • 11.  CPP/CPA enhancement suggestions

    Posted 09-03-2009 20:56
     
    
    
    Here are some brief descriptions of potential enhancement requests for
    ebXML CPP/CPA, for tomorrow's meeting. Depending on interest from the
    TC, these could be developed further.
    
    Warning: these are rough ideas, hopefully the description conveys the
    general ideas.
    
    1) Supporting end-to-end agreements in multihop: abstracting from
     hop-specific parameters
    
    In the current CPP/CPA schema, a 


  • 12.  RE: [ebcore] CPP/CPA enhancement suggestions

    Posted 10-23-2009 15:34
     
    A reminder that our bi-weekly CPPA SC is today.  
    
    Here are some additional comments, following up from my
    email of September 3rd. 
    http://www.oasis-open.org/apps/group_public/email/ebcore/200
    909/msg00005.html
    I continue the numbering from that email.
    
    6) WS-A EPR and synchronous business responses  
    (Follow up on (5) in earlier email, replacing the
    @usesTransportBackChannel attribute by anonymous EPR).
    
    In CPA 2.0 and the draft 3.0, synchronous business responses
    are modelled using nesting.  In the CollaborationInfo
    structure of the initiator, there is a CanSend element (or
    ActionBinding equivalent) that can have an CanSend.
    Similarly, the responder has a CanReceive with a nested
    CanSend.
    
    In a CPP, multiple DeliveryChannels can be used to express
    alternatives.  However, if a partner supports synchronous
    and asynchronous responses, this can not be expressed as
    separate DeliveryChannel options, that can be selected by
    CPP intersection.  You have to have multiple CanSends (resp.
    CanReceive etc.), one with an embedded CanReceive, and
    another without one.  
    
    An simple alternative way to express synchronous responses
    is to adopt WS-Addressing and the anonymous EPR.  Then we
    can describe the "response" message in the CPP as having two
    alternative channels:  one with a proper URL (that can be
    HTTP posted to asynchronously) and another with an
    http://www.w3.org/2005/08/addressing/anonymous EPR.  
    
    To accomodate this, we should change DeliveryChannelType to
    have either a transportId reference or reference to an EPR,
    as a transport reference is not needed. (In the approach
    with synchronous replies as nesting, there still is a
    required reference from the embedded action binding, though
    it is not used).   
    
    We need the EPR change and optional transport anyway for
    multihop:
    
    7)  Multiple channels
    
    With multihop, some agreement parameters are end-to-end
    (sender and ultimate recipient), and others are between
    endpoints and edge intermediary (see section 2.8.2 and 2.8.3
    in the Part 2 draft).  The partner agreement is only about
    the end-to-end agreement.  We could extend the CPP to extend
    each delivery channel option from a single channel reference
    to multiple 
    
    	
    
    Where each channel is tagged with a role:
    
            


  • 13.  RE: [ebcore] Meeting Call today Friday, Aug 21 for ebCORE?

    Posted 08-21-2009 13:43
    Hi Ian,
    
    I think that Kathryn is still on vacation, out in the backcountry.
    
    We can begin discussion on the CPPA v 3 for ebMS and AS4 and I-cloud.
    But we should have a full TC to consider whether to start a
    subcommittee, IMO. 
    
    I have several calls this morning before 10, but we need Pim on the call
    to continue the discussion. Thanks for reminding me.
    
    Dale