[OASIS Issue Tracker] (EBXMLMSG-54) Compressed SWA mimetype part property clarification

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

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

Sander Fieten commented on EBXMLMSG-54:
---------------------------------------

Because the property is REQUIRED I assume that a receiving MSH SHOULD reject a message that uses compression for a part and does not include this property, i.e. there exists a eb:PartInfo with a eb:PartProperties child that does contain a eb:Property element with name attribute "CompressionType" and text content "application/gzip" but not a eb:Property with name "MimeType".

Indeed the existance of this property does not guarantee that the compressed payload is of the specified Mime type, so rejecting the message on the absence of the "MimeType" property is maybe a bit to strong. 

An option can be to accept and process the message and return an Error with severity WARNING to indicate the missing property. 


> Compressed SWA mimetype part property clarification
> ---------------------------------------------------
>
>                 Key: EBXMLMSG-54
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-54
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile
>            Reporter: Theo Kramer
>            Priority: Minor
>
> The first bullet point of section 3.1 reads as follows
> An eb:PartInfo/eb:PartProperties/eb:Property/@name="MimeType" value is REQUIRED to identify the MIME type of the payload before compression was applied.
> What is not clear is if an MSH should reject or not reject a message if the MimeType part property is not set. In addition even if the MimeType part property is set, it could still be set to the incorrect value and the responsibility would be on the consumer to determine if the attachment conforms to requirements.



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