OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss-x message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (DSSX-27) Public Comment 201809c00001s03: restricted cardinality


     [ https://issues.oasis-open.org/browse/DSSX-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Kuehne updated DSSX-27:
-------------------------------
    Summary: Public Comment 201809c00001s03: restricted cardinality  (was: Public Comment 201809c00001s03)

> Public Comment 201809c00001s03: restricted cardinality
> ------------------------------------------------------
>
>                 Key: DSSX-27
>                 URL: https://issues.oasis-open.org/browse/DSSX-27
>             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: PRD01
>            Reporter: Andreas Kuehne
>            Assignee: Andreas Kuehne
>            Priority: Major
>              Labels: PRD01_COMMENT, TC_ESI
>             Fix For: csprd02
>
>
> Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - Â3 of 19 submitted by Liaison Andreas Kuehne on behalf of Sonia Companies via message Â[201809c00001|http://lists.oasis-open.org/archives/dss-x-comment/201809/msg00001.html]Âper attachment with accessibility issues (word file)
> {quote}following steering committee call on 17/09 and addition of 2 other editorial comments, the resulting pre-agreed comments are now for ESI approval for submission to OASIS DSS-X TC by 28 September
> {quote}
> h2. Comment Â#3:
> |Clause 4.2.1.2. The new XML Schema does not allow that in a certain request appear sub-components of different type. With the current XML Schema one instance of InputDocumentsType can only have EITHER one or more Document, OR one or more TransformedData, OR one or more DocumentHash. An InputDocumentsType instance MAY NOT have, with the current definition one Document, one TransformedData and one DocumentHash, for instance. Core v1.0 actually ALLOWED THE PRESENCE OF INPUTS OF DIFFERENT NATURE.
> Â
> REQUEST: MODIFY THE XML SCHEMA FOR ALLOWING PRESENCE OF INPUTS OF DIFFERENT NATURE (A CHOICE WITH MAXOCCURS=2UNBOUNDEDâ WOULD MAKE IT.|
> |CONCLUSION: Pass the comment to DSS-X.|



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]