[ebxml-cppa] Revised proposal for "per message" properties

[Arvola Chan <arvola@tibco.com>]

Based on a discussion I have had with Michael Wang, I like to simplify my
proposal. Essentially, we like to make the structure of
MessagingCharacteristics mirror that of BusinessProcessCharacteristics which
has an empty content model with only a number of attributes.

Also, I no longer think that MessageOrder should be a "per message"
property. Instead, its presence or absense in a message should be completely
governed by a Reliable Messaging parameter in the CPA. It should only be
present in the message header if the CPA indicates that the message order
semantics is "Guaranteed". This requires removal of the
messageOrderSemantics attribute from the MessageOrder element.

Attached please find updated schemas for ebxml-msg and ebxml-cppa
corresponding to this proposal.

The MessagingCharacteristics element now look like:

 <element name="MessagingCharacteristics">
  <complexType>
   <attribute name="ackRequested" type="tns:perMessageCharacteristics.type"
default="perMessage"/>
   <attribute name="ackSignatureRequested"
type="tns:perMessageCharacteristics.type" default="perMessage"/>
   <attribute name="duplicateElimination"
type="tns:perMessageCharacteristics.type" default="perMessage"/>
   <attribute name="actor" type="tns:actor.type"
default="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH"/>
  </complexType>
 </element>
 <simpleType name="perMessageCharacteristics.type">
  <restriction base="NMTOKEN">
   <enumeration value="always"/>
   <enumeration value="never"/>
   <enumeration value="perMessage"/>
  </restriction>
 </simpleType>
 <simpleType name="actor.type">
  <restriction base="NMTOKEN">
   <enumeration value="urn:oasis:names:tc:ebxml-msg:actor:nextMSH"/>
   <enumeration value="urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH"/>
  </restriction>
 </simpleType>

-Arvola

-----Original Message-----
From: Arvola Chan <arvola@tibco.com>
To: ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
Cc: ebxml-cppa@lists.oasis-open.org <ebxml-cppa@lists.oasis-open.org>
Date: Thursday, November 29, 2001 12:33 PM
Subject: Re: [ebxml-msg] Agenda December 3


>Attached please find a tentative schema for the evolving CPP/A spec. It
>incorporates Dale's suggestion to use "always", "never", and "perMessage"
as
>the enumerated values for tns:perMessageCharacteristics.type.
>
>The relevant constructs for "per message" properties are as follows:
>
> <element name="MessagingCharacteristics">
>  <complexType>
>   <sequence>
>    <element ref="tns:Ack"/>
>    <element ref="tns:AckSignature"/>
>    <element ref="tns:DuplicateElimination"/>
>    <element ref="tns:MessageOrder"/>
>   </sequence>
>  </complexType>
> </element>
> <element name="Ack">
>  <complexType>
>   <attribute name="requested" type="tns:perMessageCharacteristics.type"
>default="perMessage"/>
>   <attribute name="actor" type="tns:actor.type" default="toPartyMSH"/>
>  </complexType>
> </element>
> <element name="AckSignature">
>  <complexType>
>   <attribute name="requested" type="tns:perMessageCharacteristics.type"
>default="perMessage"/>
>  </complexType>
> </element>
> <element name="DuplicateElimination">
>  <complexType>
>   <attribute name="requested" type="tns:perMessageCharacteristics.type"
>default="perMessage"/>
>  </complexType>
> </element>
> <element name="MessageOrder">
>  <complexType>
>   <attribute name="requested" type="tns:perMessageCharacteristics.type"
>default="perMessage"/>
>  </complexType>
> </element>
> <simpleType name="perMessageCharacteristics.type">
>  <restriction base="NMTOKEN">
>   <enumeration value="always"/>
>   <enumeration value="never"/>
>   <enumeration value="perMessage"/>
>  </restriction>
> </simpleType>
>
>-Arvola
>
>-----Original Message-----
>From: ian.c.jones@bt.com <ian.c.jones@bt.com>
>To: ebxml-msg@lists.oasis-open.org <ebxml-msg@lists.oasis-open.org>
>Date: Thursday, November 29, 2001 8:25 AM
>Subject: [ebxml-msg] Agenda December 3
>
>
>>Agenda December 3 - Voting
>>
>>1. Roll call - Voting Membership
>>
>>2. SyncReply Module
>>
>>3. PersistDuration
>>
>>4. CPA & MS overriding parameters
>>   Proposed CPP/A schema changes to deal with ebMS perMessage parameters
>>
>>5. Editorial issues
>>
>>6. Agree our deadline for delivery - NO MORE FUNCTIONAL CHANGES
>>WHATSOEVER!!!
>>
>>7. AOB
>>
>>
>>Apologies - I may be late joining as I am on Vacation - David Fischer will
>>you lead as you need the answers to the agenda points.
>>
>>
>>Ian Jones
>>Chair OASIS ebXML Messaging Services TC
>>
>>Tel: +44 (0)29 2072 4063
>>Fax: +44 (0)29 2072 4137
>>Email: ian.c.jones@bt.com
>>
>>
>>
>>----------------------------------------------------------------
>>To subscribe or unsubscribe from this elist use the subscription
>>manager: <http://lists.oasis-open.org/ob/adm.pl>
>

updatedSchemas.zip