OASIS ebXML Messaging Services TC

Re: [ebxml-msg] Proposed CPP/A schema changes to deal with ebMSperMessage parameters

  • 1.  Re: [ebxml-msg] Proposed CPP/A schema changes to deal with ebMSperMessage parameters

    Posted 11-26-2001 19:00
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ebxml-msg message

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


    Subject: Re: [ebxml-msg] Proposed CPP/A schema changes to deal with ebMSperMessage parameters


    Bruce:
     
    I agree with you that all three schemes have pros and cons. I can see why my proposal is confusing. In your alternative 1, if inForce is set to "true" or "false", then I think perMessageDefault is not applicable, so it may not be appropriate to make this a boolean attribute. Similarly, in the alternative preferred by your fellow developers, it is not clear to me how case (b) and case (c) can be differentiated. Again, the perMessageDefault attribute may have to take on the enumerated values "true", "false", and "notApplicable", rather than being a simple boolean attribute.
     
    I will recommend to the CPP/A team that this issue be discussed in one of the upcoming conference calls. I have no problem supporting either one of your alternatives with the minor clarification indicated above.
     
    Thanks,
    -Arvola