[OASIS Issue Tracker] (BDXR-6) Adding constraint if ServiceActivationDate and ServiceExpirationDate are both present

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

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

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

From https://lists.oasis-open.org/archives/bdxr/201703/msg00015.html:
"Erlend brought up an SMP interpretation question from PEPPOL regarding the ServiceActivationDate and ServiceExpirationDate. The specification states that senders should ignore services that are either expired or not yet activated (section 2.3.4.4), however both ServiceActivationDate and ServiceExpirationDate are optional in the XSD meaning that senders could encounter services that do not have a value for either or both. All agreed that it is understood that a sender encountering a service without a ServiceActivationDate should assume that the service activation date has passed, and a sender encountering a service without a ServiceExpirationDate should assume that the service expiration date has not passed. It was agreed to include a more explicit clarification in the next major edit of SMP."

> Adding constraint if ServiceActivationDate and ServiceExpirationDate are both present
> -------------------------------------------------------------------------------------
>
>                 Key: BDXR-6
>                 URL: https://issues.oasis-open.org/browse/BDXR-6
>             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
>
> From https://lists.oasis-open.org/archives/bdxr-comment/201611/msg00004.html
> I suggest an additional constraint if ServiceActivationDate and ServiceExpirationDate are both present



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