[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-cppa] FW: Core spec, new signals and Schema
Updated ebMS header sample data (valid
this time…) <ebms:Messaging version="3.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-3_0.xsd
ebms3_22Feb2007.xsd"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 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"> <ebms:SignalMessage> <ebms:MessageInfo>
<ebms:TimeStamp>2002-07-01T13:42:37.429Z</ebms:TimeStamp>
<ebms:MessageId>uiwtoruiopwr2543890@b.example.com</ebms:MessageId>
<ebms:RefToMessageId>uiopfdsmnf4898965563434@a.example.com</ebms:RefToMessageId> </ebms:MessageInfo>
<ebbpsig:NonRepudiationInformation>
<ebbpsig:MessagePartNRInformation>
<ebbpsig:MessagePartIdentifier> </ebbpsig:MessagePartIdentifier> -
<ds:Reference URI="http://b.example.com/doc45/#b"> <ds:DigestMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue>fX/iNylcUHNLV4lCE0eC7aEGP28=</ds:DigestValue> </ds:Reference> </ebbpsig:MessagePartNRInformation>
<ebbpsig:MessagePartNRInformation> <ebbpsig:MessagePartIdentifier>
</ebbpsig:MessagePartIdentifier> - <ds:Reference
URI="http:/a.example.com/doc23/#a"> <ds:DigestMethod
Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue>fX/iNylcUHNLV4lCE0eC7aEGP28=</ds:DigestValue> </ds:Reference>
</ebbpsig:MessagePartNRInformation>
</ebbpsig:NonRepudiationInformation> </ebms:SignalMessage> </ebms:Messaging> From: Forwarding this to the list for additional
comment from the TC. Fulfills my action item from Feb 21. From: 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>uiwtoruiopwr2543890@b.example.com</ebms:MessageId>
<ebms:RefToMessageId>uiopfdsmnf4898965563434@a.example.com</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> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]