FW: Core spec, new signals and Schema

Forwarding this to the list for additional
comment from the TC.

Fulfills my action item from Feb 21.

 

Dale Moberg

 

From: Dale Moberg 

Sent: Thursday, February 22, 2007
1:54 PM

To: Jacques Durand; Pete Wenzel;
Ric Emery

Subject: Core spec, new signals
and Schema

 

The current ebMS schema is designed so that any new
SignalMessages must be from a different namespace than messaging target
namespace [1].

 

So one design is just to extend “SignalMessage” with
some elements defined in ebBP signal namespace for signed receipt
acknowledgement. [2]

 

The element, NonRepdudiationInformation, would be the
easiest to re-use.

 

The resulting Messaging element would look something like:

 

<ebms:Messaging xmlns:ebms="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-3_0.xsd"

   
xmlns:ebbpsig="http://docs.oasis-open.org/ebxml-bp/ebbp-signals-2.0"

   
xmlns:ds="http://www.w3.org/2000/09/xmldsig#">

    <ebms:SignalMessage>

       
<ebms:MessageInfo>

           
<ebms:TimeStamp> date time value</ebms:TimeStamp>

           
<ebms:MessageId></ebms:MessageId>

           
<ebms:RefToMessageId></ebms:RefToMessageId>

           
<ebbpsig:NonRepudiationInformation>

               
<ebbpsig:MessagePartNRInformation>

                   
<ebbpsig:MessagePartIdentifier> </ebbpsig:MessagePartIdentifier>

                   
<ds:Reference> all the ds reference stuff</ds:Reference>

               
</ebbpsig:MessagePartNRInformation>

               
<ebbpsig:MessagePartNRInformation>

                   
<ebbpsig:MessagePartIdentifier> </ebbpsig:MessagePartIdentifier>

                   
<ds:Reference> all the ds reference stuff </ds:Reference>

               
</ebbpsig:MessagePartNRInformation>

           
</ebbpsig:NonRepudiationInformation>

       
</ebms:MessageInfo>

    </ebms:SignalMessage>

</ebms:Messaging> 

 

[1]

  <xsd:complexType
name="SignalMessage">

    <xsd:annotation>

      <xsd:documentation
xml:lang="en"> In the core part of ebMS-3 specification, an
eb:Signal

        Message contains
eb:MessageInfo and either an eb:PullRequest element alone or together with

        series of
eb:Error elements. In part 2 of the ebMS-3 specification, new signals may be

        introduced, and
for this reason, an extensibility point is added here to the

        eb:SignalMessage
element to allow it to contain any elements. </xsd:documentation>

    </xsd:annotation>

    <xsd:sequence>

      <xsd:element
name="MessageInfo" type="MessageInfo"
maxOccurs="1" minOccurs="1"/>

      <xsd:any
namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax"/>

      <xsd:element
maxOccurs="1" minOccurs="0" name="PullRequest"
type="PullRequest"/>

      <xsd:element
maxOccurs="unbounded" minOccurs="0" name="Error"
type="Error"/>

    </xsd:sequence>

  </xsd:complexType>

 

[2]

<xsd:element
name="NonRepudiationInformation">

                       
<xsd:complexType>

                                   
<xsd:sequence>

                                               
<xsd:element ref="bpssignal:MessagePartNRInformation"
maxOccurs="unbounded"/>

                                   
</xsd:sequence>

                       
</xsd:complexType>

           
</xsd:element>

           
<xsd:element name="MessagePartNRInformation">

                       
<xsd:complexType>

                                   
<xsd:choice>

                                               
<xsd:element name="MessagePartIdentifier" type="bpssignal:non-empty-string"/>

                                               
<xsd:element ref="ds:Reference"/>

                                   
</xsd:choice>

                       
</xsd:complexType>

           
</xsd:element>