[OASIS Issue Tracker] (BDXR-1) Include encryption certificate

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

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

Erlend Klakegg Bergheim commented on BDXR-1:
--------------------------------------------

I'd like to propose to change certificate from 1..1 to 0..n where we add an attribute to the certificate element identifying certificate usage.

Do we need a pre-defined set of certificate identifiers, or should identifiers be defined by the implementing community?

> Include encryption certificate
> ------------------------------
>
>                 Key: BDXR-1
>                 URL: https://issues.oasis-open.org/browse/BDXR-1
>             Project: OASIS Business Document Exchange (BDXR) TC
>          Issue Type: New Feature
>          Components: Documentation, XML Schema
>    Affects Versions: SMP 2.0
>            Reporter: Erlend Klakegg Bergheim
>            Priority: Minor
>
> SMP version 1.0 requires 1..1 certificates per transport profile per process identifier per document type identifier.
> The current certificate element is used to provide certificate for validation of signature in transmission response.
> Pim has requested support for encryption certificate:
> https://lists.oasis-open.org/archives/bdxr/201501/msg00008.html



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