OASIS ebXML Messaging Services TC

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

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

    Posted 11-19-2001 19:19
     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 ebMS permessage parameters


    Doug:
     
    The first point in my original message was intended to differentiate message properties that originate from BPSS from those that are specific to the messaging specification. The DeliveryChannel element originally contains a Characteristics element that carries BPSS related parameters. I am recommending that Characteristics be renamed BusinessProcessCharacteristics before we add the new MessagingCharacteristics element.
     
    Here is another suggested set of schema changes to address your desire to allow
     
     "acknowledgments are required for this delivery channel and the message will indicate whether signing is required" or "any requested acknowledgement must be signed".
     
     <element name="MessagingCharacteristics">
      <complexType>
       <sequence>
        <element ref="tns:AckRequested"/>
        <element ref="tns:AckSignatureRequested"/>
        <element ref="tns:DuplicateElimination"/>
       </sequence>
      </complexType>
     </element>
     <element name="AckRequested">
      <complexType>
       <attribute name="perMessageCharacteristics" type="tns:perMessageCharacteristics.type" default="perMessage"/>
       <attribute name="includeInMessageHeader" type="boolean" default="false"/>
       <attribute name="actor" type="tns:actor.type" default="toPartyMSH"/>
      </complexType>
     </element>
     <element name="AckSignatureRequested">
      <complexType>
       <attribute name="perMessageCharacteristics" type="tns:perMessageCharacteristics.type" default="perMessage"/>
       <attribute name="flag" type="boolean" default="false"/>
      </complexType>
     </element>
     <element name="DuplicateElimination">
      <complexType>
       <attribute name="perMessageCharacteristics" type="tns:perMessageCharacteristics.type" default="perMessage"/>
       <attribute name="flag" type="boolean" default="false"/>
      </complexType>
     </element>
     <simpleType name="perMessageCharacteristics.type">
      <restriction base="NMTOKEN">
       <enumeration value="fixed"/>
       <enumeration value="perMessage"/>
      </restriction>
     </simpleType>
     <simpleType name="actor.type">
      <restriction base="NMTOKEN">
       <enumeration value="nextMSH"/>
       <enumeration value="toPartyMSH"/>
      </restriction>
     </simpleType>
     
    Regards,
    -Arvola