[OASIS Issue Tracker] (EBXMLMSG-9) Receipt format for reception awareness

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/EBXMLMSG-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61765#comment-61765 ] 

Sander Fieten commented on EBXMLMSG-9:
--------------------------------------

As noted in issue #3 the TC agreed that this seems to be an error and that the schema should indeed be changed.

> Receipt format for reception awareness
> --------------------------------------
>
>                 Key: EBXMLMSG-9
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-9
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> AS4 uses copies of UserMessage elements in receipt for non-repudation awareness.   This satifies the requirement that the content of Receipt is a non-empty sequence,  but the UserMessage element is from the same ebMS namespace as the Receipt,  whereas the schema requires it to be from another namespace.  We missed this when we changed the format for reception awareness receipts.
> 	<xsd:complexType name="Receipt">
> 		<xsd:sequence>
> 			<xsd:any namespace="##other" processContents="lax"  maxOccurs="unbounded"/>
> 		</xsd:sequence>
> 	</xsd:complexType>



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)