OASIS ebXML Messaging Services TC

Back to discussions
Expand all | Collapse all

RE: [ebxml-msg] ISSUE: Role in PartyId needs to be a required element.

  • 1.  RE: [ebxml-msg] ISSUE: Role in PartyId needs to be a required element.

    Posted 12-07-2006 23:44 
    






    how about using a single default URI, that simply means 
there is absolutely no semantics attached to this value:
    


    (I don't like falling back on pseudo-roles like 
Requester / Responder, that may actually conflict with real role 
values...)
    

     
    

    Jacques

    

    

    
From: Dale Moberg [mailto:dmoberg@us.axway.com]
    Sent: Monday, November 27, 2006 10:42 AM
    To: 
ebxml-msg@lists.oasis-open.org
    Subject: [ebxml-msg] ISSUE: Role in 
PartyId needs to be a required element.

    

    

    

    I notice that Role is still not a 
required element in the ebMS header.
    

    

    I would like the schema to require 
its use as unnecessary interoperability problems can be avoided by requiring the 
element.
    

    Also, when ebMS is used with CPPA 
(and when CPPA is connected with BPSS), it promotes integration by including the 
Role element.
    

    If the CPPA and BPSS are not used, 
it is easy to just default Role to something like Requester or 
Responder.


Related Content