← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Commented: (EBXMLMSG-12) D 3.6 D.3.6. PMode[1].Security.Sign.Attachment

From
OASIS Issues Tracker <>
Date
2013-06-19T19:37:54+00:00
ID
1167652428.22081371670663710.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Commented: (EBXMLMSG-12) D 3.6 D.3.6. PMode[1].Security.Sign.Attachment
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33869#action_33869 ] 

Makesh Rao commented on EBXMLMSG-12:
------------------------------------

Agreed in TC meeting Jun 19, 2013

Change the text of Sign.Attachment[] to " Value is a boolean i.e. True or False to reflect if the attachment needs to be signed or not"

> D 3.6 D.3.6.  PMode[1].Security.Sign.Attachment
> -----------------------------------------------
>
>                 Key: EBXMLMSG-12
>                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-12
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> The specification states:  
> "Sign.Attachment[].  An element within the Element[] list could be specified either by its XML name or by its qualified name (its XML name and the namespace to which it belongs). An element within the Attachment[] list is identified by the Content-Id."
> The Content-Id of an attachment is not specified in a processing mode but is specified per message.   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
← Prev in month ← Prev in thread
Next in thread → Next in month →