[OASIS Issue Tracker] (DSSX-15) There should be mechanism for passing constraints to the serve

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

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

Andreas Kuehne commented on DSSX-15:
------------------------------------

 I agree that policies consist of a set of constraints. But the set of applicable constraints is not limited to the ones defined by the policy. And defining a validation policy as a requestor is optional. So I wouldn't recommend to tie these topic together.

See EN 319 102-1, chap. 5.1.4.1:
Despite the the idea given in figure 11 the constraints can be originate from several different sources, even an arbitrary set of constraints given as validation parameters.

Would it make sense to support validation constraints in the verification report profile only? Dtmo only the verification report has all relevant information to interpret the set of applied constraints and their outcome in a useful way!

> There should be mechanism for passing constraints to the serve
> --------------------------------------------------------------
>
>                 Key: DSSX-15
>                 URL: https://issues.oasis-open.org/browse/DSSX-15
>             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
>          Issue Type: Bug
>          Components: Core
>            Reporter: Juan Cruellas
>            Assignee: Stefan Hagen
>
> 4. Constraints.
> There should be some mechanism for passing constraints to the server. Should this appear into the core?



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