[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (DSSX-26) Public Comment 201809c00001s02
[ https://issues.oasis-open.org/browse/DSSX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hagen updated DSSX-26: ----------------------------- Description: Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - Â2 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 Â#2: |Clause 4.2.1. âAn input document can also be a <ds:Manifest>, allowing the client to handle manifest creation while using the server to create the rest of the signature.â An initial search of the keywords ds:Manifest and Manifest does not hit any sentence explaining or developing how this situation can be managed and what does âallowing the client to handle manifest creationâ actually means. Â REQUEST: CLARIFY THE TEXT, MAYBE ADDING SOME ADDITIONAL TEXT IN THE PROCESSING CLAUSES FOR THE CASE THE INPUTDOCUMENT CONTAINS A DS:MANIFEST, IF NOT, DELETE IT. Â| |AK: Just took text as it was in DSS v1.0: it was as it is. There is no problem in adding more text. Most of the text was taken from old v1.0 to prevent additional problems to compliant implementations.| |CONCLUSION: Pass the comment to DSS-X.| was: Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - Â2 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} Â > Public Comment 201809c00001s02 > ------------------------------ > > Key: DSSX-26 > URL: https://issues.oasis-open.org/browse/DSSX-26 > Project: OASIS Digital Signature Services eXtended (DSS-X) TC > Issue Type: Bug > Affects Versions: PRD01 > Reporter: Andreas Kuehne > Priority: Major > Labels: PRD01_COMMENT, TC_ESI > > Comments from TC ESI to OASIS DSS-X TC on DSS-X V2 - Â2 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 Â#2: > |Clause 4.2.1. âAn input document can also be a <ds:Manifest>, allowing the client to handle manifest creation while using the server to create the rest of the signature.â > An initial search of the keywords ds:Manifest and Manifest does not hit any sentence explaining or developing how this situation can be managed and what does âallowing the client to handle manifest creationâ actually means. > Â > REQUEST: CLARIFY THE TEXT, MAYBE ADDING SOME ADDITIONAL TEXT IN THE PROCESSING CLAUSES FOR THE CASE THE INPUTDOCUMENT CONTAINS A DS:MANIFEST, IF NOT, DELETE IT. > Â| > |AK: Just took text as it was in DSS v1.0: it was as it is. There is no problem in adding more text. Most of the text was taken from old v1.0 to prevent additional problems to compliant implementations.| > |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]